Like some of you, however, I was not sure if I should simply remove all 'Pending File Rename Operations'. Doing this makes it sound like I will have a bunch of obsolete files in my PC that will be forgotten forever. So I decided to go just a tad deeper into the issue.
The check
Below is the first set of files in my PendingFileRenameOperations under the registry key HKLM\SYSTEM\CurrentControlSet\Control\Session Manager:
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\vcruntime140_1.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\vcruntime140.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\streamserver.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\repoman.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\officeclicktorun.exe
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\msvcp140.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\msix.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\concrt140.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660\apiclient.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20660
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\vcruntime140_1.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\vcruntime140.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\repoman.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\msvcp140.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\msix.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\concrt140.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvpolicy.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvorchestration.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvmanifest.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvisvvirtualization.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvisvsubsystemcontroller.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvisvstreamingmanager.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvisvapi.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvintegration.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvfilesystemmetadata.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\appvcatalog.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626\apiclient.dll
\??\c:\program files\common files\microsoft shared\clicktorun\updates\16.0.15601.20626
\??\C:\Program Files\Common Files\Microsoft Shared\ClickToRun\Updates
They definitely look related to 'Click-to-Run' with a 'clicktorun' path. After doing some search...
What to do
I ended up manually stopping the 'Microsoft Office Click-to-Run Service' temporarily, delete those related files, let my PC restart a final time.
A second look after the reboot at the registry key HKLM\SYSTEM\CurrentControlSet\Control\Session Manager, the value PendingFileRenameOperations is gone. This mean that the rest of the files in the value had all been taken care of by simply restarting.
As you would have guessed by now, the installation went smoothly afterwards.
Just a reminder
for people who want to manually handling stuck operations in value PendingFileRenameOperations. Do remember that there are two kinds of 'operations'. Delete or Rename. Each of them is represented by two lines. A 'Delete' is a line with the filename plus an empty line to follow. A 'Rename' is a line with the old filename plus a line with the new filename.
When I attempt to install dSPACE products or patches, the following error message is displayed: ‘Pending Reboot Detected. A reboot is pending. To continue you must first reboot your PC.’
How can I solve the problem?
Tags
Date 2017-10-10 Topics of Interest New Installation Technology, Legacy Installation Technology Product dSPACE Installation Manager Information Type Frequently Asked Questions Information Category Installation and Licensing, Troubleshooting dSPACE Release 2023-A, 2022-B, 2022-A, 2021-B, 2021-A, 2020-B, 2020-A, 2019-B, 2019-A, 2018-B, 2018-A, 2017-B , 2017-A, 2016-B, 2016-A, 2015-B, 2015-A, 2014-B, 2014-A, 2013-B, 2013-A, Prior to 2013-A Keywords A restart is pending. Restart the computer., pending reboot, dSPACE Installer, MSI Setup, dSPACE Setup