Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments.

Provide feedback on this article Request Assistance Print Article Products Related Articles Subscribe to this Article Manage your Subscriptions Search Again Situation After updating a Windows 10 computer with Microsoft Windows Symantec Endpoint Protection 12.1 Terms of use for this information are found in Legal Notices. ScriptGen: ShowServiceProgress() is returning an error (so close to the end!) CustomAction ShowServiceProgress returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI Source No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 Products Products Home Threat Protection Advanced Threat

Did this article resolve your issue? Technical Information Generally, in the case of Symantec Scan Engine the installation needs to be done with an account like Domain Admin, having Local Admin rights and being a member of Thank you for your feedback!

References: "The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP http://support.microsoft.com/kb/315353 "The Windows Installer service could not be accessed" error message when

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. After rebooting you will be able to install the antivirus. +1 Login to vote ActionsLogin or register to post comments PC Keeper Error “Windows Installer Service could not be accessed” when No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 If the error still appears then proceed further.

Symantec provides these links as a convenience only. If it works good else come to the next step Step 2: Verify the DCOM permissions This method involves changing the DCOM default impersonation level to Identify, removing the Msisip.dll file, To check the permissions on the registry key, perform the following steps. have a peek here Click Apply, and then click OK. 13.

Thank you for your feedback! Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Click SYSTEM in the Group or user names list, and then select the Full Control check box under Allow in the Permissions for SYSTEM box. Don't have a SymAccount?

If it works good else come to the next step Step 3: Verify the registry permissions Click Start, click Run, then type Regedt32. Error message when you try to add or remove a program on a computer that is running Windows XP or Windows Server 2003: "The Windows Installer service could not be accessed" Download and install the latest Windows Installer for the OS in use. Solution Workarounds: A.

Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. Thank you for your feedback! If SYSTEM is not listed in the Group or user names list, click Add, make sure that the local computer name appears in the From this location box, type system in Create a SymAccount now!' SEP Client install fails - Windows Installer: Error opening installation log file.

Then right-click My Computer and click Properties. · In all other versions of Windows, go on to the next step. 4.

© Copyright 2017 webfusionjm.com. All rights reserved.