I am trying to install DNS on a domain controller and it keeps failing with the error above. I tried running SFC, and it didn't find any errors. I also ran DISM to restore the health, but it said it was successful. So neither one of those apps worked. I would appreciate any help on this. AD installed fine.
Getting Error: 0x80073701 on a Windows Server 2016 box while trying to install the feature DNS
- Thread starter toeder
- Start date
Windows Update Bot
I am a bot. Beep.
- Feb 20, 2012
- 619
Hi @toeder,
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
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
Hello and welcome,
Follow the instructions below please.
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
Step 2:
Remove Update Manually
Follow the instructions below please.
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
- Download
SFCFix and move the executable to your desktop.
- Download the file SFCFix.zip and save it on your desktop.
- Save any work you have open, and close all programs.
- 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.
- Open the file, then copy and paste its content in your next reply.
Step 2:
Remove Update Manually
- Right-Click the Start button and click Command Prompt (Admin) on the list.
- When command prompt opens, copy and paste the following command into it, then press enter.
wusa /uninstall /KB:4541329
- Let me know if it says it was successful or if there are any errors.
FRST Registry Search
- Click the Start button and in the search box, type CMD
- When you see cmd.exe on the list, right-click on it and select Run as administrator.
- When command prompt opens, copy and paste the following command into it, press enter afterwards.
Code:REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
Note: This loads your components hive which is what we want. Please keep the command prompt window open while you perform the remaining steps. You can minimize it if you wish but keep it open. - Download the Farbar Recovery Scan Tool and save it to your Desktop:
64-bit: Downloading Farbar Recovery Scan Tool
Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST. - Right-click on the file FRST64.exe and choose Run as administrator.
- Copy and paste KB4541329 into the Search box and click the Search Registry button.
- When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
- You may close any remaining open windows now.
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST64.exe and select "Run as administrator".
- Press the Fix button.
- The tool will now process fixlist.txt.
- 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.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Attach the logfile Fixlog.txt to your next reply.
Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
This fixed the issue of install, however when I go to setup the zone and even try to replicate over from the main server it fails. I did check the config of the main server and made sure that this new box could get the data. I will have to dig into this deeper later. Right now, I have a bigger fish to fry like an activation code for a production server on Eval mode and expires in 1 day. I have the key, but it's not taking it and says I need to use the automated call system to validate it. The problem is, the box with the 6 or 7 blocks is not showing up. I luckily know how to use PowerShell pretty well, but the basic steps to remove the old key and force the new one aren't working. I do have a case with MS, but they are so damn slow to respond back it's not even funny.
Tadd
Tadd
Not sure if this information helps:
Windows Server 2016 R2 Virtual Server not Activating
Windows Server 2016 R2 Virtual Server not Activating
They are only quick on providing changes/features no one wants.
Last edited:
Has Sysnative Forums helped you? Please consider donating to help us support the site!