Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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


13 Sep 2013   #1

Windows 7 Home Premium (6.1.7601 SP1)
 
 
5 Windows Updates Won't Apply; Win7 Home Premium, 6.1.7601

I'm running (Dell OEM) Windows 7 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
5 Windows Updates Won't Apply;  Win7 Home Premium, 6.1.7601-failed-updates.png

The errors are:
  • 800B0100
  • 9C57
Name:  WUS failed.png
Views: 5
Size:  23.0 KB

Running sfc /scannow did not find any integrity violations:
Name:  sfc scannow.png
Views: 4
Size:  15.1 KB


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.




Attached Files
File Type: zip CBS20130913.zip (1.42 MB, 2 views)
My System SpecsSystem Spec
.

14 Sep 2013   #2

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
14 Sep 2013   #3

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
.


14 Sep 2013   #4

Windows 7 Home Premium (6.1.7601 SP1)
 
 

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 System SpecsSystem Spec
14 Sep 2013   #5

Windows 7 Home Premium (6.1.7601 SP1)
 
 

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


Attached Files
File Type: zip CheckSUR20130914.zip (4.8 KB, 3 views)
My System SpecsSystem Spec
14 Sep 2013   #6

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
15 Sep 2013   #7

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
15 Sep 2013   #8

Windows 7 Home Premium (6.1.7601 SP1)
 
 

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


Zip file attached with the three log files. Diolch!
My System SpecsSystem Spec
15 Sep 2013   #9

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
15 Sep 2013   #10

Windows 7 Home Premium (6.1.7601 SP1)
 
 

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 System SpecsSystem Spec
Reply

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




Thread Tools



Similar help and support threads for2: 5 Windows Updates Won't Apply; Win7 Home Premium, 6.1.7601
Thread Forum
Windows 7 Home Premium SP1 x64 7601 build error. Windows Updates & Activation
win7 home premium 64bit sp1 OEM to home prem. retail fam pack ugrade Installation & Setup
Windows 7 Home Premium Build 7601 This copy of windows is not genuine Windows Updates & Activation
Windows 7 Home Premium X64 - Updates all Failing. 800B0100 Windows Updates & Activation
Solved Windows 7 Home Premium X64 - Updates all Failing. (8007007e) Windows Updates & Activation
Configuring windows 7 Home Premium for WSUS Updates Windows Updates & Activation

Our Sites

Site Links

About Us

Find 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 02:19 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33