Error 1401 Could Not Create Key Symantec
Contents |
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL error 1402 could not open key unknown components Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee
Could Not Open Key Unknown Components Itunes
Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services error 1402 could not open key hkey_local_machine32 Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial
Could Not Open Key Unknown Components Verify That You Have Sufficient Access To That Key
Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login verify that you have sufficient access to that key or contact your support personnel Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Error 1401 Could not Create Key TECH183489 March 21st, 2012 http://www.symantec.com/docs/TECH183489 Support / Error 1401 Could not Create Key Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation Error 1401 Could not Create Key Cause Installing remotely to a server Solution Needs to install to the server from the serverApplies ToServer 2003 Legacy ID 44200 Terms of use for this in
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About
Error 1402 Setup Cannot Open The Registry Key
Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact
Could Not Open Key Unknown Components Da42bc89bf25f5bd0af18c3b9b1a1ee8
Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Error could not open key unknown components wsus 1402. Could not open key UNKNOWN\Components\.... Verify that you have sufficient access to that key or contact your support personnel when installing Symantec System Recovery (SSR) Article:000007961 Publish: https://support.symantec.com/en_US/article.TECH183489.html Article URL:http://www.veritas.com/docs/000007961 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem https://www.veritas.com/support/en_US/article.TECH135922 Error 1402. Could not open key UNKNOWN\Components\ DA42BC89BF25F5BD0AF18C3B9B1A1EE8 Verify that you have sufficient access to that key or contact your support personnel. Error Message Error 1402. Could not open key UNKNOWN\Components\ DA42BC89BF25F5BD0AF18C3B9B1A1EE8 Verify that you have sufficient access to that key or contact your support personnel. Solution To resolve the issue, perform the following steps: 1) Resolve permission issues per: http://support.microsoft.com/kb/313222 . Once done, run the installer again. 2) If step 1 is unsuccessful, open the registry. Create a backup of the registry!! Then, locate the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\DA42BC89BF25F5BD0AF18C3B9B1A1EE8 key and attempt to open. Typically an "Access Denied" error will be generated if the issue above is occurring. Right-mouse click on the key and click 'Permissions'. Grant FULL access to this folder, and check the box to allow the same permission to be granted to this key's sub-folders (descendants). Exit the registry, and install SSR. 3) If both steps above are unsuccessful, Step one, back up the registry.Step two, go to the MS KB:
360 games PC games https://support.microsoft.com/en-us/kb/838687 Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators http://www.shnake.com/?p=445 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet could not Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All could not open Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
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\Current\ControlSet001\ControlSessionManager\PendingFileRenameOperations * Thanks to Bill for this Windows Vista suggestion. This entry was posted in Symantec Endpoint Protection, Windows 2008 and tagged Symantec Endpoint Protection, windows on 24/01/2009 by admin. Post navigation ← Subent mask cheat sheet How to fix the " The pre-release version of Remote Desktop Connection has expired" issue in Windows XP SP3 → 72 thoughts on “How to fix issue with Symantec Endpoint client not installing due to a required reboot.” Ron 01/02/2009 at 8:07 am 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. Reply ↓ Mark 18/02/2009 at 6:10 am This worked perfectly! My scripting guy had been fighting with this for 2 weeks and this solved it in 2 minutes! Thank You!!! Reply ↓ Anthony L 20/02/2009 at 2:10 pm Great fix…worked for me without a restart. Reply ↓ E.B. Wing 0