fix: error 1402 ‘Setup cannot open the registry key: UNKNOWN\Components\…’ during office 2010 setup

imageAs regards to security permissions, seems like Microsoft Office 2010 installation is so sensitive. I have confirmed in several forums that is so common to receive an installation rollback for that reason; and I’m not an exception. This morning while I was upgrading my Office installation from 2007 to 2010 it horribly failed with error 1402.

If you face this situation, a very straight forward troubleshooting is to reset your computer’s security setting to a known good working state. How? Well, it is not quite difficult.

Windows keeps the original INF file where security settings values (used during initial installation) are defined. You can use that file to properly reset security setting to original values, and get rid of incorrect setting that avoid a proper installation process.

So, to overcome this specific error, simply open a command line and type the following command (this one applies to Windows Vista/7/2008):

secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose

This command generates an output file under %windir%\security\logs\scesrv.log with results, so you can check it for a more in deep troubleshooting. Also, this method  is used to troubleshoot a bunch of problems related with security settings changing inappropriately (by virus, 3rd-party applications, etc.).

If you want to know more about it check How do I restore security settings to a known working state?

About these ads

5 thoughts on “fix: error 1402 ‘Setup cannot open the registry key: UNKNOWN\Components\…’ during office 2010 setup

  1. mwafrica says:

    You people are doing a great work. I had a similar problem but know its gone.God bless you

  2. vims1990 says:

    Thanks for this. I’ve been having issues with this and I’m glad I came across your article to fix it. (in which it worked)

  3. Jose says:

    Hey, thanks… this post was really helpful. I had been trying to fix this looking for a answer everywhere (Microsoft support sucks) and I already fixed it thanks to you. I really appreciate it!!

  4. xrisco says:

    Yup, you rock! This was the fix.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 62 other followers