Windows update error - 8E5E03FB & 80070490

Sorry - it's been a hectic week (again!).

I'm a little surprised by the Blue screen errors - I don't think that anything would be affected by what we've done.

Please run new a CheckSUR and SFC /SCANNOW and post the new CBS.log and CheckSUR.log files.

That list has gotten longer!
Maybe a look at the event logs will help?

Please open Event Viewer
In the left pane, navigate to the Windows Logs
right-click on Applications and select 'Save all events as...' save as Apps.evtx
repeat for the System logs - save as Sys.evtx
Compress both files, and attach to your reply or upload to your favourite fileshare site (preferably Dropbox or OneDrive/SkyDrive) and post a link in your reply

Please post the logs as requested - I need the raw data.

Your hard disk is having problems - there are bad blocks/sectors showing in the System report
Please run a full CHKDSK scan...


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, and then reboot.
The chkdsk will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot)

then post the new Applications Event log.

The CHKDSK was surprisingly error-free...

Code:

 
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.                         
CHKDSK is verifying files (stage 1 of 5)...
  229888 file records processed.                                         
File verification completed.
  404 large file records processed.                                   
  0 bad file records processed.                                     
  2 EA records processed.                                           
  92 reparse records processed.                                      
CHKDSK is verifying indexes (stage 2 of 5)...
  299022 index entries processed.                                        
Index verification completed.
  0 unindexed files scanned.                                        
  0 unindexed files recovered.                                      
CHKDSK is verifying security descriptors (stage 3 of 5)...
  229888 file SDs/SIDs processed.                                        
Cleaning up 127 unused index entries from index $SII of file 0x9.
Cleaning up 127 unused index entries from index $SDH of file 0x9.
Cleaning up 127 unused security descriptors.
Security descriptor verification completed.
  34568 data files processed.                                           
CHKDSK is verifying Usn Journal...
  36604928 USN bytes processed.                                            
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  229872 files processed.                                                
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  9442711 free clusters processed.                                        
Free space verification is complete.
Windows has checked the file system and found no problems.
 209611775 KB total disk space.
 171400128 KB in 161856 files.
    101244 KB in 34569 indexes.
        12 KB in bad sectors.
    339547 KB in use by the system.
     65536 KB occupied by the log file.
  37770844 KB available on disk.
      4096 bytes in each allocation unit.
  52402943 total allocation units on disk.
   9442711 allocation units available on disk.

This doesn't really explain the bad-block errors that I saw in the earlier System log - although the 12KB of bad sectors could indicate a failing drive, they have been present for at least 15 months and don't appear to be growing. I was expecting at least two or three new bad sectors.

Let's see if that's made any difference to the CheckSUR - please run CheckSUR again, and post the new log file.