This error may appear anytime a Windows Update fails. To investigate possible solutions, we need to start with the specific error code. We can do this by viewing your update history. Swipe in from the right edge of the screen (or, if you're using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), and tap or click Settings . Tap or click Change PC settings , and then Update and recovery . Tap or click View your update history . View failed update error code. Please post here with your error code, so that the Community can try to help guide you appropriately.

@ showmethefacts , the joys of working with the command prompt (:-). I would paste each command and then execute it by pressing enter. That said, it is possible that pasting all four and pressing enter will have executed the four commands. You can use a Windows Explorer to display c:\windows\logs\cbs and c:\windows\logs\dism to verify that the original logs now have a .log-20150310 extension. You could use Windows Explorer to rename the files if you login to your Admin account. I just find it easier through an Admin command prompt. It is the Dism /Online /Cleanup-Image /RestoreHealth command that generates (or adds to existing) cbs/dism.log files. You only want to run the command once after you have renamed the log files so that you capture (and upload) just the latest dism run. By the way, Windows Explorer allows you to drag and drop the two log files into your https://onedrive.live.com/ window.

I don't know how I got there, but try this https://onedrive.live.com/redir?resid=F56F7AEBD0068A0B%21771 Checking System Update Readiness. (p) CBS Catalog Missing Package_1_for_KB3018943~31bf3856ad364e35~amd64~~6.3.1.0 (p) CSI Manifest Corrupt amd64_f6b912234b256abe9335cbcbcace8bbf_31bf3856ad364e35_6.3.9600.17495_none_cc72304f2bda9b9f Repair failed: Missing replacement manifest. (p) CBS Catalog Missing Package_for_KB3018943_RTM~31bf3856ad364e35~amd64~~6.3.1.0 (p) CBS Catalog Missing Package_for_KB3018943~31bf3856ad364e35~amd64~~6.3.1.0 Summary: Operation: Detect and Repair Operation result: 0x800f0906 Last Successful Step: Entire operation completes. Total Detected Corruption: 4 CBS Manifest Corruption: 3 CBS Metadata Corruption: 0 CSI Manifest Corruption: 1 CSI Metadata Corruption: 0 CSI Payload Corruption: 0 Total Repaired Corruption: 0 Good work. So, as we guessed this has something to do with Flash support. Only. What's the problem symptom?

@ Robert Aldwinckle on forums , is it possible that KB3018943 (a November 2014 IE/Flash upgrade) somehow never installed properly and that this is causing problems installing subsequent IE/Flash upgrades like KB3021953 and rollups like KB3000850? The next question is why DISM is unable to correct the corruption. @showmethefacts, if you go to your Control Panel , Programs and Features , then click on View installed updates (left navigator) and wait for the entire list to be displayed, can you search for KB3018943 in the box at the upper right? When I checked my laptop (Windows 8.1 64-bit), I cannot find any record of that fix being installed nor does it appear in c:\windows\servicing\packages.

@ Robert Aldwinckle on forums , is it possible that KB3018943 (a November 2014 IE/Flash upgrade) somehow never installed properly and that this is causing problems installing subsequent IE/Flash upgrades like KB3021953 and rollups like KB3000850? The next question is why DISM is unable to correct the corruption. I think DISM is trying to check that it has the stuff the OS would need if the current update were to be removed. I don't have that update any more either (assuming I ever did); it is that old. Please see the discussion I had with Richard to see why I think that this is probably a red herring here and not a real problem. In his case part of the thread took a detour investigating his Flash support for exactly this reason but in the end it apparently had nothing to do with his real problem. It was a few pages ago that I gave a link to it http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/update-kb3000850-fails-to-install/43125206-f39e-477f-b5b6-73a177abb589?page=4

KB3032323 Security Update for Windows 8.1 MS15-021: Vulnerabilities in Adobe font driver could allow remote code execution: March 10, 2015 https://support.microsoft.com/kb/3032323?wa=wsignin1.0

Error: We couldn’t complete the updates, Undoing changes. Don’t turn off your computer.

Anonymous

This error may appear anytime a Windows Update fails. To investigate possible solutions, we need to start with the specific error code.

We can do this by viewing your update history.

Swipe in from the right edge of the screen (or, if you're using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), and tap or click Settings.
Tap or click Change PC settings, and then Update and recovery.
Tap or click View your update history.

View failed update error code.

Please post here with your error code, so that the Community can try to help guide you appropriately.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

998 answers

Anonymous

2015-03-11T01:13:09+00:00

@showmethefacts, the joys of working with the command prompt (:-). I would paste each command and then execute it by pressing enter. That said, it is possible that pasting all four and pressing enter will have executed the four commands. You can use a Windows Explorer to display c:\windows\logs\cbs and c:\windows\logs\dism to verify that the original logs now have a .log-20150310 extension. You could use Windows Explorer to rename the files if you login to your Admin account. I just find it easier through an Admin command prompt.

It is the Dism /Online /Cleanup-Image /RestoreHealth command that generates (or adds to existing) cbs/dism.log files. You only want to run the command once after you have renamed the log files so that you capture (and upload) just the latest dism run.

By the way, Windows Explorer allows you to drag and drop the two log files into your https://onedrive.live.com/ window.
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-11T01:53:20+00:00

I don't know how I got there, but try this

https://onedrive.live.com/redir?resid=F56F7AEBD0068A0B%21771

Checking System Update Readiness.

(p) CBS Catalog Missing   Package_1_for_KB3018943~31bf3856ad364e35~amd64~~6.3.1.0

(p) CSI Manifest Corrupt   amd64_f6b912234b256abe9335cbcbcace8bbf_31bf3856ad364e35_6.3.9600.17495_none_cc72304f2bda9b9f

Repair failed: Missing replacement manifest.

(p) CBS Catalog Missing   Package_for_KB3018943_RTM~31bf3856ad364e35~amd64~~6.3.1.0

(p) CBS Catalog Missing   Package_for_KB3018943~31bf3856ad364e35~amd64~~6.3.1.0

Summary:

Operation: Detect and Repair

Operation result: 0x800f0906

Last Successful Step: Entire operation completes.

Total Detected Corruption: 4

CBS Manifest Corruption: 3

CBS Metadata Corruption: 0

CSI Manifest Corruption: 1

CSI Metadata Corruption: 0

CSI Payload Corruption: 0

Total Repaired Corruption: 0

Good work.

So, as we guessed this has something to do with Flash support. Only.

What's the problem symptom?
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-11T14:14:35+00:00

@Robert Aldwinckle on forums, is it possible that KB3018943 (a November 2014 IE/Flash upgrade) somehow never installed properly and that this is causing problems installing subsequent IE/Flash upgrades like KB3021953 and rollups like KB3000850? The next question is why DISM is unable to correct the corruption.

@showmethefacts, if you go to your Control Panel, Programs and Features, then click on View installed updates (left navigator) and wait for the entire list to be displayed, can you search for KB3018943 in the box at the upper right? When I checked my laptop (Windows 8.1 64-bit), I cannot find any record of that fix being installed nor does it appear in c:\windows\servicing\packages.
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-11T14:46:32+00:00

@Robert Aldwinckle on forums, is it possible that KB3018943 (a November 2014 IE/Flash upgrade) somehow never installed properly and that this is causing problems installing subsequent IE/Flash upgrades like KB3021953 and rollups like KB3000850? The next question is why DISM is unable to correct the corruption.

I think DISM is trying to check that it has the stuff the OS would need if the current update were to be removed. I don't have that update any more either (assuming I ever did); it is that old.

Please see the discussion I had with Richard to see why I think that this is probably a red herring here and not a real problem. In his case part of the thread took a detour investigating his Flash support for exactly this reason but in the end it apparently had nothing to do with his real problem.

It was a few pages ago that I gave a link to it

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/update-kb3000850-fails-to-install/43125206-f39e-477f-b5b6-73a177abb589?page=4
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-12T12:55:29+00:00

KB3032323

Security Update for Windows 8.1

MS15-021: Vulnerabilities in Adobe font driver could allow remote code execution: March 10, 2015

https://support.microsoft.com/kb/3032323?wa=wsignin1.0
Was this answer helpful?

0 comments No comments