Unable to add AD DS and AD LDS Tools with Server Manager Add Roles and Features Wizard

[LSNwc]

Hello,

I am unable to add AD DS and AD LDS Tools using the Add Roles and Features Wizard from the Server Manager on a Windows Server 2016 server (a VM in VMware). This server is the secondary in a Failover Cluster and Availability Group, the primary of which also has the same issue. At first there was some corruption found by sfc /scannow, but I fixed it with DISM using the ISO for my install media. I had hoped after the sfc and dism came back clean that the issue with the AD DS and AD LDS Tools would be fixed, but no joy. Any assistance you could provide in helping me repair whatever is blocking the install of the AD DS and AD LDS Tools would be greatly appreciated.

I have run the steps as described in the submission instructions before and after attempting the add roles and features wizard. I attached two sets of files in case something can be gleaned from them.

sfc /scannow and dism /Online /Cleanup-Image /RestoreHealth both came back clean each time:

c:\>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

c:\>dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.7426

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

 

[Windows Update Bot]

Hi @LSNwc,

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