Different UI interface from Windows Setup when using Rufus 3.19 #1971
Comments
|
That's just what happens when an If you want to see the original screen, you need to uncheck the first two options (Secure Boot/TPM 2.0 bypass and 4 GB+ RAM/64 GB+ disk bypass) when being asked by Rufus. |
pbatard
changed the title
|
Because this is something I was pondering about doing, mostly because you also get a command prompt briefly appearing while the bypass for Secure Boot/TMP/Disk/RAM are applied to the registry, I have now restored the ability for Rufus to patch the registry keys directly and disable the Note however that this will only work for the regular version of Rufus and not the Windows Store version (which is the reason we changed the way we inserted the registry keys in 3.19 in the first place, because Microsoft restricts the ability of Store apps from editing an offline registry). |
|
Rufus 3.18 does not change the original boot image when selecting Extended Windows 11 Installation (no TPM / no Secure Boot). |
|
That's what I'm saying. Again, "the reason (why) we changed the way we inserted the registry keys in 3.19 in the first place (is) because Microsoft restricts the ability of Store apps from editing an offline registry" which implies that Rufus 3.18 did not change it, since, as I also explained "Microsoft (decides if it) shows one type of screen or the other according to whether it detects a windowsPE pass in the unattend.xml" which is the part we added to 3.19. The fix I just added to the upcoming Rufus 3.20 restores the behaviour of Rufus 3.18 for the non Windows Store version (since we can't do anything about the Windows Store version and must set the registry keys in unattend.xml, which leads to the setup screens being altered). |
|
Thank you for your answer for me the original UI from Windows Installer is very important in VMware I am doing update integrations in SysPrep state and I need to have Repair your computer option.
Sorry for my english but I use an interpreter.
I think Rufus 3.20 will be better.
|
|
Well, because of new issue #1981, it looks like I'm going to be forced to revert the workaround I was planning to apply in Rufus 3.20 in order to restore the default initial Windows Setup screens, because it turns out that it is not possible to bypass the MSA requirement of Windows 11 without also having a In short, the only way you'll be able to get the default UI screen is you make unselect ALL the bypass options when creating the media, because I currently see no cost/effective solution where we can avoid using a I'm still looking, but I'm really not optimistic at this stage... |
…ss is also selected * In a manner that defies logic, Microsoft designed Windows setup to parse Autounattend.xml for windowsPE tasks in the PE environment, but only carry out the copying of that file to %WINDIR%\Panther for subsequent processing with the other passes *IF* there exist an actual windowsPE section. * In short, when using the Autounattend.xml method, Microsoft have made all passes there dependent on the existence of a windowsPE pass, regardless of whether that pass has any use or not. * Working around this would be fine and all (just add an empty windowsPE pass so that the later passes get executed) if the absence of a windowsPE pass didn't also determine whether the user will be presented with the default Windows setup screens that include the "Repair your computer" option or a completely different set of screens (c.f. #1971). * This means that, to keep users happy, we need to add yet another method to carry out tasks that should have remained the realm of boot.wim's Autounattend.xml, and instead create a \sources\$OEM$\$$\Panther\unattend.xml when there are no windowsPE tasks (on account that setup copies anything found under \sources\$OEM$\$$\ to %WINDIR%\). Only through this can we have the specialize and oobeSystem tasks actually carried out (for bypassing MSA requirements of skipping the data collection screens) while keeping the original Windows Setup look and feel. * Closes #1981
|
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. |
Why Rufus 3.19 changes the windows 11 boot window after applying the changes.
The original boot image is pictures 1 and 2
After applying the changes, there is no option from photo 2 "Repair your computer"
There are photo windows 4, 5 and 6.
How to restore windows from photos 1 and 2 after applying changes by Rufus 3.19
The text was updated successfully, but these errors were encountered: