Cannot Update Windows 7 x64 SP1 - Error 0x8007370B

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 11
    Windows 7 Home Premium 32 and 64 bit
    Thread Starter
       #11

    NoelDP, any idea when you might be able to get back to this? If not could you turn it over to another admin?
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #12

    OMG _ it dropped off my ToDo list!
    I'll try and get back to it this evening.
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #13

    I've uploaded a file - brkaa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it to your desktop.
    Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

    Create a new System Restore point

    Open an Elevated Command Prompt, and run the following commands.

    Code:
    IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1
    REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
    COPY "%userprofile%\desktop\brkaa\COMPONENTS" C:\Windows\System32\config
     
    .
    If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

    Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.
      My Computer


  4. Posts : 11
    Windows 7 Home Premium 32 and 64 bit
    Thread Starter
       #14

    NoelDP, It ran fine. Here is the link to the files: https://www.dropbox.com/s/0n4mbppopp...-2015.zip?dl=0
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #15

    great - the only error that CheckSUR found this time was the expected...
    Code:
    Checking Component Store
    (f)	CSI Payload File Missing	0x00000000	dao360.dll	x86_microsoft-windows-m..s-components-jetdao_31bf3856ad364e35_6.1.7600.16385_none_7b8c1dc4ef873d90
    Please run another SFC /SCANNOW and post the new CBS.log - that way I can fix any other missing files as well.
      My Computer


  6. Posts : 11
    Windows 7 Home Premium 32 and 64 bit
    Thread Starter
       #16

    NoelDP, here is the link to the CBS log files you requested SFC /scannow. Thanks again
    https://www.dropbox.com/s/x553xa0ci8...-2015.zip?dl=0
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #17

    Here's the important bits from the SFC scan...
    Code:
    	Line 520718: 2015-10-21 19:15:42, Info                  CSI    0000058b [SR] Repairing 4 components
    	Line 520719: 2015-10-21 19:15:42, Info                  CSI    0000058c [SR] Beginning Verify and Repair transaction
    	Line 520724: 2015-10-21 19:15:42, Info                  CSI    0000058f [SR] Cannot verify component files for Microsoft-Windows-Font-TrueType-MongolianBaiti, 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, manifest is damaged (TRUE)
    	Line 520727: 2015-10-21 19:15:42, Info                  CSI    00000591 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 520730: 2015-10-21 19:15:42, Info                  CSI    00000593 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 520735: 2015-10-21 19:15:42, Info                  CSI    00000596 [SR] Cannot verify component files for Microsoft.Windows.Hardware.Devices.ClassInstaller.MULTIPORTSERIAL-DriverClass, 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, manifest is damaged (TRUE)
    	Line 520736: 2015-10-21 19:15:42, Info                  CSI    00000597 [SR] Cannot repair member file [l:20{10}]"dao360.dll" of Microsoft-Windows-Microsoft-Data-Access-Components-JetDAO, 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, file is missing
    	Line 520741: 2015-10-21 19:15:42, Info                  CSI    0000059a [SR] Recovered manifest from backup for Microsoft-Windows-Font-TrueType-MongolianBaiti, 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

    I'll post a fix protocol later for everything (hopefully!)
      My Computer


  8. Posts : 11
    Windows 7 Home Premium 32 and 64 bit
    Thread Starter
       #18

    NoelDP, any luck with finishing this up?
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #19

    Sorry - not a good weekend

    Anyhow - here we go...
    I've uploaded a file - brkab.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)

    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\brkab
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\brkab
    or
    DIR E:\brkab

    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

    XCOPY <drive>:\brkab <drive>:\windows\winsxs /y /i /s /v /h

    (e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

    run the command (it should take almost no time) and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply
      My Computer


  10. Posts : 11
    Windows 7 Home Premium 32 and 64 bit
    Thread Starter
       #20

    NoelDP, here is the log file: https://www.dropbox.com/s/yzt3h1bhjz...-2015.zip?dl=0
    Thanks.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:24.
Find Us