Trying to install VirtualBox 6.1.14 but stuck on registering type libraries

Discussions related to using VirtualBox on Windows hosts.
Post Reply
xjamesx
Posts: 1
Joined: 24. Oct 2020, 16:05

Trying to install VirtualBox 6.1.14 but stuck on registering type libraries

Post by xjamesx »

Hi there,

I had an earlier version of VirtualBox installed on my Windows 10 host and am trying to upgrade to 6.1.14 but the setup screen seems to be stuck on "Registering type libraries".

I would appreciate advice on what I can do to safely (and forcefully) remove any old/corrupted VirtualBox components and install 6.1.14 from scratch?
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Trying to install VirtualBox 6.1.14 but stuck on registering type libraries

Post by scottgus1 »

Virtualbox does not distribute a tool to completely clean out a Virtualbox installation from a computer.

Virtualbox uses Microsoft's MSI system to do the install. Regarding MSI installer issues:
socratis wrote:That article seems to be: Basic troubleshooting steps for Windows Installer.

I have two other links to suggest. See also if you have any corrupted MSI database files:
Google for how to enable MSI logging, then try the installation again. If it fails, please post the log as a zip file using the forum's Upload Attachment tab.
Ammer
Posts: 9
Joined: 3. Sep 2020, 08:03

Re: Trying to install VirtualBox 6.1.14 but stuck on registering type libraries

Post by Ammer »

Buonasera, ha tutti, ha xjamesx ho avuto lo stesso problema, non so dove e finito il mio post, nessuno ha risolto il mio problema, comunque ringrazio chi mi ha risposto, ritornando al problema MSI mancante ho risolto praticamente ho installato win10 in dualboot, ho avviato l' istaller di VB alla prima schermata mi sono fermato senza installare sono andato in c windows tempo e si e ricreato il file MSI lo copiato sono andato nell' altro OS win10 ho disinstallato e installato la nuova versione il problema e stato risolto. :D
Post Reply