How To Fix Windows Server 2016 Error 0x800f0831 – Add Feature Fails

How To Fix Windows Server 2016 Error 0x800f0831 - Add Feature Fails

If you are trying to fix Windows Server 2016 Error 0x800f0831, you have landed in the right place.

If you are a Windows Server administrator, you may come across several issues that we faced concerning installation or update. The Windows server 2016 error 0x800f0831 is one of the most commonly used errors. If you are facing one such error on your Windows server or Windows 10 installation, the tutorial here should help you get the best options in resolving it.

Windows server 2016 error 0x800f0831 – What is it?

The 0x800f0831, 0x800f0831 update, 0x800f0831 install, 0x800f0831 server 2012, 0x800f0831 Windows 10 are a few specific errors you would have come across. The error basically is concerned with the installation of your Windows server or other options.

There are several reasons it may manifest itself. The standard format that you will find the error manifesting itself would be through the error message

FATAL: CBS called Error with 0x800f0831

The failure is more likely to affect you if you have no access to Windows Update server for any reason.

The error can cause several issues on your computer. It may block any of your programs from working correctly. It may also affect the performance of your PC and make it function at a slower speed. In some extreme cases, it may restart your computer repeatedly or can cause issues like BSOD errors.

Some of the scenarios that can bring forth the error would be any unsupported or non-reliable game or app or any issues with your Skype installation. You may also experience the error when you are attempting to use the webcam.

How to Fix the Windows server 2016 error 0x800f0831?

There are several fixes you can use for resolving the Windows server 2016 error 0x800f0831. There are no specific fixes available to address the error code. You can try out any of the repairs outlined in this compilation and find which of them works for you.

Fix  1 – Reset Windows Update Components

Resetting the Windows Update Components can resolve the issue most of the times. The steps involved in resolving the matter should be easy and straightforward enough.

Follow the steps here below –

  • Launch Command Prompt. You can do so by searching for it through Windows Search and choosing it from the search results. You may also launch it through the RUN dialog box and typing in the command CMD.
  • Make sure that the Command Prompt is launched as an administrator.
  • Confirm if the UAC shows up.
  • Stop the update processes. To do this, you will need to type in the following commands and press ENTER after each of them
net stop bits

net stop wuauserv

net stop appidsvc

net stop cryptsvc
  • Next, type in the following command and press ENTER. This will delete the file qmgr*.dat
%ALLUSERSPROFILE%Application DataMicrosoftNetworkDownloaderqmgr*.dat
  • Type in the following command and press ENTER
cd /d %windir%system32
  • Type in the following commands, one by one and press ENTER after each of them.
regsvr32.exe atl.dll

regsvr32.exe urlmon.dll

regsvr32.exe mshtml.dll

regsvr32.exe shdocvw.dll

regsvr32.exe browseui.dll

regsvr32.exe jscript.dll

regsvr32.exe vbscript.dll

regsvr32.exe scrrun.dll

regsvr32.exe msxml.dll

regsvr32.exe msxml3.dll

regsvr32.exe msxml6.dll

regsvr32.exe actxprxy.dll

regsvr32.exe softpub.dll

regsvr32.exe wintrust.dll

regsvr32.exe dssenh.dll

regsvr32.exe rsaenh.dll

regsvr32.exe gpkcsp.dll

regsvr32.exe sccbase.dll

regsvr32.exe slbcsp.dll

regsvr32.exe cryptdlg.dll

regsvr32.exe oleaut32.dll

regsvr32.exe ole32.dll

regsvr32.exe shell32.dll

regsvr32.exe initpki.dll

regsvr32.exe wuapi.dll

regsvr32.exe wuaueng.dll

regsvr32.exe wuaueng1.dll

regsvr32.exe wucltui.dll

regsvr32.exe wups.dll

regsvr32.exe wups2.dll

regsvr32.exe wuweb.dll

regsvr32.exe qmgr.dll

regsvr32.exe qmgrprxy.dll

regsvr32.exe wucltux.dll

regsvr32.exe muweb.dll

regsvr32.exe wuwebv.dll
  • Next, you will need to reset WinSock. To do this, type in the following commands one by one. Once again, press ENTER after each of these commands
netsh winsock reset

netsh winhttp reset proxy
  • Finally, re-register the Windows update components. For this, type in the following commands, remembering to press ENTER after each of them.
net start bits

net start wuauserv

net start appidsvc

net start cryptsvc

That completes the complete reset of your Windows Update components. This should resolve your issue with Windows server 2016 error 0x800f0831.

Fix 2 – Disable Proxy

This is yet another option that should assist you in resolving and getting rid of the Windows server 2016 error message  0x800f0831. Here are the steps you would need to follow to execute this fix.

  • Launch RUN command. You can do so by the Windows and R key combinations. You may also search for the RUN keyword and choose it from the search results.
  • Type in the following command in the RUN dialog box and click on OK


  • Choose the options for Connections and then choose LAN Settings
  • Locate the option for Automatically Detect Settings and check it.
  • Locate the option for Proxy Server and uncheck it.

That should resolve the issue, and you should be back with a working update and installation process.

These have been used by most of the users as the most straightforward options for resolving the Update or installation errors. The best solution would be to install the missing update. Now that your Microsoft Update itself is not working – the answer may be out of the reckoning.

Before you can move to the fixes outlined in the above discussion, it may be a little practical enough to opt for a few options as in the following order.

Reboot your PC

Most of the time, rebooting your PC can solve most of the issues. Just opt for the reboot option and check if it resolves the problem. Do note that it may or may not resolve your issue permanently. If it does not address the problems permanently and you find the problem recurring after a while, you may need to opt for the complete solution as outlined in the previous two fixes.

Reboot in Safe Mode

Safe mode is one of the best options to check if your issues have anything to do with the installed applications on your computer. The safe mode launches with the minimum set of drivers and other applications and thus can help you resolve a few issues.

Here is how you can reboot in Safe Mode –

  • Launch RUN dialog box. You can follow the steps as explained above.
  • Choose the Boot tab
  • Locate the Safe Boot under boot options and check the option.
  • Click on Apply and then OK.

Restart your PC, and it should now start in Safe Mode. Several other options can be used to reboot your Windows Server 2016 in safe mode, but this should be one of the easiest ones you can opt for.

Disable Antivirus software

At times, your Antivirus solutions can play spoilsport in your normal operations. It may be a good idea to check if this is the issue in your case.

Disable your Antivirus solution for a while and check if the issue is gone. If the problem is resolved with the disabled anti-virus solution, you can check the settings of your anti-virus software so that you can resolve the issue. You may also get in touch with the antivirus vendor to ensure a proper resolution or some troubleshooting. It may also be a good idea to opt for new antivirus software if your current antivirus does not solve the issue.

Run SFC scan

SFC or System File Checker is an excellent tool that can resolve most of the tasks on your computer. The tool can help you check the system files on your system and check their integrity. In case, there are any issues with your system files, they will be rectified, and the problems would be fixed.

Here is how you can use the SFC scan feature –

  • Launch Command Prompt using any of the methods we have outlined in one of the above fixes.
  • Ensure that you have launched Command Prompt as an administrator.
  • Type in the following command and press ENTER
sfc /scannow
  • It may be advisable to run the DISM commands to ensure a better resolution.

Running the DISM commands should not be a difficult task as such. You can run it from within the Command Prompt.

You would need to enter the following commands in Command Prompt and press Enter after each of those commands –

dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /checkhealth

dism /online /cleanup-image /restorehealth

Once these commands have executed successfully, you can run the SFC command, as explained in the above steps.

A few other steps would include running your computer in a clean boot mode and running the Windows Update Trouble-shooter.

If everything else fails, it may be advisable to use the option of third-party apps and tools that help you resolve the error. There are many tools available that may be helpful enough in solving the PC errors that are most commonly faced.

In Conclusion

Those were a few good options that should help you fix the Windows Server 2016 error 0x800f0831. The most crucial aspect to be remembered in the context of the error message is that it affects the update or installation functions explicitly on your Windows server. From that perspective, any solutions that help you resolve the Windows Update errors should work with this error as well.

While this tutorial has been compiled keeping Windows server 2016 in mind, the steps and fixes outlined here should ideally work with any other standard Windows 10 version or other Windows Server editions efficiently. Since the exact reasons that cause the issue is not unique and known, you may need to go with multiple options to resolve the error. We would assume the fixes featured here work efficiently in resolving the issue for you.

More Reading:

Disclaimer: The Questions and Answers provided on are for general information purposes only. We make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose.

What's your reaction?

In Love
Not Sure

You may also like

Comments are closed.

More in:Windows