SFC didn't find any problems and checkSUR (by the way new version 27 - package version 19.0 - issued May 27) found the same errors with IE10. Log's attached.
Ether MS haven't fixed the mistake in recognition of IE10 packages or there is something wrong.
Yesterday I've restored the system from the backup without IE10 - and installed while implementing updates just an hour or two ago.
I didn't get what you mean byDo you mean that it is a real problem and you have it as well?I installed SURT as well... same problem. But it's a false positive!
It's just an error in the SURT tool. It reports the errors... but there's no problem at all!
How may windows updates have to be installed now, or are all updates installed and no problems at all?
All updates are installed now and no problems at all by now.How may windows updates have to be installed now, or are all updates installed and no problems at all?
Now I'm going further and installing .NET framework 4.0.2 update
Last edited by Eclectic; 29 May 2013 at 09:33. Reason: mistake in version number
Well it seems ok. Though I'm confused a bit the reason still unknown.
I think I can mark the issue as Solved unless you have some ideas.
This is just incredible! After 6 days of normal work WinServ2008 R2SP1 has crushed again.
You can find attached screenshots of some of the listed further:
- The first wrong thing was that a task Scheduled hasn't worked out. Tasks' library is empty though I remeber 4 tasks.
- Then PDF-printer drivers have crashed. I've unistalled it and then after new installation of the printer (that never happend before with this BullZip PDF Printer) Windows has detected a change in the system that require re-activation.
- Then Windows Update failed to find new updates as well as show the list of installed
- Server Roles status is "error"
- System Update Readiness Tool (KB947821) fails
- SFC /SCANNOW shows error.
Though it is strange that no any new updates were installed after last sucessful check of the system with checkSUR (KB947821). It seems that something wrong is just awaiting whether its time or some special trigger. Will try to recover it from the restore point when the working day will be over.
Last edited by Eclectic; 05 Jun 2013 at 01:21. Reason: spell fix
May we pass this report to Microsoft somehow? It seems that known problem that is expected to be solved with checkSUR is not solved.
Or we have here a very tricky hardware fault...
Last edited by Eclectic; 05 Jun 2013 at 12:45. Reason: adding attachments
Check your hard drive for problems.
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
Once complete, look in the Event Viewer > Windows Application logs for a Wininit event - that should contain the results of the scan
post the results.
Quote