Solved Errors 0x800f0831 when installing KB5016629

st1led · Sep 4, 2022

Cromax said:
you tried in place upgrade and not clean install.. its wiping everything from scratch from ssd/hdd and start over just from latest build

Ah I see. I'd keep formatting as a very last resort due to all the work needed for re-installing apps, settings, etc. I can still probably hang on a little more with just one faulty KB update.

I'm seeing other people around with similar issues, which seems to leave a margin for this not really being peculiar to my installation -- and hene only fixable with a clean install. Perhaps it's (only?) fixable from MS side with some update re-issue or something.

glasskuter · Sep 4, 2022

st1led said:
there may be no other way than to wait for Microsoft to fix it

I don't think they will since it's not happening to everyone and the situation really came to light in June. MS hasn't fixed it yet. There's always been people having update failures, but that's when more and more folks began to have the issue. The kicker is once one cumulative fails, every cumulative afterwards will also fail. I'm running the release version on fully supported hardware and my first failure was in June, again in July. Another kicker is what one does to get an update to apply doesn't work for the next person. I worked on it for days trying all sorts of fixes but nothing worked.. (SFC ,DISM, Troubleshooter, reset WU, .net fixes, etc, etc, etc.)

What fixed mine was rather than do a repair install I restored from a backup, disabled Malwarebytes as well as stop its processes in task manager, then apply the update. I think the same principal might apply using any third party AV. When the August cumulative was released I did the same thing and it also applied. I now have a reminder set to warn me when there's an update Tuesday.

I have a theory and it's probably out in left field. I believe that once a cumulative fails some sort of bit gets set that makes it and all after it continue to fail. Whatever is happening, I don't think MS is looking for the problem very hard.

st1led · Sep 5, 2022

glasskuter said:
I don't think they will since it's not happening to everyone and the situation really came to light in June. MS hasn't fixed it yet. There's always been people having update failures, but that's when more and more folks began to have the issue. The kicker is once one cumulative fails, every cumulative afterwards will also fail. I'm running the release version on fully supported hardware and my first failure was in June, again in July. Another kicker is what one does to get an update to apply doesn't work for the next person. I worked on it for days trying all sorts of fixes but nothing worked.. (SFC ,DISM, Troubleshooter, reset WU, .net fixes, etc, etc, etc.)

What fixed mine was rather than do a repair install I restored from a backup, disabled Malwarebytes as well as stop its processes in task manager, then apply the update. I think the same principal might apply using any third party AV. When the August cumulative was released I did the same thing and it also applied. I now have a reminder set to warn me when there's an update Tuesday.

I have a theory and it's probably out in left field. I believe that once a cumulative fails some sort of bit gets set that makes it and all after it continue to fail. Whatever is happening, I don't think MS is looking for the problem very hard.

Thanks for the overview. If this ends up blocking all future updates then it becomes a deal breaker and will force me into a clean install.

I can't do a repair install from a backup point because I just can't find a restore point before this issue happened (a week or so ago), but rather just from the recent days. Not sure how older restore points have been deleted. Just for me to understand it, you managed to fix this by doing a system restore to a previous backup, and you have to do this every time a new cumulative update gets released? That's... annoying.

I also don't use any external anti-virus like Malwarebytes, just Windows Defender.

glasskuter · Sep 5, 2022

st1led said:
you managed to fix this by doing a system restore to a previous backup,

No, I never rely on system restore. It's too undependable. In fact I have it turned off. I make full system backups. I restored one of my backups.Having backups is the best thing you can do for saving your bacon when something goes wrong with your system. Most of us on this forum encourage users to make regular backups. There are several good free backup programs available. Poll on Backup software

st1led said:
I can't do a repair install from a backup point

A repair install is not done from a restore point. It is by downloading a Windows 11 iso and doing an in-place upgrade. An inplace upgrade is the same as a repair install. Your files and applications are left intact. Repair Install Windows 11 with an In-place Upgrade Tutorial

st1led · Sep 5, 2022

glasskuter said:
No, I never rely on system restore. It's too undependable. I make full system backups. I restored one of my backups.Having backups is the best thing you can do for saving your bacon when something goes wrong with your system.

A repair install is not done from a restore point. It is by downloading a Windows 11 iso and doing an in-place upgrade. An inplace upgrade is the same as a repair install. Repair Install Windows 11 with an In-place Upgrade Tutorial

I see. I tried doing that too and got a (seemingly) unrelated error: "0xC1900101 - 0x30018: The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation".

I'll make another couple of tries, but may in the meantime just open a new thread to get support for that.

glasskuter · Sep 5, 2022

An error that begins with 0xC1900101 is usually a driver error. Get help with Windows upgrade and installation errors

0xC1900101 along with 0x30018 Try solutions HERE

slcidea · Sep 5, 2022

It's not a coincidence that so many people are having problem with cumulative updates. My problem began with KB5016629 and now with KB5016691. The last cumulative update that went in without a hitch was KB5015882 and then after that something or some bug in subsequent updates is causing issues. I never had to turn off Malwarebytes in the past and another machine had no issues with the last two updates with Malwarebytes on. It's definitely some anomaly that only affects certain installations. I've done everything that people have suggested without any success. My symptoms are that the update goes through 30% and then restarts with an infinite spinning circle. I've to then shut the machine off and get it to undo the changes. Sounds like others are having different symptoms but it's definitely something that MS is either not aware of or isn't addressing yet. I tried a complete in place upgrade and that cause the same problem because these updates get pulled in by Windows Update during the upgrade. I am hoping the next major release due in Fall fixes this problem that so many are having.

glasskuter · Sep 5, 2022

slcidea said:
. I never had to turn off Malwarebytes in the past

Nor have I. I am hoping that 22H2 fixes whatever it is. It may be that MS has been focusing all their efforts on it rather than deal with all the complaints in the feedback hub.

Windows update has been a contentious thing with Windows for as long as I can remember. I have come to believe that there's a lot to be said for Apple's model of proprietary hardware in their devices as well as a more limited amount of allowed software rather than trying to support hundreds of configurations from the OEMs like MS does. Add in the fact windows users are allowed to build their own systems, 'tweak' the core of Windows OSes, and MS supports windows versions for much longer than Apple does. WU has always been a royal mess.

slcidea · Sep 5, 2022

Glasskuter, I agree with you. What I find frustrating is the lack of diagnostics to pinpoint exactly what caused the failure. It would be nice if there was a debugger that identified the step in the boot process where things got stuck. The infinite spinning wheel is hardly helpful. Like you I am also hoping that 22H2 fixes the stuff that MS is not addressing in this periodic cumulative updates. I tried everything incuding stripping the machine down to basic hardware and turning off all non-MS services and nothing has worked. If you think of something novel, do post it online.

BrianInEngland · Sep 5, 2022

glasskuter said:
I don't think they will since it's not happening to everyone and the situation really came to light in June. MS hasn't fixed it yet. There's always been people having update failures, but that's when more and more folks began to have the issue. The kicker is once one cumulative fails, every cumulative afterwards will also fail. I'm running the release version on fully supported hardware and my first failure was in June, again in July. Another kicker is what one does to get an update to apply doesn't work for the next person. I worked on it for days trying all sorts of fixes but nothing worked.. (SFC ,DISM, Troubleshooter, reset WU, .net fixes, etc, etc, etc.)

What fixed mine was rather than do a repair install I restored from a backup, disabled Malwarebytes as well as stop its processes in task manager, then apply the update. I think the same principal might apply using any third party AV. When the August cumulative was released I did the same thing and it also applied. I now have a reminder set to warn me when there's an update Tuesday.

I have a theory and it's probably out in left field. I believe that once a cumulative fails some sort of bit gets set that makes it and all after it continue to fail. Whatever is happening, I don't think MS is looking for the problem very hard.

I first had the problem with the July 12 CU (22621.232). Since then it's worked fine but there were definitely problems around June/July

slcidea · Sep 5, 2022

BrianInEngland said:
I first had the problem with the July 12 CU (22621.232). Since then it's worked fine but there were definitely problems around June/July

The last one that worked successfully for me was KB5015582 which came out on 7/21 and updated it to Build 22000.832. The two that came after that build are failing with the exact same symptom. Spinning wheel after restart during update. Update never fully completes and have to reboot and get it to undo changes. Wasted days trying to troubleshoot with no clue to the root cause. Can't even do a full upgrade using ISO because the faulty updates are automatically sucked in by the update.

BrianInEngland · Sep 5, 2022

slcidea said:
The last one that worked successfully for me was KB5015582 which came out on 7/21 and updated it to Build 22000.832. The two that came after that build are failing with the exact same symptom. Spinning wheel after restart during update. Update never fully completes and have to reboot and get it to undo changes. Wasted days trying to troubleshoot with no clue to the root cause. Can't even do a full upgrade using ISO because the faulty updates are automatically sucked in by the update.

Yes I had that on July 12th, it would revert changes after the reboot. Have you got an ISO with the newest update already integrated? Do a repair install using that.

slcidea · Sep 5, 2022

BrianInEngland said:
Yes I had that on July 12th, it would revert changes after the reboot. Have you got an ISO with the newest update already integrated? Do a repair install using that.

I believe I did try it both ways using ISO from the MS site and also using UUPdump when one user suggested. Still ran into issues. I can try it again from UUPdump

slcidea · Sep 5, 2022

BrianInEngland said:
Yes I had that on July 12th, it would revert changes after the reboot. Have you got an ISO with the newest update already integrated? Do a repair install using that.

I downloaded the latest ISO from MS and tried to do an install leaving my apps & files intact and I got the same spinning wheel after the restart. I had selected download updates during the install, which leads me to believe that the KB5016629 was probably included in the update and caused the spinning wheel problem. Running out of ideas and I'm wondering what exactly is causing the failure. Don't think it's a driver issue and leaning towards some setting in the registry.

BrianInEngland · Sep 6, 2022

slcidea said:
I downloaded the latest ISO from MS and tried to do an install leaving my apps & files intact and I got the same spinning wheel after the restart. I had selected download updates during the install, which leads me to believe that the KB5016629 was probably included in the update and caused the spinning wheel problem. Running out of ideas and I'm wondering what exactly is causing the failure. Don't think it's a driver issue and leaning towards some setting in the registry.

Get a UUP Dump ISO that contains the latest update already integrated - the update is added to the ISO image before you install it, rather than an online update. That might work.

Scott · Sep 6, 2022

slcidea said:
I downloaded the latest ISO from MS

I agree with @BrianInEngland. The "latest" ISO from MS is build .318 in which case you would need to select Check for Updates during the repair install.

There's no need to Check for Updates with the latest ISO from UUP Dump. Might be worth a shot.

slcidea · Sep 6, 2022

Scott said:
I agree with @BrianInEngland. The "latest" ISO from MS is build .318 in which case you would need to select Check for Updates during the repair install.

There's no need to Check for Updates with the latest ISO from UUP Dump. Might be worth a shot.

View attachment 38499

O.K. thanks, I'll give that a shot.

Scott · Sep 6, 2022

Just in case you aren't familiar with it.

uupdump.net

Here's a nice tutorial written by @Kari that talks about downloading the insider build. Everything applies, except you'll select 21H2, and 22000.918.

UUP Dump - Download Windows Insider ISO

UUP Dump is the most practical and easy way to get ISO images of any Insider Windows 10 or Windows 11 version, as soon as Microsoft has released a new build. UUP Dump creates a download configuration file according to your choices, downloads necessary files directly from Microsoft servers, and...

www.elevenforum.com

slcidea · Sep 6, 2022

Scott said:
Just in case you aren't familiar with it.

uupdump.net

View attachment 38530

View attachment 38531

Here's a nice tutorial written by @Kari that talks about downloading the insider build. Everything applies, except you'll select 21H2, and 22000.918.

UUP Dump - Download Windows Insider ISO

UUP Dump is the most practical and easy way to get ISO images of any Insider Windows 10 or Windows 11 version, as soon as Microsoft has released a new build. UUP Dump creates a download configuration file according to your choices, downloads necessary files directly from Microsoft servers, and...

www.elevenforum.com

Thanks, I knew how to do it and did try creating the ISO with the updates integrated and got the same result with the spinning wheel after reboot. Appears that there's some issue with KB5016691 regardless whether it is installed separately or integrated in the ISO.

Cromax · Sep 6, 2022

slcidea said:
Thanks, I knew how to do it and did try creating the ISO with the updates integrated and got the same result with the spinning wheel after reboot. Appears that there's some issue with KB5016691 regardless whether it is installed separately or integrated in the ISO.

its bc you need to clean install from scratch "keep nothing" from apps and documents then it will work

Solved Errors 0x800f0831 when installing KB5016629

Member

My Computer

aka Mama Glass

My Computers

Member

My Computer

aka Mama Glass

My Computers

Member

My Computer

aka Mama Glass

My Computers

Active member

My Computer

aka Mama Glass

My Computers

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Active member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computer