Can't check for updates, SURT fails.

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 18
    Windows 7 Home Premium x64
    Thread Starter
       #11

    NoelDP said:
    Looks like we'll have to do things the hard way

    Please follow the Windows Update Posting Instructions and post the requested data

    If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

    Hmm - I didn't notice that the SLIC table was missing here.
    Technically, this is a counterfeit install, since the OEM license cannot be moved to a new machine.
    Well, I have the log in my first post too, but here's an updated version.
      My Computer


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

    There's been a rash of these since this week's updates - it looks as though one of the updates may be responsible...

    There were problems with one of yesterday's updates - KB3004394
    If you uninstall it, that may cure the problem
      My Computer


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

    There is actually a critical error in the SFC log
    Code:
    POQ 22 ends.
    2014-12-09 15:21:59, Info                  CSI    0000006a [SR] Verify complete
    2014-12-09 15:21:59, Error                 CSI    0000006b (F) [SR] Component not found: Microsoft-Windows-Security-SPP-UX, 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[gle=0x80004005]
    2014-12-09 15:21:59, Error                 CSI    0000006c@2014/12/9:13:21:59.516 (F) d:\win7sp1_gdr\base\wcp\servicingapi\cmirepair.cpp(312): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
    [gle=0x80004005]
    2014-12-09 15:21:59, Error                 CSI    0000006d (F) [SR] Component not found: Microsoft-Windows-Security-SPP-UX, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral[gle=0x80004005]
    2014-12-09 15:21:59, Error                 CSI    0000006e@2014/12/9:13:21:59.587 (F) d:\win7sp1_gdr\base\wcp\servicingapi\cmirepair.cpp(312): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
    [gle=0x80004005]
    2014-12-09 15:21:59, Info                  CSI    0000006f [SR] Verifying 1 components
    Once you've uninstalled the update, please reboot and run SFC again, and post the new CBS.log and the MGADiag report
      My Computer


  4. Posts : 18
    Windows 7 Home Premium x64
    Thread Starter
       #14

    NoelDP said:
    There's been a rash of these since this week's updates - it looks as though one of the updates may be responsible...

    There were problems with one of yesterday's updates - KB3004394
    If you uninstall it, that may cure the problem
    NoelDP said:
    There is actually a critical error in the SFC log
    Code:
    POQ 22 ends.
    2014-12-09 15:21:59, Info                  CSI    0000006a [SR] Verify complete
    2014-12-09 15:21:59, Error                 CSI    0000006b (F) [SR] Component not found: Microsoft-Windows-Security-SPP-UX, 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[gle=0x80004005]
    2014-12-09 15:21:59, Error                 CSI    0000006c@2014/12/9:13:21:59.516 (F) d:\win7sp1_gdr\base\wcp\servicingapi\cmirepair.cpp(312): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
    [gle=0x80004005]
    2014-12-09 15:21:59, Error                 CSI    0000006d (F) [SR] Component not found: Microsoft-Windows-Security-SPP-UX, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral[gle=0x80004005]
    2014-12-09 15:21:59, Error                 CSI    0000006e@2014/12/9:13:21:59.587 (F) d:\win7sp1_gdr\base\wcp\servicingapi\cmirepair.cpp(312): Error HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) originated in function Windows::ServicingAPI::CCSIRepairTransaction::LockComponent expression: HRESULT_FROM_WIN32(14081L)
    [gle=0x80004005]
    2014-12-09 15:21:59, Info                  CSI    0000006f [SR] Verifying 1 components
    Once you've uninstalled the update, please reboot and run SFC again, and post the new CBS.log and the MGADiag report
    Update is not installed. I have had the issue since October, apparently.
      My Computer


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

    Ah - in that case I'll post a fix protocol for the errant file later.
      My Computer


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

    I've uploaded a file - sb7aa.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:\sb7aa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\sb7aa
    or
    DIR E:\sb7aa



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



    XCOPY <drive>:\sb7aa <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


  7. Posts : 18
    Windows 7 Home Premium x64
    Thread Starter
       #17

    NoelDP said:
    I've uploaded a file - sb7aa.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:\sb7aa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\sb7aa
    or
    DIR E:\sb7aa



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



    XCOPY <drive>:\sb7aa <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
    Question, can the repair environement be a Windows Install DVD?
      My Computer


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

    Yes - when you get the offer to install, there's also an offer to repair the current install.
      My Computer


  9. Posts : 18
    Windows 7 Home Premium x64
    Thread Starter
       #19

    NoelDP said:
    Yes - when you get the offer to install, there's also an offer to repair the current install.
    Ok, I copied that folder to my WinSXS, ran sfc /scannow, and zipped the log. Here you go. May I ask you what do these xcopy options do?
      My Computer


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

    Basically they force creation of the folders if they don't already exists, and overwrite of existing file without requesting confirmation.
    That seems to have fixed all the errors.

    PLease post a new MGADiag report.
      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 10:49.
Find Us