I see. Wonder why MS did that? I see the 3.1 script changes it to 0 when ResetBase is enabled (by default). Wow MS sux so often these days...
Am i to understand that we can make reset pc option succeed with script v3.1 by changing DisableResetbase to 0 in registry ?
Guys, wait abbodi1406 will update the script. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-214#post-1359031
i've integrated the cab updates into install.wim file using script v3.1 from win10 enterprise LTSB 2016 iso then create new iso to replace the old install.wim by the new one (14393.351), then installed the new iso in virtual machine then tried the resetpc option and i was able to reset the machine successfully as you can see below : Spoiler @Flipp3r : i don't know why resetpc option didn't work for you with script v3.1 but it worked for me. i see that you run script v3.1 using win10 1703 iso (15063), i run the script using win10 1607 version (14393) , maybe the script v3.1 is not fully compatible with 15063 versions, to be confirmed.
Tried it, works fine. Perhaps the default should be 0 in the script... @mehdibleu, haven't tried 1607 as everything I do is with 1703...
@Flipp3r : you said yesterday that if you reset the pc with updates integrated, the updates will remain after the reset is done but apparently it's not the case, after i reset the machine, i noticed that the updates were gone as you can see below : Spoiler: before the reset Spoiler: after the reset as you see in the screens, the updates are lost after the reset was done so how come ? how can you explain this ? are you sure that integrated updates remain after the reset of the pc is done ? here's what you said :
@Flipp3r is at 15063 and then the updates remain. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-214#post-1359011
W10UI_3.2 Splitted the ResetBase option to two, both default is NO: Code: 5. Cleanup System Image: YES 6. Reset Image Base: NO the standard DISM StartComponentCleanup operation, which delta-compress superseded components might take long time, but safer Code: 5. Cleanup System Image: YES 6. Reset Image Base: YES the DISM ResetBase operation, which removes the superseded components and rebase the image quicker and reduce image size further more, but as we now know, this come with cost and most likely breaks "Reset this PC" feature
Thanks for giving more flexibility. So, if I do not need/use the reset PC feature, (I delete the recovery folder after installing Windows to save space, anyway) there's no reason for using version 3.2? I am just a bit lazy for editing the 3.2 CMD file
Whatever post I made, you should reply with something unrelated? Reset PC won't work if you delete it. I was meaning this.
That proofs what i said was related, the resetpc option doesn't use a recovery of any kind, it's a built in option in every windows edition.
i used script v2.1 and i was able to reset the pc without loosing the integrated updates, it worked well with that script version, it wasn't the case with script v3.1, the updates were lost every time after reset pc operation. i think the problem with the script v3.1 is that resettting the image hadn't been run during the operation which could explain why the integrated updates are lost after the reset pc was done.
When attempting to install KB4025334 (14393.1532) using W10UI_3.2 on a Windows 10 LTSB 2016 with KB4025339 (14393.1480) previously installed, using Admin Cmd it attempts to unpack the .cab file but fails… I tried this twice… The 1st attempt reported the .cab file was in use and quit… The 2nd attempt appeared to be unpacking the .cab file but never succeeded nor reported any additional information… Note: I used the options: 5. Cleanup System Image: YES 6. Reset Image Base: YES with W10UI_3.2 for curiosity… Since I was unable to unpack the .cab file, I doubt this had any affect… When doing same as above with W10UI_2.1, it installed correctly using default settings…
You do know MSFT did disable the resetbase option by default a month ago so the resetbase 2.1 performed was only cleanup system image, no full resetbase.