Drag and drop the Windows 8 ISO into the New Virtual Machine Assistant. Launch VMWare and click on New. Move the Windows 8 ISO file to your Mac OS X desktop. This has been confirmed to work in both Mac OS X 10.6 Snow Leopard and Mac OS X 10.7 Lion.Next I ran wsl -set-version Ubuntu 2 which didn't work it said Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. I tried to do the same for Windows Hypervisor Platform and Windows Subsystem for Linux but they were already installed. Then installed Hyper-V through dism and restarted. I rolled back my Windows to version 19541. Actually I was now just able to manually enable all the features needed to run WSLv2 on latest insiders build (1)! I tried this and it didn't work for me.
![]() dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestartWill keep hanging at splash screen until safe mode is entered, which reverts the dism command(s). dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart Open explorer, follow prompts to download the new Edge browser (*probably not necessary to reproduce, but it's what I did all 3 times this happened to me.) Accept all updates from Windows Update, which required a reboot. Do fresh install of build 19041 from USB Fix Vmware Workstation Looping On Reboot Virtual Hine Drivers And FoundSince my system did not work well without the driver, I decided to live with the issue and not use WSL 2.Today, after reinstalling Windows 1909 in another attempt to fix the issue, I found that it was fixed and I could boot with virtualization enabled. The fan runs at full blast and the shell never starts.I did some bisection with system drivers and found that when I disabled atikmpag.sys, the AMD integrated graphics display driver, the system booted fine with virtualization enabled. I am not 100% sure it is the same problem, but on the off chance it is, I would like document my experience.Booting Windows results in it hanging on a black screen after the progress circle when virtualization (AMD SVM) is enabled in the BIOS. (UPDATE: I have since spent many hours trying to reproduce this brief initial success but did not find any way to do it.)I have been encountering a problem like this since September 2019 both on stable and Insider versions of Windows and have only just found this issue. I did not have this issue when I installed 2004 via the Update process. In every combination I tried, I was left with a binary choice of enabling Virtual Machine Platform and not being able to boot, or not enabling it and not being able to use WSL.Clearly many other users are in fact using WSL 2 successfully, leading me to wonder whether the issue is about a specific incompatible driver or other quirk on my machine or is about a subsequent patch to Windows or WSL that has made it impossible for new WSL 2 users to get past the initialization stage.My initial, one brief success may have hinged on either something I installed/configured during my regular use of the machine that was lost once I did a fresh install or perhaps was enabled by being prior to some system firmware update being applied (do the Intel microcode updates work that way?)I am not savvy on debugging windows boot issues so do not know how to proceed further. I will attempt to debug the issue once my cable arrives in 2 days' time.( The BIOS on my Gigabyte Aero 15 does not offer a Fast Boot option one way or another.)I've spent many hours since my last post trying to find a successful combination of build version, updates taken or skipped, updating or not updating drivers on my own, and previously installing WSL 1 or not. I updated to the Fast ring, build 19631.1, and the issue continued to appear.My uneducated guess is that having SVM and the Virtual Machine Platform enabled means something is triggered in atikmpag.sys to make the system hang during bootup. Visual studio for mac dotfuscatorThat hack lets me survive the reboot following enabling VirtualMachinePlatform, which lets Windows complete its setup, and gets me access to the wsl console command. That let me boot when I installed VirtualMachinePlatform.Interesting. I tried it, but no difference.Try turning off virtualization/VT-x/d in the BIOS. Given it is reproducible on at least my machine I feel like someone in QA should confirm whether the documented install procedure works on a fresh install of build 19041 with the current applicable updates on at least some machines.The Fast Boot option in Windows is located in Control Panel > Power Options > Choose what the power buttons do (on the left side).Oh! Thank you. Maybe I'll try again next weekend.Thanks, you save my day. Let me know if you're open to that and I can give you more details!Thank you for the offer! Having spent my weekend on this issue as it is, it's past due for me to return to current work, and that process does not sound quick. I rebooted, re-enabled VT-X, but was right back at the hang on boot problem.You could try the driver bisection method I mentioned in my earlier comment to diagnose if it's a driver thing, but it's very annoying and requires manual registry editing. But when I go to the Store after that and go to the Ubuntu page, it hangs on a spinning circle. So, we all came to GitHub to try to get attention. Exactly how many responses have we gotten to those initial reports over the years? You guessed it, zero!Then, not only did the next dev release not fix it, Microsoft went on to eventually cut a GA release of Windows that still had the broken change in it. When it happened, I and several others put in feedback on the Feedback Hub. I can boot into I'm sorry, but that response is at the entirely infuriating level of what the hell?Several years ago, in a developer release, Windows went from working perfectly with this brand new WSL2 to all of the sudden not working. After enter bios and disable AMD virtualization. Then suddenly, either the result of a BIOS update or drivers or Windows update or some combination thereof, the machine would not boot. Hopefully he'll keep us updated moving forward.WSL2 did work on my very costly Dell 2-in-1 for a bit on Windows 10 (I don't recall the precise build) - this was not a fresh install, but the result of the gradual updates since I've owned the machine, only about 1.5 years old now. Of-freaking-course we have been doing this for YEARS now.Shihab, about all I can offer at this point, is well, empathy.Craig Loewen kindly reached out, but did not spot any problematic drivers MS is currently aware of. Like we have control over what the manufacturers release. Hell, we've asked, begged, pleaded with you to just buy a device we pointed out we know to no longer work to figure out what was changed that caused this breakage to then be able to guide the manufacturers on how to fix it.Instead, we get "update your drivers"! pffft.
0 Comments
Leave a Reply. |
AuthorCecilia ArchivesCategories |