tiny-pilot / tiny-pilot/tinypilot
Mounting Virtual Media on Windows server 2025 as flash drive does not work.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Description
I am running version 2.7.0 of TinyPilot Pro
I have tried 3 different ISO files all with the same result. I know that 2 used to work on Server 2019 and 2016. The server hardware has not changed, the only change on the machine was different Windows Server versions.
The 2 ISO files that used to work are but no longer work are:
Windows server_2019_x64_dvd_4cb967d8.iso
clonezilla-live-3.1.0-22-amd64.iso
The new one that doesn't work:
26100.1742.240906-0331.ge_release_svc_refresh_SERVER_EVAL_x64FRE_en-us.iso
The thing is, mounting as a CD-ROM works, but from UEFI I cannot boot from the CD-ROM
What's the behavior that you expect?
A new USB Drive should appear under Windows Explorer with the correct ISO mounted.
What's happening instead?
Getting error "The directory name is invalid." in Windows Explorer and unable to access the virtual USB drive. Device Manager correctly shows USB Mass Storage Device
What are the steps to reproduce this behavior?
- Open TinyPilot in Chrome
- Click on System -> Virtuak Media -> Actions -> Show Options -> Flash Drive (default) -> Mount
- See error in screenshots
Screenshots
All of my regular drives
Mount as Flash Drive
Mount as CD-ROM
Device Manager:
Capture hardware
N/A
Logs
Contributor guide
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 reviewing the linked logs and reproducing the reported Flash Drive mount flow on Windows Server 2025, comparing it with CD-ROM mounting. The issue provides no repository file or test entry point; done means the mounted virtual USB drive is accessible in Windows Explorer and supports the reported boot scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100