Issue Checklist
Provide a clear and concise description of the issue.
I opened this issue to bring attention to the matter as I've made these observations over the last week while rinse-repeating MicroWin, making bootable ISOs and performing 10/11 installations.
I have tried to use a pre-made account with MicroWin, only to have to make one during user setup after MicroWin is installed.
So far, between Rufus and Ventoy - Rufus is the only software solution for bootable ISO USB installation media that works for MicroWin 10 & 11.
Steps to reproduce the issue.
My theory is that Rufus' "Windows User Experience" prompt right before making the bootable USB clears the account information by MicroWin. See example of Rufus prompt here:
It seems highly likely to me that Rufus clears/modifies any pre-configured account information from the ISO after pressing OK, Even when the box is unchecked, the pre-created MicroWin account doesnt appear. At the moment, there is no way to disable this prompt (as far as I know) in Rufus, and it is required to go through that prompt in order to initiate the media creation process.
Assuming that Rufus is performing the same instructions as MicroWin for these specific options, Rufus most likely sets the password to be empty (no password) when a username is entered and the choice selection is checked (after the user presses ok). Rufus is probably resetting account info and other options when boxes are unchecked in order to ensure that the instructions are fulfilled accordingly, hence the MicroWin customisations restored to default values.
Paste the full error output (if available).
No response
Additional context.
Tested with:
MicroWin-0.2 (x64)
Rufus-4.14 (Windows x64 Standard)
Boot of MicroWin11 x64 ISO still produces missing drivers prompt on Ventoy USB
-
The default (required) account creation process during the initial setup sequence works as intended, as well as editing and creating exising & additional accounts in control panel.
-
I've not investigated whether or not the pre-configured account info is preserved if the username entered in Rufus prompt is identical to the one setup in MicroWin.
-
All tests have been done with, and for Windows 10 & 11 Pro x64 (US), fully activated.
-
It would be helpful if the README can point users to the best software solution to create USB installation media from bootable ISOs that will keep all of MicroWin's changes intact, since I don't know how to pinpoint the scope of Rufus' changes at the moment and it would be a no brainer to recommend the one that works best with MicroWin.
Considering the options provided by Rufus for 10/11 ISOs are already applied by MicroWin (and the prompt has no way to be disabled), it seems counter-productive to use it for MicroWin, especially considering it reverses MicroWin's customisations AND it is a prompt that is required to press OK to continue the media creation process. Rufus is clearly intended to be used for original MS ISOs with those options in mind.
Rufus appears to work fine to get an installation of the MicroWin ISO started and completed (with most customisations intact), but if you go through the process of using MicroWin and made an account only for that account not be made as you intended, it brings to question whether it's MicroWin that doesn't work properly or if Rufus is the interference. The average user that hardly understands what MicroWin seeks to accomplish at an instructional level would be concerned about why their pre-made account didn't appear, and so brings the concern of whether or not their installation is corrupted in some fashion. Therefore, it would be helpful that during the MicroWin setup that disclaimers are provided that if you are going to use Rufus to create the installation media, to leave the account creation section blank as that can be done with Rufus otherwise it will be reset to empty values/ password removed.
Booting MicroWin11 on Ventoy continues to have missing drivers and Ventoy should not be used AT ALL. This should be added to the front page and README and remove Ventoy as a recommendation in the closing window of MicroWin (when customisations are complete).
On another note, Rufus should definitely have a checkbox to enable/disable user experience customisations prompt to make it optional to avoid these kind of issues.
Issue Checklist
Provide a clear and concise description of the issue.
I opened this issue to bring attention to the matter as I've made these observations over the last week while rinse-repeating MicroWin, making bootable ISOs and performing 10/11 installations.
I have tried to use a pre-made account with MicroWin, only to have to make one during user setup after MicroWin is installed.
So far, between Rufus and Ventoy - Rufus is the only software solution for bootable ISO USB installation media that works for MicroWin 10 & 11.
Steps to reproduce the issue.
My theory is that Rufus' "Windows User Experience" prompt right before making the bootable USB clears the account information by MicroWin. See example of Rufus prompt here:
It seems highly likely to me that Rufus clears/modifies any pre-configured account information from the ISO after pressing OK, Even when the box is unchecked, the pre-created MicroWin account doesnt appear. At the moment, there is no way to disable this prompt (as far as I know) in Rufus, and it is required to go through that prompt in order to initiate the media creation process.
Assuming that Rufus is performing the same instructions as MicroWin for these specific options, Rufus most likely sets the password to be empty (no password) when a username is entered and the choice selection is checked (after the user presses ok). Rufus is probably resetting account info and other options when boxes are unchecked in order to ensure that the instructions are fulfilled accordingly, hence the MicroWin customisations restored to default values.
Paste the full error output (if available).
No response
Additional context.
Tested with:
MicroWin-0.2 (x64)
Rufus-4.14 (Windows x64 Standard)
Boot of MicroWin11 x64 ISO still produces missing drivers prompt on Ventoy USB
The default (required) account creation process during the initial setup sequence works as intended, as well as editing and creating exising & additional accounts in control panel.
I've not investigated whether or not the pre-configured account info is preserved if the username entered in Rufus prompt is identical to the one setup in MicroWin.
All tests have been done with, and for Windows 10 & 11 Pro x64 (US), fully activated.
It would be helpful if the README can point users to the best software solution to create USB installation media from bootable ISOs that will keep all of MicroWin's changes intact, since I don't know how to pinpoint the scope of Rufus' changes at the moment and it would be a no brainer to recommend the one that works best with MicroWin.
Considering the options provided by Rufus for 10/11 ISOs are already applied by MicroWin (and the prompt has no way to be disabled), it seems counter-productive to use it for MicroWin, especially considering it reverses MicroWin's customisations AND it is a prompt that is required to press OK to continue the media creation process. Rufus is clearly intended to be used for original MS ISOs with those options in mind.
Rufus appears to work fine to get an installation of the MicroWin ISO started and completed (with most customisations intact), but if you go through the process of using MicroWin and made an account only for that account not be made as you intended, it brings to question whether it's MicroWin that doesn't work properly or if Rufus is the interference. The average user that hardly understands what MicroWin seeks to accomplish at an instructional level would be concerned about why their pre-made account didn't appear, and so brings the concern of whether or not their installation is corrupted in some fashion. Therefore, it would be helpful that during the MicroWin setup that disclaimers are provided that if you are going to use Rufus to create the installation media, to leave the account creation section blank as that can be done with Rufus otherwise it will be reset to empty values/ password removed.
Booting MicroWin11 on Ventoy continues to have missing drivers and Ventoy should not be used AT ALL. This should be added to the front page and README and remove Ventoy as a recommendation in the closing window of MicroWin (when customisations are complete).
On another note, Rufus should definitely have a checkbox to enable/disable user experience customisations prompt to make it optional to avoid these kind of issues.