When installing SQL Server 2008 one can run into “‘Reboot required check failed” situation.

After seeing it few times already, I think a solution is worth mentioning.

“Why don’t you just reboot?”, you say… Well, most likely it would not help you, but try it first.
If this would not help, then try the following:

  1. Start regedit.exe
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
  3. Locate PendingFileRenameOperations
  4. Remove any data associated with the value (you may want to export the value for later review)
  5. Reboot and rerun installation, check should pass.

Update. As a respond to some comments about solution above not always work you may consider the following:

  • Make sure that after you reboot entry in the registry does not reappear.
    If it does, remove it again, but do not reboot, just go ahead with installation process and click “ReRun”. Most likely you would be fine now.
  • You may also try and see that other ControlSet001, ControlSet002, etc do not suffer from the same problem (solution mentioned by Mike Hills below).
  • There was mentioning that some installations of Visual Studio 2008 could cause check to fail as well. So if nothing from above helped, uninstall Visual Studio (comes with light version of SQL Server), install SQL Server and then reinstall Visual Studio again.

Lets see why would entry reappear… This may happen if there is a driver or application which supports “recovery” mode or plain virus is around and after reboot it is trying to finish the deployment process again. In any situation try and look closer: what app file belongs to, if there are other solutions to the problem so that original process would finish properly, etc.

Update: Recently I was working on the unrelated setup automation for Visual Studio and stepped on a hidden gem which may work here as well: when running setup from command prompt, Windows Installer accepts a parameter called SkipRules. It worth mention the following “How to: Install SQL Server 2008 from the Command Prompt” first and then look at desired parameter

/SkipRules=VSShellInstalledRule RebootRequiredCheck

We can ignore first rule, since it is VS related, but second is the one you may want to try.


31 Comments

Max · Dec 13, 2008 at 01:01

I had the problem where Logitech re-installs its driver to :\WINDOWS\Temp\logishrd\LVPrcInj01.dll then puts a delete on reboot restart in the registry. This prvents SQL 2008 from installing because it give the restart error warning.

I thought the DLL was a trojan because you can’t see it in safe mode. Logitech had no warning on their site about this dll.

I had to remove the logitech from add/remove programs and that got it to work.

marco · Jan 2, 2009 at 15:54

thanks for the tip, have the same issue with logitech drivers. but only need to remove the value from the registry key from the first tip, no need to restart. it work fine for me.

Mike Stucka · Feb 3, 2009 at 21:27

Thank you so much! Like the other folks, I had Logitech problems. This was getting very annoying.

Achim Wagner · Feb 11, 2009 at 09:01

Thanks a lot, it worked perfect for me, instantly! I’m really glad that you’ve published this tip!!!
There were some pending file rename operations on ..\temporary internet files\index.dat in my registry.

Carla · Mar 1, 2009 at 09:18

Thanks – I too had the Logitech issue, and no amount of rebooting helped.  You saved me a ton of time trying to track this down.

Mike Hills · Apr 12, 2009 at 16:54

Thank you all
I had spent many fruitless hours until I saw this thread
It was logitech in my case as weel
One important point – I found three sets of  curent control sets 001 /002 etc
I had to remove the offending entry in all three before I finally passed the test

stefvince · Apr 30, 2009 at 17:55

It does not work for me…

Don’t have the PendingFileRenameOperations registry key…

Still searching for a fix!

Belkin_99 · May 25, 2009 at 14:08

Thats also did not work for me 
I dont have PendingFileRenameOperations in my registary.
My O/S vista64 Ultimate, I tried also remove Logitech, and it did not work.
Any help will be appreciated 

T Reg · May 27, 2009 at 14:58

Thanks!

Serguei Dosyukov · May 28, 2009 at 11:52

I’ve had some time to research more the problem above and comments that solution may not work in some cases.
I have put my findings into Update extension to the original post.

Leave a Reply