Server 2019 pending reboot problem

The link you provided is not working here, even with a VPN! So I can't see the content of the 'hack' instructions, but probabbly it has to due with changing registry permissions?

It seems you where able to import the registry key now! So you could try to update again.
 
Open regedit.exe as Administrator
Load Hive select "C:\Windows\System32\config\DRIVERS"
Enter Key Name "TEMP"
Go to "REGPATH\TEMP\DriverDatabase\DriverInfFiles\ntprint.inf"
Take Ownership of this key.
Grant Administrators Full Control in Permissions.

Edit "Default" remove ntprint.inf_ntprint.inf_amd64_83aa9aebf5dffc96 and ntprint.inf_x86_a87eceb9bd76580c
Edit "Active" enter the remaining key example for my system was "ntprint.inf_amd64_83aa9aebf5dffc96".

Take Ownership and also Delete the referenced package.
HKEY_LOCAL_MACHINE\TEMP\DriverDatabase\DriverPackages\ntprint.inf_amd64_83aa9aebf5dffc96
HKEY_LOCAL_MACHINE\TEMP\DriverDatabase\DriverPackages\ntprint.inf_x86_10ccc41e998ac968

========


Go to "REGPATH\TEMP\DriverDatabase\DriverInfFiles\ntprint4.inf"
Take Ownership of this key.
Grant Administrators Full Control in Permissions.
Edit "Default" remove all data
Edit "Active" remove all data

Take Ownership and also Delete the referenced package.
HKEY_LOCAL_MACHINE\TEMP\DriverDatabase\DriverPackages\ntprint.inf_amd64_83aa9aebf5dffc96

Unload the "TEMP" hive.
----------------------------------------------
I did only the rights hacks and ran the FRST64.exe
 
Hmm, you're DRIVERS hive had more disturbances and missing keys so I wonder if this will resolve the issue, in particular because it may cause other issues.
 
I made 4-5 inplace upgrade already, but it did not fix this problem. Shouldn't that do a clean install?

Update result: same, files attached.
 

Attachments

Last edited:
It is not a clean install from scrath, just a repair install which can resolve most of the issues. But in this case there are a lot of inconsistencies in relation to payload files and registry keys. I also noticed that a number of files in relation to (ntprint.inf) does not match with a known good system. And your DRIVERS hive is out of sync, so I would suggest to rebuild this server from scratch.
 
Hi,

You're welcome. In this case a rebuild from scratch is the best option, especially since the in-place-upgrade didn't resolve all the issues.
 

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

Back
Top