What's new

error 0x800f0831 when trying to install print server role. Server 2016

triscint

Well-known member
Joined
Jan 9, 2017
Messages
73
When trying to install the print server role on server 2016 it fails. This was not always the case. It can install other server roles, this was tested by installing the rdp server role. Uninstalling recent updates did not fix the issue. sfc scans keep showing corruption, sfcfix did not show any corruption. I have looked through the cbs log files and show multiple errors related to permissions, and missing files.

Here is some examples:
2018-11-29 14:51:10, Info CSI 000066fc Error - Overlap: Duplicate ownership for directory \??\C:\Windows\SysWOW64\F12 in component Microsoft-Windows-IE-F12App, version 11.0.14393.2457, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}


2018-11-29 14:50:51, Info CSI 000065fd Error - Overlap: Duplicate ownership for directory \??\C:\Windows\SysWOW64\lv-LV in component Microsoft-Windows-Installer-Engine.Resources, version 10.0.14393.0, arch x86, culture [l:5]'lv-lv', nonSxS, pkt {l:8 b:31bf3856ad364e35}




2018-11-30 10:00:38, Info CSI 00002b77 [DIRSD OWNER WARNING] Directory [l:32 ml:33]'\??\C:\Windows\Offline Web Pages' is not owned but specifies SDDL in component Microsoft-Windows-IE-OfflineFavorites, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

So this might be a permissions issue.

Also in the system log, I found this error that lines up with the attempted times to install the roles.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

I have also tried installing newer windows updates but this did not fix the problem. The server is a VM so I was able to restore to a restart everytime one of my permanent possible fixes for the solution did not fix the problem.
Also, there are multiple CBS logs because of attempts of troubleshooting with more recent logs.

link to logs:
CBS.zip - Google Drive
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Hello! Apologies for the delay! Do you still need assistance?
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Please open Command Prompt as Administrator and enter the following commands pressing Enter after each:





Code:
reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5"  /ve /f

Code:
reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5\10.0"  /ve /f
Let me know if you get the message: "The operation completed successfully."
 

triscint

Well-known member
Joined
Jan 9, 2017
Messages
73
both operations completed successfully. should I try the install again?
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Excellent!

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the role just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 

triscint

Well-known member
Joined
Jan 9, 2017
Messages
73
Alright, the new problem is that the command stops at 97.4, and never completes or errors out.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
I'm sorry, could you specify the file name for me? There are a lot of logs on the drive.
 

triscint

Well-known member
Joined
Jan 9, 2017
Messages
73
I'm sorry, could you specify the file name for me? There are a lot of logs on the drive.
it should be CBS(1).log everything else was manual named to create new files to help diagnostics sorting through the files but I did not want to get rid of the old data.
 
Top