I had a Windows 2008 server that I was attempting to install the Symantec Endpoint client on, but the client would not install, and the following message was left in the event log:
Symantec Endpoint Protection (SEP) Installation fails with the following error “Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”
I rebooted the server and then tried to install the client again, but the same error would appear.
I found that there was a registry entry that was giving me grief with the install, and here are the instructions that I used to fix the problem.
- Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations - Back up the registry key
- Delete the registry key
- Install the software without restarting the computer first (Restarting the computer may result in the registry key being placed back in the registry before installation.)
- Restore the registry key from the backup location.
NOTE: If you are running Windows Vista look for this key - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet001\Control\SessionManager\PendingFileRenameOperations
* Thanks to Bill for this Windows Vista suggestion.
Thanks your fix worked great. I rebooted after the install and saw that the key had been placed back in the registry. So I did not restore it.
This worked perfectly! My scripting guy had been fighting with this for 2 weeks and this solved it in 2 minutes! Thank You!!!
Great fix…worked for me without a restart.
Nice fix I was wondering why the newest version of Endpoint was telling me this Thought I would google it to see how to fix and your fix worked perfectly. THANKS
You guys are wonderful. Deleting the darn key did the trick.
Fix works great thanks so much
Hey thanks a lot for the hint, It worked great. I just renamed the KEY and ran the install and it did just fine as well!!
George
That did not work because I did not have that entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations
Symantec still will not install.
Any suggestions?
I have two registry keys, one is called HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations and the other is called HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations2 !!
How can I deal with it ?
Thanks for any help !
Delete both of the keys.
Matt
This registry hacked didn’t work at first, however it gave me a starting point to look for the right key. For Win Vista look for this key; HKLM\system\controlset001\control\session manager\PendingFileRenameOperations. I deleted the key and was then able to install the SEP application. After installation the key was recreated. Thanks!
You beauty….worked perfectly for me following Bill’s latter suggestion in Vista
Annother one solved, long live Google, and this works just fine, thanks…..
Thanks for the tip. This error seems to appear 50% of the time on Windows 7 installations of SEP. Deleting the registry key fixes it every time.
I have applied the changes in the registry and still recieve the same error. HELP! Where else do I go from here? Thanks in advance,
What operating system are you running??
All troubleshooting documentation in the distro ASSUMES a successful install. Been pulling my hair out reading through it all. This fix worked like a charm. Thank you for my sanity back!
shnake,
I am suing MS Vista home premium. I also went to ControlSet001 and removed the FileRenameOperations. Is there another file that needs to be deleted or can it be a possible virus that I have that is preventing this?
Thanks in advance.
shsnake,
Thanks for the reply. it was operator error “again” I was deleting the FileRenameOperations folder and not just the file. DAH!!!
Thanks again
This worked for me. Thank you!
I have Windows Vista Home Premium 64-bit. I ran into this problem trying to load Symantec Enpoint Protection v11.00.4202 for 64-bit. I had deinstalled the previous version of SEP 11.00.4014 and rebooted before trying to load new version but still had this problem. Could not find any registry key values as described above. In my search on the web found someone that mentioned this problem being associated with Logitech webcam software. Deinstalled the Logitech webcam and the Symantec load was then successful.
Thank you!
It works fine on Windows 7 Ultimate too! (Without restart.)
Thanks for the post. Saved me for sure.
Perfect
I have Windows Vista 64, and I ran into this problem. I couldn’t delete the registry key, but after reading about the Logitech webcam problems, I uninstalled all the logitech stuff, and it has worked. Thanks for the info!
So I couldn’t find the reg keys in Vista as described above. I did have the Logitech Webcam software installed and once I uninstalled specifically the Logitech Video (high Quality) software, that nailed it. No more stupid annoting error 10005.
Thanks to Craig for posting about the logitech packages. Hopefully re-installing the camera software will not be an issue. Cheers.
Works for Windows 7 as well.
Worked great with Windows 7 Enterprise! I’ve installed Endpoint on 5 other Windows 7 computers without any problems. But this time the installation error kept showing up until I deleted the specified registry entry.
Thanks!!
You guys might be looking for the folder in the registry. There isn’t a folder within Session Manager for “FileRenameOperations”
It’s a registry entry (on the RIGHT side).
Doh!
OK, for those with Windows (crappy) Vista 64 Home Premium, that stupid Norton 360 and the Logitech Web cam software….Here’s what you do to get the Endpoint to work….Use the Norton Uninstall tool to uninstall Norton 360 then uninstall all Logitech software for the webcam…Install the Endpoint software then reinstall the webcam drivers and such. I love the registry suggestion but am scared to try it and did this instead. Works now (whew)!!!
Great thing is, it works. Less than great thing is… I still can’t push SEP from the SEP Management Server to my Windows Server 2008R2 and have a successful install.
I spent a few hours on the phone with a rather rude Tech Support individual at Symantec, who walked me through a number of steps to get SEP pushed out. My steps were as follows:
Turn off User Access Control
Turn off Windows Firewall
Enable Network Discovery
Turn off Windows Defender (for me, Defender wasn’t installed–no service to stop)
Delete pendingfilerenameoperations registry key.
Push the installation from SEP Management Console.
When I would do this and try the push, msiexec.exe would show up in the process list, but the installation never shows up and never completes. I could wait as long as I like, but nothing happens.
So, the support rep has me install Live Update (lusetup.exe) locally, then install SEP locally, and says it’s a Microsoft issue and ask them for a fix, have a nice day. Thanks for nothing, Symantec.
Okay, so my question is, are any of you aware of this “fix” or update from Microsoft that will address how Windows handles third-party installations in regards to the pendingfilerenameoperations registry key?
HELP!!! I have tried all the above with now success!! I am running Windows 7 Home Premium 64bit and I get the same error then when I try to re-install it I get “Pending system changes that require a reboot have been detected” error. I have deleted the registry entries but they keep coming bck every time I try to re-install. HELP!!!
I too am having the same trouble as Teo. Running Windows 7 Home Premium 64bit, when I start windows no PendingFileRenameOperations appears, but once I start the installation PendingFileRenameOperations appears in ControlSet001 and CurrentControlSet (not ControlSet002) with identical values. I delete key during or after installation to no avail. People who got it to work: after deleting the key does it reappear during installation with a bunch of values like …AppData\Local\Temp\CCI7A4F.tmp ? BTW this was a clean 7 install and all I’ve installed was Office, minimal Toshiba drivers and firefox.
Wow! It was that simple. I had this software for a little while and couldn’t get it to load. Thanks, this worked like a champ.
It was the Logitech Quickcam software on Windows 7 for me.
Heather:
November 29th, 2009 at 8:16 am
You guys might be looking for the folder in the registry. There isn’t a folder within Session Manager for “FileRenameOperations”
It’s a registry entry (on the RIGHT side).
Doh!
You are absolutely right!
Jadie, Thanks! Nothing worked until I installed live update manually. It shouldn’t be this difficult.
[...] then directed me to this great blog post which had the step-by-step instructions for resolving the [...]
I had the same problem with Scott W. and Teo. You need to start the installation for symantec and when you see “FileRenameOperations” appear delete it right away and the installation will continue. Good luck.
help i have the rebood error and have tried the registration edits from both symantec and here
I ran the window repair… and nothing has helped yet… i have the problem on an inspiron 1505 and a new studio… lap top
Any thoughts ????
thanks bill
I follow step by step the instructions of Jadie and worked great for me on a 32bit Windows 7 Professional, it’s amazing how symantec doesn’t fix this issues.
You don’t need to delete the whole key, Export the Session Manager key to a reg file, and then just delete the key values in the value name PendingFileRenameOperations. Then after install, run the reg file to restore the values.
thnx, worked like a charm. was having the problem after upgrading from win server 2008 to 2008 R2.
@craig whitey thank you! I’ve got vista x64 on my HP dv9933cl laptop. I uninstalled all of the Logitech software (3 different instances), rebooted, and then Symantec installed fine. No registry hack required!
Worked like a charm. thank you.
It worked fine on 32 Bit Windows 7 professional. It’s really amazing.
OMG !!! You are just awesome…. Works like a charm !!!!
Hey folks,
I’ve tried the above solutions. Spent about 4 hours on this and still cannot get rid of the “…pending changes”. b
I did renaming “PendingFileRenameOperations” with a 2 and deleting it in CurrentControlSet and/or ControlSet001 or deleting the contents. Running “64Bit_SEP_MR4_Home_User_Installation_Setup” on Vista sp2.
What else I can do? Please help.
thanks,
I did this, and it worked once, and it installed. then when i looked for Symantec in C:// Programfiles it wuznt there.
IT did the installer and it wasnt there. then i retried the installer and it asked me for me to reboot!!! and the key wasnt there!
Work fine!!!