FAQ update regarding windows 11 24H2

[tmtm24680135]

<!-- PLEASE READ THIS CAREFULLY:

1. You MUST read and complete the steps from the checklist below, by placing an x into each [ ] (so that it shows '[x]', NOT '[ x]' or '[x ]'), BEFORE clicking on 'Submit new issue'.

2. Failure to perform these steps, WHICH ARE ONLY THERE TO HELP YOU, will usually result in your issue being dismissed without notice.

3. If you are reporting an issue when trying to run Rufus, or when trying to boot a media created by Rufus, you MUST provide a log, period. Please do not assume that the developer(s) will be able to "guess" the specifics of your environment, what image you used, what type of media you used it with or the many many other critical parameters that the log provides data for. To investigate an issue, a log from Rufus is ALWAYS required.

4. If you still choose not to provide a log when reporting a problem, you agree that your issue will be closed without any further investigation.

YOU HAVE BEEN WARNED. -->

Checklist

• [ ] I have been made aware that if my problem can be summarized as "I've created or tried to create a media using Rufus, and ...", and I am not including a log, this issue will be summarily closed.
• [x] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
• [x] I performed a search in the issue tracker for similar issues using keywords relevant to my problem, 24H2
• [ ] I clicked the 'Log' button (🗒️) or pressed Ctrl-L in Rufus, or used DebugView, and copy/pasted the log into the section that says <FULL LOG> below.
• [ ] The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

Additionally (if applicable):

• [ ] I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
• [ ] I also tried one or more of the following:
  • [ ] Using a different USB drive.
  • [ ] Plugging the USB into a different port.
  • [ ] Running Rufus on a different computer.
• [ ] If using an image, I clicked on the (✓) 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

It seems that version 4.6 has added support for Windows 11 24H2, but the FAQ (https://github.com/pbatard/rufus/wiki/FAQ#this-pc-doesnt-currenty-meet-windows-11-system-requirements) still implies it is not supported. If 4.6 indeed supports Windows 11 24H2, maybe that FAQ entry should indicate that release 4.6 is required for Windows 11 24H2 and support for Windows 11 releases after that are TBD. Log --- ``` ```

[pineapple63]

The FAQ entry is to do with checks that Rufus does NOT bypass Microsoft does not provide a registry key to bypass those checks (PopCnt and SSE4.2), and if you do try to get around those checks, the upgrade will fail (and worst case the system may even crash)

[pbatard]

As @pineapple63 explained, it just appears that you misread the FAQ entry and interpreted it to mean that anybody who tried to upgrade to 22H4 using Rufus 4.5 will see the error dialog, whereas this is an entry for people who might still get an error, with the error dialog, when using Rufus 4.6.

The FAQ entry makes no condition about the version of Rufus, and simply provides info about what it means, regardless of the version of Rufus you used to perform the upgrade, if you see the error.

[tmtm24680135]

I definitely did not realize windows 11 24H2 starts enforcing requirements that cannot be by passed which had built-in auto-bypass - maybe the FAQ entry title can be changed to reflect this to reduce confusions like mine.

The commit (https://github.com/pbatard/rufus/commit/98a42a235f67f6e535b6ab07c23bd4eb5f8ba770) included in version 4.6 did help forming my tunnel vision. I just test version 4.6 with W11 24H2 on my machine and it is working - thus I was seen the memory and tpm checks which happens also to be two checks:-) Thanks for all the great work.