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.
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/1kRIGGmjQ2NINULu_wL9dO9sT3ZMUSJjP/view?usp=sharing Just download the .zip file, unpack it at and replace the original Win32DiskImage.exe...
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/1kRIGGmjQ2NINULu_wL9dO9sT3ZMUSJjP/view?usp=sharing Just download the .zip file, unpack it at and replace the original Win32DiskImage.exe...
Win32Diskimager has a bug that make it run into into an 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/1kRIGGmjQ2NINULu_wL9dO9sT3ZMUSJjP/view?usp=sharing Just download the .zip file, unpack it at and replace the original Win32DiskImage.exe...
Win32Diskimager has a bug that make it run into into an 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/1kRIGGmjQ2NINULu_wL9dO9sT3ZMUSJjP/view?usp=sharing Just download the .zip file, unpack it at and replace the original Win32DiskImage.exe...
Win32Diskimager has a bug that make it run into into an 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/1kRIGGmjQ2NINULu_wL9dO9sT3ZMUSJjP/view?usp=sharing Just download the .zip file, unpack it at and replace the original Win32DiskImage.exe...
+1 Windows 10.
Allow reading device without Windows Drive Letter
This is awesome.
Confirming I can replicate also Win 10 64 bit 20H2 (19042.423) release
+1
Waiting for this too. But has someone maintaining this project?
I saw that version 0.9.5 is producing the following error when starting (https://ibb.co/S7jQ5wD) but after confirming Win32 Disk Imager starts and works properly! I think this could help finding the bug or at least avoid crashing of the program in version 1.0.
I have a similar issue: my 1TB SSD has a data partition which is (like the system partition) encrypted with VeraCrypt. When the data partition is NOT mounted everything works fine, but when the data partition is mounted Wn32 Disk Imager crashes while starting. On my old Laptop I have a second hardware SSD which is mounted via VeraCrypt and the problem does not occur... Is this issue related? Hope there will be a solution in the future...
Same here.
If Google File Stream is loaded, win32DiskImager Crashes on Startup
Thanks Oliver Genthe I have confirmed this is also my issue. If I quit Google Drive File Stream, win32diskimager will start.
I just wanted to post here, having had a similar issue. It seems that my Google Drive Stream software creates a drive on my Windows 10 PC. I assume any other similar software may do similar. While the drive is mounted (I tried varieus drive letters with no difference), the DiskImager software will not load and has a similar error report to the above. Disabling the File Stream software is the only way to get the DiskImager software to work. It's a minor inconvenience, but an easy work-around.
This may also be of interest. If I close my Drive File Stream software after opening the DiskImager software (probably a minute after realising that the software has not loaded up correctly), I get the attached error message.
Hi, for me it looks like Bugs like this need to reported here: https://launchpad.net/win32-image-writer For me it looks like it has been reported as https://bugs.launchpad.net/win32-image-writer/+bug/1685077
Some more info as I continued working on this....I accidently found that after I received the error message, if I continue to click the READ button another (or a few more) times, it works! But maybe not. After it creates the image file, I then click VERIFY...get the error again, but with enough reties it starts reading/verifying. But the verification always fails. I then did try a USB reader and the same thing happened with it. I will eventually try the USB reader on another PC and see the problem...
An error has occurred when attempting to lock the volume.
I am experiencing the same issue. Here is some information from Event Viewer which might be useful. The first error to appear in EventViewer Log Name: Application Source: Application Error Date: 18/06/2020 08:55:13 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: MartinOHanlon-Laptop Description: Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, time stamp: 0x58bdb94c Faulting module name: ntdll.dll, version: 10.0.18362.815, time stamp: 0x2995af02...
I like your app, but may be you known a good alternative until this problem is fixed
Agree, have the same problme on Win 10 64bit latest updates
Try https://downloads.raspberrypi.org/imager/imager.exe
Doesn't work anymore on may computer (Win10 x64 Pro), maybe since Win10 2004 Update?
In your post, you said: Your three options are: 1. Disable UAC (not recommended. Very bad for security) 2. Copy the file to a local disk first 3. Create an elevated command prompt and mount the network share again as 'Administrator' Doesn't do anything. I never run with UAC. It's the first thing I disable when I install Windows. As should every power user. UAC is for people who really should be using a Mac, but simply don't know it yet. That's idiotic, and does absolutely nothing to address the problem....
UAC is one part of the problem. If you read the link I sent - You need to enable the 'EnableLinkedConnections' through Local GPO to allow a shared drive mapped by a user when elevated. This ticket should be closed. It's not a W32DiskImager problem. On Apr 25, 2020, at 20:30, Tuyen tuyen99@users.sourceforge.net wrote: I don't really understand the purpose of your post. As I said, I've completely turned off UAC...so that has no bearing on it. [tickets:#33] https://sourceforge.net/p/win32diskimager/tickets/33/...
Are you referring to my initial post that said "The problem may be due to UAC" or the later post by JD that said "This is Windows UAC acting properly"? I was quoting JD on 2017-04-28 with his explanation on 2017-04-22. I'm not sure what to make of other's statements myself. I'm not the one that claimed UAC is the problem.
I don't really understand the purpose of your post. As I said, I've completely turned off UAC...so that has no bearing on it.
That seems good to know but counter to what was suspected by others. I'm still using Windows 10 and it's a shame that Win32 Disk Imager doesn't work with it because there have been times since I reported the problem in 2016 that I could have used it. I didn't turn off UAC when I used it on either Win 7 or Win 10. See my reply 2017-04-28.
https://support.microsoft.com/en-us/help/3035277/mapped-drives-are-not-available-from-an-elevated-prompt-when-uac-is-co On Apr 24, 2020, at 1:26 AM, Tuyen tuyen99@users.sourceforge.net wrote: I know this thread hasn't been touched in nearly three years, but this has nothing to do with UAC. I'm running Windows 10 Pro, and even with UAC turned completely off, I still can't get Win32 Disk Imager to access a mapped network drive (Z: in my case). If the problem was fixable back in 2017 by turning UAC...
I know this thread hasn't been touched in nearly three years, but this has nothing to do with UAC. I'm running Windows 10 Pro, and even with UAC turned completely off, I still can't get Win32 Disk Imager to access a mapped network drive (Z: in my case). If the problem was fixable back in 2017 by turning UAC off, then that's really unfortunate, because in 2020 it doesn't do shit.
I encountered the same problems (verify error after writing, verify error after reading). Maybe the solution is very easy: If the SD-Card contains partitions which are accessible from Windows (FAT, FAT32, NTFS), Windows will create or change contents in the folder "System Volume Information" after writing or reading (because volume is locked for writing and reading and unlocked after this), so verification fails because content on SD-Card meanwhile was changed by Windows before you start the Verify....
Ok, thanks for the info, there was no offense intended - other things are more important. I was just hoping to get rid of the qt environment on my pc soon that I installed for testing... ;)
Hmm, no reaction yet. Is this project still active? Does anybody know? Has it moved to another platform?
Sorry, didn't see this merge request earlier. I have had to greatly reduce the attention I pay to this app as I am working 60+ hours a week for a startup (even during lockdown - remote access). Add to that the constant changes to Windows (a Windows 10 update a couple of years ago completely invalidated a different bug fix, which would require a lot of extra code to detect and work through depending on Windows updates installed), and I just haven't had time to properly fix some of these issues. Is...
Fixes startup crash with virtual devices
It looks like Microsoft may have fixed this issue in their own driver in June 2019. I just used the same machine with the latest Windows 10 updates, with the same thumb drive, writing to it some similar Linux images, and I had no problem. Here is a screenshot of the current Microsoft driver, for reference: https://imgur.com/a/GmckCqJ
I agree, that would be very helpful.
Read Only Allocated Patitions simply does not work
Totally at sea. Trying to use Win32 Disk Imager.
When you have something to merge, let me know. Closing this for now.
Nothing to merge.