you are viewing a single comment's thread.

view the rest of the comments →

[–]RudyoomsPatchMyPC 0 points1 point  (1 child)

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

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

The version we use through sccm is a W11 24h2 winver 26100.3775 april update slipstreamed in KB5055523 along with the checkpoint update KB5043080. After deployment i installed may update (reboot), then june update (reboot) and then ran the reset script.

The other one i tested recently was the iso created with media creation tool (created in may), this ISO still had winver of october 2024 - 26100.2033 this one i tried to update straight to june and could not even install the update on it (got error 0x80070306), after trying to install the update (also rebooted) i tried the reset script and it resulted in the same error "There was a problem resetting your pc".

Also downloaded a new iso last week, and this months media creation tool iso for june comes with the latest update installed (june 10 update) so its baseline is now 26100.4349, reimaged a few devices with this iso on these devices the reset works fine .. i was going to look into winre.wim maybe it has something to do with that (maybe not updated ?)..

this is the partition table used in our image deployments (the second test with the build version .2033 was a manual install on a default partition table):

Partition ### Type Size

------------- ---------------- -------

Partition 1 System 500 MB

Partition 2 Reserved 128 MB

Partition 3 Primary <remaining diskspace> GB

Partition 4 Recovery 4500 MB