CodingWonders / CodingWonders/MicroWin
Boot of MicroWin11 x64 ISO still produces missing drivers prompt on Ventoy USB
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 335
- Forks
- 19
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Issue Checklist
- I checked for duplicate issues.
- I searched for existing discussions.
- I checked for an existing pull request that addresses this issue.
Provide a clear and concise description of the issue.
Boot of MicroWin11 x64 ISO still produces missing drivers prompt on Ventoy USB. I used a 64gb Kingston Data Traveler USB 3.0 thumbdrive to create the Ventoy disk, and in there placed my MicroWin 11 ISO.
On boot of MicroWin 11 ISO through Ventoy, I was presented with the missing drivers message.
I have tried enabling / disabling secure boot, UEFI modes between "Windows UEFI" & "Other OS" and have tried re-generating original ISO, making new MicroWin ISO etc.. all futile solutions.
Steps to reproduce the issue.
Use Ventoy disk to store the MicroWin11 x64 ISO and boot from it in Ventoy options.
Paste the full error output (if available).
No response
Additional context.
It would be helpful to remove Ventoy as a recommendation completely from the closing window (customisatons complete message) because it is the reason Chris removed it and the issue is still present.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the MicroWin11 x64 ISO boot from a Ventoy USB with the stated secure-boot and UEFI settings. Trace the customisation-complete message that recommends Ventoy and compare the generated ISO's boot behavior; done means the missing-drivers prompt is resolved or the Ventoy recommendation is removed if the incompatibility cannot be addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100