[SOLVED] Error 0x80073701 w/Windows Update & New Roles/Features Add (Win Server 2016)

[sansnil]

Here you are.

CBS.zip - Google Drive

 

[Sysnative Windows Update]

Can you try installing the update again, with ProcMon? I need to confirm the point at which it fails.

 

[sansnil]

You bet. Should I grab the procmon log before rebooting (when it prompts me) or launch procmon again after rebooting? I think the failure point happens after the reboot so not sure if procmon will capture it.

 

[Sysnative Windows Update]

Sorry I'm confused at this point, please just install the update as you normally would (no ProcMon) but keep an eye on the screen to see where exactly it fails and let me know.

 

[sansnil]

I don't really get a specific error message. What happens is this:

1. I initiate the update in Windows Update
2. After running while I'm prompted to reboot to finish the update
3. After I select 'Restart' I see the "Windows is updating your system" message for a while then the system reboots.
4. On reboot I see another "Windows is updating your system" for a while then I can login as normal.
5. When I login I go to Windows Update I see a message "Some updates were unable to be installed" and see the update is listed as failed in this update history

 

[Sysnative Windows Update]

Please give me C:\Windows\Inf\setupapi.dev.log as well.

 

[sansnil]

Here you go.

 

[Sysnative Windows Update]

Could you temporarily remove OpenVPN while we troubleshoot?

 

[sansnil]

Sure. Disabling the services good enough or full uninstall?

 

[Sysnative Windows Update]

I would prefer a full uninstall.

 

[sansnil]

You got it. Uninstalled.

 

[Sysnative Windows Update]

Excellent. When able, reboot the Server into Clean Boot state: https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows and retry the update.

 

[sansnil]

Rebooted into Clean Boot state.

 

[Sysnative Windows Update]

Try update now.

 

[sansnil]

Same failure I'm afraid.

 

[Sysnative Windows Update]

Attach the most current CBS and setupapi.dev.log.

 

[sansnil]

Attached herein.

 

[Sysnative Windows Update]

Unbelievable, not a trace of errors in the logs. I'm sorry to ask this, but would you be able to provide a screen recording (video) of the whole update process or photos? This is very strange and I would like to get to the bottom of this.

 

[sansnil]

I can do that no problem give me a bit of time. I tried one other thing which was running procmon's bootlogging while trying the update. I also used the Windows Update Minitool to see if I'd get better results. I'm not sure my idea was very helpful though as after the update prompted for reboot the server blue screened when rebooting. It was probably procmon so I had to restart again of course but here are the logs in the remote chance there's something useful in there. I was hoping to catch the point when the update failed during reboot... I noticed the Minitool's logs showed the first error started with the Windows Update Orchestration Service in case meaninful as well. I didn't see that level of detail in the normal Win Update history.

Bootlog.zip - Google Drive

 

[Sysnative Windows Update]

This is very helpful info actually. Can you please provide the MiniTool logs as well?

And this:

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 to run 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).
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.

Thanks.