New
#20
Last edited by PanosG; 07 Jul 2021 at 03:45.
Last edited by PanosG; 07 Jul 2021 at 03:45.
Installed very fast, everything OK
Woke up this morning requesting a reboot lol. All good.
Downloaded and installed both KB5003537 and KB5004945 just now. Everything done and running smoothly!
Now on 19043.1083.
Not sure if it's related to this KB, but one of the two PCs had corruption when I ran "sfc /scannow" after installing this KB.
After running dism with /restorehealth, then running sfc again, the corruption issue is resolved.
2nd PC didn't have this issue, so again, probably unrelated.
Just what is 'corruption'? It's a catch-all word that people toss around, and as such doesn't mean anything. Chase down some of those sfc errors in \CBS\CBS.log. Most of them are something like this:
Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice
I have a few questions: How does this happen? It's been happening for years. Cosmic rays? Why do people just shrug their shoulders and put up with this "corruption", as if it were somehow inevitable, like the weather. Why is every single update on Windows so fraught that everyone feels a need to check in to say they got it smoothly, or it totally screwed up in this or that way? Why is this even acceptable?
I'm sure you can add your own questions to this list.
Permissions and/or ownership set twice seems to be a trivial error that has no consequences. Invariable when I've looked the 'twice set' settings are both set to the same thing. SFC /ScanNow can fix this on its own, no need for DISM.
I have a few questions: How does this happen? It's been happening for years. Cosmic rays?
Generally I've only seen this after installing one of the optional 'Preview' CUs. Lax coding at MS? Or an unavoidable consequence of it being a 'preview'? I don't know, but I no longer bother installing any optional previews....