The 8.1 update KB2919355 failed with error codes : 80246007, 800F0922 , 8024200D . Somebody help??
Error: We couldn’t complete the updates, Undoing changes. Don’t turn off your computer.
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.
Windows for home | Previous Windows versions | Windows update
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.
998 answers
Sort by: Most helpful
-
Anonymous
2015-05-14T10:09:36+00:00 -
Anonymous
2015-05-13T09:19:33+00:00 Hello,
This issue may arise when there are issues with the Windows update components. Try the following methods to fix the issue.
Method 1: Run the Windows Update Troubleshooter
Try to run the Windows update troubleshooter, it will detect and resolve the most common issues with the Windows updates. To do so, follow the link below. You may also follow some other common solutions on the same articles.
https://support.microsoft.com/en-us/gp/windows-update-issues
Method 2: Reset Windows Update components
If the issue is with the Windows update components, this method will resolve the issue by repairing all the components associated with it. Click on the link below and follow the article on the same.
How do I reset Windows Update Components?
https://support.microsoft.com/en-us/kb/971058
To do so: Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
*How to back up and restore the registry in Windows*
Method 3: Clean Boot
A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows. To know more, follow the article below:
http://support.microsoft.com/kb/929135
Note: After troubleshooting, refer to this section ‘How to reset the computer to start normally after clean boot troubleshooting’.
Hope this information was helpful.
-
Anonymous
2015-05-12T17:48:34+00:00 Not sure if this is error codes but failed to install the following:
1st: KB2934520
2nd: KB3000850
3rd: KB3035583
4th: KB3035583
5th: KB3048778
6th: KB3038314
There might be more but i am not sure looking at the list hurt my eyes and might have missed some of them.
-
Anonymous
2015-05-12T05:30:04+00:00 Updates have been failing for about a week now. I have the following codes that failed:
KB3036562, 3048778, 3035583, 3000850, 3042085, 3044374,3024755, 3004394, 2989930, 3036562, 3012702, 3020338, and a bunch more. Now, do I just wait for Microsoft to fix whatever is broken or do I have to do something myself? I am not comfortable hacking into system files- I'll break something.
-
Anonymous
2015-05-12T02:55:41+00:00 still have a bunch of the logs from my bout with KB2919355-itis.
One with 0x80246013? All we are trying to do first is get the text for that code as a supplementary clue.
MS can't get DISM right (which I think makes sense in many ways as a strategy) so I can't imagine them being able to create a tool to make their unusable diagnostics more usable and it doesn't make any sense economically anyway to spend development resources on such a project. Fix the product and fix the repair tool before spending effort on making diagnostics which were not designed for self-support more useful for self-support.
I still say that, if you want to do self-support, using ProcMon to find and supplement whatever diagnostics you are given is the most effective way to puzzle out what you have been given. It would be nice if we had access to at least the support documentation but I can think of several reasons why even that it is not available.
BTW in W10 some tools we rely on such as WindowsUpdate.log are going away, so it might even be a waste of effort documenting how to make use of it, let alone try to code something that would try to make use of it. If anything it would be better to make expert systems for it. I wouldn't be surprised if MS Support already have such things but they have access to the source and support documentation which would make development of them feasible and relatively efficient.
FYI
Robert