SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,675 questions
Couldnot Open Key UNKNOWN\Components\. when install SQL2019
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 39%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Quest
1
Reputation point
Hi ,
Uninstalled SQL 2016 version completely and install SQL 2019 Developer version in windows 10 , while installing getting the error prompt "Error 1402. Could not open key UNKNOWN\Components.... Verify that you have sufficient access to that key or contact your support personnel " .
I have tried all the suggestion from MIcrosoft forums ,I gave Full Control under adminstrator account and run the query in cmd Prompt "SECEDIT /CONFIGURE /CFG %WINDIR%\INF\DEFLTBASE.INF /DB DEFLTBASE.SDB /VERBOSE /AREAS REGKEYS" and still issue persists. Any help is appreciated.
{count} votes
-
Erland Sommarskog 100.9K Reputation points MVP2022-05-26T11:50:01.863+00:00 Do you notice the link in the bottom of the picture? That link takes you a folder with lots of log files. I am not saying that you will be able to resolve the issue with help of these log files, because they are very verbose. Most of it is Greek to me as well, But if you are lucky, the penny may drop.
The one to start with is detail.txt.
Sign in to comment
4 answers
Sort by: Most helpful
-
-
Quest 1 Reputation point
2022-05-26T12:04:32.497+00:00 I tried to click that file to check , same error persists with some explanation and when i click the error link it goes to Microsoft website .
-
Erland Sommarskog 100.9K Reputation points MVP
2022-05-26T12:23:11.103+00:00 I didn't say that it would be easy, did I?
The summary file does not give that much more information, but the talk of the MOF compiler and the WMI server suggests that your machine is a little hosed.
As I said, the file to start with is detail.txt, and then possibly look in the other files. And, no, I am not promising that you will spot the root cause that way, or for matter that anyone else will. But it can be worth giving a shot before you take more drastic measures.
One option if you don't want to flatten the machine, is to create a virtual machine and install SQL Server on the VM.
Sign in to comment -
-
CathyJi-MSFT 21,086 Reputation points Microsoft Vendor2022-05-27T03:31:19.27+00:00 Hi @Quest ,
>Could not open key: UNKNOWN\Components\E76F7102E9174B94484FD2237D1B06C6\7705D418F39C2E248B571707701C689B.
>Could not open key: UNKNOWN\Components\023B3CE874798074CA60E2B343A45479\4D4F33C25A9E1ED4CAEFA33164E47630.
>Could not open key: UNKNOWN\Components\1C577CC61E2D0E84E920735D0B9EEA23\763D39D9CC2A8734DB3697FEF37EC687.The error is generally caused by insufficient or incorrect permissions on the named registry keys or parent container of such registry keys. Error seen in summary log is pointing to three registry paths. To resolve this issue, select appropriate permission to the Windows Registrys that mentioned in summary log. Note: Back up the registry key before you modify any key in the registry.
1.Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
2.Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components. The 'S-1-5-18' key may be different on your computer.
3.Once you find the registry key (such as E76F7102E9174B94484FD2237D1B06C6) displayed in the error message under components, you need to provide permission for the key.
Right Click the GUID –> go to Permissions –>
Click on Advanced –> Click Add –> Type <hostname>\administrators and click Ok –> Click Ok –> Click Ok
Refer to the blog SQL SERVER – FIX – Error 1402 – Could not Open Key: UNKNOWN\Components to get detail information.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
-
Quest 1 Reputation point
2022-05-27T03:43:32.627+00:00 Hi Cathyji-msft,
I tried all the suggestions referred from the link and gave permissions also but my situation didn't change anything. When I right click the parent key not getting an error prompt but child key says key couldn't opened.
-
CathyJi-MSFT 21,086 Reputation points Microsoft Vendor
2022-05-27T05:56:32.137+00:00 Hi,
According to your screenshot, it is still permission issue. Please give the permission to the child key.
-
Erland Sommarskog 100.9K Reputation points MVP
2022-05-27T08:46:59.467+00:00 Is this your private machine, or is this in a corporate environment?
What anti-malware software do you have installed?
-
Quest 1 Reputation point
2022-05-27T09:23:46.59+00:00 Its Corporate environment and using Trend Micro security Agent Anti malware.
After Uninstall sql 2016 and then install sql 2019 , suddenly got this issue
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 1%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETP%3C/text%3E%3C/svg%3E)
Tom Phillips 17,716 Reputation points2022-05-27T12:43:55.22+00:00 That sounds like you are not a local administrator on your machine and the SQL 2016 WAS installed with a local administrator account. So you were unable to remove all the SQL 2016 objects.
You need to be a local administrator to install SQL 2019 and overwrite the SQL 2016 objects.
See:
https://www.mssqltips.com/sqlservertip/6646/sql-server-uninstallation-error-could-not-open-key/
Sign in to comment -
-
Erland Sommarskog 100.9K Reputation points MVP
2022-05-27T09:34:15.21+00:00 Its Corporate environment and using Trend Micro security Agent Anti malware.
After Uninstall sql 2016 and then install sql 2019 , suddenly got this issue
It is not implausible that the permissions errors you see are due to Group Policy or (over-)zealous surveillance of the registry from TrendMicro. We certainly have seen cases where the anti-malware software has prevented SQL Server from being installed. Although, the UNKNONWN thing suggests that something is really wonky. But it could be a combination of both.
Anyway, I suggest that you discuss with your IT department. Possibly, your machine has to be refreshed from your corporation standard image.