-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Windows User Experience dialog does not display when Partition scheme is set to MBR #1956
Comments
Ah I see. You need to make sure that partition scheme is set to GPT, then you'll see it. I'll try to fix MBR for the release. |
ok |
Fix has been applied for the release, but I will keep this issue opened for visibility. |
I have selected GPT as the partitioning scheme in Rufus 3.19.1906 BETA with Windows 11 install media and still doesn't show the Windows User Experience Dialog after clicking START, it just starts formatting and writing the image to the drive without asking anything else except confirmation. |
@leonsk29, you should have seen it with GPT.
|
Also where exactly did you get your Windows 11 ISO? |
You're right, I didn't remember that was a custom ISO involving Windows 10 setup media with a Windows 11 image. Now I tested it with a proper Windows 11 22H2 ISO and it shows up. So sorry for bothering you, my mistake. Best... utility... ever. Thank you! |
Thanks for the update, no worries. A Windows 10 setup will definitely screw our version detection since we look into For the record, you want to see something like |
Hi Where i can get the 3,19.1907 Fixed version ? |
You will get it when Rufus 3.19 is officially released on July 1st (or later). If you really can't wait, you can always pick the ALPHA build from the MinGW Artifcats. |
Please don't close this issue. It is fixed, but I want to leave it open for visibility until the release. |
Locked, as I already explained why I want to keep that issue opened, and appear to be ignored. |
Closing this issue with the release of Rufus 3.19. |
Has the tpm bypass feature been removed in beta version?
The text was updated successfully, but these errors were encountered: