Endpoint Protection

There are a few custom MSI return codes when a Symantec Endpoint Protection client installation fails.

Codes and definitions are:

• 10005: Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the migration job
• 11708: Symantec Endpoint Protection installation operation failed.
• 1064: This version of Symantec Endpoint Protection does not support 64-bit platforms.
• 1063: Symantec Endpoint Protection installation operation failed.

These are worth noting should you use the Symantec Endpoint Protection Integration Component as failures will report MSI codes including these.

The resolutions of these issues are prensent in KB of Symantect. These issues are known issues.

•10005: Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the migration job

For this either you restart the system or delete the registry key for pendingfilerenameoperations

•11708: Symantec Endpoint Protection installation operation failed.

This is a generic error message that you will see in your Event Viewer after install fails

•1064: This version of Symantec Endpoint Protection does not support 64-bit platforms

This is for un-supported OS
.
•1063: Symantec Endpoint Protection installation operation failed

This error code you will find at the end of every failed  SEP or SEPM install log

THe SEP installation failure is not  bug but it is some system related uncompatibilies that needs to be fixed after checking the logs.

Do you have links to those KBs?

re: Symantec Endpoint Protection has detected that there are pending system changes that require a reboot..

For this either you restart the system or delete the registry key for pendingfilerenameoperations


I have no registry key named: "pendingfilerenameoperations" only a key named filerenameoperations which I deleted and that did not work.

Rebooting does not work. 

There are no pending operations I know of.

I'm not sure about this particular issue. Have you tried support?

I'm not sure about this particular issue. Have you tried support?

 Once you highlight Session Manager PendingFilerenameOperations should be on the right hand side.

On Windows Vista, I found it under:
 Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager

And deleting the value fixed the problem for me.

Thanks Peter H. as this was the fix after many hours and many attempts.  Deleted the entry and it worked like a charm!