1 of 1 people found this helpful
There are occasions when a Windows update fails, for various of reasons. My opinion is that if it states that it is indeed 'Installed Successfully' and there are no explicit detections by the Software, I see no reason to be concerned.
You may benefit form running a 'SFC /SCANNOW' to check the Integrity of your Windows Updates that are installed...Just my Personal Opinion/Observation. Perhaps one of my Colleagues will pick up this thread and add to the discussion.
All the very Best,
1. No, don't worry. Various applications can place those rather strange looking files on the hard drive. I've seen them on mine from time to time. (see pic below for the current list at default view)
2. I wouldn't advise that as it may be essential to some process or other. You could go ahead with what you suggest, but I would set a System Restore point first just in case. BTW it may not be successful anyway. Some files will not allow ownership change or grant permission to change by anyone.
Thanks catdaddy. I think I will run the scannow as you suggest.
Thanks Ex_Brit. I think I'll skip deleting it as you suggest and instead run the sfc scannow as catdaddy mentions above.
You're welcome. Warning, an sfc/ scannow will revert any modifications you've made that aren't recognized 7 compatible, such as in my case: adding and activating Vista Windows Mail amongst several I did.
Also it may ask you for the installation media. It also takes a long time sometimes.
See also the warning in the Tutorial here: SFC /SCANNOW Command - System File Checker - Windows 7 Help Forums
With all due respect, if the original poster has not made any modifications, as mentioned. I see no reason to be concerned? Please correct me if I am incorrect...In addition from my experience it generally takes around 8-11 minutes.
Agreed, there's nothing to be concerned about.
An 11 minute system file check is a lucky break. Mine's taken much longer as a rule. Just talking from my own experience,. not trying to disagree with anyone.
I must make a correction , as Peter mentioned Scan time can vary. Just ran one myself and it took 26 minutes. So miles/time may vary.