@Jose89: Like it says - you need admin rights. We don't do Windows tuition here so we won't go into details (Google will have those). In the meantime note that you can use "Run as adminstrator" to run the installer with elevated (admin) rights, if you have access to an admin password. If this was an unattended OS install and you didn't even look at the startup dialogs then the default password was "changeme".
And p.s. this was a not a 7.0.12 specific issue. Please only use this topic to discuss new matters arising from the 7.0.12 release.
Beside the flickering search menu, there are other 3d acceleration issues in the new impletention.
The canvas in paint 3d does not show up, and ms solitaire collection app does not initiate at all.
`
The workaround is `VBoxManage setextradata "Win10Test" "VBoxInternal/Devices/vga/0/Config/VMSVGA10" "0"`, and the issues above are gone now and I can even play ms solitaire collection without problems.
For those with 3D issues with Windows VMs: At least the flickering should be fixed with the latest 7.0 test builds. Update both the host package and Guest Additions inside the VM.
drm/vmwgfx: Print errors when running on broken/unsupported configs
virtualbox implemented an incomplete version of the svga device which
they decided to drop soon after the initial release. The device was
always broken in various ways and never supported by vmwgfx.
vmwgfx should refuse to load on those configurations but currently
drm has no way of reloading fbdev when the specific pci driver refuses
to load, which would leave users without a usable fb. Instead of
refusing to load print an error and disable a bunch of functionality
that virtualbox never implemented to at least get fb to work on their
setup.
Does this mean 3d accel with vmsvga will completely useless in later kernel version if virtualbox does not take any actions?
Don't ask me for the correlation between the very misleading commit message and what the change actually does.
In the end this change just disables the VMware-specific message logging and adds some messages to the kernel log but other than that I see no disabling of functionality.
I just upgraded to VBox 7.0.12 and upgraded the VM Guest Additions on my two Win7 vms. Both are now broken. One gives errors just at the login screen, the other won't boot at all. Ouch!
No need, the guest additions signing issue was solved in the test builds.
Download them from here: https://www.virtualbox.org/wiki/Testbuilds
install the new guest additions and it's gonna work