Emrys Davies wrote:
I am trying to fix the corrupted component store. Does what you have
suggested help that endeavour. If it does, it
is quite a way beyond me unless you walk me through it gently.
The theory is, you should be able to run a CheckSUR
even on a C: that doesn't need it.
It's supposed to repair/verify the WinSXS folder.
Steps:
1) Click the download for your OS, either the 32 bit one or the
64 bit one. Your System control panel contains a text string
identifying the OS.
System == System Type: 32-bit Operating system
32-bit W7SP1
https://www.microsoft.com/download/details.aspx?id=3132
64-bit W7SP1
https://www.microsoft.com/download/d....aspx?id=20858
2) The file that is downloaded, is a .msu, an executable file.
You double click it.
Windows6.1-KB947821-v34-x86.msu 239,126,136 bytes
Windows6.1-KB947821-v34-x64.msu 564,744,309 bytes
3) It will take at least ten minutes for the running MSU
installer to complete.
4) When it finished, the details (that I can see here) are in:
C:\Windows\Logs\CheckSUR.log
Here is a picture of my step (4).
https://i.postimg.cc/ZqrDjCVr/check-...tput-files.gif
I found that file by searching in Explorer for "CBS"
which stands for Component Based Servicing. The WinSXS
folder is the "trove" that CBS uses for maintaining your
OS and keeping copies of necessary things.
If something was corrected, it should be in the log.
I ran that demo on a virtual machine. I made a backup.
Now, I'll be doing a restore to a previous point in time,
just to reduce bloat...
CheckSUR has "versions", which is why the version 26
I installed today, if I downloaded and ran two months
from now, it could be version 27, and it would install
like version 26 did. Version 27 would "Supercede"
version 26, which is why Version 27 would install.
You only need to run that, when other parts of the
system provide feedback something is wrong with your
WinSXS store.
Sometimes the errors in WinSXS are "false positives".
You'll know this when CheckSUR says it "couldn't fix something"
and there might be mention the file was an HTML file.
An HTML file is not normally a part of the store and
could be ignored. The store would have DLLs and some
sort of catalog files, which you can examine at
your leisure to see what's in there.
If your store is corrupted, it will likely be
repairing more important items.
Paul