Update error 80070643

Hi Chuck,

That's great news! Thanks for posting back the results.


As for what did this, it's hard to tell. Essentially, what happened here was that your computer has a big list of things to do over a reboot and something caused one of these lines to hang, so it couldn't do the rest. I'd say that it's more likely to be a minor bug in Windows than anything you've done, so don't worry about it.


You're most welcome for the help :) It has been a pleasure working with you.


Just one corrupt file to fix:

Code:

2013-06-21 21:20:29, Info                  CSI    00000533 [SR] Repairing 1 components2013-06-21 21:20:29, Info                  CSI    00000534 [SR] Beginning Verify and Repair transaction
2013-06-21 21:20:29, Info                  CSI    00000535 [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-06-21 21:20:29, Info                  CSI    00000536 [SR] Cannot repair member file [l:18{9}]"MSDTC.LOG" of Microsoft-Windows-COM-DTC-Runtime, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-06-21 21:20:29, Info                  CSI    00000537 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

I'm not sure where this file is meant to go on your computer but I know the WinSxS path, so I'll fix that one and let SFC reform the hardlink :)

SFCFix Script


Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a files should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/...her/SFCFix.zip

SFC Scan

1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   
   sfc /scannow
   
   
   Wait for this to finish before you continue
   
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
   
   
   
   
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

Hi Chuck,

Excellent! That fixed the corruption:

Code:

2013-06-22 09:16:56, Info                  CSI    000002fb Repair results created:
POQ 127 starts:
 
POQ 127 ends.
2013-06-22 09:16:56, Info                  CSI    000002fc [SR] Repair complete

You're all good to go!


Tom