none
KB3000483 Fails to Install with error: 0x800F0831 RRS feed

  • Question

  • Hi,

    I'm managing a Citrix farm with eight servers running Server 2012 R2 and do windows updates via WSUS once a month after patch Tuesday. One of our servers will not install the KB3000483 update and keeps failing with error 0x800F0831. All the other Citrix servers have the update and are working fine and are all identically built and updated together.

    I've tried the following things:

    Regenerated the SoftwareDistribution and Catroot2 folders (stop WSUS services, rename folders and reboot)

    Repaired the SXS and image directory using SFC /scannow and DISM restore health from Server2012 media source (found errors and repaired them).

    Download and install the package manually with logging (fails and shows above error)

    None of which have worked so just wondering if anyone had any ideas please?

    Thanks,

    James

    Monday, October 3, 2016 10:00 AM

All replies

  • Hi,

    Thanks for your post.

    Please follow the below suggested methods and see if it helps to resolve the issue with the failed updates and then try again to check.

    Method 1:

    A. Check whether the Windows date and Time set to Automatic and synced.

    B. Disconnect all the peripheral devices except for the mouse and keyboard.

    C. Follow these steps to run the Windows inbuilt troubleshooter:

    • Write Troubleshooting in the search box and hit enter.
    • Click on Troubleshooting tab.
    • Click on view all option on the upper left corner.
    • Select the Windows Update option from the list.
    • Click Next to run the Troubleshooter.

    Method 2:

    This issue might also occur due to corruption in Windows Update component files. I suggest you to reset Windows Update component. Kindly follow the below given steps.

    1. Press Windows key + X, select Command prompt (Admin) to bring up elevated Command prompt.

    2. Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.

    • net stop bits
    • net stop wuauserv
    • net stop appidsvc
    • net stop cryptsvc

    3. Rename the software distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.

    • Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak

    • Ren %systemroot%\system32\catroot2 catroot2.bak

    4. Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.

    • net start bits

    • net start wuauserv

    • net start appidsvc

    • net start cryptsvc 

    5. Restart your server and check if it works this time when you try to update.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, October 3, 2016 12:09 PM
    Moderator
  • Hi Alvin,

    Many thanks for your response, unfortunately I have already tried all of the above to no avail, do you have any other ideas please?

    Thanks,

    James

    Monday, October 3, 2016 12:30 PM
  • Hi,

    Would you please paste the detailed description of error 0x800F0831 in our forum so that we could do further analysis?

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, October 5, 2016 2:25 AM
    Moderator
  • Hi,

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, October 12, 2016 8:59 AM
    Moderator
  • Hi .. just wondering if there has been any resolution for this. 
    I'm having the same exact problem with this very update.  (All others go through fine) 
    I have ran the sfc /scannow (No errors)
    also dism /online /cleanup-image /restorehealth (got an error there) 

    https://dl.dropboxusercontent.com/u/255611/Technet/DISMResult.png

    and here's a link to the dism.log: 
    https://dl.dropboxusercontent.com/u/255611/Technet/dism.zip

    As far as I can tell, all other updates are installing ok, except for that one (KB3000483)
    I have also tried renaming SoftwareDistribution, and Catroot2. No success. 
    I have also tried uninstalling the whole set of updates that were installed within that batch,and then reinstalled KB3000483. Failed again. 
    Any assistance would be greatly appreciated!! 

    • Edited by Babylon78 Friday, November 18, 2016 12:23 AM
    Friday, November 18, 2016 12:21 AM
  • Hello,

    I am having the exact same problem. No matter what I do KB3000483 Fails to Install with error: 0x800F0831. This only occurs on some machines, but not all machines. It is consistently occurring on newly provisioned machines via MDT. This happens if I use WSUS or choose Microsoft servers.

    Regards,

    DLofstedt

    Tuesday, January 17, 2017 8:50 PM
  • I too have this same 0x800F0831 error and cannot find a fix, however mine is with 5 different updates.

    KB3182203
    KB3175024
    KB3179574
    KB3174644
    KB3192392

    Others install fine, nothing works, I've tried everything on this page.

    Chris

    • Proposed as answer by snefkeify Thursday, April 6, 2017 3:05 PM
    • Unproposed as answer by snefkeify Thursday, April 6, 2017 3:05 PM
    • Proposed as answer by INTanGIBle656 Monday, June 12, 2017 10:07 PM
    • Unproposed as answer by INTanGIBle656 Monday, June 12, 2017 10:07 PM
    Monday, February 20, 2017 1:26 AM
  • Me too with KB3000483 and KB3000850, with and without WSUS.

    Sven

    Thursday, April 6, 2017 3:07 PM
  • I seem to be having this problem as well, different Windows Updates (one for the April Roll up, the other an October Security Update) on two different Windows Server 2012 R2 machines. 

    Unfortunately I don't have the luxury of being able to reboot these servers at will, and didn't find this thread until after my maintenance window had expired, but I get the impression that the directions to fix this don't work anyway.  Anyone have a real good explanation as to why these fail?  I deployed upwards of 20-30 updates at once and get the same error on two different machines for different updates.  Manually downloading and installing manually led to the same results.  I now have to report back to corp. security as to why these two updates didn't get applied (we're PCI Compliant).

    I don't think "dunno" is an acceptable answer. 

    After digging around a bit more, in the C:\Windows\Logs\CBS\CBS.log I found some entries that say the updates are actually installed.

    Server1:

    2017-04-19 04:00:21, Info                  CBS    Appl: Package: Package_25_for_KB4015550~31bf3856ad364e35~amd64~~6.3.1.4, Update: 4015550-27_neutral_GDR, Applicable: Applicable, Dis"margin:0in 0in 0.0001pt;font-size:15px;font-family:Calibri, sans-serif;color:#000000;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;orphans:auto;text-align:start;text-indent:0px;text-transform:none;white-space:normal;widows:auto;word-spacing:0px;-webkit-text-stroke-width:0px;">2017-04-19 04:00:21, Info                  CBS    External EvaluateApplicability, package: Package_25_for_KB4015550~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 04:00:21, Info                  CBS    External EvaluateApplicability, package: Package_for_KB4015550_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 04:00:21, Info                  CBS    External EvaluateApplicability, package: Package_for_KB4015550_RTM~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 04:00:21, Info                  CBS    External EvaluateApplicability, package: Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.18654.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 04:00:21, Info                  CBS    Session: 30587106_4265151842 initialized by client WindowsUpdateAgent.

    Server2:

    2017-04-19 00:06:48, Info                  CBS    Appl: Package: Package_24_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4, Update: 3192392-25_neutral_GDR, Applicable: Applicable, Dis"margin:0in 0in 0.0001pt;font-size:15px;font-family:Calibri, sans-serif;color:#000000;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;orphans:auto;text-align:start;text-indent:0px;text-transform:none;white-space:normal;widows:auto;word-spacing:0px;-webkit-text-stroke-width:0px;">2017-04-19 00:06:48, Info                  CBS    External EvaluateApplicability, package: Package_24_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 00:06:48, Info                  CBS    External EvaluateApplicability, package: Package_for_KB3192392_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 00:06:48, Info                  CBS    External EvaluateApplicability, package: Package_for_KB3192392_RTM~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 00:06:48, Info                  CBS    External EvaluateApplicability, package: Package_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed

    2017-04-19 00:06:48, Info                  CBS    Read out cached applicability from TiLight for package: Package_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4, ApplicableState: 112, CurrentState:64

    2017-04-19 00:06:48, Info                  CBS    Session: 30587082_3214288303 initialized by client LM.Detection.

    • Edited by LeodeFler Wednesday, April 19, 2017 8:06 PM Adding more info.
    Wednesday, April 19, 2017 7:26 PM
  • Hi all

    I have had this same error on a couple of servers. I tried all the normal fixes everyone recommends.

    SFC /scannow

    DISM /Online /Cleanup-Image /StartComponentCleanup

    DISM.exe /Online /Cleanup-image /Scanhealth

    dism /online /cleanup-image /restorehealth Tried manual install

    Reset WSUS services and deleted software distribution etc

    And about 1000 other things nothing seemed to work.

    The fix I used.

    Go to C:\Windows\Logs\CBS open CBS.log and do a search for KB

    You should see a KB that has failed to install or is absent or anything.

    Manually download that KB and install it and any others that are showing in the CBS.log file. Restart the computer and try and run WSUS again. This worked for me and I hope it works for you also.


    Monday, June 12, 2017 10:14 PM
  • Do you all really think it's helpful to state that you are having the same issue?
    Thursday, June 15, 2017 6:55 PM
  • I'm having the same issue
    Thursday, December 14, 2017 5:07 AM
  • I had this issue on Windows 2012 R2 Server.


    HRESULT 0x800f0831 on installing .net 4.7.2

    In order to fix this I found the following line in C:\Windows\Logs\CBS\cbs.log


    Mark store corruption flag because of package: Package_3_for_KB4040967~31bf3856ad364e35~amd64~~6.3.1.0. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]

    I was able to install .net 4.7.2 once I had downloaded KB4040967 from the MS Catalogue Site

    https://www.catalog.update.microsoft.com/Search.aspx?q=4041092

    Hope this helps you guys out.

    JTMi
    Wednesday, March 6, 2019 2:48 AM