Windows10 Update Broke Image Writer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Image Writer |
New
|
Medium
|
Tobin Davis |
Bug Description
Win32 Disk Imager Version 0.9.5 and Version 1.0
Edition Windows 10 Pro
Version 20H2
Installed on 5/26/2021
OS build 19042.1083
Experience Windows Feature Experience Pack 120.2212.3530.0
Flashing a device without a partition table works, overwriting a mass storage device with a partition table always stalls the application in the "Starting" state. Don't feel bad same thing happens in Etcher and Upswift's imgWriter.
Formatting the device in Windows no longer restores the mass storage device to it's "blank size" by destroying the "old" partition. Hope you can figure out what Windows did to you. I'd start by looking into it not allowing even people and apps with full admin privileges' to touch partition tables???
I have been working around this by using G-Parted on another OS to wipe the disk.
Of course now I'm just using dd on the other machine but that is not an option for other people in my organization.
Target device is a SanDisk Ultra microSDHC 16GB UHS-1 Card.
Changed in win32-image-writer: | |
assignee: | nobody → Tobin Davis (gruemaster) |
importance: | Undecided → Medium |
This is exactly why I haven't been working on W32IW for a long time. My main job is Linux based (actually this was written so that Windows users had a way to create Ubuntu boot disks from ISO images). I am a Linux user/developer, and outside of maintaining this program, I don't use Windows at all (since 1998).
Between work, the lack of a Windows system to do real development/ testing, and all of the alternative tools out there now, I really haven't had much reason to fix this or the other big bug (program crashes when there is a foreign mount - aka google drive, network drive, ramdisk, etc). That one, the program is designed to ignore based on the published apis for those types of drive mounts, but none of them follow the Windows spec.