Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Discussions related to using VirtualBox on Linux hosts.
Post Reply
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

Link to my ticket: https://www.virtualbox.org/ticket/18255

Hi Community,

I am new here. I am running a Windows 10 image on my Ubuntu 16.04 host. I had a minor issue that my second monitor only gets to 1280x1024 resolution instead of 1600x1200. I don't know, I think this wasn't in the beginning so. I only use the windows image for the work with special windows programs. So it could be, that I do not use it for months.

I was informed about a new update to 5.2.22. I neglected to update in the first place. Then I unfortunately decided to do the update. On the homepage, 6.0 was announced, so I decided to download that and installed it according to the command line instructions.

When I finally booted the image again, the second monitor was very very small (guess VGA), and the first was 1280x1024 (if I remember correctly). After a while I came to the conclusion, that the guest additions probably needs to be reinstalled. So I removed it from the program's section and reinstalled it (with hopefully now the correct 6.0 version). But since then, there have been errors during the install and no second monitor is shown and the first one could not get over 1280x1024 instead of full hd.

I tried and tried and searched and searched. And here I am, a small issue became very big because of my stupid idea of updating - and probably the follow-ups.

I hope anybody here in the forum can give me tips how to solve this issue without wasting my Windows 10 image. Cause obviously I spent a lot of work in it.

Thanks in advance
Peter
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by socratis »

Thank you Peter for posting this in the forums as well, and thank you for linking to the ticket!

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Image
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

Hi,

in the ticket there are two logs, the bigger one I have created the way described, but there was no need to zip it.

One thing came today into my mind. I have various installation packages for virtualbox (5.0, 5.1, 5.2,6.0) in my package manager but only one extension package. Is this independent of the installed version?

Today I tried to again install virtualbox 6.0 (after removing/purging with apt) but installing of the extension package ended this time with an error.

Second time it was successfully installed but it is irritating that the version differs from 6.0, namely 5.1.38:

Code: Select all

[...]
DKMS: install completed.
Setting up libgsoap8:amd64 (2.8.28-1) ...
Setting up libvncserver1:amd64 (0.9.10+dfsg-3ubuntu0.16.04.2) ...
Setting up virtualbox (5.1.38-dfsg-0ubuntu1.16.04.1) ...
vboxweb.service is a disabled or a static unit, not starting it.
Setting up virtualbox-ext-pack (5.1.38-0ubuntu1.16.04.1) ...
removing old virtualbox extension packs
virtualbox-ext-pack: downloading: http://download.virtualbox.org/virtualbox/5.1.38/Oracle_VM_VirtualBox_Extension_Pack-5.1.38.vbox-extpack
The file will be downloaded into /usr/share/virtualbox-ext-pack
License accepted.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Successfully installed "Oracle VM VirtualBox Extension Pack".
Setting up virtualbox-qt (5.1.38-dfsg-0ubuntu1.16.04.1) ...
Processing triggers for shim-signed (1.33.1~16.04.1+13-0ubuntu2) ...
Secure Boot not enabled on this system.
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.10) ...
Processing triggers for ureadahead (0.100.0-19) ...
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by socratis »

Hmm... it seems that you have a mix of the Ubuntu VirtualBox fork and the official VirtualBox. You'll need to completely remove/uninstall/delete/purge everything VBox*, VirtualB*, VM* and install the official version from the Linux Downloads section of VirtualBox. You can even add VirtualBox as a repository, so you could use your traditional install/upgrade/uninstall tools.

Finally, as far as the ExtPack goes: the Extension Pack (ExtPack) gets installed on the host and it has to match the VirtualBox version. It provides functionality such as USB2-3, Webcam, VRDP, PXE, PCI passthrough on Linux hosts, VDI Encryption. You have to download it and install it separately from the main VirtualBox program, due to its license.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

It must fit, I know now. But on my ubuntu system all is mixed up. Meanwhile I tried after again remov/purge wit apt, to manually download 16.04 version with fitting extension pack, which I then installed via the GUI of vbox and not via commandline like before (when I took the repo mentioned on the oracle web site):

Now I get this error, when I try to start the image of win 10:

Code: Select all

RTR3InitEx failed with rc=-1912 (rc=-1912)  The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing  '/sbin/vboxconfig'  may correct this. Make sure that you do not mix
The command vboxconfig did not change anything about this. And surely I did not mix anything here. It was all 6.0 and every time I tried to remove/purge in the ubuntu way to get rid of every component installed previously by:

Code: Select all

sudo apt remove virtualbox-6.0
sudo apt remove virtualbox-dkms
sudo apt purge virtualbox-6.0
sudo apt purge virtualbox-dkms
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

I changed the Graphics Controller with 6.0 to
<Display controller="VBoxSVGA" VRAMSize="256" monitorCount="2" accelerate3D="true" accelerate2DVideo="true"/>
and after reinstalling 5.2.22 (because of the kernel module probs) to:
<Display controller="VMSVGA" VRAMSize="256" monitorCount="2" accelerate3D="true" accelerate2DVideo="true"/>
I also tried out in the past and now to install the guest additions with no 3d assistance, with Direct3d and the other recommended 3d option. But it all fails with the same error. In the past I also changed the config file, but not with the last trials.

In the attachment you see, direct3d installation option as the last one.

At least it is starting again with one monitor 1280x1024, and it is not finding some hardware related to the vboxvdeow8.inf file.
Attachments
Windows10-2019-01-03-12-42-08.log.zip
VBox.log from today with v5.2.22
(36.87 KiB) Downloaded 318 times
Last edited by socratis on 3. Jan 2019, 18:32, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

Thank you Socratis!

I followed your tips but unfortunately found out that the system was already in the past removed completely, at least none of your propositions did match.

From the error message, I assume the error is somewhere in the windows image, maybe in corelation with the guest addition and maybe the config file of the virtual machine?

Actually I am installing a second installation of the windows 10 image. But nevertheless this is all done, because I want to save my old installation. So I just want to exclude some error sources. If it works, I am right, and the error must be somewhere in the image (but is surely related to the virtualbox, because the error occured during an update)...

I will come back in an hour or so to report. Isn't there anything more that could cause the inconsistency?

Best
Peter
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

Windows 7 image worked perfectly, Guest Additions could be installed withour any problems. So the reason stays inside the guest, and something was changed during the update to 6.0 and afterwards the new extension pack (via Ubuntu, not GUI of vb, that time and trial). So how can I repair my windows image, so that installation of the guest additon drivers will work again?

Is there a possibility that the DriverStore/FileRepository folder in Windows/System32 is somehow misarranged?
Last edited by peddanet on 3. Jan 2019, 18:40, edited 1 time in total.
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

The installation process of my Windows 10 image claims always an error with vboxvideow8 driver. But in my Windows 7 image, which I installed without problems recently there is only a vboxvideo folder and driver no w8 addendum one.
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by socratis »

There's something wrong with your VM, I don't/can't know which part.
00:00:00.668115 File system of '/home/pwein/VirtualBox VMs/Windows10/Snapshots' (snapshots) is unknown
00:00:00.671165 File system of '/dataInternExt4_I/VM/winVirtualBox.vmdk' is ext4
00:00:00.668142 File system of '/dataInternExt4_I/VM/Windows10.vdi' is ext4
Why isn't the VM's HD in the default location? Why there's a second VMDK there?
00:00:00.686969 CpuExecutionCap <integer> = 0x000000000000005a (90)
00:00:00.686975 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:00.908239 CPUM: Physical host cores: 4
You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). Lower the CPUs to 2, and take the ExecutionCap to 100%.
00:00:00.687266 VMSVGAEnabled <integer> = 0x0000000000000001 (1)
I don't know why this is set like that. I guess it has to do something with you messing around with the VBOX directly... Don't.
00:00:00.882920 AIOMgr: Endpoint for file '/dev/sda1' (flags 000c0723) created successfully
00:00:00.882985 AIOMgr: Endpoint for file '/dev/sda2' (flags 000c0723) created successfully
Not sure what you're doing here, but are you attaching the '/dev/sda1' and '/dev/sda2' in the VM?
00:00:09.823059 VMMDev: Guest Additions information report: Version 5.2.0 r118431 '5.2.0'
And to top it off, you still have the old Guest Additions (GAs).

I suggest you start from scratch. Clean your host. If necessary clean/purge everything (except the VMs) and install a fresh 6.0.0 official VirtualBox, this is about 6.0.0 not a misconfiguration after all. Download the official Win10 ISO. Create a new VM. Stick with the defaults. Try it like that...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

@socratis

Thank you for your tips! In the end I created a new Windows image, and it works and astonishing, it works with 5.2 and with 6.0 (with installing the related guest additions , in the latter one v6.0.4)

But my old image is destroyed! That was my assumption from the beginning. Isn't there a way of completely cleaning up the windows target system from guest additions? It is not not longer installed... but I assume the problem was first that I run the target system with the wrong guest additions, than tried to deinstall it and finally got no way to remove it completely.

6.0.4 then every time hangs during installation with the above error. But it has clearly nothing to do with the host system, because this works now with 6.0 and another windows distribution (actually it is the same minus some programs like my tax and anti virus software...).

Do you have had any experiences pointing in that directions?


Another naughty problem only occuring with the new host system:
Ubuntu 16.04 host: If I shift the VM Box Manager to my second monitor, the resolution of the used fonts changed and it is unreadable small. Do you know this feature as well?
peddanet
Posts: 9
Joined: 3. Oct 2017, 15:29

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by peddanet »

Meanwhile I have repaired Windows: System data recovery, also have reinstalled the image iso (complete repair/reinstall program of windows 10 home), no effect.
I have diffed the two configurations, and merged the differernces likely but no effect.

It always have driver problems when looking into the

Log in "good" windows" version:

Code: Select all

(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00" using INF "C:\Windows\System32\DriverStore\FileRepository\vboxguest.inf_amd64_c50a273df32834ff\VBoxGuest.inf".
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxWddm.inf' (Plug and Play).
(1) 0 - Looking for Model Section [Model.NTamd64.6.0]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00" using INF "C:\Windows\System32\DriverStore\FileRepository\vboxwddm.inf_amd64_ec29ed0af7521b99\VBoxWddm.inf".
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(

Log in bad windows version:

Code: Select all

(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxguest.inf_amd64_fbdad43efe6399c8\VBoxGuest.inf".
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxWddm.inf' (Plug and Play).
(1) 0 - Looking for Model Section [Model.NTamd64.6.0]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxwddm.inf_amd64_cfe87e81d2b9ba78\vboxwddm.inf".
(1) 0 - Installation did not occur because the hardware isn't currently present.
(1) 0 - Marked Phantom Device with Hardware/Compatible Id 'PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00' for reinstall on next plug-in.
(1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\WINDOWS\System32\DriverStore\FileRepository\vboxwddm.inf_amd64_cfe87e81d2b9ba78\vboxwddm.inf'.
(1) 0 - RETURN: DriverPackageInstallW  (0xE000020B)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxguest.inf_amd64_fbdad43efe6399c8\vboxguest.inf".
(1) 0 - Will force install because driver is not better and force flag is set.
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxWddm.inf' (Plug and Play).
(1) 0 - Looking for Model Section [Model.NTamd64.6.0]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxwddm.inf_amd64_cfe87e81d2b9ba78\vboxwddm.inf".
(1) 0 - Installation did not occur because the hardware isn't currently present.
(1) 0 - Marked Phantom Device with Hardware/Compatible Id 'PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00' for reinstall on next plug-in.
(1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\WINDOWS\System32\DriverStore\FileRepository\vboxwddm.inf_amd64_cfe87e81d2b9ba78\vboxwddm.inf'.
(1) 0 - RETURN: DriverPackageInstallW  (0xE000020B)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxguest.inf_amd64_f4ec6b27e8b64243\VBoxGuest.inf".
(1) 0 - Will force install because driver is not better and force flag is set.
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxVideoW8.inf' (Plug and Play).
(1) 0 - Looking for Model Section [Model.NTamd64.6.2]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxvideow8.inf_amd64_a4cb093f54329ecf\VBoxVideoW8.inf".
(1) 0 - Installation did not occur because the hardware isn't currently present.
(1) 0 - Marked Phantom Device with Hardware/Compatible Id 'PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00' for reinstall on next plug-in.
(1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\WINDOWS\System32\DriverStore\FileRepository\vboxvideow8.inf_amd64_a4cb093f54329ecf\VBoxVideoW8.inf'.
(1) 0 - RETURN: DriverPackageInstallW  (0xE000020B)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxguest.inf_amd64_f4ec6b27e8b64243\vboxguest.inf".
(1) 0 - Will force install because driver is not better and force flag is set.
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxVideoW8.inf' (Plug and Play).
(1) 0 - Looking for Model Section [Model.NTamd64.6.2]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxvideow8.inf_amd64_a4cb093f54329ecf\vboxvideow8.inf".
(1) 0 - Installation did not occur because the hardware isn't currently present.
(1) 0 - Marked Phantom Device with Hardware/Compatible Id 'PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00' for reinstall on next plug-in.
(1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\WINDOWS\System32\DriverStore\FileRepository\vboxvideow8.inf_amd64_a4cb093f54329ecf\vboxvideow8.inf'.
(1) 0 - RETURN: DriverPackageInstallW  (0xE000020B)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_CAFE&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxguest.inf_amd64_f4ec6b27e8b64243\vboxguest.inf".
(1) 0 - Will force install because driver is not better and force flag is set.
(1) 0 - ENTER UpdateDriverForPlugAndPlayDevices...
(0) 0 - RETURN UpdateDriverForPlugAndPlayDevices.
(1) 0 - Installation was successful.
(0) 0 - Install completed
(1) 0 - RETURN: DriverPackageInstallW  (0x0)
(1) 0 - ENTER:  DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxVideoW8.inf' (Plug and Play).
(1) 0 - Looking for Model Section [Model.NTamd64.6.2]...
(1) 0 - Installing devices with Id "PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00" using INF "C:\WINDOWS\System32\DriverStore\FileRepository\vboxvideow8.inf_amd64_a4cb093f54329ecf\vboxvideow8.inf".
(1) 0 - Installation did not occur because the hardware isn't currently present.
(1) 0 - Marked Phantom Device with Hardware/Compatible Id 'PCI\VEN_80EE&DEV_BEEF&SUBSYS_00000000&REV_00' for reinstall on next plug-in.
[b](1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\WINDOWS\System32\DriverStore\FileRepository\vboxvideow8.inf_amd64_a4cb093f54329ecf\vboxvideow8.inf'.[/b]
(1) 0 - RETURN: DriverPackageInstallW  (0xE000020B)
jj_0
Posts: 1
Joined: 17. Apr 2019, 17:35

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by jj_0 »

FWIW, I had the same or similar issue. I resolved it by uninstalling the Guest Additions from the W10 guest, shutting down, turning off 2D and 3D acceleration. After that starting the W10 guest worked for me and I could reinstall the 6.0.6 Guest Additions. Turning on 2D and 3D acceleration after that didn't break it again, so I'm not 100% sure this is the proper solution...
When it didn't work I only had the Microsoft Basic VGA adapter. After the reboot I had the VirtualBox Graphics Adapter (WDDM).
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Update to 6.0.0 caused my Windows 10 image not to resolute anymore the 2 monitors (#18255)

Post by socratis »

@jj_0
The OP was using 6.0.0, you're using 6.0.6.
Maybe the problem got fixed somewhere between start of January and mid April... ;)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply