[SOLVED] dism error 0x800f081f windows server 2019

[Prometheus_Link_333]

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

FAILS saying that it can't find the Source. I tried the 2019 Retail and a newer version of 2019 Eval.

I found that some had luck after removing .Net Framework 3.5 but this did not help.
dism /online /disable-feature /featurename:NetFX3

Let me know what else is needed.
Please & Thanks,
Prometheus

 

[Prometheus_Link_333]

I'm sorry I didn't upload the requested files. Here they are and my apologies for the delay.

Also this is the script I set up for all the computers that I need to test.

⠀⠀⠀⠀⠀(at)Echo Started: %date% %time%
SFC /SCANNOW
⠀⠀⠀⠀⠀(at)Echo Completed: %date% %time%
DISM.exe /Online /Cleanup-image /Scanhealth
⠀⠀⠀⠀⠀(at)Echo Completed: %date% %time%
DISM.exe /Online /Cleanup-Image /StartComponentCleanup
⠀⠀⠀⠀⠀(at)Echo Completed: %date% %time%
DISM.exe /Online /Cleanup-image /Restorehealth
⠀⠀⠀⠀⠀(at)Echo Completed: %date% %time%
SFC /SCANNOW
⠀⠀⠀⠀⠀(at)Echo Completed: %date% %time%
PAUSE

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[Prometheus_Link_333]

I have been watching this forum and these fixing posts for years.
Many times the info here helped me without needed to actually get the SFCFix.
This time I just could find the issue and reached out for help.

I ran it as directed but it looked like it needed Admin permissions, so I ran it a 2nd time from CMD and that time looked successful.
So, it seems that my issue was just the 1 file - C:\WINDOWS\WinSxS\wow64_microsoft-windows-directui_31bf3856ad364e35_10.0.17763.1131_none_0ef02b79f4b3ced9\Windows.UI.Xaml.dll
This is the same directory location that the ComponentsScanner listed in the report.
So, just running that program gives huge insight into these issues. I just didn't know how to interpret it.

Thank You So Much!
Prometheus

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved...

 

[Prometheus_Link_333]

Hi Maxstar! This server is acting up again in the same way it was in August.

It has the same error as last time so I'm going to try the same fix.

wow64_microsoft-windows-directui_31bf3856ad364e35_10.0.17763.1131_none_0ef02b79f4b3ced9 has 1 f! marks, expected 0