Installing W10 warns for non compatibity of WDDM

[NMe]

Hello,

I have video troubles when upgrading a guest from W7 x32 Home to W10 x32 Home.

Host machine :
DELL XPS 17
i7, RAM 8Go
SSD 512 Go
video : Intel HD Graphics 3000, updated from Intel
NVIDIA GeForce GT 555 M 1600 x 900, updated from NVIDIA
W10 x64 Pro
VB v.6.1.0 r135406

Guests :
VM#1 : W10 x32 Home, Guest add v.6.1.0 r135406, 3D installed (VBoxSVGA, WDDM)
Upgrade from W7 to W10 2 days ago
Works OK (W7 then W10)

VM#2 : W7 x32 Pro, Guest add v.6.1.0 r135406, 3D installed (VBoxSVGA, WDDM)
Works OK (W7)
Installing W10 warns for non compatibity of WDDM !

Any suggestion to test why this particular VM fails, when host and other VM work OK ? (and an another couple host + VM works also ; all regularly licenced with different Windows 7 licences).

If required, I join the last logs and définitions

Thanks again,

NMe

[scottgus1]

Try this web search:

Windows 10 WDDM site:forums.virtualbox.org

Maybe someone has a similar issue with a solution? I don't know how to solve this myself, unfortunately.

[NMe]

Thank you for answer.

I "googled" on VirtualBox Forum and elsewhere.

For this specific issue (WDDM stated non compatible by W10 installer), I notice than Windows type (x32/64, Home/Pro) is rarely defined.

My own experience is :

- With 2 hosts ("hard" machines), x64, Windows Pro (W7 to W10), after updating graphics drivers from official sites (Intel, NVIDIA), W10 x64 Pro install succeded (despite a few errors, stops and re-installs, which show some reliably of the W10 install process) ;

- With 2 guests (virtual machines), x32, Windows Home (W7 to W10), in the previous hosts and after W10 installed, W10 x32 Home install succeded (and, again, despite a few errors, stops and re-installs ) ;

- With 1 guest, x32, Windows Pro (W7 to W10), W10 install warns for WDDM non compatible.

Could be possible than control of WHQL may be different between x32/x64 and/or Home/Pro combinations ? Or than WDDM (VBosDispD3D.dll) presents different tags to control ?

Comparing dxdiag.exe (W10 version) in one of the guests running successfully W10 x32 Home, and comparing with dxdiag.exe (W7 version) in the guest W7 x32 Pro to upgrade, I did not see any signifiant (for me) difference, letting me think than VirtualBox part is correctly installed. Log confirms than WDDM is not WHQL signed, but the two W10 x32 Family guests run fine anyway.

I should test again, confirming unsigned WDDM.
However, previous errors and tests seem indicate than W10 install failed when I confirm unsigned driver.

VirualBox version is 6.1.0 r.135406, VB Extensions and Guest Additions corresponding.
Installs from Microsoft ISO Windows 10 Home and Pro on USB key (one for x32, one for x64).
Joined, the 2 dxdiag.exe logs.

Many thanks,

NMe

[scottgus1]

That's a lot to try to digest. Let's clarify one thing:

after updating graphics drivers from official sites (Intel, NVIDIA)

Where are you updating these graphics drivers, in the physical PC or in the Virtualbox guest OS's?

FWIW I seem to remember way back in 2017-ish when the 'get 10 free for a year' buzz was happening, folks may have had to do two things before trying to upgrade 7 & 8 guests to 10:

1. uninstall Guest Additions and shut down.

2. change the guest type in the guest's General settings to Windows 10.

3. try the upgrade.

[NMe]

Thank you to consider my problem.

1/I updated Intel HD Graphics 3000 from the official Intel Update Site. NVIDIA GeForce GT 555M has beeb updated from the Official NVIDIA site. Luckily, each of them had an update. Updates on the physical host, before to upgrade to W10.

2/Euhh, my english is a litte bit weak ... What do you mean by FWIW ... ?

Uninstall Guest Additions seems a way. I tried, but I had to restore the VM. "Abrupt" uninstall GA in the VM suppresses display. I assume it exists a "soft" method ?

As I said previously, I tried to force (confirm) non compatibility. The VM is now W10, but only with Microsoft base video.

Please have a look on two printscreens, comparing the 2 VMs.

Many thanks,

NMe

[NMe]

Solved :

In the guest (after upgrading to W10) :
1/Manually share the folder "CD reader (D:) VirtualBox Guest Addtions" ;
2/Execute setup.exe as an administrator.

The drivers are actually replaced, and W10 uses them as they should be.

Nevertheless, Windows Explorer marks this folder as unconnected (small bottom right red cross).

Hope it is a reliable solution.

If that can help ...

NMe

[scottgus1]

Good that you found a solution!

I'm going to guess that this:

Execute setup.exe as an administrator.

is the deciding factor. I'm not sure what part of the whole issue the folder sharing is supposed to handle, but I do know that sometimes Windows just doesn't do what it's supposed to do unless you install via Run As Administrator.