Windows Update Error Code 0xc0000005 (Build 22471)

%3CLINGO-SUB%20id%3D%22%5C%26quot%3Blingo-sub-3033280%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3EWindows%20Update%20Error%20Code%200xc0000005%20(Build%2022471)%26lt%3B%5C%2Flingo-sub%26gt%3B%3CLINGO-BODY%20id%3D%22%5C%26quot%3Blingo-body-3033280%5C%26quot%3B%22%20slang%3D%22%5C%26quot%3Ben-US%5C%26quot%3B%22%3E%3CP%3EHi%2C%20I%20am%20having%20issues%20trying%20to%20update%20from%20version%2022471%20to%20any%20version%20that%20gets%20released.%20I%20am%20in%20the%20Dev%20channel%20and%20have%20been%20successfully%20getting%20and%20installing%20all%20updates%20leading%20up%20to%20this%20one.%20I%20did%20manage%20to%20get%20to%20the%20version%20that%20was%20released%20the%20week%20after%20this%20one.%20I%20was%20having%20issues%20with%20that%20version%20so%20I%20reverted%20back%20to%2022471.%20I%20think%20that%20this%20might%20have%20caused%20the%20issue%2C%20but%20I'm%20not%20sure.%20I%20have%20had%20a%20few%20different%20error%20codes%20when%20installing%20the%20updates%2C%20but%20after%20following%20fix%20tutorials%20for%20those%20error%20codes%20I%20end%20up%20getting%20to%20the%20error%20code%200xc0000005%20and%20then%20being%20stuck.%3CBR%20%2F%3E%3CBR%20%2F%3EHowever%2C%20the%20strange%20thing%20is%2C%20if%20I%20am%20not%20watching%20the%20update%20in%20the%20settings%20app%20(the%20settings%20app%20isn't%20open%20and%20the%20update%20tries%20to%20install%20without%20me%20knowing%2C%20it%20will%20get%20to%20the%20stage%20where%20it%20is%20ready%20to%20restart%20to%20complete%20the%20install.%3CBR%20%2F%3E%3CBR%20%2F%3EOnce%20the%20update%20has%20reached%20the%203rd%20and%20final%20section%20of%20the%20restarts%20phase%20(after%20the%2033%25%20and%20up%20section%20that%20installs%2Factivates%20the%20drivers%20to%20allow%20multiple%20screens%20to%20work)%20it%20gets%20so%20far%20through%20and%20then%20restarts%20and%20undoes%20the%20changes%20and%20I%20end%20up%20back%20on%2022471.%20I%20have%20tried%20updating%20to%20the%20ISO%20version%20that%20is%20higher%20than%20the%20one%20I%20am%20on%2C%20but%20that%20fails%20before%20reaching%20restart.%20And%20I%20have%20tried%20every%20version%20that%20has%20come%20out%20since%20to%20see%20if%20it%20works.%20But%20no%20luck.%20I%20have%20used%20the%20troubleshooter%20on%20windows%20update%20and%20it%20detects%20an%20issue%20but%20doesn't%20fix%20it.%20I%20have%20used%20CHKDSK%20%26amp%3B%20sfc%20%2Fscannow%20and%20that%20haven't%20worked.%20Is%20there%20any%20way%20to%20force%20the%20update%20past%20the%20final%20stage%20of%20the%20update%20even%20if%20it%20could%20cause%20an%20issue%20that%20can%20be%20fixed%20by%20updating%20to%20the%20one%20after%20it%20or%20something%3F%20I%20really%20just%20want%20to%20get%20to%20the%20next%2Fcurrent%20version.%26lt%3B%5C%2FP%26gt%3B%26lt%3B%5C%2Flingo-body%26gt%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-SUB%3E
Occasional Contributor

Hi, I am having issues trying to update from version 22471 to any version that gets released. I am in the Dev channel and have been successfully getting and installing all updates leading up to this one. I did manage to get to the version that was released the week after this one. I was having issues with that version so I reverted back to 22471. I think that this might have caused the issue, but I'm not sure. I have had a few different error codes when installing the updates, but after following fix tutorials for those error codes I end up getting to the error code 0xc0000005 and then being stuck.

However, the strange thing is, if I am not watching the update in the settings app (the settings app isn't open and the update tries to install without me knowing, it will get to the stage where it is ready to restart to complete the install.

Once the update has reached the 3rd and final section of the restarts phase (after the 33% and up section that installs/activates the drivers to allow multiple screens to work) it gets so far through and then restarts and undoes the changes and I end up back on 22471. I have tried updating to the ISO version that is higher than the one I am on, but that fails before reaching restart. And I have tried every version that has come out since to see if it works. But no luck. I have used the troubleshooter on windows update and it detects an issue but doesn't fix it. I have used CHKDSK & sfc /scannow and that haven't worked. Is there any way to force the update past the final stage of the update even if it could cause an issue that can be fixed by updating to the one after it or something? I really just want to get to the next/current version.

0 Replies