Solved Repeated windows update; no error message

[fay]

I am having a problem with one certain windows update:

Security Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems

It has installed at least 30 times. Right after I install it, it pops right back up to install again. Why does it keep doing that if it installed successfully? Is it bad that it installed that many times? I don't understand.

Will you help me please?
Thank you
Fay

There are no error messages with the windows updates.
I tried to upload the CBS.log but i keep getting this error message:
Server Error


500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.



How do I get the file to you?

 

[NoelDP]

The 500 error when attempting to upload is almost always because the file you're attempting to upload is too large - strip out the CBSPersist files until the resulting file is less than 8MB, then try again.

Make sure that you follow these instructions,...

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

 

[fay]

Is this better?

 

[NoelDP]

Great!
CheckSUR found and fixed one problem.

SFC found a problem - but was unable to fix it.

 Line 68657: 2015-01-02 14:43:18, Info                  CSI    0000036d [SR] Repairing 4 components
 Line 68658: 2015-01-02 14:43:18, Info                  CSI    0000036e [SR] Beginning Verify and Repair transaction
 Line 68661: 2015-01-02 14:43:26, Info                  CSI    00000370 [SR] Cannot repair member file [l:24{12}]"korwbrkr.lex" of Microsoft-Windows-WordbreakerStemmer-Korean, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68664: 2015-01-02 14:43:26, Info                  CSI    00000372 [SR] Cannot repair member file [l:24{12}]"korwbrkr.lex" of Microsoft-Windows-WordbreakerStemmer-Korean, Version = 7.0.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 68665: 2015-01-02 14:43:26, Info                  CSI    00000373 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

We'll have to fix this manually...

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



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



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

 

[fay]

I was just wondering; the files that can't be repaired from the SFC scan, I noticed it said Korean beside it. Do I even need those?

 

[NoelDP]

Probably not - but they are part of the original installation and should still be present. It's actually a kind of spell-checker for Korean, for use by all browsers, and anything else that may come into contact with foreign documents..

 

[fay]

OK. Here is the new CBS log

 

[NoelDP]

Great - SFC is happy with that now.

2015-01-05 11:37:19, Info                  CSI    0000035f [SR] Repairing 3 components
2015-01-05 11:37:19, Info                  CSI    00000360 [SR] Beginning Verify and Repair transaction
2015-01-05 11:37:21, Info                  CSI    00000361 Repair results created:
POQ 148 starts:
 
POQ 148 ends.
2015-01-05 11:37:21, Info                  CSI    00000362 [SR] Repair complete

I'm a little confused about the 3 components it says it's repairing, since none show in the report.
Please attempt the update again - if it fails, post the C:\Windows\windowsupdate.log file

 

[fay]

I tried the update again and this is what happened.

 

[NoelDP]

The 80240016 error implies that Windows thinks there is another install going on.
See this article.
Windows Update error 80240016 - Microsoft Windows Help

 

[fay]

OK. I clicked on the link you provided. It did update successfully; however, I tried the update again just to see if it would show up again, and it did. Why does it keep showing up?

 

[NoelDP]

Hmm - please post the c:\windows\windowsupdate.log and I'll see if it tells me anything.

 

[fay]

OK here is the log

 

[NoelDP]

The update found here is this one...

2015-01-07 06:04:41:859  364 29ec Report REPORT EVENT: {E98CADBA-8673-4212-84B1-6AAAEDF5020A} 2015-01-07 06:04:36:860-0700 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ‎Thursday, ‎January ‎08, ‎2015 at 6:00 AM:  - Security Update for Microsoft XML Core Services 4.0 Service Pack 2 for x64-based Systems (KB954430)

However, you have Service Pack 1 installed already - of which this update is a part.

I think you can safely hide this, as it seems to be a false-positive error (the second one this week on this update!)

 

[fay]

Cool. Thank you so much. NoelDP