virtualbox.org

Hello,

For my work, I use the version 4.3.12 of virtualbox. It used to work fine on my last computer but recently I got a new one with windows 10 2004 and since, when I try to launch it, I got the compatibility assistant program who block it. I tried different things, I disabled the compatibility assistant in the service.msc file and in the gpedit.msc and the Hyper-v is disabled too but it still doesn't work. I start to run off of solutions, I know the sofware version is not recent but my work want me to continue with it.

If anyone has a solution, I will take it. Thank you.

You need to use a much newer Version of VirtualBox that knows what Windows 10 is

I know it would be better if I use a newer version but it's impossible with my work place and the version 4.3.12 worked fine on my last computer with windows 10 1909

Things advance. 4.3.12 is no longer compatible.

If your workplace insists on 4.3.12 and insists on Windows 10 2004, then they have insisted themselves into a corner we can't get them out of. Tell your boss you are unable to work, and let the boss and IT sort it out.

The insistence on 4.3.12 is significant: that was the last version of Virtualbox without hardening. The bosses probably had a hardening glitch with their setup at the time and never advanced.

The hardening algorithm has been worked on a tad since then. They need to set up a test workstation with 10 2004, their work software and modern Virtualbox and try it. If hardening troubles happen, post the VM's hardening and vbox.logs, let us look into it. Many times there are workarounds or exceptions that can be implemented.

I found a way to make it works. I downloaded the ADK for windows 10 version 2004 and I used the compatibility administrator to disable the compatibility on all the virtualbox executable. When I start it in admin mode, it works fine.

Lexasr wrote:When I start it in admin mode, it works fine.

Keep in mind that running Virtualbox as Administrator opens the host to greater attack vectors for malware, especially so with 4.3.12 which does not check injected DLLs for security signing.

At best it's a not-very-wise workaround. At worst it's pink-slip-generating tomorrow's News story of a billion-dollar data breach.

The true fix is to get your company's IT department to allow modern Virtualbox. A lot has been done to make hardening work.