-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Machine hangs on "Booting Windows..." #109
Comments
It could be anything - every motherboard manufacturer seems to have its own quirks. I'll try to get hold of a Thinkpad to test. |
Noted, thank you. Is there anything I can do on my end in the meantime? |
Probably not, unfortunately. I'll let you know if I think of anything. |
This looks similar to #87 and #88.
I have got a OBS Studio recording of what I've witnessed, I thought a minute of recording is enough to show it hangs as the previous VM boots under that. 2024-06-08.21-54-16.mp4 |
As a last resort, I attempted building Quibble from main. 2024-06-08.22-28-25.mp4 |
Update: This also applies to NTFS installations, they won't boot with Quibble |
I added the NTFS driver from Quibble 20230328 to every other Quibble and attempted booting them under VMware. |
Update: LTSB 2016 made non-bootable by updating before conversion |
actually I just can't get it working anymore |
I have been working on this for half the day and I'm just about to call it quits. My machine is a Thinkpad T530 with the 1vyrain firmware mod, 360GB SATA SSD, 8GB of DDR3 RAM, and an Intel Core i5-3320M CPU. The partition scheme currently consists of my ESP, 8GB of Linux swap, 49GB Linux root (Fedora), 114.3GB Linux home (fedora) and a 163.3GB partition of Windows 10 22H2 which was freshly converted from NTFS to BTRFS. I made sure to install the driver(s) before trying Quibble, and have tried both specifying UUIDs and the default Microsoft method in the freeldr.ini configuration file. The latter works, and only lets me get to the Booting Windows... prompt. What else could I do here? Quibble and all the necessary files are on the root of my ESP, if it's in a subfolder it refuses to boot windows with a corrupt EFI error.
The text was updated successfully, but these errors were encountered: