|
Can't Install Nero 8 -- Keeps asking for reboot
|
|
|
shieber
Newbie
|
19. October 2007 @ 07:33 |
Link to this message
|
I've tried installing over ver 7 and installing after a clean uninstall of 7, including using the Nero cleaner.
But always, when I runthe ver 8 installer, It tells me that a previous install or upgrade requires a system reboot. I reboot but the same message comes up. Ver 8 never gets installed.
I have ccleaner but it is not set to run on boot up.
Any ideas.
sh
|
|
Advertisement
|
 |
|
|
|
shieber
Newbie
|
19. October 2007 @ 07:37 |
Link to this message
|
The actual message the Nero 8 installer produces is:
"A system reboot was requested by previous software installation (e.g. a Windows update). Please reboot your computer to resume the installation of Nero 8"
Originally posted by shieber:
I've tried installing over ver 7 and installing after a clean uninstall of 7, including using the Nero cleaner.
But always, when I runthe ver 8 installer, It tells me that a previous install or upgrade requires a system reboot. I reboot but the same message comes up. Ver 8 never gets installed.
I have ccleaner but it is not set to run on boot up.
Any ideas.
sh
|
|
shieber
Newbie
|
19. October 2007 @ 19:16 |
Link to this message
|
I tried just about everything I coudl think of. This is what finally did the trick:
1 Click Start
2. click Run.
3. In the Open box, type regedit, and then click OK.
4. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
5. Locate and delete any PendingFileRenameOperations values in the key.
6. Click Yes when you are prompted to confirm the deletion.
7. Quit Registry Editor.
sh
|
|
briama
Suspended due to non-functional email address
|
21. October 2007 @ 06:56 |
Link to this message
|
I have the same problem with the update to Nero 8
I have looked at the solution above and do not have any PendinFileRenameOperations!
I still going round in circles between Nero 7 & 8
I have closed down Zone alarm
Help PLEASE
|
|
Cor70
Newbie
|
21. October 2007 @ 07:18 |
Link to this message
|
|
This solution first didn't work for me either, but i reboot my system after deleting the value of the key. But after deleting the value of the key and no reboot, it worked.
Thanx for your solution shieber.
|
|
Guyy
Member
|
21. October 2007 @ 13:33 |
Link to this message
|
@Cor70
If you have any windows update downloading, wait for it to finish all the downloads then reboot before running the nero installer. That's what i did when i was having the same problem.
|
|
shieber
Newbie
|
22. October 2007 @ 06:38 |
Link to this message
|
|
The pendingfilerename value is a leftover from an install -- some file could not be replaced or renamed while the install was running so the instruction is left to be performed after reboot. These instructions are usually executed at boot time -- it's one of themain reason some installs require rebooting before they are comeplete. Sometimes, for a variety of reasons, one or more of these instructions can be left behind.
If you have any other installs, windows update, etc., that can leave the machine in such a state. Once you have rebooted and still get the message from the installer to reboot, then it's likely a leftover instruction in the registry.
sh
|
|
Guyy
Member
|
22. October 2007 @ 16:21 |
Link to this message
|
@shieber
Quote:
4. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Locate and delete any PendingFileRenameOperations values in the key
tip committed to memory lane. thanks for sharing.
|
|
gdw_29
Suspended due to non-functional email address
|
24. October 2007 @ 08:44 |
Link to this message
|
|
Thanks This Was Really Beginning To Bug Me
This message has been edited since posting. Last time this message was edited on 24. October 2007 @ 08:44
|
|
teeje
Newbie
|
31. October 2007 @ 00:00 |
Link to this message
|
|
Excellent tip. Thanks!
|
|
rockgod78
Newbie
|
3. November 2007 @ 11:58 |
Link to this message
|
4. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Locate and delete any PendingFileRenameOperations values in the key
I do not have any folder named "PendingFileRenameOperations" and am experiencing the same problem (ie. continuous asking for reboot). I do have a folder in there called "FileRenameOperations" and one value in there called "Default". Value type is: REG_SZ and under data is says "(value not set)".
Am I missing something?
Thanks in advance.
|
|
pakcikt
Newbie
|
3. November 2007 @ 23:31 |
Link to this message
|
|
My Experience is the same as Rockgod 78 - Can anyone suggest further?
Thanks
|
|
shieber
Newbie
|
4. November 2007 @ 09:02 |
Link to this message
|
You don't want to delete that key. "Default" is a normal placeholder that windows uses in regitry entries. It means that the this particular fix isn't going to work for you. Sorry. Have you contacted Nero?
Originally posted by rockgod78:
4. Locate and click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Locate and delete any PendingFileRenameOperations values in the key
I do not have any folder named "PendingFileRenameOperations" and am experiencing the same problem (ie. continuous asking for reboot). I do have a folder in there called "FileRenameOperations" and one value in there called "Default". Value type is: REG_SZ and under data is says "(value not set)".
Am I missing something?
Thanks in advance.
sh
|
|
shieber
Newbie
|
5. November 2007 @ 06:53 |
Link to this message
|
Nero sent me a new build, 8.1.1.1, that supposedly fixes this problem. Tech told me they were aware of the prob and that some progs where using certain keys in the registry that was causing this prob for Nero. The build is not yet listed on the updates page
http://www.nero.com/enu/downloads-nero8-update.php
So I suspect they are still working on a few other little buggies in the Nero 8.1 before they release the next build. So if the fix I posted doesn't help you, patience might pay off -- or else writing to Tech support, describing the prob and see if they can give you a link to the newer build of Nero 8.
sh
|
|
mr_stick
Newbie
|
10. November 2007 @ 06:55 |
Link to this message
|
|
Thanks shieber, that was just what I was after.
Rockgod78, PendingFileRenameOperations is not a key, it's a value. What you need to do is select the Session Manager key and you should then see the PendingFileRenameOperations in the right-hand pane.
HTH
C
|
|
shieber
Newbie
|
10. November 2007 @ 09:33 |
Link to this message
|
|
Rockgod78 might be seeing that it isn't there. It seems the prob can sometimes occur for other reasons. However, build, 8.1.1.1, seems to solve the prob in either case. Only the full lang version about 460MB is available form Tech Support. Once they are ready to put out a general release of the next build, there will be a single language version. But best bet for now is contact tech support, explain prob and ask for build 8.1.1.1
sh
|
|
rockgod78
Newbie
|
11. November 2007 @ 21:57 |
Link to this message
|
|
you guys rock... thanks so much.. worked!
|
Newbie
|
16. February 2008 @ 14:27 |
Link to this message
|
Originally posted by shieber:
The pendingfilerename value is a leftover from an install -- some file could not be replaced or renamed while the install was running so the instruction is left to be performed after reboot. These instructions are usually executed at boot time -- it's one of themain reason some installs require rebooting before they are comeplete. Sometimes, for a variety of reasons, one or more of these instructions can be left behind.
If you have any other installs, windows update, etc., that can leave the machine in such a state. Once you have rebooted and still get the message from the installer to reboot, then it's likely a leftover instruction in the registry.
|
Newbie
|
16. February 2008 @ 14:34 |
Link to this message
|
Originally posted by shieber:
The pendingfilerename value is a leftover from an install -- some file could not be replaced or renamed while the install was running so the instruction is left to be performed after reboot. These instructions are usually executed at boot time -- it's one of themain reason some installs require rebooting before they are comeplete. Sometimes, for a variety of reasons, one or more of these instructions can be left behind.
If you have any other installs, windows update, etc., that can leave the machine in such a state. Once you have rebooted and still get the message from the installer to reboot, then it's likely a leftover instruction in the registry.
I tried to install Nero 8 and it didn't work, got the same reboot error. Removed the PendingFileRename usinf RegEdit, turned automatic updates off, tried again. Nothing. Then after a couple of hours, while searching on google for a fix, I got to this forum and found this thread. I tried to see if the registry leftovers are at fault, and installed FarCry. It worked perfectly. Tried again with Nero, and it didn't work. But why the leftovers haven't affected the FarCry install but they continually mess up the Nero one?
|
Newbie
|
16. February 2008 @ 14:46 |
Link to this message
|
|
And how can I get rid of those leftovers? Is there a program that can do that?
|
Senior Member
7 product reviews
|
16. February 2008 @ 15:05 |
Link to this message
|
Camaro09,
Download/run Nero 8 CleanTool. Make sure you tick Clean All. Restart your machine. At first boot, download/install this version instead. Input your serial key when prompted anytime during the installation process.
|
Newbie
|
17. February 2008 @ 00:18 |
Link to this message
|
@pryme_H: This is the first time I install Nero, I've reformated my computer a week ago.
|
Senior Member
7 product reviews
|
17. February 2008 @ 00:37 |
Link to this message
|
Ok. Do you currently have an older version of Nero installed in your system at all?
|
Newbie
|
17. February 2008 @ 01:07 |
Link to this message
|
after 2 weeks looking on forums about a fix for Nero, I think I've found a way to get rid of the problem. Maybe I'm wrong and it's all got to do with the Nero 8 installer that pryme_H gave to me, in which case I am a big n00b :D. If it isn't from the installer, I've found a fix that worked for me. First thing, thanks to Lew, http://www.sniggins.com/remove_those_temp_files.html .I've read the binaries in the leftover instructions, and all except one file were in the Windows Temp folder, but please READ THE INSTRUCTIONS ON THE LINK FIRST. Deleted. Secondly, start regedit and delete that filerenamepending leftover. Final step, go to C:\Documents and Settings\USER_NAME\Local Settings\Temp. Here, press "c". You should/will be directed to the first file that starts with "c". Look for a "Cleaner-something.log" file. Delete it. Run Nero Installer. It will install, don't get worried if the progress bar freezes in place for some time, it will work. After you've installed and done the settings, you will be asked for a final reboot to complete instalation. Bingo! It works, I've just written the first DVD using the new PC.
|
|
Advertisement
|
|
|
Senior Member
7 product reviews
|
17. February 2008 @ 03:55 |
Link to this message
|
|
Whatever the basis is, I'm just glad you were able to patch things up!
|
