Thanks for the report. So, in Windows 10 1809 (in this case, LTSC 2019), the "Reset this PC" feature won't work if "ResetBase=2" is used. Some remarks about it: "ResetBase=1" will have the same issue in Windows 10 and would be very possible to have it in Windows 11. For critical mission environments, where the maximum stability for the long term is needed, the "ResetBase" option must not be used (the default value, "0"). It's not about the "Reset this PC" (buggy) feature, but it's because some future updates, imaging processes, or other kinds of IT management could fail because of the extreme compression and deletion inside the WinSxS folder. "CleanUp" option is safe to use. It's likely that in Windows 10 builds 19041/2/3/4/5 and Windows 11 (from 21H2 to 26H2), the "ResetBase" ("1" or "2") option could bring the same problems. If building an updated Windows 10/11 ISO (UUPDump + UUP Converter), using "Create ISO with install.wim", "Integrate Updates", and "CleanUp" results in almost the same final size as the official monthly Consumer/Business ISO, it is much better to just download the official ISO instead of doing this whole process. Now, if instead of creating an ISO with "install.wim", you create an ISO with "install.esd". The size reduction could be worth it and be preferable to the official monthly ISO.
Excellent ! Thanks for your testing in Windows 11 26H2 (26300.9550). So, in conclusion, "ResetBase" (option "1" or "2") damages the "Reset this PC" feature, and it's very likely to produce some future instability in imaging or other IT scenarios). So, those 400 MB saved (when used "ResetBase=2") are not worth it. When creating updated ISOs (using UUP-Converter, W10UI, or W10MUI), just use Cleanup, Not ResetBase.
Yeah, those are running now too, i did them a few months ago but can't remember their outcome anymore I remember we discussed that, only the LTSB were still supported so i ran the test on them, and when my memory still works fine the tests went fine too. Updating soon...
What? But a few days ago, there were two tests (Win10 LTSC 2019 and Win11 26H2) and when "ResetBase" was enabled, the "Reset this PC" feature failed.
What do you think 1809 actually is? Hint, 2019 LTSC = 17763.xxx and 1809 = 17763.xxx ps, on 26H2 it worked fine.
Again: What? I know perfectly that 1809 is 2019 LTSC (17763); there's no need for sarcasm. You did two tests with 1809 (LTSC-2019) and 26300 (Win11 26H2) with "ResetBase" disabled ("0" value), and you showed that "Reset this PC" worked. Unlike when you enable "ResetBase", the "Reset this PC" failed in both Win10 and Win11. So I made a conclusion that it's better to not enable "ResetBase". And abbodi1406 said: which is wrong. And now you said that: when you showed the opposite (with "ResetBase" enabled, the feature failed).
I use emoji's for a reason... But here the facts: 2019 LTSC with resetbase = fails: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-786#post-1923838 26300 with resetbase = working fine: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-786#post-1924182 2016 LTSB with reserbase = fails: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-786#post-1924271 And what is the conclusion here?