Although one user at the end of the thread in late October reports that they were still seeing this problem.
Windows 10 virtualbox loop update#
I know for certain that I booted this VM back in July and I didn't have any issues with the driver.īut in any case, this pretty much confirms that I'm seeing the same issue as these previous users, it's just that a VirtualBox update fixed it for most of them and not for me.
(It didn't hang, just gave me an error about not being able to load the driver.) This is kind of weird because the versions are from July. They worked fine, although I had to switch from xHCI to OHCI to get it to boot. I also decided to try the old kernel and VirtualBox suggested in this comment. This is with the retail 2019 LTSC, which is also based on v1809. Unfortunately, I already deleted the newer version so I can't double-check. Run NETPLWIZ, go to Advanced tab, then check 'Require users to press Ctrl+Alt+Delete' and click OK or Apply. Just to confirm, I inserted the older ISO to the virtual CD drive of my existing Windows 10 installation and it successfully booted into the live medium. Requiring Ctrl+Alt+Delete to unlock the PC lets you use 'Windows spotlight' as the lock screen background without seeing ads. I had to go thru the long update process though, which I was trying to avoid by downloading the latest installer.
Windows 10 virtualbox loop install#
I was able to install and boot the installed Windows with no problem at all. However, using an older ISO (Win10_1809Oct_v2_English_圆4) worked. Which specific Windows ISO are you using?Ībout a month ago, I tried to install Windows 10 on a VM using the most recent (at the time) ISO from the Microsoft website. I haven't tried reverting back to old kernel versions and old versions of VirtualBox yet, because the ones reported working in these other threads are quite old at this point and I'd like to avoid that if at all possible. Switch from the prebuilt host modules to the DKMS modules. Things I have tried to do to fix the problem (based on suggestions in the other threads):Ĭhange the USB controller version from USB 3.0 to USB 2.0 or USB 1.0.ĭisable the network adapter entirely (some posts claim the issue is with using the bridged adapter, but I'm using NAT).Ĭhange the graphics controller, disable 3D acceleration, enable / disable PAE, enable / disable hardware acceleration. When I attempt to reboot the computer, it hangs at the end of the shutdown process, requiring a physical poweroff and restart.
The process becomes a zombie consuming 100% of one CPU core.
0 kommentar(er)
