FedoraQt
Driver Error(Your driver is probably damaged)
First of all my native language is Turkish and some translatitions might not be same as program's default text/response but I can answer any question and am ready to help.
I opened the app and followed in this order:
Download Automatically => Official Editions / Fedora Workstation => 41 / Intel/AMD 64bit / MyUsbDriver => after this process it does all the writing and after writing It starts checking the process last time and it gives me and error:
Error You driver is probably damaged
However I reformatted my driver back and checked from Windows to see if there is any problem and it says that my driver is okay. I am also adding the Windows check result to below: chkdsk D: /f The type of the file system is exFAT. Volume Serial Number is XXXX-XXXX Windows is verifying files and folders... File and folder verification is complete.
Windows has scanned the file system and found no problems. No further action is required.
15311552 KB total disk space. 32 KB in 1 files. 64 KB in 2 indexes. 0 KB in bad sectors. 96 KB in use by the system. 15311360 KB available on disk.
32768 bytes in each allocation unit.
478486 total allocation units on disk.
478480 allocation units available on disk.
Maybe it's related to Turkish translation or I am doing something wrong idk. I can also try default version with English but I didn't see any language version choice while downloading or making the installation. Can anyone help?
Hi, does it always end with the error? The error doesn't mean your USB drive is damaged the way you probably think, but it just means the image was not properly written onto it.
Have you used the latest version of MediaWriter (5.2.3)? I see the issue is closed now, so maybe the next attempt worked?
Hello, No, I tried for a few times, failed in each with same error and I switched to Mint, closed the issue. But If you would like to explore the problem, I can help with that taking ss etc. Checking specific stuff or trying the english verion.
If I can help I would be glad to but other than that this issue doesn't have any urgency or importance for me anymore. Thank you for responding even it was close
- What Fedora Media Writer version did you use?
- What Windows version do you have?
- Have you also tried a different USB drive?
- Also
MediaWriter-helper.logwould be helpful. You can find it in your Documents directory.
It's also possible the check failed, but the image was still written properly, even though I haven't seen the check failing in the past so not sure why it's happening.
Experiencing the same issue after deciding to jump back to Fedora after over a decade. Obviously not bothering to switch over to Fedora now. I've tried various things that were suggested (Admin, different stick, etc. etc.) with no success, and I am already tired of formatting/restoring/reformatting the USB stick.
Confirmed the stick is fine by using it to boot and install a different Linux distro with 0 issues.
Using version 5.2.5 on Windows 10 64-bit, with the latest Fedora image that it chose to use (42 workstation for Windows 10 x86/64)
Here's the log contents. Writing a log file to my Documents directory directly instead of applocal, temp, or a subdirectory is janky.
D@288ms: Starting the application
D@288ms: WinDriveProvider Looking for the drives
D@288ms: WinDiskManagement[D]: "Enumerating USB devices"
D@441ms: WinDiskManagement[D]: "Device with index 3 is not removable"
D@441ms: WinDiskManagement[D]: "Device with index 1 is not removable"
D@441ms: WinDiskManagement[D]: "Device with index 4 is not removable"
D@441ms: WinDiskManagement[D]: "Device with index 2 is not removable"
D@441ms: WinDiskManagement[D]: "Device with index 0 is not removable"
D@441ms: WinDiskManagement[D]: "Found removable device with index 5"
D@442ms: WinDiskManagement[D]: "Enumerating partitions for device with index 5"
D@484ms: WinDiskManagement[D]: "Found partition with index 2 mounted to H"
D@484ms: WinDiskManagement[D]: "Obtaining disk drive information for disk with index 5"
D@510ms: WinDiskManagement[D]: "DeviceID \\\\DESKTOP-AAC7J2T\\ROOT\\Microsoft\\Windows\\Storage:MSFT_Disk.ObjectId=\"{1}\\\\\\\\DESKTOP-AAC7J2T\\\\root/Microsoft/Windows/Storage/Providers_v2\\\\WSP_Disk.ObjectId=\\\"{c75f5d0b-57e7-11ef-a9fa-806e6f6e6963}:DI:\\\\\\\\?\\\\usbstor#disk&ven__usb&prod__sandisk_3.2gen1&rev_1.00#0101de45443e0fbc03dee8b3b2edf1cd507fa7ade83ae32d6759c01b58aa7e3#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\\\"\""
D@510ms: WinDiskManagement[D]: "Disk is offline: 0"
D@510ms: WinDiskManagement[D]: "Disk name: USB SanDisk 3.2Gen1"
D@510ms: WinDiskManagement[D]: "Size 30784094208"
D@510ms: WinDiskManagement[D]: "Sector size 512"
D@510ms: WinDiskManagement[D]: "Serial number 0101de45443e0fbc03de"
D@510ms: Adding new drive to the list with index 5
WinDiskManagement[D]: DeviceID \\DESKTOP-AAC7J2T\ROOT\Microsoft\Windows\Storage:MSFT_Disk.ObjectId="{1}\\\\DESKTOP-AAC7J2T\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Disk.ObjectId=\"{c75f5d0b-57e7-11ef-a9fa-806e6f6e6963}:DI:\\\\?\\usbstor#disk&ven__usb&prod__sandisk_3.2gen1&rev_1.00#0101de45443e0fbc03dee8b3b2edf1cd507fa7ade83ae32d6759c01b58aa7e3#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\""
WinDiskManagement[D]: Disk is offline: 0
WinDiskManagement[D]: Disk name: USB SanDisk 3.2Gen1
WinDiskManagement[D]: Size 30784094208
WinDiskManagement[D]: Sector size 512
WinDiskManagement[D]: Serial number 0101de45443e0fbc03de
WinDiskManagement[D]: Refreshing disk drive information
WinDiskManagement[D]: Successfully refreshed the disk.
WinDiskManagement[D]: Removing assigned drive letters for device with index 5
WinDiskManagement[D]: Checking drive: \\.\C:
WinDiskManagement[D]: Checking drive: \\.\D:
WinDiskManagement[D]: Checking drive: \\.\E:
WinDiskManagement[D]: Checking drive: \\.\F:
WinDiskManagement[D]: Checking drive: \\.\G:
WinDiskManagement[D]: Removing partitions on disk with index 5
WinDiskManagement[D]: Partitions deleted successfully.
WinDiskManagement[D]: Trying to lock the drive
WinDiskManagement[D]: Successfully locked the drive
WinDiskManagement[D]: Refreshing information about partition layout
WinDiskManagement[D]: Clearing partition table information
WinDiskManagement[D]: Refreshing information about partition layout
WinDiskManagement[D]: Successfully cleared the partition table
WinDiskManagement[D]: Clearing disk drive
WinDiskManagement[D]: Refreshing information about partition layout
WinDiskManagement[D]: Successfully cleared the disk drive
WinDiskManagement[D]: Creating GPT partition table
WinDiskManagement[D]: Refreshing information about partition layout
WinDiskManagement[D]: Successfully created GPT partition over the whole disk.
WinDiskManagement[D]: Refreshing disk drive information
WinDiskManagement[D]: Successfully refreshed the disk.
WinDiskManagement[D]: Mounting logical volume
WinDiskManagement[D]: Successfuly mounted logical volume \\?\Volume{79576727-45a2-11f0-aa0f-94e6f741af72}\ as H
WinDiskManagement[D]: Formatting partition mounted to drive letter H:
WinDiskManagement[D]: Volume successfully formatted to exFat.
WinDiskManagement[D]: Trying to unlock the drive
WinDiskManagement[D]: Successfully unlocked the drive
Quick glance, but it looks to be what it did after I used Fedora Media Writer to restore the USB stick and install OpenSuse
@CGAWarlock yes, it looks like a log from restoring your device, you will have to try to write Fedora again and then get the log.
I have the exact same error on the drive is probably damaged, but I know it's not damaged. Here's the log:
WinDiskManagement[D]: Obtaining disk drive information for disk with index 1
WinDiskManagement[D]: DeviceID \\KIAT-ACER\ROOT\Microsoft\Windows\Storage:MSFT_Disk.ObjectId="{1}\\\\KIAT-ACER\\root/Microsoft/Windows/Storage/Providers_v2\\WSP_Disk.ObjectId=\"{aaf5fa19-216d-11ec-bcab-806e6f6e6963}:DI:\\\\?\\usbstor#disk&ven_general&prod_udisk&rev_5.00#6&2a49058c&0&_&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\""
WinDiskManagement[D]: Disk is offline: 0
WinDiskManagement[D]: Disk name: General UDisk
WinDiskManagement[D]: Size 31457280000
WinDiskManagement[D]: Sector size 512
WinDiskManagement[D]: Serial number
WinDiskManagement[D]: Preparing device for image writing
WinDiskManagement[D]: Removing assigned drive letters for device with index 1
WinDiskManagement[D]: Checking drive: \\.\C:
WinDiskManagement[D]: Checking drive: \\.\D:
WinDiskManagement[W]: Checking volume: D:\
WinDiskManagement[D]: Successfully removed mountpoints for volume: D
WinDiskManagement[D]: Checking drive: \\.\E:
WinDiskManagement[W]: Checking volume: E:\
WinDiskManagement[D]: Successfully removed mountpoints for volume: E
WinDiskManagement[D]: Removing partitions on disk with index 1
WinDiskManagement[D]: Partitions deleted successfully.
WinDiskManagement[D]: Refreshing disk drive information
WinDiskManagement[D]: Successfully refreshed the disk.
WinDiskManagement[D]: Trying to lock the drive
WinDiskManagement[D]: Successfully locked the drive
WinDiskManagement[D]: Refreshing information about partition layout
WinDiskManagement[D]: Trying to lock and unmount logical volume
WinDiskManagement[D]: Trying to lock the drive
WinDiskManagement[D]: Successfully locked the drive
WinDiskManagement[D]: Unmounting logical volume
WinDiskManagement[D]: Successfully unmounted logical volume
WinDiskManagement[C]: Starting to write plain data
WinDiskManagement[D]: Trying to unlock the drive
WinDiskManagement[D]: Successfully unlocked the drive
WinDiskManagement[D]: Trying to unlock the drive
WinDiskManagement[D]: Successfully unlocked the drive
WinDiskManagement[D]: Refreshing information about partition layout
WinDiskManagement[C]: Couldn't update disk properties.
WinDiskManagement[C]: Starting verification of written data
WinDiskManagement[C]: Check failed
Actually, I have tried different ISOs: Omarchy, Ubuntu; and tried to burn using Rufus, BalenaEthcher; tried different USBs; tried to burn on different PCs, and even vibe code an app to burn. I do not know why but the closest I came to a working USB was the vibe coding app, it launched the USB with a panic screen with error cannot read block 0,0.
