Windows 10 Update KB5012599 Failed to Install - Error Code: 0x800f0831

Anonymous
2022-04-15T15:33:10+00:00

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.

0 comments

46 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-05-05T14:50:07+00:00

    Today, I just got a new kinston ssd to slap into my Acer aspire tc 105 to speed it up. I put a clean install of windows on it. I used a usb with windows 10 on it which i made that same day. Everything updates fine except

    .NET FRAMEWORK 3.5 AND 4.8 (KB5012157)

    Cumulitive Update for Windows 10 Version 21H2 (KB5012599)

    .NET FRAMEWORK 3.5 AND 4.8 (KB5010472)

    CUmulitive UPdate Preview for Windows 10 Version 21H2 (KB5011831)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-05-05T03:01:13+00:00

    I have the same issue, the update wont install and fails

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-05-02T13:52:14+00:00

    Thanks. Eventually I gave up on other approaches and ran the media creation tool. It took a few hours but eventually I got a clean, up to date version of Win 10 with all security updates.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-05-02T08:21:15+00:00

    Chuck Kapigian was right but it has to be done for all "duplicate events" in cbs.log

    In my case:

    cd HKLM:\

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_*_for_KB4486159~31bf3856ad364e35~amd64~~10.0.1.2752*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_for_KB4486159~31bf3856ad364e35~amd64~~10.0.1.2752*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    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 }

    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 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_*_for_KB4054590~31bf3856ad364e35~amd64~~10.0.1.2072*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_for_KB4054590~31bf3856ad364e35~amd64~~10.0.1.2072*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_*_for_KB4486129~31bf3856ad364e35~amd64~~10.0.1.3106*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_for_KB4486129~31bf3856ad364e35~amd64~~10.0.1.3106*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_*_for_KB4486135~31bf3856ad364e35~amd64~~10.0.1.2752*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Get-ChildItem 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages' | Where-Object { $_.Name -like  "*Package_for_KB4486135~31bf3856ad364e35~amd64~~10.0.1.2752*" } | foreach { Set-ItemProperty $($_.Name+"*") -Name CurrentState -Value 0 }

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-05-01T15:56:58+00:00

    I've tried the various suggestions but nothing has worked for me. And I haven't seen a peep out MS on this KB5012599 issue. Seems like it's given up on Win 10 despite its assertions to the contrary. Very disappointing, especially for those of us running relatively new machines that to our dismay, cannot run Win 11.

    Was this answer helpful?

    0 comments