Answered by:
fatal 0x800f0831 on Win Server 2012r2

Question
-
My Windows Server 2012r2 will not patch.
I have stopped Bits and WSUS, cleaned out the c:\windows\SoftwareDistribution\Downloads folder and renamed the WindowsUpdate.log file. Nothing I'm doing seems to work and I keep getting this 0x800f0831 error with the update install attempts. What is "CBS called Error with 0x800f0831" listed in the log snip below?
I have several updates that will not load but this one is KB3077715. I even manually downloaded it and it still won't install. This is not the only one by the way. 21 updates total, will not load.
The Client is also the WSUS Server
Can anyone help here?
Thanks in Advance
Below is a part of the log file********************
2017-04-17 19:58:53:484 6780 480 Handler :: START :: Handler: CBS Install
2017-04-17 19:58:53:484 6780 480 Handler :::::::::
2017-04-17 19:58:53:485 6780 480 Handler Starting install of CBS update 4F5C726D-963F-42CF-A7F9-6DA2DA0A0C1D
2017-04-17 19:58:53:486 6780 480 Handler CBS session identity: 30586846_4077077428
2017-04-17 19:58:53:490 6780 480 Handler CBS package identity: Package_for_KB3077715~31bf3856ad364e35~amd64~~6.3.1.1
2017-04-17 19:58:53:492 6780 480 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\a843896ba139b2bb6bfa23d94e50fcdd\windows8.1-kb3077715-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\a843896ba139b2bb6bfa23d94e50fcdd\inst
2017-04-17 19:58:57:919 6780 1b3c Handler FATAL: CBS called Error with 0x800f0831,
2017-04-17 19:58:58:098 6780 480 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x800f0831
2017-04-17 19:58:58:098 560 130c AU >>## RESUMED ## AU: Installing update [UpdateId = {9720DCB0-A888-4599-A3C7-288386CC255A}]
2017-04-17 19:58:58:098 560 130c AU # WARNING: Install failed, error = 0x800F0831 / 0x800F0831
2017-04-17 19:58:58:203 6780 480 Handler :::::::::
2017-04-17 19:58:58:203 6780 480 Handler :: END :: Handler: CBS Install
- Edited by getrdone161 Tuesday, April 18, 2017 1:47 AM
Tuesday, April 18, 2017 1:23 AM
Answers
-
I ran every thing that I could find on the user forums and had to call
MS. This ended up being a update inside the December 2016 roll ups
that was failing and preventing future updates from updating.
The Technician used the CBS.log file to find out what update was failing
and the DISM tool.I can't post the link but if you search MS support for 947821 there are several KB articles there on how to use the tool. Be sure to use the /online switch
He manually removed the package that was failing in the earlier roll up
then installed the newest May 2017 roll ups to get this fixed.
This took Several days but appears to be working now- Marked as answer by getrdone161 Thursday, May 18, 2017 1:23 PM
Thursday, May 18, 2017 1:23 PM
All replies
-
Hi getrdone161,
1. Please reset windows update components on the affected machine:
https://support.microsoft.com/en-us/kb/971058
2. Please run sfc /scannow to check if there are corrupted or missing system files on the machine;
3. Please check if we can install the latest monthly rollup for Server 2012R2:
https://support.microsoft.com/en-us/help/4015550
Best Regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Tuesday, April 18, 2017 7:58 AM -
#1 does not appear to be for server 2012r2?Tuesday, April 18, 2017 12:17 PM
-
#1 does not appear to be for server 2012r2?
Download in the following link and run on Server 2012R2, we have tested it, it also works on Server 2012R2:
Best Regards,
Anne
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Thursday, April 20, 2017 2:39 AM -
Hi,
Just to check if you got any progress with the issue? Welcome to feedback.
Best Regards,
Anne
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Wednesday, April 26, 2017 7:53 AM -
It's still failing to load the same 13 updates after running the update repair tool.
Error message Code 800F0831
Tuesday, May 9, 2017 1:31 PM -
I have reset all the windows update components with no luck, same issue. what should I try next?Saturday, May 13, 2017 1:55 PM
-
I ran every thing that I could find on the user forums and had to call
MS. This ended up being a update inside the December 2016 roll ups
that was failing and preventing future updates from updating.
The Technician used the CBS.log file to find out what update was failing
and the DISM tool.I can't post the link but if you search MS support for 947821 there are several KB articles there on how to use the tool. Be sure to use the /online switch
He manually removed the package that was failing in the earlier roll up
then installed the newest May 2017 roll ups to get this fixed.
This took Several days but appears to be working now- Marked as answer by getrdone161 Thursday, May 18, 2017 1:23 PM
Thursday, May 18, 2017 1:23 PM