Closed EhabEldeeb closed 1 year ago
EhabEldeeb
commented
1 year ago Update: 2 more logs added: 3.20 did not ask me for any User Experience options (even tho it's written in changelog), and it worked fine 3.21 is where the issue started, it asked me for options, and it did not go through.
pbatard
commented
1 year ago 3.20 did not ask me for any User Experience options
On account of this from your log:
Could not locate file sources/compatresources.dll in ISO image
That 7.7 GB ISO is doesn't look official, or at least, it is definitely not a retail Windows ISO, so please don't expect the same level of support as official retail Windows ISOs. Where exactly did you obtain that image? I did change the method of detecting the Windows version from the ISO in 3.21, which we need to do to be able display the Windows User Experience dialog, which accounts for 3.20 not prompting you (because it couldn't read the version from compatresources.dll and 3.21 prompting you about it, since it was able to do so (Detected: Windows 10 ISO (Build 19041.2006)).
But I'm not seeing much of anything wrong with your logs so I would STRONGLY encourage you to try with a retail Windows ISO, such as the one you can download from Rufus (see here) as I will only investigate this matter if you confirm that you are seeing the same issue with official retail ISOs. Oh, and I would very much like a log from version 3.22 to see what options you picked in WUE (3.21 and earlier won't show that but 3.22 and later do).
pbatard
commented
1 year ago Also what happens if you don't select any option on WUE? Have you tried that?
I'm also a bit surprised that Windows 10 22H2 from MCT would report Build 19041.2006, whereas retail 22H2 version should be 19045.2006, though I guess Windows version reporting has always been screwy (which is why I had to change the method we used to detect it).
Oh and more importantly, what BIOS and UEFI systems did you try. I see you have both x86 and x64 installation images in your ISO, so are you booting x86 UEFI or x64 UEFI?
pbatard
commented
1 year ago I have now created a dual x86 Windows 10 22H2 from MCT and I am seeing no issue when it comes to dual BIOS + UEFI boot using Rufus 3.22. This means that I did test that a Rufus created media from that ISO could boot in either BIOS/Legacy or UEFI mode.
From the logs you provided it does look to me like you did not enable dual BIOS+UEFI boot with Alt-E, otherwise you would see Using Windows 7 MBR in the log rather than Using Rufus MBR as you do.
I have no idea why your 3.19 worked for dual boot, and I can't say I am that interested, when it does look to me like you might be under the impression that Rufus creates dual BIOS+UEFI drives by default (like the MCT does), whereas, as explained in the FAQ it won't unless you use the Alt-E cheat mode (or you happen to create a BIOS/Legacy only media, but have a UEFI firmware that includes an NTFS driver, since the use of NTFS is really all that's preventing UEFI boot).
As I am not seeing anything for me to do here, and I am especially not seeing any signs of regression when testing with the same ISO as the one you should be using, I will close this issue.
EhabEldeeb
commented
1 year ago Answering your questions in order
No
i might have downloaded it a bit earlier than the current version
booting x64 UEFI
i do press Alt-E .. maybe i have forgotten in the last one? i've been trying various versions of rufus
i will try one more time without choosing any WUE using rufus 3.22
thanks for your prompt reply 🥇
github-actions[bot]
commented
1 year ago This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
Windows 10 22H2 2in1 ISO downloaded from MediaCreationTool is working with dual boot (BIOS and UEFI) until Rufus version 3.19, and it shows me the error "No device drivers were found" with newer versions. (same USB, same port, same PC using rufus, same target machine, ---- 3.19 works, further versions are not working)
suspected: ver 3.20 "Windows User Experience options for Windows 10" might have broken something on the way...
I will attach log file for version 3.19 (which is working fine) another log will be provided for 3.20+ to be provided if required.
Log