[SOLVED] Windows Server 2016 - Unable to remove features or use DISM

[XtremeCatalyst]

Hi,

Been scratching my head on this one for a while and I have tried a heap of things. Unfortunately the KB that is being referenced in the logs is unable to be found online, maybe it was pulled from the Microsoft Update Catalog.

I am hoping someone can guide me, I am seeing the following errors when running dism commands:



Never posted here before but this forum seems to come up a lot when googling dism related issues :)

I am getting similar errors when trying to remove server features too. I have attached the CBS.log.

 

[XtremeCatalyst]

I have also run a search on the registry using FRST64, as seen in another thread. I also ran the reg load command for the components directory.

Here is the output when searching KB4525236.

 

[Maxstar]

Hi and welcome to Sysnative,

Start the

Farbar Recovery Scan Tool 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 FRST.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.

 

[XtremeCatalyst]

Thanks Maxstar! See the attached fixlog.txt.

 

[Maxstar]

Hi,

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

 

[XtremeCatalyst]

The DISM command ran successfully but the feature removal is still failing, I have attached the CBS log hoping it contains clues.

 

[Maxstar]

Hi,

Step 1. 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.

wusa /uninstall /KB:4467684

• Let me know if it says it was successful or if there are any errors.
• When you get the message: The update KB4467684 is not installed on this computer, then perform step 2.

Step 2. Follow these instructions to perform a regsearch with FRST.

• 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.

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.

KB4467684

• 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.

 

[XtremeCatalyst]

Step 1 failed to find the update

Step 2 resulted in the attached SearchReg.txt

 

[Maxstar]

Here's the next fix:

Start the

Farbar Recovery Scan Tool 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 FRST.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.

Aftwerwards try to remove the feature again and if it fails attach a new copy of the CBS logs.

 

[XtremeCatalyst]

You're a legend! Feature removed without a problem.

I have attached the Fixlog.txt, but it seems like my problem is resolved! How did you do it?

 

[Maxstar]

Hi,

Great, glad to hear the issue has been resolved. Some remnants of older updates were causing this issue.