Solved Windows 7 won't apply updates.

[IronBat]

For a while I have been having problems installing updates, I have tried many things and none of them have helped. I have run the KB947821 update and I have not seen any progress on the progress bar at all after 8+ hours. I have run the Disk cleaner removing all the updates and the like, turned off security programs, fixed an error with KB3022345 (but it seems to have come back). I have also tried the fixit and followed some of the steps like making sure there is not removable media present etc. I would have done a System restore but I don't think I have a restore point that goes back far enough.

There is no error code that I am aware of, Windows update goes through the install fine and says the system needs to restart. Before it gets to the desktop it says that it is configuring the computer for about half an hour and then it changes to failure to install, reverting changes.

I have removed the .cab files for the attached .zip as they made the file to large for the attached file size.

Please help!

 

[NoelDP]

Here's the errors from the SFC scan...

	Line 5383: 2015-09-03 18:50:05, Info                  CSI    00000347 [SR] Repairing 2 components
	Line 5384: 2015-09-03 18:50:05, Info                  CSI    00000348 [SR] Beginning Verify and Repair transaction
	Line 5387: 2015-09-03 18:50:05, Info                  CSI    0000034a [SR] Cannot repair member file [l:22{11}]"xmllite.dll" of Microsoft-Windows-ServicingStack, Version = 6.1.7601.18766, 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 5390: 2015-09-03 18:50:05, Info                  CSI    0000034c [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 5393: 2015-09-03 18:50:05, Info                  CSI    0000034e [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

The last two aren't really errors - they are the result of having installed KB3022345 or KB 3068708 and can be ignored.
I'll post a fix protocol for the other error when I can get to it.

 

[IronBat]

Thanks

Here's the errors from the SFC scan...
The last two aren't really errors - they are the result of having installed KB3022345 or KB 3068708 and can be ignored.
I'll post a fix protocol for the other error when I can get to it.

Thanks that would be great, I have been trying to fix this for months.

 

[NoelDP]

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

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

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

 

[IronBat]

I have done as you said but when I did the copy command it said 0 files copied. Also I checked the zip file I downloaded and it doesn't have any files in it.

I have included the log file anyway.

 

[NoelDP]

Ooops! - seems I forgot to insert the necessary file!.
Try it again now.

Sorry about that!

 

[IronBat]

No problem, it happens.

Applied the fix and attached the log file.

 

[NoelDP]

Great - SFC is now clear of significant problems - the others are MS's fault
Now please try CheckSUR again - does it work now?

 

[IronBat]

Great - SFC is now clear of significant problems - the others are MS's fault
Now please try CheckSUR again - does it work now?

Yes success! It installed in a little over two hours [emoji1]. Can I install the other updates now?

 

[NoelDP]

PLease post the resulting CheckSUR log - that is a fairly long scan time and could indicate some hefty problems.

 

[IronBat]

Guess it wasn't as long as that, there is still an error though.

 

[NoelDP]

Close to it - 5500+ seconds

Summary:
Seconds executed: 5585
 Found 1 errors
  CSI Manifest Zero Length Total count: 1

Unavailable repair files:
	winsxs\manifests\amd64_dc2fa106d5a22e59d0829f61f98865d5_31bf3856ad364e35_6.1.7601.22981_none_51a1628a14a14a85.manifest

I'll post a fix protocol for that later - gotta go to work now.

 

[NoelDP]

Sorry - got sidetracked!

I've uploaded a file - ibtab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder ibtab in the same place.
Open this folder - there should be one folders inside it (Manifests)


Copy the content of the manifests folder (.manifest files) into this folder:

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

Now run the CheckSUR tool again (it may take a while)

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

 

[IronBat]

Sorry - got sidetracked!

I've uploaded a file - ibtab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder ibtab in the same place.
Open this folder - there should be one folders inside it (Manifests)

The zip is empty.

 

[NoelDP]

Sorry about that - try it again now.

 

[IronBat]

Okay

Took over six hours this time but I think it's fixed.

 

[NoelDP]

Summary:
Seconds executed: 23945
Found 1 errors
Fixed 1 errors
CSI Manifest Zero Length Total count: 1
Fixed: CSI Manifest Zero Length. Total count: 1

I think that's some kind of record time!
At least it got there in the end.
I have no idea why it should have taken that long

Does Windows Update work now?
DO a Check for Updates - it may take a while - and attempt to install only the oldest update.
If it goes in OK, try the rest.
If not, post the C:\Windows\windowsupdate.log file.

 

[IronBat]

Great success! All the pending updates installed successfully.[emoji2] Many thanks for all the help, not being able to fix it was really bugging me. Might get an extra year or so out of it now.[emoji3]

 

[NoelDP]

Great! I like it when a plan come together

Good lcuk.