The error mentioned is one of the errors the readiness tool is supposed to be able to fix, but not always. You can read about it at this Microsoft site and at the bottom it lists the location of 2 log files.
If you can, copy those 2 log files to your desktop along with the WindowsUpdate.log in the Windows directory and zip them and try to send them directly to me in a private message. .
Failed to evaluate Installed rule
I will also suggest you open an Administrative Command Prompt window and type the following and enter after. Give it time to work and if it comes back with some could not fix types of messages, we will have to check that.
SFC /scannow
This command just checks your system files. It is supposed to replace any bad ones, if it can.
Administrative command prompt your can click on Orb, type cmd in the search box, then CTRL+Shift+Enter
If none of this seems to help, I might recommend you rename the SoftwareDistribution folder in the Windows directory. This should cause your system to rebuild itself.
I will continue to check your logs, just in case I can find something definite.
3) Went to try and run the System Update Readiness Tool for Windows 7 and it says "Not applicable to this Computer"
If your command window says Administrator in the title and it gave you that message, it does not look good. I would be very hard to tell what condition your system files are in.
View attachment 16583View attachment 16584
According to what I found, this type of message (SFC error) might be caused by the fact the Trusted Installer is not running.
You can check by opening the Services dialog. Hit Winkey + R and then type services.msc
Go to the Windows Module Installer and see if it is running. If it is not, and mine was not, try to start it. If it will not start, we might be narrowing down the problem.
It seems to be set to a manual start so something has to start it. Just for testing, you might try the SFC again after having started it. In my case, running an SFC did start the Windows Module Installer. If you have already started it prior to doing the SFC, you might want to stop the service then see if an SFC will start it if it is set to a manual start.
The Trusted Installer is the entity that has ownership of the Windows core files and is used to replace or repair them.
1) OK, tried to run the SFC /scannow as an administrator and got a message "Windows Resource Protection could not start the repair service"
.
The TrustedInstaller.exe may have been removed by AVAST which is running. Sometime this week when we can get together I will examine the AVAST logs, and try to send him a zipped file from my PC with that file in it. I have experimented with how to install it in the C:\windows\servicing folder and think by opening an elevated cmd prompt as Admini, I can use a copy command - it worked on my Win 7 Ultimate last night (although when cmd asked me if I wanted to overwrite I just quit). We shall see. Apparently one needs the TrustedInstaller.exe in order to run SFC /scannow. AND SFC /scannow is the only way to restore missing Windows files.Any more information on the TrustedInstaller front? Running an SFC from outside of Windows has to be done using special commands. Check the link for an explanation.
Link Removed - Invalid URL