Device stating pending reboot after rebooting couple of times

Maulik Busa 20 Reputation points
2024-04-16T13:35:31.0533333+00:00

Hi everyone, we have multiple device in our org that are indicating laptop's are pending for a reboot where there is no updates that waiting for reboot in settings.. i tried to pull reboot state through PowerShell using command Test-PendingReboot -detailed.. We are using third party tool name Automox which patches all devices on weekly bases and indicates if devices are up to date or not.. it pulls this data from registry keys and from last couple of months im seeing this issue on many devices. its indicating that device is not compliant because reboot is pending.. so far ive tried is to reset windows update services but no luck so far.. any advice will be highly appreciated.

ComponentBasedServicing : False

PendingComputerRenameDomainJoin : False

PendingFileRenameOperations : True

PendingFileRenameOperationsValue : {??\C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\New\PrintConfig.dll,

??\C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\PrintConfig.dll,

??\C:\WINDOWS\system32\spool\DRIVERS\x64\3\New\PrintConfig.dll,

??\C:\WINDOWS\system32\spool\DRIVERS\x64\3\PrintConfig.dll...}

SystemCenterConfigManager :

WindowsUpdateAutoUpdate : False

IsRebootPending : True

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,758 questions
{count} votes

Accepted answer
  1. Hania Lian 8,106 Reputation points Microsoft Vendor
    2024-04-18T03:32:49.1933333+00:00

    Hello,

    It seems like the reboot status on the client devices is getting stuck due to some pending file rename operations. These could be caused by some failed/corrupted updates or some other problems with the system files.

    Your PowerShell output suggests that these file rename operations are related to PrintConfig.dll located in your printer drivers folders.

    Here’s what you could try:

    Restart the Print Spooler service: Open Services.msc, find the “Print Spooler” service, right click, select ‘Restart’.

    Update Printer Drivers: This issue may be related to outdated or corrupted printer drivers. Try updating your printer drivers to the latest version.

    Rename the Spooler files manually: You could manually rename these problematic files using Command Prompt with Administrator rights:

    Open Command Prompt as administrator.

    Go to the spooler driver folders using the cd command, i.e., cd C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\

    Rename the problematic files using ren command, i.e., ren PrintConfig.dll PrintConfigOLD.dll

    Do this for other folder as well.

    Registry Clean-up: Try cleaning up the Registry Keys related to PendingFileRenameOperations. Always back up your registry before doing this.

    Open the Registry Editor (regedit.exe).

    Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

    You’ll see a Multi-String Value in the right pane titled PendingFileRenameOperations. Edit this key and remove all entries under it. Reboot.

    Best Regards,

    Hania Lian

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Maulik Busa 20 Reputation points
    2024-04-29T12:56:02.7733333+00:00

    Hi Hania, sorry for the delayed reply but it seems to be resolved by updating services. we can close this thread now.

    Best Regards,

    Maulik Busa

    0 comments No comments