Solved Windows Update Failing Continuously

[homebrewdr]

Hi. I found the post about Windows Update problems. I'm trying to follow that format here.

Here is all the information I know to provide:

Windows 7 Home Premium 64bit
I ran the SURT.
Ran sfc/scannow
I get: Windows Resource Protection found corrupt files but was unable to fix some of them.
Windows Update Error Code: 800703EE
Compressed CBS log: Attached. This is not the latest CBS log, but it is the only one I was able to upload (under 8 mb). It is from yesterday, the 19th

I've been trying different things for a few days to no avail. Tried the MS update fixer. I've tried running sfc/scannow in safe mode with the same result. Disk cleanup, de-fragmentation, etc.
Anything else you need to help let me know.

Any help would be appreciated, as I am officially frustrated!

 

[NoelDP]

CheckSUR shows the following problems...

Unavailable repair files:
 winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18717_none_0ec82865a7c8e466.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-directxtransforms_31bf3856ad364e35_11.2.9600.17633_none_845de0afcb21d443.manifest
 winsxs\manifests\amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.1.7601.18679_none_1aea3d051245fa8a.manifest
 servicing\packages\Package_51_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_51_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat

SFC shows the following problems...

 Line 3535: 2015-02-20 22:25:42, Info                  CSI    00000333 [SR] Repairing 3 components
 Line 3536: 2015-02-20 22:25:42, Info                  CSI    00000334 [SR] Beginning Verify and Repair transaction
 Line 3541: 2015-02-20 22:25:42, Info                  CSI    00000337 [SR] Cannot verify component files for Microsoft-Windows-OLE-Automation, Version = 6.1.7601.18679, 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 3544: 2015-02-20 22:25:42, Info                  CSI    00000339 [SR] Cannot repair member file [l:20{10}]"jnwmon.dll" of Microsoft-Windows-TabletPC-JournalNoteWriterQFE, Version = 6.1.7601.18493, 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 3549: 2015-02-20 22:25:42, Info                  CSI    0000033c [SR] Cannot verify component files for Microsoft-Windows-IE-DirectXTransforms, Version = 11.2.9600.17633, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 3552: 2015-02-20 22:25:42, Info                  CSI    0000033e [SR] Cannot repair member file [l:20{10}]"jnwmon.dll" of Microsoft-Windows-TabletPC-JournalNoteWriterQFE, Version = 6.1.7601.18493, 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 3553: 2015-02-20 22:25:42, Info                  CSI    0000033f [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2971850~31bf3856ad364e35~amd64~~6.1.1.1.2971850-4_neutral_GDR"
 Line 3558: 2015-02-20 22:25:42, Info                  CSI    00000342 [SR] Recovered manifest from backup for Microsoft-Windows-OLE-Automation, Version = 6.1.7601.18679, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
 Line 3565: 2015-02-20 22:25:42, Info                  CSI    00000344 [SR] Repair complete

I'll post a fix protocol later, for the CheckSUR errors, then we'll work on the SFC problems.

 

[NoelDP]

I've uploaded a file - hbdaa.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 hbdaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And 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.

 

[homebrewdr]

I've uploaded a file - hbdaa.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 hbdaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And 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.

Hi. Thanks for your reply. I am following your instructions to the T, but I have no CheckSUR file in the location you are specifying. C:\Windows\Temp\CheckSur.. I can't get that far, because it doesn't exist on my system. What now?

 

[NoelDP]

Createteh folder and put the files in it - it should still work

 

[homebrewdr]

Createteh folder and put the files in it - it should still work

Here you go. I created the file. Attached are the CheckSur.log and CheckSur.persist

btw, thanks for helping me out

 

[NoelDP]

The log files are the same as the original ones posted - apart from the dates.
This begs the question of what is forcing the system to corrupt the same MUM file each time.
Please check that you placed the files in the correct locations and run CheckSUR again.
Please also open an Elevated Command Prompt and run the following command...

DIR C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0 
ICACLS C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0 
 
.

post the results.


Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[homebrewdr]

The log files are the same as the original ones posted - apart from the dates.
This begs the question of what is forcing the system to corrupt the same MUM file each time.
Please check that you placed the files in the correct locations and run CheckSUR again.

You had told me to place those files into: C:\Windows\Temp\CheckSur\Servicing\Packages, as well as the other location in winsxs

I created that like you said in that exact location, but are you sure I can't put it in just C:\Windows\Servicing\Packages and C:\Windows\winsxs\Manifests (without the temp part)?

I'll go ahead and run everything again and run the command prompt

 

[homebrewdr]

After rebooting my pc and double checking the locations, I noticed the files weren't in the folders, but 1 step back. Must of been a stupid mistake on my part. I corrected this, ran it again, and BAM! Success! Thank you!

For good measure, attached are the Checksur files and here was the command prompt:
Next I'll run sfc/scannow to see if anything is different with that.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DIR C:\Windows\servicing\Packages\Microsoft-Windows-Internet
Explorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0
Volume in drive C has no label.
Volume Serial Number is 5EBE-58AB

Directory of C:\Windows\servicing\Packages

02/23/2015 02:02 AM 1,505 Microsoft-Windows-InternetExplorer-Option
al-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0
1 File(s) 1,505 bytes
0 Dir(s) 40,800,759,808 bytes free

C:\Windows\system32>ICACLS C:\Windows\servicing\Packages\Microsoft-Windows-Inter
netExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Packag
e~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0 NT SERVICE\TrustedInstallerF
)

NT AUTHORITY\SYSTEMRX)

BUILTIN\AdministratorsRX)

BUILTIN\UsersRX)

Successfully processed 1 files; Failed processing 0 files

C:\Windows\system32>

 

[NoelDP]

great - there's still that mysterious file to deal with, but that should be simple enough...

Please open an Elevated Command Prompt, and run the following commands:

TAKEOWN /F C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0 /A
ICACLS C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0 /grant Administrators:(F)
DEL C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7600.16385.mum_old0 
 
.

then reboot and run CheckSUR and SFC /SCANNOW again - post the new full CBS folder.

 

[homebrewdr]

then reboot and run CheckSUR and SFC /SCANNOW again - post the new full CBS folder.

The CBS.log was too large to upload so I split the file into 2. Hopefully that is all you need. The zipped CBSpersist file is 13.5 mb, so I'd have to find an upload platform for that.

 

[NoelDP]

There's just this error in the SFC scan data...

 Line 8699: 2015-02-23 08:35:11, Info                  CSI    0000032a [SR] Repairing 1 components
 Line 8700: 2015-02-23 08:35:11, Info                  CSI    0000032b [SR] Beginning Verify and Repair transaction
 Line 8703: 2015-02-23 08:35:11, Info                  CSI    0000032d [SR] Cannot repair member file [l:20{10}]"jnwmon.dll" of Microsoft-Windows-TabletPC-JournalNoteWriterQFE, Version = 6.1.7601.18493, 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 8706: 2015-02-23 08:35:11, Info                  CSI    0000032f [SR] Cannot repair member file [l:20{10}]"jnwmon.dll" of Microsoft-Windows-TabletPC-JournalNoteWriterQFE, Version = 6.1.7601.18493, 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 8707: 2015-02-23 08:35:11, Info                  CSI    00000330 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2971850~31bf3856ad364e35~amd64~~6.1.1.1.2971850-4_neutral_GDR"
 Line 8712: 2015-02-23 08:35:11, Info                  CSI    00000332 [SR] Repair complete

I'll post a fix sometime tomorrow.

 

[NoelDP]

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



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



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

 

[homebrewdr]

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

I got this far. It says unfound for C, unfound for D, and Drive not ready for E. I double checked the extraction location was to "C:\" I tried this a couple of times and still didn't work. Any suggestions?

 

[homebrewdr]

Figured out that I had to change the name of the contents of your file to hbdab to follow your instructions. The downloaded file was hbdab, but the unzipped contents were amd____etc.

Ran sfc/scannow. Says the same thing about errors being found but some of them cant be fixed

Attached is the new CBS.log file. Thanks

 

[NoelDP]

Sorry - my fault (comes of being in a hurry!)

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

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


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

 

[homebrewdr]

No worries.

Attached is the CBS log file.

The sfc/scannow said that it found no errors in the system's integrity. This is good. Thank you so much for your help. It hasn't said that for over a year now. Does everything else in the log file look good?

 

[NoelDP]

There's still errors from damaged Package files - please run the CheckSUR tool, and post the log...

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

 

[homebrewdr]

There's still errors from damaged Package files - please run the CheckSUR tool, and post the log...

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

Attached is CheckSUR, CheckSUR persist, and the CBS log. The CheckSUR itself shows no errors

 

[NoelDP]

Interesting...

2015-02-26 05:10:25, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2015-02-26 05:10:25, Info                  CBS    Warning: Unrecognized packageExtended attribute.
2015-02-26 05:11:02, Info                  CBS    End of file unexpectedly reached [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
2015-02-26 05:11:02, Info                  CBS    Failed to get next Token [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
2015-02-26 05:11:02, Info                  CBS    Wrong XML DECL [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
2015-02-26 05:11:02, Info                  CBS    Invalid xml format [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
2015-02-26 05:11:02, Info                  CBS    Manifest parsing error at line: 1, context: 
X
B [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
2015-02-26 05:11:02, Info                  CBS    Failed to parse the manifest from the buffer. [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
2015-02-26 05:11:02, Error                 CBS    Failed to parse package manifest: [URL="file://\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\Windows\Servicing\Packages\Package_51_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum"]\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6\Windows\Servicing\Packages\Package_51_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum[/URL] [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]

I've never been sure why WU goes off into the Shadow copies to hunt for packages - so we may be able to ignore this error.

How is WIndows Update behaving now?