[SOLVED] Server 2019 Roles and Features not installing Error 0x800f0831

trumpet9

Member
Joined
Apr 24, 2025
Posts
16
Hi all,

I recently attempted to install some roles and features on a Windows Server 2019 machine and encountered the error 0x800f0831.

After reviewing possible solutions, I decided to run DISM, but unfortunately, this is also failing.

The server has the latest cumulative update installed as of March, and updates have been installing without any issues.

When I run DISM /ScanHealth, it indicates that a repair is required.

I’ve tried running DISM /RestoreHealth using both the online and ISO-based sources, but both attempts return errors, as shown below:

DISM /Online /Cleanup-Image /RestoreHealth

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:2 /LimitAccess

In both cases, I receive the following error:

Error: 0x800f081f - The source files could not be found.

I’ve attached the CBS.zip file and the ComponentsScanner.txt for further analysis.

Thanks in advance.
 

Attachments

Hi @trumpet9,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hi all,

Any assistance would be greatly appreciated. I’ve tried all the suggestions I could find, but unfortunately, I’m still having no luck. I would also appreciate any insights into what might be causing this issue. I don’t understand why Windows is unable to repair the corrupted files using the DISM tool, whether through an ISO or online.
 
Hi and welcome to Sysnative,

Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code:
wusa /uninstall /KB:5022840
  • Let me know if it says it was successful or you get the message: The update KB5022840 is not installed on this computer.
 
Hi and thanks.

I get the message - The update KB5022840 is not installed on this computer.
 
Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code:
KB5022840
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
I run the reg load using command prompt successfully but the FRST64 tool just keeps disappearing after initially running the registry backup, I don't get a chance to run the search button.
 
It looks like FRST64.exe is quarantined by your security software, are you able to whitelist FRST64.exe? The reason why it's detected as potential thread is because it's not digitally signed, but this tool is absolutely safe to use.
 
I presumed that was the case, unfortunately, I don't have access to whitelist the FRST64 tool! always a stumbling block :)
 
Unfortunately not, it looks like they have locked down the menu options and I cannot control any aspect other than to see the version installed.
 
Okay, please provide the following files, then I can run FRST here and create another fix.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.


Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Are you able to contact the security departement to whitelist FRST, this because it will save a lot of time to create a manual fix.
 
Okay, let me know the result it should be possible when you load the COMPONENTS hive manually as before.
 
Great.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool in Safe Mode again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST64.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

Afterwards reboot the server in the normal mode and try to install the roles/features and when it fails attach a new copy of the CBS logs.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top