When I attempt to use windows update, it starts but fails. It gives Error Code 800706BA and occasionally 800706BE Last week, MS Tech Support spent several hours fixing the problem. They resolved it by remoteing in and tweaking something to do with Digital Signatures. It worked great...for two days. The the same problem resumed. I emailed the Tech who fixed it and asked what he did so that it could be "fixed" again. He dutifully replied that my previous issue had been resolved and I would need to open a new service ticket to address this occurance. I truly appreciate the initial fix...sure wish it woulda stuck. Anyone have insight on how to get this actually resolved? Win7 Entp Sp1 All antivirun/antimalware has been uninstalled. THX

Tried to run this: System Update Readiness Tool for Windows Vista (KB947821) [February 2012] but it also wont install. Corrupt Digital Signature apparently stops everything (thats just my guess). And, yes...Its a valid version of the software. Nothing funky.

Hi, Please download the following version of System update Readiness Tool to install first. http://www.microsoft.com/download/en/details.aspx?id=20858 If you encounter any problem, please update the log file %SYSTEMROOT%\Logs\CBS\CheckSUR.log to Skydrive. According to your description, I assume that the servicing store may be corrupted. You may also consider performing an In-place upgrade to repair this kind of issue. Juke Chou TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere. Juke Chou TechNet Community Support

"VryFrustrated" wrote in message news:8e7b5d2b-ce83-46fd-9030-be3428f3ed94... Tried to run this: System Update Readiness Tool for Windows Vista (KB947821) [February 2012] but it also wont install. Corrupt Digital Signature apparently stops everything (thats just my guess). And, yes...Its a valid version of the software. Nothing funky. Hmmm - please provide an MGADiag report ( I suspect that it will have a slew of File Mismatches) To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 ) Once saved, run the tool. Click on the Continue button, which will produce the report. To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Check whether microsoft.com or drweb.com work? It could be also a virus which locks access to many update- and antivirus sites. If so, download from kaspersky.ru free version to clean the system. Using different computer, sure. GL, Ilya

Installing the readyness tool fails. Message: "Windows Update stand alone installer has stopped working."

"VryFrustrated" wrote in message news:ee6a7af9-725f-444c-9d73-299fcedaf166... MGADiag report: Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: 0x0 Windows Product Key: *****-*****-*****-*****-6PV89 Windows Product Key Hash: a738/vTW2vBDCCgfN7SKYzD6XPw= Windows Product ID: 55041-049-9660365-86599 Windows Product ID Type: 6 Windows License Type: Volume MAK Windows OS version: 6.1.7601.2.00010100.1.0.004 OK - no errors there at all - so I was wrong :) I'll crawl back into my hole now. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Does Microsoft.com work? are you asking me if I can see the website Microsoft.com? Yes, it works. As for DrWeb.com and Kaspersky.ru I am hesitant to install anything since I have UNinstalled my antivirus protection and am essentially running around the internet buck-arse naked at the moment. Not as liberating as it may sound. I had been running Microsoft Security Essentials AND Malwarebytes. I ran frequent full scans. Neither found any infections before I uninstalled them afdter reading that having two malware programs might cause conflicts.

Ohhhhh no you dont. So far you're the only one who's suggested anything that has DONE something. So you're back in the ring. :) Gimme some more ideas. could it be a "service" that has been turned off? If so...which one?

Just as a point of Info - MSE and MalwareBytes get along fine, as they are looking at different things. I run both happily here - although I don't use the Real-Time Protection mode of Malwarebytes. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Awesome...good to know. I'll re-install them before my delicates get a sunburn.

First try to run this solution (microsoft fixit) http://support.microsoft.com/mats/windows_update/en-us If that doesn't work then try to download and re-install windows update agent http://support.microsoft.com/kb/949104

Installed and ran both of the above. BOTH said they fixed issues with Windows Update. YAY Unfortunately the problem still exists. Interestingly, when I click on "View installed updates" I see that not ALL of the updates fail...just 90% of them. I guess Im only "Mostly dead" (Princess bride Reference) Example- Security Update to .NET framework installed successfully Windows Malicious Software removal tool installed successfully. However During the same update session - Security Update to Windows 7 Failed Update to windows 7 failed Cumulative Security update for IE9 failed

Some of the downloaded updates are probably corrupted. http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/5728fc8d-4ba7-4d08-994a-2144b79a8f96 1. Click "Start", in "Start Search" item, type: "notepad" (without quotes) and press Enter. 2. Copy the following commands and then paste them into the opened Notepad window: net stop wuauserv net stop CryptSvc ren %windir%\system32\catroot2 catroot2.old ren %windir%\SoftwareDistribution sold.old net start CryptSvc net start wuauserv pause 3. After pasting the above commands, please close the Notepad window. Choose "Save" when you are prompted to save the file. Type "rename.bat" as the file name and save it to the Desktop. 4. Return to the Desktop, right click the rename.bat file and choose "Run as administrator". 5. You will see a DOS-like window processing.

I followed your instructions. It ran the DOS-like process. I re-ran Windows Update. It Downloaded the updates. Appeared to Hang-up when "Creating a restore point" and errored-out with the same 800706BA error. Rince and repeat...tried it three times.

you need to run from cmd prompt sfc /scannow

I followed your instructions. It ran the DOS-like process. I re-ran Windows Update. It Downloaded the updates. Appeared to Hang-up when "Creating a restore point" and errored-out with the same 800706BA error. Rince and repeat...tried it three times. You may need to increase the space alocated for System Restore. Or turn off system restore temporarly but then if something goes wrong you don't have way to restore your system unless you have a backup of some sort.

Done it several times...as administrator. Just did it again. Always stops at 53% and gives the message: "Windows Resource protectiBut I am hopingon could not perform the requested operation" See why Im frustrated? grrr I know Im precariously close to jumping off the "reinstall" edge. Before I do that, I'll upgrade to Win8 just as a hail-mary to see if that slaps something awake and starts working miraculously. (delusional, I know) But I am hoping that somehow someone will know the magic trick to fixing the digital signature issue that fixed this problem last week. (See post #1)

Pleasee upload your CBS.log file (you'll have to copy it to the desktop first) to your public SkyDrive and post a link in your response - it may give us a clue to what's killing it.Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 http://support.microsoft.com/kb/929833

sfcdetails > > 2012-04-25 10:41:09, Info CSI 00000021 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:09, Info CSI 00000022 [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:14, Info CSI 00000024 [SR] Verify complete 2012-04-25 10:41:15, Info CSI 00000025 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:15, Info CSI 00000026 [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:19, Info CSI 00000028 [SR] Verify complete 2012-04-25 10:41:20, Info CSI 00000029 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:20, Info CSI 0000002a [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:26, Info CSI 0000002c [SR] Verify complete 2012-04-25 10:41:27, Info CSI 0000002d [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:27, Info CSI 0000002e [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:30, Info CSI 00000030 [SR] Verify complete 2012-04-25 10:41:30, Info CSI 00000031 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:30, Info CSI 00000032 [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:31, Info CSI 00000034 [SR] Verify complete 2012-04-25 10:41:31, Info CSI 00000035 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:31, Info CSI 00000036 [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:36, Info CSI 00000038 [SR] Verify complete 2012-04-25 10:41:36, Info CSI 00000039 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:36, Info CSI 0000003a [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:39, Info CSI 0000003c [SR] Verify complete 2012-04-25 10:41:40, Info CSI 0000003d [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:40, Info CSI 0000003e [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:42, Info CSI 00000040 [SR] Verify complete 2012-04-25 10:41:43, Info CSI 00000041 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:43, Info CSI 00000042 [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:45, Info CSI 00000044 [SR] Cannot repair member file [l:28{14}]"igd10umd32.dll" of igdlh.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch 2012-04-25 10:41:48, Info CSI 00000046 [SR] Cannot repair member file [l:28{14}]"igd10umd32.dll" of igdlh.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch 2012-04-25 10:41:48, Info CSI 00000047 [SR] This component was referenced by [l:174{87}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~x86~~6.1.7601.17514.INF_igdlh" 2012-04-25 10:41:48, Info CSI 00000049 [SR] Verify complete 2012-04-25 10:41:48, Info CSI 0000004a [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:48, Info CSI 0000004b [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:52, Info CSI 0000004d [SR] Verify complete 2012-04-25 10:41:52, Info CSI 0000004e [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:52, Info CSI 0000004f [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:54, Info CSI 00000051 [SR] Verify complete 2012-04-25 10:41:54, Info CSI 00000052 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:54, Info CSI 00000053 [SR] Beginning Verify and Repair transaction 2012-04-25 10:41:55, Info CSI 00000055 [SR] Cannot repair member file [l:22{11}]"sysmain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C1, Version = 6.1.7601.17571, 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 2012-04-25 10:41:56, Info CSI 00000057 [SR] Cannot repair member file [l:22{11}]"sysmain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C1, Version = 6.1.7601.17571, 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 2012-04-25 10:41:56, Info CSI 00000058 [SR] This component was referenced by [l:150{75}]"Package_2_for_KB2492386~31bf3856ad364e35~x86~~6.1.1.0.2492386-8_neutral_GDR" 2012-04-25 10:41:57, Info CSI 0000005b [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\apppatch"\[l:22{11}]"sysmain.sdb"; source file in store is also corrupted 2012-04-25 10:41:58, Info CSI 0000005d [SR] Verify complete 2012-04-25 10:41:58, Info CSI 0000005e [SR] Verifying 100 (0x00000064) components 2012-04-25 10:41:58, Info CSI 0000005f [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:03, Info CSI 00000061 [SR] Verify complete 2012-04-25 10:42:03, Info CSI 00000062 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:03, Info CSI 00000063 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:07, Info CSI 00000068 [SR] Verify complete 2012-04-25 10:42:07, Info CSI 00000069 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:07, Info CSI 0000006a [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:11, Info CSI 0000006d [SR] Verify complete 2012-04-25 10:42:12, Info CSI 0000006e [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:12, Info CSI 0000006f [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:16, Info CSI 00000073 [SR] Verify complete 2012-04-25 10:42:16, Info CSI 00000074 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:16, Info CSI 00000075 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:25, Info CSI 0000007f [SR] Verify complete 2012-04-25 10:42:26, Info CSI 00000080 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:26, Info CSI 00000081 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:31, Info CSI 00000083 [SR] Verify complete 2012-04-25 10:42:32, Info CSI 00000084 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:32, Info CSI 00000085 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:37, Info CSI 00000087 [SR] Verify complete 2012-04-25 10:42:38, Info CSI 00000088 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:38, Info CSI 00000089 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:38, Info CSI 0000008b [SR] Cannot repair member file [l:14{7}]"dpx.dll" of Microsoft-Windows-DeltaPackageExpander, Version = 6.1.7601.17514, 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 2012-04-25 10:42:41, Info CSI 0000008d [SR] Cannot repair member file [l:14{7}]"dpx.dll" of Microsoft-Windows-DeltaPackageExpander, Version = 6.1.7601.17514, 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 2012-04-25 10:42:41, Info CSI 0000008e [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery" 2012-04-25 10:42:41, Info CSI 00000091 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:14{7}]"dpx.dll"; source file in store is also corrupted 2012-04-25 10:42:41, Info CSI 00000093 [SR] Verify complete 2012-04-25 10:42:42, Info CSI 00000094 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:42, Info CSI 00000095 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:45, Info CSI 00000097 [SR] Verify complete 2012-04-25 10:42:46, Info CSI 00000098 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:46, Info CSI 00000099 [SR] Beginning Verify and Repair transaction 2012-04-25 10:42:50, Info CSI 0000009b [SR] Verify complete 2012-04-25 10:42:50, Info CSI 0000009c [SR] Verifying 100 (0x00000064) components 2012-04-25 10:42:50, Info CSI 0000009d [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:00, Info CSI 000000a1 [SR] Verify complete 2012-04-25 10:43:01, Info CSI 000000a2 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:01, Info CSI 000000a3 [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:10, Info CSI 000000a5 [SR] Verify complete 2012-04-25 10:43:10, Info CSI 000000a6 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:10, Info CSI 000000a7 [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:24, Info CSI 000000a9 [SR] Verify complete 2012-04-25 10:43:24, Info CSI 000000aa [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:24, Info CSI 000000ab [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:34, Info CSI 000000ad [SR] Verify complete 2012-04-25 10:43:35, Info CSI 000000ae [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:35, Info CSI 000000af [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:39, Info CSI 000000b1 [SR] Verify complete 2012-04-25 10:43:39, Info CSI 000000b2 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:39, Info CSI 000000b3 [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:42, Info CSI 000000b5 [SR] Verify complete 2012-04-25 10:43:43, Info CSI 000000b6 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:43, Info CSI 000000b7 [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:44, Info CSI 000000b9 [SR] Verify complete 2012-04-25 10:43:45, Info CSI 000000ba [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:45, Info CSI 000000bb [SR] Beginning Verify and Repair transaction 2012-04-25 10:43:47, Info CSI 000000bd [SR] Verify complete 2012-04-25 10:43:48, Info CSI 000000be [SR] Verifying 100 (0x00000064) components 2012-04-25 10:43:48, Info CSI 000000bf [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:01, Info CSI 000000dd [SR] Verify complete 2012-04-25 10:44:02, Info CSI 000000de [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:02, Info CSI 000000df [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:03, Info CSI 000000e1 [SR] Verify complete 2012-04-25 10:44:03, Info CSI 000000e2 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:03, Info CSI 000000e3 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:07, Info CSI 000000e5 [SR] Verify complete 2012-04-25 10:44:07, Info CSI 000000e6 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:07, Info CSI 000000e7 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:10, Info CSI 000000e9 [SR] Verify complete 2012-04-25 10:44:10, Info CSI 000000ea [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:10, Info CSI 000000eb [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:12, Info CSI 000000ed [SR] Cannot repair member file [l:18{9}]"IMTCS.IMD" of Microsoft-Windows-IME-Traditional-Chinese-BigramDictionary, Version = 6.1.7600.16385, 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 2012-04-25 10:44:15, Info CSI 000000f0 [SR] Cannot repair member file [l:18{9}]"IMTCS.IMD" of Microsoft-Windows-IME-Traditional-Chinese-BigramDictionary, Version = 6.1.7600.16385, 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 2012-04-25 10:44:15, Info CSI 000000f1 [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery" 2012-04-25 10:44:16, Info CSI 000000f4 [SR] Could not reproject corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:18{9}]"IMTCS.IMD"; source file in store is also corrupted 2012-04-25 10:44:16, Info CSI 000000f6 [SR] Verify complete 2012-04-25 10:44:16, Info CSI 000000f7 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:16, Info CSI 000000f8 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:23, Info CSI 000000fb [SR] Verify complete 2012-04-25 10:44:23, Info CSI 000000fc [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:23, Info CSI 000000fd [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:34, Info CSI 000000ff [SR] Verify complete 2012-04-25 10:44:34, Info CSI 00000100 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:34, Info CSI 00000101 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:36, Info CSI 00000103 [SR] Verify complete 2012-04-25 10:44:36, Info CSI 00000104 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:36, Info CSI 00000105 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:38, Info CSI 00000107 [SR] Verify complete 2012-04-25 10:44:38, Info CSI 00000108 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:38, Info CSI 00000109 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:45, Info CSI 0000010b [SR] Verify complete 2012-04-25 10:44:45, Info CSI 0000010c [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:45, Info CSI 0000010d [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:50, Info CSI 0000010f [SR] Verify complete 2012-04-25 10:44:50, Info CSI 00000110 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:50, Info CSI 00000111 [SR] Beginning Verify and Repair transaction 2012-04-25 10:44:57, Info CSI 00000113 [SR] Verify complete 2012-04-25 10:44:57, Info CSI 00000114 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:44:57, Info CSI 00000115 [SR] Beginning Verify and Repair transaction 2012-04-25 10:45:01, Info CSI 00000117 [SR] Cannot repair member file [l:26{13}]"MFC42.dll.mui" of Microsoft-Windows-MFC42x.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2012-04-25 10:45:06, Info CSI 0000011b [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[ml:28{14},l:26{13}]"MFC42.dll.mui" by copying from backup 2012-04-25 10:45:06, Info CSI 0000011d [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:26{13}]"MFC42.dll.mui" from store 2012-04-25 10:45:08, Info CSI 00000123 [SR] Verify complete 2012-04-25 10:45:09, Info CSI 00000124 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:45:09, Info CSI 00000125 [SR] Beginning Verify and Repair transaction 2012-04-25 10:45:18, Info CSI 00000144 [SR] Verify complete 2012-04-25 10:45:18, Info CSI 00000145 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:45:18, Info CSI 00000146 [SR] Beginning Verify and Repair transaction 2012-04-25 10:45:20, Info CSI 00000148 [SR] Cannot repair member file [l:24{12}]"M1033DSK.WIH" of Microsoft-Windows-MulanTTSVoiceENUDsk, Version = 6.1.7600.16385, 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 2012-04-25 10:45:25, Info CSI 0000014a [SR] Cannot repair member file [l:24{12}]"M1033DSK.WIH" of Microsoft-Windows-MulanTTSVoiceENUDsk, Version = 6.1.7600.16385, 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 2012-04-25 10:45:25, Info CSI 0000014b [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery" 2012-04-25 10:45:26, Info CSI 0000014e [SR] Could not reproject corrupted file [ml:520{260},l:154{77}]"\??\C:\Program Files\Common Files\SpeechEngines\Microsoft\TTS20\en-US\enu-dsk"\[l:24{12}]"M1033DSK.WIH"; source file in store is also corrupted 2012-04-25 10:45:28, Info CSI 00000150 [SR] Verify complete 2012-04-25 10:45:28, Info CSI 00000151 [SR] Verifying 100 (0x00000064) components 2012-04-25 10:45:28, Info CSI 00000152 [SR] Beginning Verify and Repair transaction 2012-04-25 10:45:37, Info CSI 00000153 [SR] Cannot repair member file [l:18{9}]"netbt.sys" of Microsoft-Windows-NetBT, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked

"VryFrustrated" wrote in message news:6eb0d886-4110-45d0-9f58-4dadc61abd8f... Please upload the complete log file to your SkyDrive. this contains much more detail than is extracted. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Ive pasted my SFCdetails here twice and it keeps disappearing When I try to paste my CBS.log, this page crashes. I dont have a skydrive

"VryFrustrated" wrote in message news:0b0b3c97-8e29-4388-9625-c6572e288afc... Ive pasted my SFCdetails here twice and it keeps disappearing You cannot attach files to posts in these forums - you have to upload them to a fileshare site (such as SkyDrive) and post a link here. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

work'n on it.... stand by Getting link now https://skydrive.live.com/redir.aspx?cid=572cdd3b748bd3d0&resid=572CDD3B748BD3D0!135&parid=572CDD3B748BD3D0!112&authkey=!ABqmULj0acMKSKo

"VryFrustrated" wrote in message news:7b33d610-a229-4819-b5ac-9c4115fd8ca5... work'n on it.... stand by Getting link now https://skydrive.live.com/redir.aspx?cid=572cdd3b748bd3d0&resid=572CDD3B748BD3D0!135&parid=572CDD3B748BD3D0!112&authkey=!ABqmULj0acMKSKo OK - got it. 14.6MB could take some time to work through - relax for a while :) (hours, rather than minutes!) Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Yeah, 14mb for a txt file shocked me too. My wife is "suggesting" I spend some quality time with my honey-do list. That'll be a pleasant distraction since it will provide a sense of accomplishment. My email: Texan@austin.rr.com

That went quicker than I thought - although I'm not too sure about the results. You have 93 points of failure in that log which would appear in the - which is just for today. The majority of the failures are for pending deletions. There are also a huge number of other failed entries for access to files in the WinSxS folder. To be honest, I don't think I'd even consider a repair install on this - it looks to me as if it may be doomed to fail. I would certainly not even consider any attempt a normal upgrade to Win8 - that is sure to make things worse - although you could take the opportunity to do a clean install of Win8 if you feel so inclined. Your best option as far as I can see is to reimage the system - after backing up data to external media. Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

Yeah... Thats what I was afraid of. Thank you , ALL, for your efforts.

You're welcome. Good Luck!Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth