Didn't work.
Windows 10 Update KB5012599 Failed to Install - Error Code: 0x800f0831
KB5012599 downloads 100%, then after a period of inactivity it pauses at Installing 20% for an extended period of time, after which it shows that it has installed 100%, but about a minute after that it generates the 0x800f0831 error with matching failure to install message.
I have spent the last 2 hours trying to fix this problem, including running the Windows Update Trouble Shooter plus a host of other suggestions, but nothing works.
Never had any issues with Windows 10 updates till now.
I don't know what to do.
Windows for home | Windows 10 | 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.
46 answers
Sort by: Newest
-
Anonymous
2022-04-21T17:45:07+00:00 -
Anonymous
2022-04-21T10:32:23+00:00 For us this update failure appears to affect Windows machines 20H2 and 21H2 which have .NET 4.8 (KB4486153 or similar) and have been upgraded from earlier versions of Windows 10 like 1809. New fresh builds of 20H2 or later don't seem to have this issue.
Installs via SCCM, Windows update or manual download and install fail. CBS.log has the key info as above.
This is happening to lots of people judging by the various posts. Reddit r/sysadmin has posts. Cleanups of Windows update folders and components is having no effect other than to delete your recent update history.
More than two of us have raised official support calls with Microsoft. They have collected log and config info and we are waiting for results of that analysis. It looks like this may require an official fix from Microsoft such as a new/updated KB.
We also have a ticket in with MS. Roughly 80% of our environment is failing to apply this update.
-
Anonymous
2022-04-21T06:35:49+00:00 For us this update failure appears to affect Windows machines 20H2 and 21H2 which have .NET 4.8 (KB4486153 or similar) and have been upgraded from earlier versions of Windows 10 like 1809. New fresh builds of 20H2 or later don't seem to have this issue.
Installs via SCCM, Windows update or manual download and install fail. CBS.log has the key info as above.
This is happening to lots of people judging by the various posts. Reddit r/sysadmin has posts. Cleanups of Windows update folders and components is having no effect other than to delete your recent update history.
More than two of us have raised official support calls with Microsoft. They have collected log and config info and we are waiting for results of that analysis. It looks like this may require an official fix from Microsoft such as a new/updated KB.
-
Anonymous
2022-04-20T10:47:46+00:00 Find all the instances of this reg key and change the current state of all of them to 0
Example:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_18_for_KB4486153~31bf3856ad364e35~amd64~~10.0.1.3106
Or run this powershell script
CD HKLM:\ Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like "*Package_*_for_KB4486153~31bf3856ad364e35~amd64~~10.0.1.3106*' } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }
-
Anonymous
2022-04-20T09:20:15+00:00 Same problem here... dism and sfc won't help... setup.exe from an iso does but this can't be the solution for 100+ computers