Same here. The program immediately returns an empty/almost-empty image if the Allocated Partitions option is checked. Windows 10. Happy to track down further troubleshooting information on request. But at the moment, this option simply doesn't work at all.
Thanks Adam, that does help. Wish it also had verification in it. But this is a step towards the promised land .... Best
I know this is old, but I am interested in Peter's command line version - especially due to built-in compression. However, I cannot find a pre-built binary. I did try using 7-zip on the results from Win32DiskImager and, while a hugely slow process, it took a 512GB image file down to like 150GB. So that is a marked improvement! Thanks to all!
I was able to overcome this limitation by downloading a file i found called CommandLineDiskImager.exe and passing the parameters for the filename and the target (which is the Drive Letter) Ie: ".\CommandlineDiskImger.exe Name.bin D:" https://github.com/davidferguson/CommandLineDiskImager Hope that helps! On Sun, Mar 1, 2026, 9:48 PM David P. White dpwhite@users.sourceforge.net wrote: Anyone know if a command line interface exists/has been added? That would be a great help to folks like me. Best!...
Anyone know if a command line interface exists/has been added? That would be a great help to folks like me. Best!
Possible to make auto-verify an option on read?
Fix compiler and static analysis warnings in disk handling code
This is by design of Windows. Since Win32DiskImager runs as Administrator, network shares and mapped network drives are not shown in the dialog. But you can enter the name of a share like \\server\my_images" and select/enter a file name like test.img, and Win32DiskImager will display the Image File as //serer/my_images/test.img . The only caveat is an error shown like: Failed to get the free space on drive \\s. Error 161: The specified path is invalid. Checking of free space will be skipped. I got...
duplicate of #54
This is by design of Windows. Since Win32DiskImager runs as Administrator, network shares and mapped network drives are not shown in the dialog. But you can enter the name on a share like \server\my_images" and select/enter a file name like test.img, and Win32DiskImager will display the Image File as //serer/my_images/test.img . The only caveat is an error shown like: Failed to get the free space on drive \s. Error 161: The specified path is invalid. Checking of free space will be skipped. I got...
Elapsed time counter
I have a similar issue. 64GB microSD FAT32 and I get 58GB image file. With "Read Only Allocated Partitions", the .img file is 512 bytes.
Similar for me: I was running pCloud (a DropBox alternative), that also creates a virtual removable drive. Quitting pCloud, and Win32DiskImager.exe works again. Conclusion: any tools, that create virtual drives, should be quit before running Win32DiskImager.exe.
Just to add "Me too" - silently fails, even when launched from the installer.
this issue is back, the app do not start and silently failed
Read Only Allocated Partitions generates empty file
Many thanks - your work is greatly appreciated. Merry Christmas, Pete From: tickets@win32diskimager.p.re.sourceforge.net tickets@win32diskimager.p.re.sourceforge.net on behalf of Tobin Davis gruemaster@users.sourceforge.net Sent: Wednesday, December 18, 2024 6:16 PM To: [win32diskimager:tickets] 88@tickets.win32diskimager.p.re.sourceforge.net Subject: [win32diskimager:tickets] #88 DiskImager has stopped working This has been fixed in source, will be releasing a binary soon. The fix is really only...
Beware of fake sites
This is the same as bug #88. Both have been temporarily fixed in source and the fixed binary will be released shortly.
This has been fixed in source, will be releasing a binary soon. The fix is really only temporary, as I try to determine the actual root cause of the issue (why the program is getting the wrong info on drive type from the OS). But if I can't root cuase this, I will at least try to get an update out soon.
Confirming that this is still an issue on Windows 11 with Google Drive - the app simply won't launch unless I quit Google Drive first.
Being able to script the write or read to disk with an additional option to confirm would be a great addition. I did find that I can pass the file and the drive destination, but nothing will allow me to kick it off with a write task to start it . The assumption would also be that using the command line would run silently or at least close when complete and pass back an exit code.
Update translation line numbers
Minor cleanups
Merge commit 'ee3007'
Store selected filter from QFileDialog and make that the first one in the next file selection
initial merge for setup config
Please don't post empty merge requests. Let me know when you have something to contribute.
Merge commit '5cf549' into footstark2
Sorry for the massive delay. See my blog. I have merged this in a modified form, as I had to start from scratch on a new system (I don't have any Windows systems), and setting up the laptop forced an upgrade to the QT build environment, making this merge difficult (but I took the heart of it and made it work). My next step is to figure out why these odd drive types fail my initial screen in the first place (likely MS not following their api protocols, again).
Fixes startup crash with virtual devices
Update to QT 6.8, cleanup areas
Update ignore for all build* folders
Sorry for being gone for so long
win32
Merged, thanks.
Fixed an Italian translation
Merged, thanks.
Another fix to Italian translation
No changes.
Research & Develop
merger
No changes to merge.
merger
Had same problem. Cause was locally mounted Veracrypt drives. After unmounting Win32DiskImager can be started. Please fix this!
I will try. Thank you for the recommendation.
Here is located version based on this open source code ("fork), which corrects this bug: https://github.com/dnobori/DN-Win32DiskImagerRenewal
Here You have corrected version ("fork" of this source code), search in Your favourite search engine: "DN-Win32DiskImagerRenewal"
Remember - if its critical to your workflow, the workaround is to exit google drive. You can always restart it later on. There may also be other drive-stream apps that cause the same problem, onedrive can be configured that way and probably others like synology etc.
Updated Link to make it run again modified on: 2023-12-07 Win32Diskimager has a bug that make it run into into a recursive endless loop when it finds a Volume that has been mounted as a virtual disk. E.g. when used together with Google Drive or Veracrypt. So it runs until an internal Stackoverflow occurs without displaying any messages. The patch below for Win32DiskImage Version 1.0 fixes this bug: https://drive.google.com/file/d/10x5hIScQPyU0vAnDbJbW7wyAG0NJYNp-/view?usp=sharing Just download the...
Win32Diskimager has a bug that make it run into into a recursive endless loop when it finds a Volume that has been mounted as a virtual disk. E.g. when used together with Google Drive or Veracrypt. So it runs until an internal Stackoverflow occurs without displaying any messages. The patch below for Win32DiskImage Version 1.0 fixes this bug: https://drive.google.com/file/d/10x5hIScQPyU0vAnDbJbW7wyAG0NJYNp-/view?usp=sharing Just download the .zip file, unpack it at and replace the original Win32DiskImage.exe...
+1
The problem has not yet been fixed even after the bugs and solutions were pointed out here several years ago. The bad thing is that this app is recommended by several Linux distros and some only work if you record using it. So I would like to reinforce my request to correct the bugs that require us to close certain apps for them to work.
There are no commits to merge
Wrong showing of elapsed time after one hour
I"m wondering if the permissions are based on the raw data properties on the original files. When they get copied over, do they retain those access/read/write permissions both ways? Are the files themselves retaining the permissions from the original source drive?
It is able to handle ISO files just fine. the issue is that the open file by default asks for only bin and img format. If you click on format and change it from bin, img to *.* you are then able to open it. it just needs an adjustment to allowed images format
Have a nearly same problem. I can read a sd-card and write a imageto a local pc-folder. If i try to write the image back to a other SD-card i have "write-errors - permission denied" so as if the sd-card is write-protectet. But it is a brand new card. any hints?
Confirming - closing Google Drive and OneDrive (in my case) allowed to start Win32DiskImager without problems.
i gigured out why my diskimager suddenly was crashing as like the posters above. I did a SUBST X: c:\foo SUBST creates a virutal disk that was causing diskimager to crash.
Thank you all, saved my day! Needed to close nextcloud VFS + google drive VFS in order to start the app.
For me, it was Keybase which creates a virtual drive. Quitting keybase completely and relaunching and diskimager ran fine. Hope this helps! And thanks to the answers below for putting me on the right track!
It seems this bug is related to all virtual drives. Ram disk drive is either preventing the program to run.
Quitting Google Drive fixed it for me. Thanks to fiksve for the suggestion!
I had to stop pcloud ...
Read Only Allocated Patitions do not work
I had to stop MS OneDrive and Google Drive to get it back up and running. You can stop them from the tray.
Research & Develop
Elapsed time wrong displayed over 60mn
The only version I can find has a file size of 190,976, also that google drive link is dead, a reupload would be much appreciated.
Another fix to Italian translation
Fixed an Italian translation
Windows 21H2 (home edition) same problem. Win32DiskImager process starts and it eats a lot of memory until it hit around 160M, then it get killed ... In the event log there is error: Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, time stamp: 0x58bdb94c Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0x027db076 Exception code: 0xc00000fd Fault offset: 0x00045dd4 Faulting process id: 0x870 Faulting application start time: 0x01d7f92a0f6e510b Faulting application...
Ignore drives argument
same here tested on 2 computers running win10x64 21H2 Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, time stamp: 0x58bdb94c Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0x027db076
I've seen the same problem. For me it looks as if another program I installed is interfering. Linux File Systems for Windows may be blocking access to Win32DiskImage Viewer. I killed the task and it allowed disk viewer to open finally. Perhaps another program is doing the same for others.
I cannot run disk imager, nothing happens when clicked. The windows event viewer contains Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, time stamp: 0x58bdb94c Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0x027db076 Exception code: 0xc00000fd Fault offset: 0x00045dd4 Faulting process ID: 0x2378 Faulting application start time: 0x01d7fd0264b1e2ad Faulting application path: C:\Program Files (x86)\ImageWriter\Win32DiskImager.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll...
DiskImager has stopped working
Windows 21H2 (home edition) same problem. Win32DiskImager process starts and it eats a lot of memory until it hit around 160M, then it get killed ... In the event log there is error: Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, time stamp: 0x58bdb94c Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0x027db076 Exception code: 0xc00000fd Fault offset: 0x00045dd4 Faulting process id: 0x870 Faulting application start time: 0x01d7f92a0f6e510b Faulting application...
I have the same issue, but with Windows 10 Pro, 20H2, OS Build 19042.1348. On Windows 10 Home, 21H1, OS Build 19043.1320, I get a different error. ( An error occurred with querying properties. This usually means something is currently accessing the device; please close all applications and try again. Error 122: The data area passed to a system call is too small.)
For Windows 10 Home, I am using version 0.9.5. Even with the error I was able to create a RaspberryPI image that did boot.
I can only support this issue. Win 10 Pro x64 - 21H1 (Build 19043.1384). The application starts up, requests admin privileges and then closes without any further notification so it seems to "not start" at all. Eventlog shows: Source - Application Error, EventID: 1000, faulty application: Win32DiskImager.exe, Version: 1.0.0.0, faulty module: : ntdll.dll, Version: 10.0.19041.1288 Exception : 0xc00000fd offset: 0x00045dd4 ID of the faulty Prozess: 0x2ef8
Same here, closing Google Drive solves the issue...
Same her, closing Google Drive solves the issue...
Hit this one too. Nowdays "Google File Stream drive" was rebranded to official "Google Drive" app and was pushed to insane amount of Google Drive service end-users. Have to close Google Drive app for now as a workaround. Looking forward for any source code patch appearing so it'd be possible to rebuild win32diskimager instead of relying on some binaries from third parties which is never a good idea for nowdays internet.
win32diskimage
This is awesome.
win
win
Cannot write IMG to SD card
I've been using it to load .wic (Open Embedded Image Creator) files without changing extension, just need to switch to the 'all files' mask to select them. I think any image type that is just 'dd' copied on linux would work.
I went through the source code and can provide a bit more context, as it seems there are 2 issues here: First, an error is thrown on some mounted virtual disks (I can reproduce with VeraCrypt, but not with a VHD created via Disk Management app). The error message is "Incorrect Function", which can be retrieved in a debugger by breaking at address Win32DiskImager.00404A4E; Second, this error is thrown inside method GetDisksProperty(), while the MainWindow instance is being created. The error logic...
Yes, - it doesn't like fake drive letters. Fortunately it works when the file stream is disabled (or just right click and exit).
Same error when using pCloud drive. When pCloud is disabled, Win32Diskimager works correctly.
