Server 2019 DISM /Online /Cleanup-Image /RestoreHealth Error: 0x800f081f

Same, Undoing Changes... This time KB4571748 and KB4571462 we listed. KB456349 never got installed, but is not listed now.

1598360455108.png
 

Attachments

Okay, time to dig deeper:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
Okay. Let's clear McAfee remnants and clear temp files. The Server will ask for a reboot after the fix. Allow it.


Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.


When this is done, I would like to focus on the network part more, based on the logs I've seen thus far something network related (feature) is causing this mess. My current suspect is the DNS Server Role.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 26-08-2020
Ran by gh0st (26-08-2020 14:53:37) Run:1
Running from C:\Temp
Loaded Profiles: gh0st
Boot Mode: Normal
==============================================

fixlist content:
*****************
2020-08-25 08:27 - 2019-12-16 12:20 - 000000000 ____D C:\ProgramData\McAfee
2020-08-25 08:27 - 2019-12-16 12:20 - 000000000 ____D C:\Program Files\Common Files\McAfee
2020-08-25 08:26 - 2019-12-16 12:19 - 000000000 ____D C:\Users\gh0st\AppData\Local\Temp\McAfeeLogs
2020-08-25 08:26 - 2019-12-16 12:19 - 000000000 ____D C:\Program Files (x86)\McAfee
EmptyTemp:
*****************

C:\ProgramData\McAfee => moved successfully
C:\Program Files\Common Files\McAfee => moved successfully
C:\Users\gh0st\AppData\Local\Temp\McAfeeLogs => moved successfully
C:\Program Files (x86)\McAfee => moved successfully

=========== EmptyTemp: ==========

BITS transfer queue => 10510336 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 82406728 B
Java, Flash, Steam htmlcache => 0 B
Windows/system/drivers => 3842240 B
Edge => 0 B
Chrome => 20260994 B
Firefox => 0 B
Opera => 0 B

Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 0 B
systemprofile32 => 0 B
LocalService => 0 B
NetworkService => 0 B
gh0st => 8343689 B
Administrator => 8382307 B

RecycleBin => 0 B
EmptyTemp: => 127.6 MB temporary data Removed.

================================


The system needed a reboot.

==== End of Fixlog 14:53:46 ====
 
Built-in account is enabled, renamed though. That's what I'm using all the time for troubleshooting.
 
I've been fighting with this for few months now, every month same issue since June... installing it manually make no difference either. Server was installed in December '19...
 
I can do that, but it's just another thing that can be removed, stripped down... I can;t find anything indicating what really is causing this issue.

I was hoping that DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:d:\install.wim:1 /LimitAccess would help, but it does not see the install.wim source
 
That would be a good step forward. The error code is significant. 0x800f0922.

It is almost certainly related to a feature that is present. At least from my experience.

As for DISM that was never an issue. An irrelevant shortcut file got corrupt and I replaced that. This issue runs much deeper than that.

The Source and LimitAccess parameters rarely help as you need a clean source (which is hard to find in most cases unless you have another Server) as System components get updated every month and the source image does not.
 

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

Back
Top