Symantec Endpoint Protection will not install
I have been attempting to install the corporate edition of Symantec Endpoint Protection and keep getting the message it was interupted and it wont install. I have used the troubleshooter and rolled to Vista but it still will not install. It starts and the it rolls itself back and says try to repeat instalation. This version is for windows Vista, both the 32 bit and 64 bit system. Any help would be appreciated.
June 22nd, 2009 4:16am
Honorbound,Did you try to run the SEP installer in "windows vista compatiblity mode".On the following link you can find more information on how to run in the windows vista compatiblity mode.http://www.howtogeek.com/howto/windows-vista/using-windows-vista-compatibility-mode/Does this resolve your issue?Kind RegardsDFTIM me
June 22nd, 2009 5:47am
I have tried both the service pack 1 and 2 vista as well as vista and it continues to say it was interupted during the install process. This is version 11.0.1 symantenc enpoint for home use. This program will install on an untouched service pack 1 of vista as it has been installed on another computer with this system, just windows 7 it will not install. Something seems to be interuping the install process.
June 22nd, 2009 7:13am
Symantec is working on Windows 7 compatibility for their System Endpoint Protection product. The version you are using is definitely not working on Windows 7 RC. The latest version mentioned in the Symantec forums is 11.0.4202.More information is available at http://www.symantec.com/connect/forums/windows-7-rcRay
June 22nd, 2009 7:30am
Honorbound,I found some users who successfull could install SEP on windows 7 beta(Build7000) and windows 7 RC1 (build 7100).With the following procedure. Before you start try to download the latest version of SEP from symantec. 1. Run LUSETUP.EXE from the SEP client folder 2. Click Yes to install LiveUpdate (this might be hidden by another window) 3. <wait while LU installs> 4. Click OK (this too might be hidden by another window) 5. REBOOT THE COMPUTER 6. Logon again 7. Double click setup.exe from the SEP client folder 8. Walk through the install wizard 9. Let it run LiveUpdate (if you chose to, or used Typical) 10. RebootDoes this resolves your problem?Kind RegardsDFTIM me
June 22nd, 2009 7:32am
Hello Honorbound,I have experienced the same issue with Symantec Endpoint, the only workaround I have found that is successfull is to install it on Windows Vista and do an upgrade installation of Windows 7. Im not sure of the specifics to how this works but it does. Hope this helps.-Scott
June 23rd, 2009 11:20am
I tested SEP 11.0.4 with windows vista and it was working normal but I could not upgrade to windows 7 unless to remove SEP firstly.So try to use SEP 11.0.5 as Symantec Endpoint 11.0.5 is now supporting windows 7http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009072315130848http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009072315265848
October 11th, 2009 8:15am
Hi, I had the same of installing SEP 11.0.5 corporate edition. As mentioned by you, I installed LUSETUP.EXE first and then ran the SETUP.EXE. It worked fine this time. I did not even boot in between. Thank you very much for your instructions.
March 11th, 2010 5:50pm
Hello all, I've tried to installl the LUSETUP.EXE first and have gotten no luck at all. It will go to the motion of installing, and then it will "roll back" and then I get this message... "The wizard was interrupted before Symantec Endpoint Protection could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again." then after I try reinstalling it again i get this... "Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation." What gives?
April 1st, 2010 8:01pm
This is a known issue. This from Symantec. The PendingFileRenameOperations registry value can be backed up and deleted. Symantec Endpoint Protection can then be installed, and the PendingFileRenameOperations value replaced in order to facilitate installing Symantec Endpoint Protection without affecting the operating system or 3rd party applications negatively. This method will leave several temporary installation files in the logged in user's temp directory that would normally be deleted after a reboot. Open the Windows Registry editor (regedit.exe) browse to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager Verify the following Reg Multi String value PendingFileRenameOperations exists under this key. Note: If you do not find the PendingFileRenameOperations value in the location above, this error message can be generated if there are pending changes in: HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SessionManager\PendingFileRenameOperations Right-click on the SessionManager registry key that contains the PendingFileRenameOperations value and choose Export Provide a file name and location for the exported registry key and click Save Delete the PendingFileRenameOperations value from the registry If HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired exists, right-click on the RebootRequired registry key and choose Export. Provide a different file name than in step 4 for the exported registry key and click Save Delete RebootRequired sub-key Install Symantec Endpoint Protection normally Before rebooting, double-click on the .reg files created in Step 4 and 7 to merge the previous PendingFileRenameOperations value and RebootRequired sub-key. Dave Article URL http://www.symantec.com/docs/TECH103109
December 1st, 2011 1:22pm
Those Registry edits Did NOT Work!!!! Same Error. I merged them back, or guess I should say I tried.... to merge them back....second one wouldnt...Died of an error, Rebooted went back to check, old entries are gone.... Hope this dosen't cause other issues down the road.... Why is Symantec and why have they always been such problem children?? I have been doing this for years..... Why don't they just close up shop? How many Stress Assosiciated Heart issues have they caused? Ridiculous!!!!
June 17th, 2012 2:00pm