Virtualbox can't be installed on an encrypted Windows Host

[melihtozlu]

Hi,

does anybody know how I can install Virtualbox on an encrypted Windows Host? I have encrypted my device with veracrypt but I could install it without the encryption. But now if I would like to install it, it shows me an error (don't remember the reason). Thing is that I can see the Virtualbox application before the download should finish actually (I even can open it) but shortly before it should finish actually it reverses the download and deletes all the program files (which I could see too).

I really hope somebody can help me out because I really don't want to decrypt me device...

Thanks!

[mpack]

If you can't tell us the error, we can't tell you the solution.

[melihtozlu12]

If you can't tell us the error, we can't tell you the solution.

Again, the error is not really helpful since it doesn't say an error code or something like that. But if you really need to know the "error" then here: Oracle VM Virtualbox 6.1.4 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.

And once I click on Finish a new window opens up with the following message: Installation failed! Error: Serious error during installation.

But like I said, I don't really think it be really helpful. It's just sad to see that Virtualbox does not work with an ecreypted system.

[mpack]

Why did you register a new account just to continue a conversation?

That reads like a permissions error, and the error is with MSI (the standard Windows installer), not VirtualBox. It doesn't seem to have anything to do with encryption.

Did you run the VirtualBox installer using "Run as administrator" ?

[melihtozlu12]

Why did you register a new account just to continue a conversation?

That reads like a permissions error, and the error is with MSI (the standard Windows installer), not VirtualBox. It doesn't seem to have anything to do with encryption.

Did you run the VirtualBox installer using "Run as administrator" ?

I forgot my username (and since it's the same like my old email, I can't recover it).
And yes, I tried to install with admin rights before I wrote this post and I even now decrypted my system. It still doesn't work! Why??

[mpack]

Actually, I didn't ask if you tried to install with admin rights. That means different things to different people (e.g. it can mean logging in as the admin user). I need a specific answer to a specific question: did you use "Run as administrator" to run the installer?

And ultimately, this is a Windows support issue, i.e. almost certainly it's that you don't have sufficient admin rights to install drivers. Maybe you don't have rights to install software, period.

[melihtozlu12]

Actually, I didn't ask if you tried to install with admin rights. That means different things to different people (e.g. it can mean logging in as the admin user). I need a specific answer to a specific question: did you use "Run as administrator" to run the installer?

And ultimately, this is a Windows support issue, i.e. almost certainly it's that you don't have sufficient admin rights to install drivers. Maybe you don't have rights to install software, period.

Ok, then please explain to me what the difference between installing a program with admin rights and running as adminsitrator to run the installer is? If you still didn't get the answer: Yes, I tried to "Run as administrator to run the installer".
Yes, in the meantime I thought that too (that this is a Windows issue) but apparently it isn't because I literally tried every possible solution and it didn't work:
first tried to google it and the site is full of that (just google oracle vm virtualbox setup wizard ended prematurely "site:virtualbox(.)org")
then tried to disable net framework (3.5)
also tried to install the 2 programs which were recommended here (Repair MSI and Windows Repair)
and tried virtualbox portable as well as to reboot my system after every single step above

So, the only "workaround" which I could find for me is, that while installing the program, I copied the program files to another folder (before the installation was cancelled and rolled back) because this folder is deleted during the roll back. So I can only start VM from these copied files, but I don't think that's the point of this thing.

[melihtozlu12]

Why is this forum so dead lately? Still help needed, BUMP!

[Martin]

It is still a Microsoft problem with the Microsoft MSI Installer on your system.
We Virtualbox users cannot help you with this.

[melihtozlu12]

It is still a Microsoft problem with the Microsoft MSI Installer on your system.
We Virtualbox users cannot help you with this.

I really don't think it's a MS problem. I tried every step MS recommended me (except resetting my system) but also read here in the forum that I should untick the bridged network thing while installing. And that has solved my problem. I just don't understand why? Is it actually important and what's the use of it?

[mpack]

I really don't think it's a MS problem.

By definition it's an MS problem.

At this point there is no VirtualBox code running (*), all you are doing is running the standard Windows installer, and it's the standard Windows installer that is deciding that you aren't allowed to continue. If it was a VirtualBox problem then everyone else would have the same problem, on Win10 hosts, and they do not.

Plus it's clearly a permissions issue, as I already said. It is probably the case that you don't have the rights needed to install drivers. Another possibility is that your certificates database is corrupted, but I've never heard of that happening with Win10, that was a Win7 trait. Probably you simply have the security setting too high on your PC, e.g. you have it set to silently reject untrusted driver certificates instead of prompting you to add this vendor to the trusted list.

(*) The exe you download is just a stub that unpacks an embedded .MSI then launches the Windows installer. If the stub code failed then you wouldn't get as far as the MSI message you see.