Server 2019 pending reboot problem

I had to do a revertpendingactions for working environment, but now i did an update again.
There is 2 backups: before_update and after_update.
There was no pending.xml before update, the file created after update is attached.
 

Attachments

Hi,

Now we have the same 0x800700b7 error as before, so please attach the setupapi.dev.log.
 
Let's start from the beginning with a file search for ntprint.inf.

Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.
 

Attachments

Okay, please attach a new copy of the DriverDatabase and the DRIVERS hive.

Export registry key as hive file.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into the command prompt and press enter.
Code: 
reg save "HKLM\SYSTEM\DriverDatabase" "%userprofile%\Desktop\DriverDatabase.hiv"
  • Once done, a file will appear on your desktop, called DriverPackages.hiv.
  • ZIP this file and attach it to your next reply.

Upload your DRIVERS Hive
  • Navigate to C:\Windows\System32\config and locate the DRIVERS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named DRIVERS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

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 Files button.
Code: 
ntprint.inf
  • When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also.
  • Post the logfile Search.txt as attachment in your next reply.
 
Do you have a similar server to provide a copy of the DRIVERS hive from, so I can compare some things?
 
I have an another Win2019 server az another VPS provider, what is up to date. (the win update works well)
 
Okay, could you please attach a copy of the DRIVERS from that machine?
 
Great, please do the following on the server with the ntprint.inf issue to replace the DRIVERS subkey.

Start the
577bf0efb8088-FRST.png
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.
 

Attachments

Rich (BB code): 
Registry ====> HKEY_LOCAL_MACHINE\DRIVERS\DriverDatabase\DriverInfFiles\ntprint.inf <==== Access Denied
Registry ====> ERROR: Error accessing the registry.
Unfortunately the fix failed, so I'll need to do some tests here on a VM to see what happens?
 
You must log in or register to reply here.

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

Back
Top