There seems to be a bug, what else is new, that affects some folks, sometimes only if using an MS account and not if using a local account, but whatever. The circumstance that would probably affect some of us is that -- "This issue only affects devices in which any of the local built-in accounts have been renamed, such as Administrator or Guest. " See here for the whole story - https://support.microsoft.com/en-us...sing-the-sign-in-options-or-users-mmc-snap-in. "To prevent the issue and not recieve the safeguard hold, you will need to name all built-in user counts back to their default name before attempting to update to Windows 10, version 2004 or Windows 10, version 20H2." [ I love that MS doesn't seem to use spell check in their own user notifications, see "recieve" above. LOL ]
So this pertains to people having Win10 installed and then updating to either 20h1 or 20h2: "If you are trying to update to Windows 10, version 2004 or Windows 10, version 20H2, you might encounter an update compatibility hold..." It should not affect sysprep updating as that uses built-in user account normally. Annoying enough though! Now Edge browser is also integrated in Win10 from 20h2 onward -- not the Appx version, the new implementation deposits Edge in WinSxS and installs it in Program Files (x86). Just the aforementioned literally adds .5gb to the install.wim So far, as you update the Edge installer via a new Edge WU update or as .msu (after the original one which is also the Enablement update that makes Win10 2004 into 20H2), yet another Edge installer gets deposited in WinSxS (three of them, at that point, or 250b) which means it bloats the install.wim even more. And it looks like this is the model for now, meaning every Edge update -- of which there will be a lot -- will add another 100mb to WinSxS, whereas the install of it takes up about 600mb. Just a totally insane model. I tried to delete the Edge installers from WinSxS, but I think it messes with future updates so it may require those previous versions to be there in order for any new updates to be installed. If so, this is a disastrous model. Just thinking of the IT people using sysprep, fighting bloat and unnecessary complexity, they must be fuming by now.
