Opened 6 years ago
Last modified 6 years ago
#17719 new defect
Windows installer for 5.2.10 fails with dozens of "Could not write value to key" registry errors
| Reported by: | Kriston | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.10 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Windows |
Description
Windows installer for 5.2.10 fails with dozens of "Could not write value to key" registry errors.
Representative screen shots attached.
Attachments (3)
Change History (4)
by , 6 years ago
| Attachment: | virtualbox-registry-1.png added |
|---|
by , 6 years ago
| Attachment: | virtualbox-registry-2.png added |
|---|
by , 6 years ago
| Attachment: | virtualbox-registry-3.png added |
|---|
comment:1 by , 6 years ago
Note:
See TracTickets
for help on using tickets.
This is not a VirtualBox bug, this is a problem with your Windows setup (obviously). The permissions in your registry are botched, and it seems that even the Administrator (or the "Installer") does not have the necessary permissions to create some registry keys.
Why did this happen? Usually sloppy installers. So, a program (MyApp) that gets installed wants to modify the permissions to its registry keys, so no one has access (for whatever reason). Now, instead of modifying the permissions to the registry key "
Software\Classes\Interface\{MyApp}" to be read-only, it modifies (by mistake) the key "Software\Classes\Interface\", the parent. From that point on, every application will be botched. What's worse? Say you find which application did it (MyApp). Even uninstalling it, will rarely undo the damage.For reference, the permissions for a Win10 (you never mentioned your host, you should have) installation, the permissions for the "
Software\Classes\Interface\" key are:If yours differ, you're in trouble. I do not know of a utility that "resets" the permissions in the Windows registry, so my advice would be to do a backup of your files (not your programs necessarily) and then re-install Windows. Something/someone has *really* messed up with your registry. Not in a position you want to find yourself in...
May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".