Hello,
As far as I remember, FMW never worked for me. Now I’ve got some spare time to help you with debugging — I’ve checked all (ALL) versions and none of them works. Silly thing is Fedora RPM version hangs up as well on my system, but I can no more test it as all my Fedoras stopped working (yep), it’s why I try to repair them with USB installer (so far I was using Rufus to make bootable USB, and it worked, but since some time it stopped — not only Fedoras stopped working, but installers as well, stupid UEFI NVRAMs probably).
My hardware is:
- MSI P67A-GD65(B3) with Sandy Bridge ROM — so motherboard with first UEFI implementation, Mr Roderick W. Smith (author of rEFInd) says first implementations of UEFI were buggy enough to make silly issues, BIOS modded with Intel OROM to support Trim for RAIDed SSDs,
- i5-2550K not overclocked, 16 GB of RAM, GTX 970
- main drives: 2xSSD Agility-3 60 GB in RAID-0 (motherboard software RAID), GPT style, bootable through UEFI,
- storage drive: 3 TB Toshiba hard drive, GPT style,
- two sound cards, not relevant probably.
Report from debug:
D@30ms: Application constructed ((null):0)
D@32ms: Injecting QML context properties ((null):0)
D@34ms: WinDriveProvider construction ((null):0)
D@34ms: DriveManager construction ((null):0)
D@35ms: ReleaseManager construction ((null):0)
D@39ms: Loading the QML source code ((null):0)
W@3830ms: qrc:/components/DownloadDialog.qml:82:26: QML Item: Binding loop detected for property «width» (qrc:/components/DownloadDialog.qml:82)
D@4084ms: Starting the application ((null):0)
D@4085ms: WinDriveProvider Looking for the drives for the first time ((null):0)
W@4085ms: Could not get disk extents for «\.I:» ((null):0)
D@4085ms: WinDriveProvider Finished looking at drive letters ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive0» is present ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive0» IOCTL_STORAGE_QUERY_PROPERTY ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive0» IOCTL_STORAGE_QUERY_PROPERTY with a bigger buffer ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive0» detected: «Intel» «Raid 0 Volume» , nonremovable notUSB ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive1» is present ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive1» IOCTL_STORAGE_QUERY_PROPERTY ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive1» IOCTL_STORAGE_QUERY_PROPERTY with a bigger buffer ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive1» detected: «» «TOSHIBA DT01ACA300» , nonremovable notUSB ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive2» is present ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive2» IOCTL_STORAGE_QUERY_PROPERTY ((null):0)
D@4085ms: WinDriveProvider «\.PhysicalDrive2» IOCTL_STORAGE_QUERY_PROPERTY with a bigger buffer ((null):0)
Report regards to Windows 10 Pro x64, which was upgraded from Windows 7 Ultimate x64 (no clean install further).
Drive I: mentioned in report is my DVD optical drive, and it is probably the source of all my issues both with Fedoras (already installed, and installers), and FMW. I’ve noticed some time ago (3 weeks maybe) there was a mess in my UEFI BIOS, and optical drive is listed twice in an UEFI boot list — there’s no option to remove any of them (such BIOS), so probably clearing NVRAMs would help (yesterday I’ve done this to another Sandy Bridge laptop which has issues with F4 Recovery Mode reaction, and it helped), or rebuilding EFI partition at least. Will see later, if nothing here helps.
Cheers,
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Open
pwl4909 opened this issue
Jul 12, 2017
· 19 comments
Open
Windows 10, flash drive is not writable
#96
pwl4909 opened this issue
Jul 12, 2017
· 19 comments
Comments
Hello,
The following error was given for two different flash drives. Using the preset Fedora Workstation, and then a custom image using the downloaded iso. The drives were also set back to factory default using Fedora Media Writer several times.
Thank you for any help.
The drive becomes undetected, so I can no longer view what is inside. After
plugging back in FMW recognizes the drive as already having a live
partition on it. At this point I restored to factory default and tried
again. I am wondering if the live partition was successful and ran into a
snag at the end.
Would there be a safe way to verify the flash drive? would there be any
risk in trying to boot from the flash drive?
…
It breaks most likely just after it «cleaned» the drive and before anything gets written to it.
From Windows you can not manually verify the drive but it’s definitely broken anyways.
There’s no risk in trying to boot from the flash drive.
Only the «Access is denied.» error is relevant. (The error handling is messed up after that point that’s why you get multiple errors.)
I’d guess that either:
- you don’t have permission.
- another program already uses the disk.
- diskpart holds on to the disk for longer than expected.
- Windows does something else that’s weird.
Generic Windows debugging as always:
- Reboot
- Make sure that the drive is not mounted.
- Make sure nothing else is running on the system apart from FMW and System32 foo.
- Try the same flash drive on another Windows machine to see if the error persists.
- Make sure to scan your System for Viruses if none of the above helps.
This seems to be a bigger issue. Rufus has the same issue when writing in ISO mode. Writing the ISO Image in DD Mode did work perfectly fine though. So this seems to be an issue with how Windows 10 handles things differently.
What exactly do you suspect to be the issue?
What’s DD and ISO mode?
How Windows 10 handles what differently?
That’s strange because FMW basically uses a DD-like approach to writing the iso to the flash drive. Are you sure the drive is alright? That means, can you use it as a regular flash drive, write and then read data successfully to/from it?
Yes I can access the drive normally, I have also attempted this with a
different flash drive with the same result and the flash drives are
different as in not the same brand.
Additionally I have tried this on a different windows 10 computer with the
same result.
…
+1 for this exact same problem.
Win 10 setup that I previously managed to successfully installed F25 without a hitch. Attempting to clean install F26 and I hit the above issues, with multiple USB drives, fresh installs of the MediaWriter and generic Windows debugging precautions. No FedoraMediaWriter.log is produced.
Same issues with both a 64GB corsair originally formatted as ExFAT and a 2GB giveaway drive originally formatted as FAT32. In both cases after FMW fails the drive shows up in W10 disk management as «unallocated». Reformatting makes the flash drive usable again by everything (except FMW).
Will just download the 64bit ISO and burn it to DVD…
What exactly do you suspect to be the issue?
Honestly, no idea. Just pointing out that it doesn’t seem to be MediaWriter itself, but something underneath? I haven’t looked at any code so really no idea, just thought that pointing a direction might help 
Are you sure the drive is alright?
Brand new drive fresh out the box, never been formatted before. And after I tried and failed with MediaWriter it worked fine with Rufus, at least the writing, I didn’t get the time to try the booting part yet.
I was able to install Ubuntu properly from the flash drive, I plan on
trying FMW this weekend with the previous version of Fedora to further
isolate the issue. If no luck with that attept it from ubuntu.
…
On Jul 25, 2017 6:33 PM, «Tarulia» ***@***.***> wrote:
What exactly do you suspect to be the issue?
Honestly, no idea. Just pointing out that it doesn’t seem to be
MediaWriter itself, but something underneath? I haven’t looked at any code
so really no idea, just thought that pointing a direction might help
Are you sure the drive is alright?
Brand new drive fresh out the box, never been formatted before. And after
I tried and failed with MediaWriter it worked fine with Rufus, at least the
writing, I didn’t get the time to try the booting part yet.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#96 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF8_yPUDH_KiZVmPJ9Hk8ziH0w1PoGjPks5sRm0hgaJpZM4OVB5F>
.
I was able to successfully install Fedora 25, using FMW onto the same 4GB flash drive that was giving me issues with 26 on Windows 10. I would have to think that means something with 26 is messing things up. I admittedly have limited knowledge of what is going on under the hood here.
I’m getting a very similar error on Windows 10:
At this point, my USB drive doesn’t show up in Windows Explorer anymore (but it does show up in Disk Management). I’ve tried every combination of ejecting and unmounting and restoring, but I always get this error. If I restart the program with this drive plugged in, it seems to recognize the fact that the drive has already been written:
So all I did was to turn off my Real-Time Protection.
Settings -> Update & Security -> Windows Defender -> Open Windows Defender Security Center -> Virus & Threat Protection -> Virus & Threat Protection Settings -> Real-Time Protection.
And it worked for me, it started writing the iso to the usb.
So all I did was to turn off my Real-Time Protection.
Settings -> Update & Security -> Windows Defender -> Open Windows Defender Security Center -> Virus & Threat Protection -> Virus & Threat Protection Settings -> Real-Time Protection.
And it worked for me, it started writing the iso to the usb.
This worked for me as well. Thanks for the suggestion.
I’d be interested in a way to get my USB drive working again. Deleting/creating new partitions does not help, I can’t format the usb drive or give it a drive letter. Nothing I tried was working. I ended trying Etcher to flash the image on the usb drive and the two drives I tried to use with Media Writer could not be written to by Etcher either, but a third one was working perfectly fine. Now I have no clue how to get the two usb drives working again…
For making my usb work again, I used a third party app called MiniTool partition. I cleaned the disk with the app and initialize with GPT option. It was working again. I’m not sure why I’m getting error for installing linux using fedora media writer.
When i stuck used format usb to clean all partition than fedoraqt work here the utility for windows — Link redacted by @MartinBriza because the project is really sketchy and was linked to via a bit.ly link.
The solution provided by Junaid94 above worked for me as well — Windows 10 w. latest patches, latest FMC, and Fedora 36 ISO is finally on my removable disk!
So all I did was to turn off my Real-Time Protection. Settings -> Update & Security -> Windows Defender -> Open Windows Defender Security Center -> Virus & Threat Protection -> Virus & Threat Protection Settings -> Real-Time Protection. And it worked for me, it started writing the iso to the usb.
this problem is affecting me, on windows 10. the indicated fix does not change the results. rufus is giving write-protection errors i haven’t diagnosed so it’s possible it’s some kind of partial hardware failure.
0
1
Приветствую!
Прошу помощи.
Парни подскажите как вернуть флэшки чтобы читались в Win.
Дело было так.
Скачал образ DVD Centos8, с помощью Fedora пытался сделать загрузочную флэшку, запись образа завершилась с ошибкой, что за ошибка непонятно, вместо букв были ромбики, видимо шрифта нет. Писал на usb из под Win.
В Centos 7 флэш видиться, даже с файлами, ничего не дает сделать, пишет что только для чтения. Разные темы почита, пробовал что-то делать, не получается ничего.
Из под Win в той же Fedore пытаюсь восстановить флэшку, говорит воссстановил, но Win не видит ее.
В чем дело могло быть при записи ISO и как восстановить флэшки?
Проблемы 184753^^FedoraMediaWriter-win32-4.1.0.exe обычно наблюдаются во время запуска программы Fedora Media Writer и обычно возникают в результате повреждения исполняемого файла или, в некоторых случаях, случайного или намеренного удаления вредоносным ПО. Как правило, самый лучший и простой способ устранения ошибок, связанных с файлами EXE, является замена файлов. В качестве дополнительного шага по устранению неполадок мы настоятельно рекомендуем очистить все пути к неверным файлам и ссылки на расширения файлов EXE, которые могут способствовать возникновению такого рода ошибок, связанных с 184753^^FedoraMediaWriter-win32-4.1.0.exe.
Типы Исполнимые файлы, которые используют EXE, также известны в качестве формата Windows Executable File. Ниже представлен список самых последних версий файлов практически для всех версий Windows (а также для некоторых %%os%%), которые вы также можете скачать. В нашей базе представлены не все версии 184753^^FedoraMediaWriter-win32-4.1.0.exe, поэтому нажмите на кнопку Request (Запрос), чтобы наши сотрудники её получили. Если ниже отсутствует необходимая версия файла, мы рекомендуем вам связаться непосредственно с Red Hat, Inc..
Как правило, при размещении файла 184753^^FedoraMediaWriter-win32-4.1.0.exe в надлежащем каталоге, проблемы, связанные с данным файлом, больше не возникают, однако следует выполнить проверку, чтобы убедиться в том, что проблему удалось устранить. Вы можете проверить результат, запустив приложение Fedora Media Writer и проверить, появляется ли проблема.
| 184753^^FedoraMediaWriter-win32-4.1.0.exe Описание файла | |
|---|---|
| Формат файла: | EXE |
| Категория: | Operating System |
| Софт: | Fedora Media Writer |
| Версия: | 4.1.0 |
| Автор: | Red Hat, Inc. |
| File: | 184753^^FedoraMediaWriter-win32-4.1.0.exe |
| Размер (в байтах): | 23833128 |
| SHA-1: | 7994b66ff54ae24448b22cba985efbfdbaea9746 |
| MD5: | 2c88493424e0b4653e766eff491906f8 |
| CRC32: | d1a11fc9 |
Продукт Solvusoft
Загрузка
WinThruster 2023 — Сканировать ваш компьютер на наличие ошибок реестра в 184753^^FedoraMediaWriter-win32-4.1.0.exe
Windows
11/10/8/7/Vista/XP
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
EXE
184753^^FedoraMediaWriter-win32-4.1.0.exe
Идентификатор статьи: 611894
184753^^FedoraMediaWriter-win32-4.1.0.exe
| Имя файла | Идентификатор файла (контрольная сумма MD5) | Размер файла | Загрузить | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| + 184753^^FedoraMediaWriter-win32-4.1.0.exe | 2c88493424e0b4653e766eff491906f8 | 22.73 MB | ||||||||||||||||
|
||||||||||||||||||
| + 184753^^FedoraMediaWriter-win32-4.1.0.exe | 2c88493424e0b4653e766eff491906f8 | 22.73 MB | ||||||||||||||||
|
Ошибки 184753^^FedoraMediaWriter-win32-4.1.0.exe
Частичный список ошибок 184753^^FedoraMediaWriter-win32-4.1.0.exe Fedora Media Writer:
- «Ошибка программного обеспечения 184753^^FedoraMediaWriter-win32-4.1.0.exe. «
- «Ошибка программного обеспечения Win32: 184753^^FedoraMediaWriter-win32-4.1.0.exe»
- «Извините за неудобства — 184753^^FedoraMediaWriter-win32-4.1.0.exe имеет проблему. «
- «Файл 184753^^FedoraMediaWriter-win32-4.1.0.exe не найден.»
- «184753^^FedoraMediaWriter-win32-4.1.0.exe не может быть найден. «
- «Ошибка запуска программы: 184753^^FedoraMediaWriter-win32-4.1.0.exe.»
- «184753^^FedoraMediaWriter-win32-4.1.0.exe не выполняется. «
- «184753^^FedoraMediaWriter-win32-4.1.0.exe остановлен. «
- «Ошибка в пути к программному обеспечению: 184753^^FedoraMediaWriter-win32-4.1.0.exe. «
Ошибки 184753^^FedoraMediaWriter-win32-4.1.0.exe EXE возникают во время установки Fedora Media Writer, при запуске приложений, связанных с 184753^^FedoraMediaWriter-win32-4.1.0.exe (Fedora Media Writer), во время запуска или завершения работы или во время установки ОС Windows. Отслеживание того, когда и где возникает ошибка 184753^^FedoraMediaWriter-win32-4.1.0.exe, является важной информацией при устранении проблемы.
Создатели 184753^^FedoraMediaWriter-win32-4.1.0.exe Трудности
Проблемы Fedora Media Writer и 184753^^FedoraMediaWriter-win32-4.1.0.exe возникают из отсутствующих или поврежденных файлов, недействительных записей реестра Windows и вредоносных инфекций.
Особенно ошибки 184753^^FedoraMediaWriter-win32-4.1.0.exe проистекают из:
- Недопустимая (поврежденная) запись реестра 184753^^FedoraMediaWriter-win32-4.1.0.exe.
- Вирус или вредоносное ПО, которые повредили файл 184753^^FedoraMediaWriter-win32-4.1.0.exe или связанные с Fedora Media Writer программные файлы.
- 184753^^FedoraMediaWriter-win32-4.1.0.exe ошибочно удален или злонамеренно программным обеспечением, не связанным с приложением Fedora Media Writer.
- Другое приложение, конфликтующее с 184753^^FedoraMediaWriter-win32-4.1.0.exe или другими общими ссылками.
- Fedora Media Writer (184753^^FedoraMediaWriter-win32-4.1.0.exe) поврежден во время загрузки или установки.
Fedora Media Writer USB Installation Crashing
I’ve used Fedora Media Writer in the past several times to install via USB. Right now I have Fedora 29 and Windows 10 that I can load via grub. I’m trying to actually reinstall Fedora using the USB method.
Fedora Media Writer creates the USB media successfully. I boot from the USB and begin installing. At some point down the list it just stops and hangs there forever. Does anyone have any idea what’s going on? I can’t seem to create a working USB installation using Fedora Media Writer.