virtualbox.org

Host is Linux Debian 9.7 running Virtualbox 6.0.4. Guest is Windows 10 64 bit fully updated. From Virtualbox manager I added the Extension pack 6.0.4 then booted the windows guest. Running VBoxWindowsAdditions-amd64.exe from within the Windows 10 guest fails. I did verify my downloads with md5sum.

Thx Jason

You have confused me. Title says that extension pack (a plugin for the host) fails to install. The text says that extension pack did install, but installing Guest Additions (an entirely other feature) failed.

Which is it? And can we have the precise error message you got on failure?

How long has the Win10 guest been working?

Also a VM log would be nice: With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Guest Additions did not Install. Extension pack installed successfully. Thx for clearing that up for me.

This Win10 guest has been working for a day now. I created if from a .vdi disk that I have been using with older versions of virtualbox for a few years now.

I copied the text from the window that I see when running the VBoxGuestAdditions.exe. File is attached. Error occurs during VBoxDrvInst.exe. 0xE000020B

Also attached a VM log as a zip file.

Can you tell me why the guest is using an EFI BIOS? The virtual drive is only 80GB, so it certainly isn't because you wanted to handle >2048GB drives. EFI was originally implemented in order to support OS X guests. While in theory it can support Win10 guests too, this seems like an unnecessary complication to me. I note that EFI is not the default for Win10 guests, you must have changed it for a reason.

Strangely, the log shows that GAs 6.0.4 seem to be installed and running.

00:00:04.740302 VMMDev: Guest Log: VBoxGuest: Windows version 10.0, build 17134
00:00:04.757417 VMMDev: Guest Additions information report: Version 6.0.4 r128413 '6.0.4'
00:00:04.757737 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x0003B100 (Windows 10, 64-bit)
...
00:00:01.123551 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007fbd3fd7f000 w=1024 h=768 bpp=32 cbLine=0x1000 flags=0x0

You have installed the WDDM drivers 3D accelerated drivers, though you don't seem to have enabled either 2D or 3D acceleration in the VM settings. This might be what the installer is complaining about (i.e. it can't find the relevant hardware feature).

Guest uses EFI BIOS to boot. When I un-check the EFI BIOS setting and then Start the virtual machine I get 'FATAL: No bootable medium found! System halted.'
I checked both the Enable 2D and 3D acceleration buttons, Started virtual machine and tried running guest additions setup again. Same errors.

I have attached log of the virtual machine again.

Guest Additions information report: Version 6.0.4 r128413 '6.0.4'
Agree! This is strange?

You can't just change the motherboard (i.e. turn off EFI), you'd have to reinstall the OS.

What graphics accelerator did you select in the VM settings? I note that VMSVGA is intended for Linux guests only and again would not have been the template default for a Win10 guest. For Win10 guests you should choose VBoxVGA (which is actually not the default either, but the current default (VBoxSVGA) is new in v6.0.0 and still buggy).

Solved! Fixed!

What graphics accelerator did you select in the VM settings?

VBoxSVGA was set after fresh install of Virtualbox and virtual machine would show black screen on Start. I changed to VMSVGA and it would boot with apparently no issues. Tried to run VBoxGuestAdditions.exe and setup failed.

Changed Virtual Machine Display Graphics Controller to VBoxVGA, per your advice, and started virtual machine. It booted and I was able to successfully install VBoxGuestAdditions.exe. I can now see my Windows 10 Virtual machine in Full Screen.

Thank you mpack!

Jason in Vacaville CA

Thanks for reporting back, glad it's working for you. I'll mark the topic as solved.

O-M-G
I've been trying for days to get past those GuestAddition VBOXDrvInst.exe errors. I too originally got just a black screen when using VBoxVGA and only VMSVGA seemed to work but was locked down to small screen size. I switched display options multiple times with no luck. I wonder if I changed something else along the way that led to success later when making this change again. But I read countless 'solutions' and 'solved' blogs. Watched multiple videos. Took extensive notes, made multiple printouts.... recovery mode steps.... fresh downloads.... reinstalls.... countless hours.... everything. Then I stumbled upon j_keiter's experience that was exactly like mine. When he stated that he followed mpack's advice and posted "Solved! Fixed!" just by switching to VBoxVGA I had nothing to lose so I did the same and it worked!!!! No more VBOXDrvInst errors and have full screen window. I can't believe after how long I've looked for an answer and how frustrated I have been for this long that this one simple change made all the difference but is not found anywhere else. I am sooooo grateful for j_keiter's description, mpack's answer, and the luck I had in finding it. Thank you very much to you both.