5 Windows Updates Won't Apply; Win7 Home Premium, 6.1.7601

Page 1 of 2 12 LastLast

  1. subbes
    Posts : 5
    Windows 7 Home Premium (6.1.7601 SP1)
       New #1

    5 Windows Updates Won't Apply; Win7 Home Premium, 6.1.7601


    I'm running (Dell OEM) Win7 Home Premium on a Dell Inspiron 5520. The machine's used for dev work and runs a VM in Parallels Workstation, has sundry techy nonsense installed like python, nxlog, wireshark, git/svn. Antivirus is F-Secure; had Avast! instead for a while but it interfered with VMs. Some files were restored from backups of another Inspiron 5520 with a bad HDD.

    I have the following 5 updates that won't install:
    • Internet Explorer 10
    • KB2676562
    • KB2758857
    • KB2872339
    • KB2726535

    Attachment 285781

    The errors are:
    • 800B0100
    • 9C57

    Attachment 285782

    Running sfc /scannow did not find any integrity violations:
    Attachment 285783


    Attached is the contents of Logs/CBS. I cut out the .cab files and cbs.bld to reduce file size; let me know if you need them.
      My Computer
    Quote Quote

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

    There are a fair number of problem files there -
    Code:
    Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.22379_none_b74a85ec2c171ea6.manifest
 winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22379_none_c6996fb40738a459.manifest
 winsxs\manifests\amd64_microsoft-windows-consolehost_31bf3856ad364e35_6.1.7601.22379_none_d2cf6efb32033843.manifest
 winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22379_none_f2318ceb8634fb3e.manifest
 winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22379_none_14f23e4ccc3ea83b.manifest
 winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22379_none_85761ffde47d832a.manifest
 winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18205_none_ca621acbcab9bc3b.manifest
 winsxs\manifests\wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.22379_none_c19f303e6077e0a1.manifest
 winsxs\manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.18205_none_6e437f48125c4b05.manifest
 winsxs\manifests\wow64_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22379_none_324f890209a7d654.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18205_none_d0ac2b8722469d97.manifest
 winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22379_none_1f46e89f009f6a36.manifest
 winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22379_none_8fcaca5018de4525.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22379_none_d0ee1a063b996654.manifest
 winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22379_none_fc86373dba95bd39.manifest
 winsxs\manifests\wow64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22379_none_c014624816718091.manifest
 winsxs\manifests\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22379_none_6e856dc72baf13c2.manifest
 winsxs\manifests\amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22379_none_b5bfb7f5e210be96.manifest
 winsxs\manifests\amd64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22379_none_0aae4fa7491b124a.manifest
 winsxs\manifests\wow64_microsoft-windows-smss_31bf3856ad364e35_6.1.7601.22379_none_1502f9f97d7bd445.manifest
 winsxs\manifests\amd64_microsoft-windows-csrsrv_31bf3856ad364e35_6.1.7601.22379_none_27fadeafd5471459.manifest
 winsxs\manifests\amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7601.22379_none_caa4094ae40c84f8.manifest
 winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18205_none_c6578134ede5db9c.manifest
 winsxs\manifests\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22379_none_692597a0abb965cc.manifest
 winsxs\manifests\x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22379_none_0d06fc1cf35bf496.manifest
 winsxs\manifests\amd64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.18205_none_b708976d12c455e9.manifest
 winsxs\manifests\wow64_microsoft-windows-ntdll_31bf3856ad364e35_6.1.7601.18205_none_c15d41bf472517e4.manifest
 servicing\packages\Package_2_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_2_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_3_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_3_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_4_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_4_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_5_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_5_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2859537_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2859537_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_2_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_2_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_3_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_3_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_4_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_4_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_5_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_5_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_for_KB2859537_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_for_KB2859537_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
 servicing\packages\Package_for_KB2859537~31bf3856ad364e35~amd64~~6.1.1.3.cat
    I'll post a fix protocol in a bit.

    There's no data from your SFC scan in the CBS.log? when did you run it? (the CBS data goes back to 4 a.m. 11th Sept)
      My Computer
    Quote Quote

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

    I've uploaded afile - sbsaa.zip - to my SkyDrive at Noel's SkyDrive

    Please downloadand save it.

    Right-click onthe downloaded file, and select Extract all…

    Extract to thedefault location - which will create a new folder sbsaain the same place.

    Open this folder- there should be two folders inside it (Manifests,and Packages)

    Copy the content of the Packages folder to thefolder

    C:\Windows\Temp\CheckSur\Servicing\Packages

    Andthe content of the manifestsfolder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Nowrun the CheckSUR tool again (it may take a while)


    Postthe new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer
    Quote Quote

  6. subbes
    Posts : 5
    Windows 7 Home Premium (6.1.7601 SP1)
    Thread Starter
       New #4

    Thanks much, I will give those a try this afternoon! I ran sfc just after SURT on the 11th; is there no log in CBS because it found nothing wrong?
      My Computer
    Quote Quote

  7. subbes
    Posts : 5
    Windows 7 Home Premium (6.1.7601 SP1)
    Thread Starter
       New #5

    Just couldn't wait to give it a try. CheckSUR and CheckSUR.persist attached.
      My Computer
    Quote Quote

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

    I *knew* I'd missed one - but couldn't work out which one! :)

    Code:
    Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.22379_none_b5bfb7f5e210be96.manifest
    I'll post a fix for that in a bit
      My Computer
    Quote Quote

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

    Sorry for the delay....


    I've uploaded afile - sbsab.zip - to my SkyDrive at Noel's SkyDrive

    Please downloadand save it.

    Right-click onthe downloaded file, and select Extract all…

    Extract to thedefault location - which will create a new folder sbsabin the same place.

    Open this folder- there should be one folder inside it (Manifests,)




    Copythe content of the manifestsfolder (.manifest files) into this folder:



    C:\Windows\Temp\CheckSur\Winsxs\Manifests



    Nowrun the CheckSUR tool again (it may take a while)



    Postthe new CheckSUR.log file, and the CheckSUR.persist.log file.


    Then run another SFC /SCANNOW and post the new CBS.log file
      My Computer
    Quote Quote

  11. subbes
    Posts : 5
    Windows 7 Home Premium (6.1.7601 SP1)
    Thread Starter
       New #8

    No prob. Cheers for taking the time to do this.


    Zip file attached with the three log files. Diolch!
      My Computer
    Quote Quote

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

    Good - CheckSUR fixed the remaining problem, and the SFC scan is clear.

    With any luck, the updates should now install - do a manual Check for Updates first to sync it properly.
      My Computer
    Quote Quote

  13. subbes
    Posts : 5
    Windows 7 Home Premium (6.1.7601 SP1)
    Thread Starter
       New #10

    I began installing the updates, running in chronological order. Every one has installed correctly so far; my only remaining update is one from 10/9/13 which I'm going to sit on for a few more days in case there are any nasty effects reported.

    I'm going to mark this as solved; if it turns out the 10/9 update won't install I'll re-open the thread, but I doubt that'll happen.

    Cheers much!
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
Win7 takes forever to apply updates
in Windows Updates & Activation

Hey everyone. I do not think I am alone on this problem. My computer has become a little "old" applying updates. When it actually did "download" the updates, it restarted and when it booted up to install the updates, it took three hours. After three hours, it failed to install updates and reverted...
Win 7 Home Premium Build 7601 not genuine
in Windows Updates & Activation

Hi All, I have a very long history of update and activation problems on this computer in the last year. I posted my problem on the Microsoft forums and a very nice, generous, patient person has been helping me troubleshoot it for a while. You can read through that post for a complete history of...
Windows 7 Home Premium SP1 x64 7601 build error.
in Windows Updates & Activation

Did not upload .rars. Please use this link to this thread for the uploads, and diagnostics. https://www.sevenforums.com/windows-updates-activation/304080-windows-7-home-premium-sp1-x64-7601-build-error-revised.html#post2525127 Thank you.
Hello, I'm working on helping my cousin out with his laptop that has Windows 7 Home Premium 64bit. He got the laptop from a friend and wanted to do a clean install of Windows so he used my copy of Windows 7. He had the same OS before wiping the hard drive and installing a new copy. It's been fine...
Hi Guys, In the past i have tried to fix these errors that i continually have. I have tried many different types of fixes and just seem to be getting knowhere. The majority of the issues have an error code of 8007007e. Please see below two pictures, one showing my failed history, and the...
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 04:08.
Find Us