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.

No error codes are shown just failed to install and the date. Nothing has installed since 18th June.

my erro code is 8024000B please help i don't know how to fix it. http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-8024000b-while-installing-kb-2267602/c0cd97c6-2d30-44ce-8dfe-7995f69fbcfe (BING search for (8024000B OR 0x8024000B) "Windows 8.1" site:support.microsoft.com )

my erro code is 8024000B please help i don't know how to fix it. Thanks Joel

Error Code was 80246007 I don't see a solution thread posted for that one. http://support.microsoft.com/kb/916251/en-us (BING search for (80246007 OR 0x80246007) "Windows 8.1" site:support.microsoft.com )

Today, quite unexpectedly, I finally successfully installed KB2919355 , almost three months after it first failed in April! I now suspect the main culprit was the Cisco VPN Client software which we use to connect to our cloud servers (and which I have now discovered is not actually formally supported for Windows 8.0 or 8.1). As you may recall I was travelling for a prolonged period in April and May and was thus disinclined to try removing this software while away from the office. Even now I am back at home I would not have done so if the VPN itself had not started malfunctioning in the last week. After checking various things, it was suggested to me that I should try uninstalling and re-installing the VPN. In parallel I had also seen another more minor update fail and seen a suggested workaround to attempt the update in a clean boot state. So after uninstalling the VPN software, I also arranged to make a clean boot (disabled all the non-MS services and all the start-up items). In addition, I removed the SD card which I use to supplement the meagre 128GB SSD on the Surface Pro . I then re-tried the minor update, but this still failed. I very nearly gave up at this stage, but something made me decide to try the KB2919355 update one last time, just in case these preparations would make any difference. The download and install proceeded as before as far as the first re-start, after which it started configuring windows updates from 0-30%. Every previous time the 'circling dots' progress indicator would move to the left of the screen immediately before the second reboot and the continuation of configuring windows updates from 30-100%, and then the frustrating 'failed to configure windows updates, undoing changes'. This time the 'circling dots' stayed in the centre until the screen faded for the second reboot , and then it proceeded from 30-100% ... stayed at 100% for a nail-biting 30s ... and then succeeded . I was absolutely stunned! And sure enough the Windows Store icon materialised on the taskbar together with the various other changes promised. So quite unexpectedly the KB2919355 issue is finally resolved for me. This is just as well because by now I had established from multiple calls with MS technical support and a separate call with Surface support that my only option to fix the OS was going to be a restore back to Windows 8.0, re-do the upgrade to 8.1 and all the updates and hope that it would work in a clean build. Frankly I had no interest in spending two days rebuilding the machine back to its current state. My next step was going to be to try to arrange a trade in for a higher spec. Surface Pro 3 (which would at least have made the effort worthwhile), whereas it seems that this will no longer be necessary. However, this was not the end of the story. Re-enabling the non-MS services, start-up items and memory card was fine; but when I came to re-install it, the Cisco VPN Client would not re-install at all! It was the subsequent troubleshooting from here that alerted me to the fact the Cisco VPN Client is not formally supported for Windows 8.0 or 8.1 . (Because of this, we are now looking for an alternative solution, but in the short-term I really needed this to work.) To cut a long story short, it turns out that there are known issues with the Cisco VPN Client on Windows 8.0, and especially after the upgrade to 8.1. Citrix, which is responsible for the Deterministic Network Enhancer (DNE) (which you may not realise is) built into various versions of Windows, offers tools which will fix the relevant network components and then update the DNE system to work with Windows 8.1: http://www.citrix.com/go/lp/dne.html Their WinFix tool claimed to fix the reported network driver corruption and then their DNEupdate package installed without issue. And then the Cisco VPN Client would install (version 5.0.07.0440-k9 for x64), and my previous issues were all resolved. Circumstantially it is possible that that the Cisco VPN Client not being supported in Windows 8 was the root cause of all my grief with the failed KB2919355 update, but I will never know for sure. I am just hoping that my long-suffering Surface Pro is now in a stable and no longer corrupt state so that I can get on with my life! I hope that all of the details above may be of some value to other users with similar issues. Thanks to everyone here who has offered suggestions and been equally generous with sharing the details of their own solutions.

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

2014-07-08T04:51:46+00:00

No error codes are shown just failed to install and the date. Nothing has installed since 18th June.
Was this answer helpful?

0 comments No comments
Anonymous

2014-07-06T15:32:18+00:00

my erro code is 8024000B please help i don't know how to fix it.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-8024000b-while-installing-kb-2267602/c0cd97c6-2d30-44ce-8dfe-7995f69fbcfe

(BING search for

(8024000B OR 0x8024000B) "Windows 8.1" site:support.microsoft.com

)
Was this answer helpful?

0 comments No comments
Anonymous

2014-07-06T09:01:05+00:00

my erro code is 8024000B please help i don't know how to fix it.

Thanks Joel
Was this answer helpful?

0 comments No comments
Anonymous

2014-07-03T23:34:18+00:00

Error Code was 80246007 I don't see a solution thread posted for that one.

http://support.microsoft.com/kb/916251/en-us

(BING search for

(80246007 OR 0x80246007) "Windows 8.1" site:support.microsoft.com

)
Was this answer helpful?

0 comments No comments
Anonymous

2014-07-03T23:16:51+00:00

Today, quite unexpectedly, I finally successfully installed KB2919355, almost three months after it first failed in April!

I now suspect the main culprit was the Cisco VPN Client software which we use to connect to our cloud servers (and which I have now discovered is not actually formally supported for Windows 8.0 or 8.1). As you may recall I was travelling for a prolonged period in April and May and was thus disinclined to try removing this software while away from the office. Even now I am back at home I would not have done so if the VPN itself had not started malfunctioning in the last week.

After checking various things, it was suggested to me that I should try uninstalling and re-installing the VPN. In parallel I had also seen another more minor update fail and seen a suggested workaround to attempt the update in a clean boot state.

So after uninstalling the VPN software, I also arranged to make a clean boot (disabled all the non-MS services and all the start-up items). In addition, I removed the SD card which I use to supplement the meagre 128GB SSD on the Surface Pro. I then re-tried the minor update, but this still failed. I very nearly gave up at this stage, but something made me decide to try the KB2919355 update one last time, just in case these preparations would make any difference.

The download and install proceeded as before as far as the first re-start, after which it started configuring windows updates from 0-30%. Every previous time the 'circling dots' progress indicator would move to the left of the screen immediately before the second rebootand the continuation of configuring windows updates from 30-100%, and then the frustrating 'failed to configure windows updates, undoing changes'. This time the 'circling dots' stayed in the centre until the screen faded for the second reboot, and then it proceeded from 30-100% ... stayed at 100% for a nail-biting 30s ... and then succeeded. I was absolutely stunned! And sure enough the Windows Storeicon materialised on the taskbar together with the various other changes promised.

So quite unexpectedly the KB2919355 issue is finally resolved for me. This is just as well because by now I had established from multiple calls with MS technical support and a separate call with Surface support that my only option to fix the OS was going to be a restore back to Windows 8.0, re-do the upgrade to 8.1 and all the updates and hope that it would work in a clean build. Frankly I had no interest in spending two days rebuilding the machine back to its current state. My next step was going to be to try to arrange a trade in for a higher spec. Surface Pro 3 (which would at least have made the effort worthwhile), whereas it seems that this will no longer be necessary.

However, this was not the end of the story. Re-enabling the non-MS services, start-up items and memory card was fine; but when I came to re-install it, the Cisco VPN Client would not re-install at all! It was the subsequent troubleshooting from here that alerted me to the fact the Cisco VPN Client is not formally supported for Windows 8.0 or 8.1. (Because of this, we are now looking for an alternative solution, but in the short-term I really needed this to work.)

To cut a long story short, it turns out that there are known issues with the Cisco VPN Client on Windows 8.0, and especially after the upgrade to 8.1. Citrix, which is responsible for the Deterministic Network Enhancer (DNE) (which you may not realise is) built into various versions of Windows, offers tools which will fix the relevant network components and then update the DNE system to work with Windows 8.1:

http://www.citrix.com/go/lp/dne.htmlTheir WinFix tool claimed to fix the reported network driver corruption and then their DNEupdate package installed without issue. And then the Cisco VPN Clientwould install (version 5.0.07.0440-k9 for x64), and my previous issues were all resolved.

Circumstantially it is possible that that the Cisco VPN Client not being supported in Windows 8 was the root cause of all my grief with the failed KB2919355 update, but I will never know for sure. I am just hoping that my long-suffering Surface Pro is now in a stable and no longer corrupt state so that I can get on with my life!

I hope that all of the details above may be of some value to other users with similar issues.

Thanks to everyone here who has offered suggestions and been equally generous with sharing the details of their own solutions.
Was this answer helpful?

0 comments No comments