Error with Windows 10 Enterprise 1903 build 18362.476 and VirtualBox v6.0.14 error

[Emailx45]

my MS Windows is in Portuguese-BR! my user Windows: "PCuserWin" -> is a administrator, per default! Then, all my software are installed in this profile! My user Administrator, stay disabled, per default!

I use VirtualBox since v5. My pc is:

• CPU Intel i7 4770K
• RAM 8GB Corsair Vengeance
• VGA Gigabyte nVidia GTX650 Ti Boost 2GB
• SSD 120GB Corsair to Operating System MSWindows
• HDD 1TB free to my virtual machines (normally 2 or 3 for test, and later I delete it)

My antivirus Kaspersky Internet Security v2020, never got in the way of installing VirtualBox or virtual machines!

I do not see any changes on my computer so this new error appears!

---

Sometimes i had this problem when try install "Package" as normal user (no Admin) as always:

• all my downloads stay (always) in Drive "D" (include VirtualBox + Package)
• my Drive "C" only MSWindows, Kaspersky, RAD Studio 10.3.2, and other utilities -> normally, only apps to work! No games!

to avoid this error, I try install it using run VirtualBox app "As Administrator", or, I copy the file "Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack" to into my folder VirtualBox on Disk"C". then, works!

---

Falha ao instalar o Pacote de Extensões D:/Downloads/__Utils/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-1644' -> 'C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')

rcExit=1.

Código de Resultado: E_FAIL (0x80004005) Componente: ExtPackManagerWrap Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

---

Now, using same MSWindows 1903 build 18362.476, i had another error when trying create new VM to test new ISO MSWindows 1909 (downloaded from Microsoft directly):

---

Falha ao abrir uma sessão para a máquina virtual Windows101909. <-- my VM

(VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Código de Resultado: E_FAIL (0x80004005) Componente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

---

But my "VIRTUALIZATION" always is activated on BIOS and MSWindows, since always! I never had this error before.

I always create my VM with 2GB and 1 (or 2 cpu virtual), and 80GB disk. I never use 2 VM in same time. Later test the new system, I delete my VM. Then, i have many disk space!

[Emailx45]

NOTE: I tried create a new VM to MSWindows XP 64bits and I had same error with VT-x

---

Falha ao abrir uma sessão para a máquina virtual WindowsXP2019. <-- my VM

(VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Código de Resultado: E_FAIL (0x80004005) Componente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[Emailx45]

NOTE 2: I DONT USE MSWINDOWS SANDBOX OR HYPER-V apps

[Socratis]

It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, 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 most probably not a bug and someone has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help me, is going to help you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

Finally, when you open a ticket, you do not dump all your problems on it. You wouldn't even do that in the forums, we like to observe the "​One issue, one thread" rule... ;)

So, please open a new thread in the ​VirtualBox on Windows Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.