Server 2019 pending reboot problem

[nzsolt13]

On one server, the updates always only go to 30% during reboot, then after reboot poqexec does not finish the remaining task, so the server goes into "pending reboot" state. Further reboots do not help either. What could be the problem?

Thanks for help!

 

[nzsolt13]

It seems we have ntprint.inf problem. We did some dism restorehealth with Windows 2019 DVD and there was a clean 2018.11 state.
Then we made a Windows update again, the install is interrupted after reboot. In the cbs.log and setupapi.dev.log there is an ntprint.inif error:
[HRESULT = 0x800700b7 - ERROR_ALREADY_EXISTS]
We have attached the newest log files.

What can be the solution?
Thanks!!

 

[nzsolt13]

Hi, we can donate more (again) if somebody have solution or suggestion for us.

 

[Maxstar]

Hi and welcome to Sysnative,

Please do the following to perform a FileScan for ntprint.inf.

Download

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.

• 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.

 

[nzsolt13]

Hi, thanks for reply!
I have attached the file.

 

[Maxstar]

Please run the following commands in an elevated prompt to check the hash values and copy and paste the result in your next post.

certutil -hashfile C:\WINDOWS\WinSxS\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17763.4492_none_32a8c0071b63dfd7\ntprint.inf SHA256
certutil -hashfile C:\WINDOWS\System32\DriverStore\FileRepository\ntprint.inf_amd64_2121e11a60e09843\ntprint.inf SHA256

 

[nzsolt13]

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> certutil -hashfile C:\WINDOWS\WinSxS\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17763.4492_none_32a8c0071b63dfd7\ntprint.inf SHA256
SHA256 hash of C:\WINDOWS\WinSxS\amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17763.4492_none_32a8c0071b63dfd7\ntprint.inf:
c518fe421eb9c233cd776b8579df2680f7ca53634f120b2774bc5f4678519294
CertUtil: -hashfile command completed successfully.
PS C:\WINDOWS\system32> certutil -hashfile C:\WINDOWS\System32\DriverStore\FileRepository\ntprint.inf_amd64_2121e11a60e09843\ntprint.inf SHA256
SHA256 hash of C:\WINDOWS\System32\DriverStore\FileRepository\ntprint.inf_amd64_2121e11a60e09843\ntprint.inf:
c518fe421eb9c233cd776b8579df2680f7ca53634f120b2774bc5f4678519294
CertUtil: -hashfile command completed successfully.
PS C:\WINDOWS\system32>

 

[Maxstar]

Could you please provide a (zipped) copy of this folder "amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17763.4492_none_32a8c0071b63dfd7" with the ntprint.inf file to look at.

 

[nzsolt13]

There were 2 dirs: 3532 and 4492

 

[Maxstar]

Please attach also a copy of the COMPONENTS and DRIVERS hive to verify some things.

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS 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 COMPONENTS.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.

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.

 

[nzsolt13]

files upload

 

[Maxstar]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• 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.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.

SFC /Scannow

 

[nzsolt13]

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.


There is a system repair pending which requires reboot to complete. Restart
Windows and run sfc again.

 

[Maxstar]

The attached CBS log is from after the restart or not?

 

[nzsolt13]

I did not restart, i just follow your suggestion.
I made a restart about 1 hour ago, because COMPONENTS file was locked.

 

[Maxstar]

Okay, please restart the server and run SFC /Snannow again and post the result. If it fails attach a new copy of the CBS logs.

 

[nzsolt13]

Same after reboot. (after reboot it counts 30%, then restart)
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.


There is a system repair pending which requires reboot to complete. Restart
Windows and run sfc again.

 

[Maxstar]

Please run the steps in post#4 again to perform the File Scan for a new result.

 

[nzsolt13]

log attached

 

[Maxstar]

Hi,

Please open an elevated command prompt, run the following command and post the result.

DISM /image:C:\ /cleanup-image /revertpendingactions