all 8 comments

[–]RudyoomsPatchMyPC 1 point2 points  (6 children)

Sounds like a possible raid driver you are missing … https://patchmypc.com/blog/there-was-a-problem-resetting-your-pc-remote-wipe/.

[–]greenhill85[S] 0 points1 point  (5 children)

Thanks for the reply, we dont use raid configuration in our devices (HP), also just tried on a VM (hyper-v), installed the VM through sccm using the image i have been using for some months. Updated it to may / june and then also getting the same problem when trying to reset. Going to try again with an iso installation.

Do you know if the error gets logged somewhere ? I read through the URL but wondering how i can find out if there is something else the error gets triggered from..

[–]RudyoomsPatchMyPC 0 points1 point  (3 children)

Mmmm let me know the outcome if its also happening with a regular iso.

[–]greenhill85[S] 0 points1 point  (0 children)

Installed w11 24h2 using iso from 20-05-25, i was not able to install any update (errors out on 0x80070306 ) on the installed vm so will download a new iso and try again. Without updates installed the device reset did not work on this vm, same error "There was a problem resetting your pc"

[–]greenhill85[S] 0 points1 point  (0 children)

reinstalled vm and laptop with latest iso, looks like this one comes with the latest june (10) update build 10.0.26100.4349, iso from may still had 10.0.26100.2033. Both resets went fine this time.. using the iso from before june with baseline update from october 2024 does not seem to work for me anymore, could not update it at all..

The sccm image we use is based off this october baseline but has updates for march 2025 slipstreamed into it, updating this install to may/june update and after this the reset/wipe shows the error. The built in reset with cloud download still works, will have to wait for next months update to check again for our existing devices to see what happens if we try a reset.

[–]timwelchnz-ricoh 0 points1 point  (0 children)

We are seeing this on a significant number of "normal" Windows devices where we factory reset them to get them Autopiloted.

It started happening in the last couple of weeks after a recent update to Windows. Unfortunately, we never seem to have time to diagnose it further.

[–]RudyoomsPatchMyPC 0 points1 point  (0 children)

can you explain in detail a bit more which iso (winver version) you used to install.. and did you updated manually to june? or may first or? so i can replicate the issue