@Akeo Thanks a lot. Do we still need to disable Secure Boot during installation if the ISO was larger than 4GB in GPT/UEFI mode?
@Akeo Thanks a lot for your hard work and for the best tool made ever since sliced bread. Quick question, do we still need to disable Secure Boot during installation for ISOs that are above 4GB as it was in the past few versions?
Err, are you going to be asking that every time there's a release now? Because, no offence, but it's going to grow old really fast... If you don't see any news of the contrary then you should assume that any existing behaviour is unchanged.
I would humbly suggest updating the first post - or, asking to have this thread archived, such that you can start one where the first post identifies current releases. I'm loving Rufus - enough that I'm going to make a donation to FSF in your name as a result.
@user_hidden started this thread, maybe @Yen or someone else in the staff could transfer ownership for editing OP to @Akeo Food for thought
I am, but updates to WppRecorder.sys as part of KB's are completely pointless as the issue is with what happens when you use the WppRecorder.sys that comes from an ISO. As long as Microsoft hasn't released a retail ISO, that people can download, with an updated WppRecorder.sys, what they do during in their in-band updates is irrelevant and has no impact whatsoever on fixing the Windows To Go problem. Now, the minute you tell me there exists a new retail ISO that people can freely download, with an updated WppRecorder.sys, then I'm interested...
For what is worth, I have just tested Windows To Go using on of the latest Window 10 19H1 insider ISOs (Windows10_InsiderPreview_Client_x64_en-gb_18343.iso) and it looks like Microsoft have fixed that WppRecorder.sys issue.
Not completely pointless, at least you can install update before the first boot using dism/powershell to solve the bug or even repack the install.wim w/ the update but it is more work to do.