Apologies for rather lengthy hiatus.
I'm back and all is well - and now did manage to get KB4512508 installed either:
Code:
C:\WINDOWS\system32>sfc /verifyonly
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
C:\WINDOWS\system32>
Code:
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18362.295
[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>
Alas! Just before I ran the installer, I thought it prudent to check once again C:\WINDOWS\System32\DriverStore\FileRepository\ folders just in case something else is amiss - and there was. What I have not spotted before were two additional folders whose INF files exhibited the same issue (i.e. were empty despite their size suggesting otherwise):
Their dates were changed though to yesterday/today as they have been modified by my re-installation attempts.
I decided to take a risk and got these files off original Windows 10 release 1903 install.esd file this time - bearing in mind that their file version had to be manually upped to 10.0.18362.267 as well (in line with the very first xboxgip.inf file).
So all is definitely well and I thank you very much for your help and understanding.
As to the reasons why there was a problem: I am fairly confident that my PC is absolutely fine hardware- and software-wise. It's definitely not a coincidence that
only core Microsoft's INFs were impacted - as I wrote earlier the culprit is faulty KB4505903 (released end of Jul '19) and subsequent my casual but otherwise non-threatning component clean-up that unexpectedly messed it all up.
One really wonders what's the use of DISM/SFC combo if they report that all is well - when it's clearly not.
One also wonders if there's another tool that allows finding such discrepancies somehow? Or perhaps there's no cure for Microsoft's very random but more and more frequent quality shortcomings?
One thinks about the joys going forward where two simultaneous releases (H1 & H2) are to be serviced by the same CU (or so I hear?).
One lastly wonders how may users, once they become aware that there is an issue that prevents their PC from being updated (and kept secure), will have to resort to either manual tweaks and modifications as per the above or - more likely - to complete OS reinstallation, conveniently known as in-place upgrade.
Therefore based on that experience I strongly recommend deferring from installation of any non-security CUs that Microsoft is pushing in haste, and without any comprehensive tests. Testament to this are numerous threads describing latest bunch of issues experienced by those who agreed to have it installed on their PCs.
Thanks again for your support, most appreciated.
