Not able to install SqlServer 2008 says Restart computer failed

Question

While trying to install SqlServer2008 it show Restart computer as failed. I have restarted my computer and still it shows the same error. Cant proceed further. Please advice on how to proceed to install SqlServer 2008.

 

Thanks

Ashok

 

Answer 1

You can uninstall SQL Server 2008 first.

Try to use this link for your reference.

http://msdn.microsoft.com/en-us/library/ms144259(SQL.100).aspx

Answer 2

Does symantec installed on your machine? dose the machine infected with  KAVO virus?

 

Madhu

SQL Server Blog

SQL Server 2008 Blog

 

Answer 3

Symantec Antivirus is installed in my system. But no known virus infection

 

Answer 4

Check your system's pending file rename operations registry key. It should be cleared after you reboot your system. If not, something must be wrong.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

Answer 5

I have the same issue - i've checked the pending file operations, and there are none.

Also, the Link in the Setup (http://go.microsoft.com/fwlink/?LinkId=94001) leads to a Firewall configuration page that does not explain what the rule evaluates exactly.

Answer 6

I am stuck at 'Previous release of Microsoft Visual Studio 2008' and the detail show that VS 2008 SP1 is missing, installed it and still can't proceed.

 

Any help is greatly appreciated.

Thanks

 

 

Answer 7

BMWAustin wrote:

I am stuck at 'Previous release of Microsoft Visual Studio 2008' and the detail show that VS 2008 SP1 is missing, installed it and still can't proceed.   Any help is greatly appreciated. Thanks

 

You'd want to install just the basic (i.e. db engine only).

 

http://support.microsoft.com/kb/956139

 

 

Answer 8

I will say if you are getting stuck now, the best way is to uninstall everything.

And then,

Install SQL Server 2008 first since you want SQL Server 2008.

Install VS 2008 +SP1 second.

 

Since SQL Server 2008 is not released, installing SQL Server 2008 first is the easiest thing.

Answer 9

I have the same issue, but I've also found the culprit.  After installing .NET Framework 3.5 SP1, Windows Update attempted to install a Hotfix KB953595. It is listed as installation was Successful, but it cannot be removed through Control Panel, and when I look for the installation package in \Windows\SoftwareDistribution\Downloads, there is no package for this Hotfix, so I can't figure out how to force it's uninstall.

 

There is also nothing listed as pending under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

 

so I am at a loss as to how to uninstall a Hotfix that isn't there.

 

Nor have I been able to find the hotfix & download it & re-install it.

Answer 10

Did you click "show updates" in ARP? If you install  Hotfix KB953595, it should show up in your ARP.

Answer 11

Thanks for the response Ray.  Yes it does show up, but with the Uninstall button disabled.  The uninstall button is enabled for all of the other Updates.  So, I went looking for the installation package in \Windows\SoftwareDistribution\Downloads, but there is no package for this Hotfix, which I'm sure is why the Uninstall button is disabled, so I can't figure out how to force it's uninstall.  

-Scott

Answer 12

OK, here's the resolution I came up with.  I gave up on uninstalling the Hotfix, and just uninstalled the .NET Framework 3.5 SP1 which also removed the Hotfix.  I then re-installed the .NET Framework 3.5 SP1 without the Hotfix and went on to successfully finish the SQL Server 2008 installation.

Answer 13

That's so great to hear that.

Answer 14

Hey, I've been suffering the same issue. I uninstalled .NET 3.5 SP1 and it did remove the hotfix, however when I reinstall SP1 it also automatically reinstalls the hotfix which doesn't get me anywhere. SQL 2008 fails to install unless you have SP1 installed, so this appears to be a no win situation. How did you install SP1 without the hotfix?

 

Thanks, Ed

 

Answer 15

I have been struggling with this today, too. I have a new machine with Vista Home Premium. I get through all prereqs for SQL Server 2008 except the Restart Computer has failed on it and I can't install SQL Server 2008. However. I have restarted and still get it.

 

I have uninstalled .NET 3.5 SP1, reinstalled it, installed Visual Studio 2008, but still get the Restart computer failed. I don't see how to uninstall the Hotfix as there is no option in add/remove programs.

 

Answer 16

I was able to get around this problem by running the .exe for the installer which unpacked everything into a GUID-named folder on c:\  (which is a pretty bad idea for them to do, imho, instead of %temp% or something). I had to do this because letting the installer complete normally it would delete the folder. Once the installer window came up, I forcefully terminated the installer which left the folder intact. Then I opened a command line and ran setup manually (which is in the root of this folder), using the additional arguments mentioned earlier in the thread for skipping the forcereboot check. I don't recall the exact parameters but I had to add something like "Action=Install" to the command line before it would work. Once the installer GUI came up, it allowed me to install despite it saying that it still needed a reboot.

 

By the way, this was a really unpleasant experience that wasted several hours for me - and apparently at least a few other people - for something that *really* should have just been a warning for the installer especially since there is no indication of what, specifically, is triggering the installer to believe a reboot is required.

 

Also, if the package EXE had an option to just "unpack & install manually" that would have also been helpful because it was a bit of a chore just figuring out where the setup.exe was actually coming from.

 

Regards,

 

Answer 17

can you please tell us what parameters you used that allowed you to forcefully bypass the computer reboot check. 

I've tried all other ways but nothing seems to work.

Answer 18

 

Clearing the value in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations and without restart the computer, I was able to install SQL Server 2008.  This issue really bugged me.

Answer 19

Sorry for the delay, Ed.  It must be something in the way you are doing the re-install.  I had downloaded and saved locally the .NET 3.5 SP1 package first before re-installing it, and was not forced to also install the hotfix.  Hopefully by now you've resolved the issue.  Sorry I can't be of more help.

-Scott

Answer 20

 

This worked for me.  Was an HP server and some piece of HP software was listed here.  Once I deleted it the install went through.

Answer 21

This trick worked for me too.

 

Answer 22

What is the parameter to skip the forceboot check in the command line install.

Answer 23

Updating the registry helped me.  Thanks

 

Answer 24

Removing the  PendingFileRenameOperations value, as mentioned here worked for me.

I've been bugged with this for days, and now finaly could proceed the installation.

I'm running Windows Server 2008 Standard Edition x64, with VS2008 and all/most updates (SP1 ++)...

Thanks!

Answer 25

I just cleared the Pending File Operations key and it worked.

Thanks to Everybody.

Answer 26

Searching for the string PendingFileRenameOperations and removing everything

containing this helped me to solve the problem and uninstall this SQL server. Which I never use and don't know what it is. I just wanted a simple C comiler (for noobs) and installed bloated MS Visual express something. It unistalled ok, but left me with this junk.

Answer 27

\??\D:\TEMP\logishrd\LVPrcInj01.dll
\??\D:\TEMP\logishrd\
\??\D:\TEMP\logishrd\LVPrcInj02.dll
\??\D:\TEMP\logishrd\

Above was mentioned in PendingFileRenameOperations in my system. ____ logitech software, or ____ windows update system...

didn't even have to restart sql server setup, could just re-run the tests! Thanks all that replied.

Answer 28

 
Thank you Amy, Clearing the value in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations defionetly works. You may remember we had the same issue with SQL 2005 and I think with SQL2K ....

-Ivan

---

Ivan Sanders http://linkedin.com/in/iasanders http://dimension-si.com/blog

Answer 29

I am running Vista SP1 with Visual Studio 2008 SP1, and .NET 3.5 SP1 having the same problem many have had. I like many others do not have a KEY registry entry for:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

What many seem to think (as I did) that there is a KEY value of PendingFileRenameOperations.  There is no KEY by that name.  There is however a Value Pair named "PendingFileRenameOperations" under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Navigate to the above registry location and then look in the right side pane for the value pair.  Rename it or delete the value found there.

In my case I have a Logitech CAM device that incorrectly completes its install without deleting the value pair.

After correcting the registry my install completed as expected.

Answer 30

Larry is right. Thats how i found the registry entry. I deleted the gargabe in there and was able to get through that hurdle just to run into more problems. An hour later i finally was able to install the Tool Pack ( which is all i wanted ). This is the worst installer i have seen in a long time. It took 4 hours and a ton of frustration to finally get access to the Management studio.

Answer 31

Larry's answer fixed it for me to, on Vista Business 32bit SP1.  Just deleted the values and reran the test...

Answer 32

Thank you for this solid information.  I have worked on this for some time and this worked out very well, once I deleted the value identified above and reinstalled, it worked well.

Thanks for the help.

CHS

Answer 33

One other thing I found, but didn't see posted here was the following:

http://scottonwriting.net/sowblog/posts/13456.aspx

Basically, the Express Editions don't get updated with VS SP1, and will cause the SQL install to fail.  Uninstalling the Express Editions, installing SQL, then reinstalling the express editions (now with SP1) worked for me.

Answer 34

The same issue arose when I tried to UNINSTALL SQL2008 - restart computer: failed.

I cleared my PendingFileRenameOperation keys, and the uninstall worked (Vista business)

(reason for uninstall - because Windows 7 RC won't install with SQL there!)

---

developer

Answer 35

i couldn't find the registry in an explorer window... so i used ccleaner and that works fine.

nvm. im such a noob. you guys should EXPLAIN how to get there. ...nobody... okay i will.
open a command prompt as administrator. type in regedit.exe
then go to the directory specified above.
your welcome my fellow noobs.

Answer 36

Thanks Amy!!   Your solution worked.  I simply deleted the values in the PendingFileRenameOperation option, and I got the install to finally work!  Only wasted 2 hours trying to resolve this issue :).  Glad I found this thread.

Jason
http://www.stocknod.com

Answer 37

That was the magic.  I hit my head against this for just a tools install for 2 hours.  Thanks!

Answer 38

Thanks, that helped me as well.  Unfortunately I wasn't as lucky as the others, I spent days working on it.  Freakin' ____

Answer 39

I have the same problem on my XP and VISTA computer.  Have you solved this problem?  I'd like to know how to do it too.

Thanks.

Answer 40

Clearing the value here worked for me on Vista

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

Answer 41

Here is what I did on my client machine. ( I was able to install VB Studio '08 and SQL Srvr. '08 on Windows 2003 Ent/w no issues).
But, on my XP client machine, I got the same error that the a restart failed.

I went to my registry: HKEY_LOCAL_MACHINE\SYSTEM\CONTROL\SESSION MANAGER\

Looked for the filerename issue. Checked to ensure it was not a file that can cause me problems later on, and deleted this key. Again!
Make sure it is not a file that can cause you problems. How do you know it won't cause you problems once you delete the failed registry key?
Ensur you know which file it is that the install was trying to rename and if need be rename it yourself by: right clicking on the key itself and select "Modify". I delete it mine and rerun the install, everything works well and I see no errors in my Application log; system or WPS.

All the best! Good luck!

Answer 42

I am installing SQL Server 2008 AND SQL Server 2008 R2 on a Windows 2008 server, and I am getting the above issue even after rebooting. This issue is happening with both SQL Server 2008 and SQL Server 2008 R2.  The registry fix doesnt apply because that key doesnt exist at all (There is no CONTROL node in my registry) .  I had to install Visual Studio 2008 + SP1 first because the install will fail because I am missing VS 2008 SP1. 

All of the above work arounds do not work.

- Registry Node doesnt even exist,

- This is frist time i have EVER had this problem installing SQL 2008

- Have Rebooted 5 times

Any other ideas? 

---

Rex Whitten

Answer 43

Rex,
Please check my post above (Dec 31, 2008) and verify your registry path. It took me several times to realize that I was in the wrong place.

Depending on the tools you are requesting installed you may not need VS 2008. You will need .NET 3.5 sp1.  VS 2008 sp1 install .NET 3.5 sp1.

If you could post your exact error message that would be helpful.

Larry

Answer 44

Thank you James this recommendation. I have cleared the value of this key after backing it up in case. I am able to uninstall SQL server 2008. 

Shane

Answer 45

Just delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations"

Answer 46

The exact error in the Installation of SQL 2008 and SQL 2008 R2 is on the Setup Support Rules step of the SQL install, where it lists installation rules. The rule that repeatedly shows up red is:
 
"Restart Computer"

Again, none of the registry values could be found, andf trying to break up these values and navigating to them manually turned up none of the keys specified. I even did a search in the registry for : PendingFileRenameOperations, which returned nothing.

---

Rex Whitten

Answer 47

Cleaning up the key mentioned in your response did the trick for me. Thank you.

Answer 48

Rex,
I see that you have been diligent in searching for the restart source.  This week while trying to install on Server 2008 R2 with SQL 2008 R2 I had a similar issue.

The solution in this case was to completely uninstall the prior version of SQL Server then do a cold boot.  Then before doing anything else I went to the registry location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\CONTROL\SESSION MANAGER\

Then I found the entry.

Someone has posted an invalid registry path above.

Larry

Answer 49

Your posted registry path is incorrect.

This is the correct path.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\CONTROL\SESSION MANAGER\

The PendingFileRenameOperation value is in the right side of your screen.

Larry

Answer 50

Here is what I did on my client machine. ( I was able to install VB Studio '08 and SQL Srvr. '08 on Windows 2003 Ent/w no issues).
But, on my XP client machine, I got the same error that the a restart failed.

I went to my registry: HKEY_LOCAL_MACHINE\SYSTEM\CONTROL\SESSION MANAGER\

Looked for the filerename issue. Checked to ensure it was not a file that can cause me problems later on, and deleted this key. Again!
Make sure it is not a file that can cause you problems. How do you know it won't cause you problems once you delete the failed registry key?
Ensur you know which file it is that the install was trying to rename and if need be rename it yourself by: right clicking on the key itself and select "Modify". I delete it mine and rerun the install, everything works well and I see no errors in my Application log; system or WPS.

All the best! Good luck!

Gonzarelli,
I should have quoted you in my previous response... Sorry.
Your posted registry path is incorrect.

This is the correct path.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\CONTROL\SESSION MANAGER\

The PendingFileRenameOperation value is in the right side of your screen.

Larry

Answer 51

Thank you! worked great!

Answer 52

setup.exe /SkipRules=RebootRequiredCheck /ACTION=install

Answer 53

I am running WINDOWS SERVER 2008 R2  and you solution worked for me.

ThanX

---

Its a Dog Eat Dog World

Answer 54

Thanks LookItsGreg.

Installing from command prompt is always more powerful than from the GUI.  

You installation command worked for me.

---

andy

Answer 55

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

What many seem to think (as I did) that there is a KEY value of PendingFileRenameOperations.  There is no KEY by that name.  There is however a Value Pair named "PendingFileRenameOperations" under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

Navigate to the above registry location and then look in the right side pane for the value pair.  Rename it or delete the value found there.

In my case I have a Logitech CAM device that incorrectly completes its install without deleting the value pair.

After correcting the registry my install completed as expected.

Excelent! Thank you J Larry,

Your answer was very informative. I had difficulty with a logitech camera a long time ago... And that install problem is just rearing it's ugly head while trying to install the visual management studio. I deleted the KEY value that refrenced a logi install. And all is well.

Again thank you for sharing your solution.

 - jeffa

Answer 56

THIS WORKED! Uninstalled my figgin' Logitech Webcam and BAMMO! Worked! Thanks!!!

Answer 57

Jan's fix along with other comments worked for me. It was a Logitech web cam that had me hosed.

Answer 58

THIS WORKED! Uninstalled my figgin' Logitech Webcam and BAMMO! Worked! Thanks!!!

there is no need to uninstall their software
just clear the 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
key as mentioned before.
mine also had some logitech cleanup values in there(apparently logitech's setup doesn't clean them after install...)
but this one could also be microsoft's fault since i updated logitech through windows update...AND restarted my machine.

Answer 59

There may be more PendingFileRenameOperations entries under trees like ControlSet001.

Open regedit, position at root of registry, control-F to open Find, and search for all instances of PendingFileRenameOperations.

For any entries where the registry location doesn't end in BackupRestore\KeysNotToRestore, delete the value stored in the registry entry.

Answer 60

Check your system's pending file rename operations registry key. It should be cleared after you reboot your system. If not, something must be wrong.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

I just cleared that key and it was gravy from then on!

Answer 61

As a noob, when you are all referring to clearing the key, with the PendingFileRenameOperations listed in the Name column, are you highlighting it and deleting it? Or are you selecting modify and then deleting the value?

Answer 62

Hi Guys,

came upon this thread by accident, had this problem a while back

some hints,

search the registry for pendingfilerenameoperations (pendingfilerename operations are not always msupdates )

i found that i had  logitech programs pending in controlset001 (naughty logitech-please deletey key after installation)

if there is any pending data there ( 3 or 4 files for me) then clear that.

cheery

 

 

 

 

Answer 63

Hi,

Greately worked for me too .

but carefull before deleteing, take a backup of that PendingFileRenameOperations

1) PendingFileRenameOperations -> single click on it ->go to file menu->select export ->give path and name-> click on save.

2) PendingFileRenameOperations -> right click ->delete-> re run sql server install/uninstall.

 

Thank you

guru

Answer 64

Thanks! I was also missing the key, but found the value pair, deleted it, and then it worked. Indeed it was left there by a Logitec cam install.

Catherine

Answer 65

Hello,

 

I would like to achieve the opposite behaviour. Could you provide valid values for PendingFileRenameOperations registry key? For the testing purposes of my installation package I would like to check the scenario when there is a pending reboot. I tried

key:PendingFileRenameOperations

value: \??\C:\temp.txt

and many different combination but everytime i run System Configuration Checker rule it is passed (no restart required)

OS; XP SP3

SQL: SQL Server 2008 Express R2

---

asd

Answer 66

Thanks everyone on this thread especially Larry - bang on the money
and Catherine - yes, looks like logitech was the culprit here too.

Answer 67

Thanks Larry,

i was looking for that PendingFileRenameOperation value for almost hours

Regards

Peter

Answer 68

Thanks for this good infos. I needed that. I know some sites about Broker. Infos you can get on Broker-Vergleich . Its an objective compare of Broker.

Answer 69

Hello,

 

I would like to achieve the opposite behaviour. Could you provide valid values for PendingFileRenameOperations registry key? For the testing purposes of my installation package I would like to check the scenario when there is a pending reboot. I tried

key:PendingFileRenameOperations

value: \??\C:\temp.txt

and many different combination but everytime i run System Configuration Checker rule it is passed (no restart required)

OS; XP SP3

SQL: SQL Server 2008 Express R2

---

asd

It has to refer to a file that is locked. Find one in use that is never released by the operating system and put that in there.

Answer 70

The method that works is to delete ALL registry key values for the PendingFileRenameOperations, like make sure you do a full search for ALL the keys, then do NOT restart, just run SETUP and it works

 

If you restart, usually the items that you just deleted from the key values returns because they are temporary files used by web cams, wireless mice, etc.

 

-Phil

Answer 71

Clearing out the entries in:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\CONTROL\SESSION MANAGER\

The PendingFileRenameOperation

Worked for me too!

I smell a KB article coming....maybe...hopefully...

---

David Baur

Answer 72

The real issue here is that the #*@ developers at Logitech decided it was OKAY to place an active-and-consistently-used DLL in your temp folder .. be it C:\windows\temp  or  c:\temp  or   whatever value is in the environment variable  %TEMP%

 

Answer 73

The real issue here is that the #*@ developers at Logitech decided it was OKAY to place an active-and-consistently-used DLL in your temp folder .. be it C:\windows\temp  or  c:\temp  or   whatever value is in the environment variable  %TEMP%

Answer 74

The real issue here is that the #*@ developers at Logitech decided it was OKAY to place an active-and-consistently-used DLL in your temp folder .. be it C:\windows\temp  or  c:\temp  or   whatever value is in the environment variable  %TEMP%

Answer 75

The real issue here is that the #*@ developers at Logitech decided it was OKAY to place an active-and-consistently-used DLL in your temp folder .. be it C:\windows\temp  or  c:\temp  or   whatever value is in the environment variable  %TEMP%

Answer 76

Steven, actually .. it's best to leave those alone, as they are "archives" only.

Moreover, be sure NOT to delete or clear the BackupRestore\KeysNotToRestore registry setting .. it's part of the normal system operation and unrelated to this issue altogether.

Answer 77

Thanks dear after following your steps its working perfectly.

Answer 78

It had some value. I edited registry and deleted the key. It solved my installation problem.

 

Khuzaima Shajapurwala

Answer 79

i've seen numerous instances where the "pending reboot" issue is caused by things like gpo-deployed network printers that require enabling the plug-n-play enumerator service prior to initializing the print spool.  in these cases, you can fix the source of the problem by enabling the PNP-X IP Bus Enumerator Service for SSDP / WS discovery protocols.

Deleting the key works, too, but I thought I'd mention this since you might see the issue return after your next reboot.

---

heuristik

Answer 80

Thanks LookItsGreg. I did the installation from the command prompt with the parameters you provided and it worked perfectly.

Answer 81

THANK YOU Larry! Worked for me.

 

Nick

Answer 82

It works for me..Thanks!

Answer 83

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

i don't found this path.in which directory? please mention brifely.

Answer 84

setup.exe /SkipRules=RebootRequiredCheck /ACTION=install

Your a star - worked a treat! Just got me out of a sticky situation!! Thanks very much :)