N-central Troubleshooting
Reboot Required service fails under File Rename Pending
Last Modified
Thu Apr 04 19:51 GMT 2019
Description
This article addresses the issue where the Reboot Required service fails under File Rename Pending on a device even after reboot.
Environment
- N-able N-central
Solution
- The service is pulling the data from the PendingFileRenameOperations registry found under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
- If that registry key has a value on it, the service will fail and report that a reboot is required. Example values present are:
??\C:\Windows\system32\spool\V4Dirs\2EA2C703-384D-42B4-BBD7-5702F0B52CA9\d298d2f0.BUD\
??\C:\Windows\system32\spool\V4Dirs\2EA2C703-384D-42B4-BBD7-5702F0B52CA9\d298d2f0.gpd\
??\C:\Windows\system32\spool\V4Dirs\2EA2C703-384D-42B4-BBD7-5702F0B52CA9\
??\C:\Windows\system32\spool\V4Dirs\FE9921E3-09E4-4E18-9E51-7DE5CAC31D7F\9a072afe.BUD\
??\C:\Windows\system32\spool\V4Dirs\FE9921E3-09E4-4E18-9E51-7DE5CAC31D7F\9a072afe.gpd\
??\C:\Windows\system32\spool\V4Dirs\FE9921E3-09E4-4E18-9E51-7DE5CAC31D7F\
??\C:\Windows\system32\spool\V4Dirs\305E8698-C6E4-4B70-993D-8FA38C9BDF2C\6edc5785.BUD\
??\C:\Windows\system32\spool\V4Dirs\305E8698-C6E4-4B70-993D-8FA38C9BDF2C\6edc5785.gpd\
??\C:\Windows\system32\spool\V4Dirs\305E8698-C6E4-4B70-993D-8FA38C9BDF2C\
??\C:\Windows\system32\spool\V4Dirs\43353384-7C28-4071-B896-CBD29B5A9B5D\5d21f260.BUD\
??\C:\Windows\system32\spool\V4Dirs\43353384-7C28-4071-B896-CBD29B5A9B5D\5d21f260.gpd\
??\C:\Windows\system32\spool\V4Dirs\43353384-7C28-4071-B896-CBD29B5A9B5D\OKV4CL00.ser
- The first step is to reboot the device.
- If you have rebooted the device but the registry value is not clearing up, its not an issue with the monitoring because we are just pulling this data from the registry.
- The next step would be to perform a manual cleanup of the registry values or contact Microsoft if the registry values are not clearing even after you have performed a reboot.
- You are looking to delete the contents of the property PendingFileRenameOperations found under the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager