Fedora Writer does not recognize USB external disks
I am using Windows 11 24 H2. The program does not recognize any externals USB. Wiondows does. What is the problem????
Can you please provide both logs you find in your documents directory? Those are MediaWriter.txt and MediaWriter-helper.txt.
Actually, MediaWriter-helper.txt won't be there so just the first one please.
Hello Jan, I only find the FEDORA WRITER MEDIA.txt, I made a bootable USB with RUFUS. I hope it works. I can't with the FEDORA MEDIA WRITER. I installed and uninstalled several times. Thank you
El dom, 15 dic 2024 a las 14:04, Jan Grulich @.***>) escribió:
Actually, MediaWriter-helper.txt won't be there so just the first one please.
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2543866144, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z6XDFUCV5DOYLUJQIT2FV443AVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTHA3DMMJUGQ . You are receiving this because you authored the thread.Message ID: @.***>
Hello Jan, I only find the FEDORA WRITER MEDIA.txt, I made a bootable USB with RUFUS. I hope it works. I can't with the FEDORA MEDIA WRITER. I installed and uninstalled several times.
Can you please attach the file here?
Also, what version do you have? Have your tried latest version, which currently is 5.2.2?
Hi again Jan, yes, I have tried 5.2.2 for windows 64 bits.
El dom, 15 dic 2024 a las 14:20, Jan Grulich @.***>) escribió:
Also, what version do you have? Have your tried latest version, which currently is 5.2.2?
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2543871911, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z5Z4GXU5SWZ2S6LYAT2FV6ZDAVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTHA3TCOJRGE . You are receiving this because you authored the thread.Message ID: @.***>
Can you please attach here the log file? It can give us a hint about the problem.
Where is this file located?
El dom, 15 dic 2024 a las 20:17, Jan Grulich @.***>) escribió:
Can you please attach here the log file? It can give us a hint about the problem.
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2544010533, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z67GHWXBA7AXSEZNFT2FXIULAVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBUGAYTANJTGM . You are receiving this because you authored the thread.Message ID: @.***>
It's the FedoraMediaWriter.log file you mentioned you found in your documents directory.
Here it is.
El dom, 15 dic 2024 a las 20:57, Jan Grulich @.***>) escribió:
It's the FedoraMediaWriter.log file you mentioned you found in your documents directory.
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2544030805, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z7KMZASMRKBBHXFTPD2FXNJHAVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBUGAZTAOBQGU . You are receiving this because you authored the thread.Message ID: @.***>
I'm sorry, but you didn't seem to attach the file and I'm not sure you can do that by sending an email.
I sent to you twice…
El El dom, 15 dic 2024 a las 23:11, Jan Grulich @.***> escribió:
I'm sorry, but you didn't seem to attach the file and I'm not sure you can do that by sending an email.
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2544126286, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z522KKC64A27G35NSL2FX5B3AVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBUGEZDMMRYGY . You are receiving this because you authored the thread.Message ID: @.***>
Here again…
@.: Application constructed @.: Localization QLocale(Spanish, Latin, Spain) @.: Injecting QML context properties @.: DownloadManager User-Agent: "FedoraMediaWriter/5.2.2 (Windows 11 Version 24H2; x86_64-little_endian-llp64; es_ES)" @.: WinDriveProvider construction@.: Application constructed @.: Localization QLocale(Spanish, Latin, Spain) @.: Injecting QML context properties @.: DownloadManager User-Agent: "FedoraMediaWriter/5.2.2 (Windows 11 Version 24H2; x86_64-little_endian-llp64; es_ES)" / removed snip * @.: WinDriveProvider Looking for the drives @.: WinDiskManagement[D]: "Enumerating USB devices" @.*: WinDiskManagement[D]: "Device with index 0 is not removable"
Hi @jihaba, as mentioned, if you send a reply over an email, it doesn't attach the file here to the issue, only now when you copied it I can see it, but I would prefer it being attached instead.
Anyway, from the log I can see it only found one disk, which is not removable. I assume this is your main disk. There are no other disks reported by Windows, which to me doesn't look like an issue in Fedora Media Writer. I'm now trying to update to Windows 11 24H2 to see if I can reproduce this issue. I'll let you know. Thank you.
Ok, thanks. I have used NERO to make a DVD with the installer and RUFUS to make a bootable USB with FEDORA WORKSTATION 41. I have tested it and it works fine.
El lun, 16 dic 2024 a las 8:50, Jan Grulich @.***>) escribió:
Hi @jihaba https://github.com/jihaba, as mentioned, if you send a reply over an email, it doesn't attach the file here to the issue, only now when you copied it I can see it, but I would prefer it being attached instead.
Anyway, from the log I can see it only found one disk, which is not removable. I assume this is your main disk. There are no other disks reported by Windows, which to me doesn't look like an issue in Fedora Media Writer. I'm now trying to update to Windows 11 24H2 to see if I can reproduce this issue. I'll let you know. Thank you.
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2544832207, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z5E7CLYTBBUNOENT2T2F2A3JAVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBUHAZTEMRQG4 . You are receiving this because you were mentioned.Message ID: @.***>
I have updated to Windows 11 24H2 and sadly (luckily for me), I couldn't reproduce this issue. It detected two USB flash disks without any issue.
Can you share what USB disk it didn't detect? Is that a regular USB flash disk? An USB hard drive?
Regular USB flash disk, 8 Gb, maxell. I tried with others, same result. Windows detect my USB DISKS but FEDORA WRITER DON'T. Don't worry, as I mentioned to you I have written the FEDORA INSTALLER using other ways. Thanks a lot
El lun, 16 dic 2024 a las 10:16, Jan Grulich @.***>) escribió:
I have updated to Windows 11 24H2 and sadly (luckily for me), I couldn't reproduce this issue. It detected two USB flash disks without any issue.
Can you share what USB disk it didn't detect? Is that a regular USB flash disk? An USB hard drive?
— Reply to this email directly, view it on GitHub https://github.com/FedoraQt/MediaWriter/issues/787#issuecomment-2545021097, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDWX5Z63IOESO7D73U4TR632F2K47AVCNFSM6AAAAABTUK4ZUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBVGAZDCMBZG4 . You are receiving this because you were mentioned.Message ID: @.***>
Regular USB flash disk, 8 Gb, maxell. I tried with others, same result. Windows detect my USB DISKS but FEDORA WRITER DON'T. Don't worry, as I mentioned to you I have written the FEDORA INSTALLER using other ways. Thanks a lot
I'm glad you found a solution, but I care, because I want Fedora Media Writer to work for everyone. I will keep this issue open to see if there are other people having issues with 24H2 update, but since it has worked for me, it's hard to investigate what is going on.
One thing you can try is to open Windows Powershell and check what is reported when you type:
Get-WmiObject -Query "SELECT * FROM Win32_DiskDrive"
or from
Get-CimInstance -Query "SELECT * FROM Win32_DiskDrive"
Does this list your USB drives? This is what we use in Fedora Media Writer to detect all disks.
Hi! I have the same problem with Windows 10. I have tried 4 different USB-sticks from various manufacturers, but none of them are recognised by the Media Writer. The sticks are ok and work fine with Windows, MacOS, MP3-Players and other standalone devices.
Hi @Greenhorn-new, can you please include outputs from the commands above? Also can you please attach MediaWriter log?
Here is the command output:
PS C:\WINDOWS\System32> Get-WmiObject -Query "SELECT * FROM Win32_DiskDrive"
Partitions : 3 DeviceID : \.\PHYSICALDRIVE0 Model : SanDisk SD7SB2Q-512G-1006 Size : 512105932800 Caption : SanDisk SD7SB2Q-512G-1006
Partitions : 1 DeviceID : \.\PHYSICALDRIVE1 Model : Verbatim STORE N GO USB Device Size : 61845880320 Caption : Verbatim STORE N GO USB Device
PS C:\WINDOWS\System32> Get-CimInstance -Query "SELECT * FROM Win32_DiskDrive"
DeviceID Caption Partitions Size Model
\.\PHYSICALDRIVE0 SanDisk SD7SB2Q-512G-1006 3 512105932800 SanDisk SD7SB2Q-512G-1006 \.\PHYSICALDRIVE1 Verbatim STORE N GO USB Device 1 61845880320 Verbatim STORE N GO USB Device
PS C:\WINDOWS\System32>
The log file is attaches
Hi @Greenhorn-new, sorry for not looking into this earlier.
What do you get from:
Get-CimInstance -Namespace "ROOT\Microsoft\Windows\Storage" -ClassName "MSFT_Disk"
This is what seems to fail at least based on the FMW log.
Well apparently my friend is having a similar issue, as the issue I made was closed because it is a duplicate of this. Hopefully the log I posted in that issue could help shed some light on this.
I would like to get also output from
Get-CimInstance -Namespace "ROOT\Microsoft\Windows\Storage" -ClassName "MSFT_Disk"
Can any of you @Techokami or @Greenhorn-new provide this output?
That's a Powershell command, isn't it? In any case, it generates errors:
Thanks @Techokami, I think we are getting to the reason why FMW doesn't list any drives for some.
Does this command make a difference?
Get-WmiObject -Namespace "ROOT\Microsoft\Windows\Storage" -Class "MSFT_Disk"
I wonder whether following https://www.tweaking.com/fix-wmi-corrupted-in-windows/ can fix this. Can you go through "Restart WMI Service" and "Rebuild WMI repository" following with a system restart to see whether the command will work now?
My friend tried running the other command, it still gives an error:
Also, he tried to follow the instructions you linked, but nothing for WMI was available in the Windows Troubleshooter. He hasn't tried any of the other advanced commands on that page yet. EDIT: He did in fact try everything else on that page, and no dice.
@Techokami what Windows version do you use? Is your Windows fully updated? I just installed Windows 10 Home into a VM and it works there, same on my Windows 11 machine.
Again, I am not the one with the problem (I am already on Fedora 42), it is my friend who is having issues and I am here on his behalf. But the answer to your question is in the screenshot in my previous message.