Odd Issue..

Try running
sfc /scannow
at an elevated command prompt. I use step 3.
Run it as many times until no errors reported.

Someone else may be better able to help and interpret your log file.
When you say you have a Todo backup do you have images. If so try a system image restore.
Whatever, make sure you have a good backup of your data in case you need to do a clean install.

The SFC scan found a large number of errors, and managed to fix most of them - but there remain a couple....

Code:

 Line 107129: 2013-09-17 00:29:57, Info                  CSI    00001a4a [SR] Repairing 580 (0x0000000000000244) components
 Line 107130: 2013-09-17 00:29:57, Info                  CSI    00001a4b [SR] Beginning Verify and Repair transaction
 Line 107133: 2013-09-17 00:29:58, Info                  CSI    00001a4d [SR] Cannot repair member file [l:22{11}]"install.ins" of Microsoft-Windows-IE-AdminKitBranding, Version = 10.2.9200.16521, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 107136: 2013-09-17 00:29:58, Info                  CSI    00001a4f [SR] Cannot repair member file [l:22{11}]"install.ins" of Microsoft-Windows-IE-AdminKitBranding, Version = 10.2.9200.16521, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

Please run the CheckSUR tool - it will probably find a few more problems...

Please downloadand save the CheckSUR tool from http://support.microsoft.com/kb/947821

(you'll need tolook in the details for Windows 7, downloading from the Microsoft DownloadCenter)



Run it - The toolcan take anywhere from 5 mins to a couple of hours to run (or 'Install')depending on how much it has to do, and may exit silently - it may appear tofreeze for most of that time, but be patient.

The result islogged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file



Then zip theCheckSUR.log and attach it to your reply.

Just a thought maybe a restoring to a Windows update restore point may throw something up??

It's possible - from the looks of the errors, it seems that an entire Windows directory (C:\Windows\diagnostics) went AWOL