On my old Laptop I have a second hardware SSD which is mounted via VeraCrypt and the problem does not occur. When the data partition is NOT mounted everything works fine, but when the data partition is mounted Wn32 Disk Imager crashes while starting. I have a similar issue: my 1TB SSD has a data partition which is (like the system partition) encrypted with VeraCrypt. I saw that version 0.9.5 is producing the following error when starting () 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. But has someone maintaining this project?
zip file, unpack it at and replace the original Win32DiskImage.exe.Īllow reading device without Windows Drive LetterĬonfirming I can replicate also Win 10 64 bit 20H2 (19042.423) release
The patch below for Win32DiskImage Version 1.0 fixes this bug: Just download the. So it runs until an internal Stackoverflow occurs without displaying any messages. when used together with Google Drive or Veracrypt. 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. 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.
When pCloud is disabled, Win32Diskimager works correctly. Fortunately it works when the file stream is disabled (or just right click and exit). Yes, - it doesn't like fake drive letters. 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.
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). I think any image type that is just 'dd' copied on linux would work. wic (Open Embedded Image Creator) files without changing extension, just need to switch to the 'all files' mask to select them. 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.
Have to close Google Drive app for now as a workaround. Nowdays "Google File Stream drive" was rebranded to official "Google Drive" app and was pushed to insane amount of Google Drive service end-users. Same her, closing Google Drive solves the issue. Same here, closing Google Drive solves the issue. Eventlog shows: Source - Application Error, EventID: 1000, faulty application: Win32DiskImager.exe, Version: 1.0.0.0, faulty module: : ntdll.dll, Version: 1.1288 Exception : 0xc00000fd offset: 0x00045dd4 ID of the faulty Prozess: 0x2ef8 The application starts up, requests admin privileges and then closes without any further notification so it seems to "not start" at all. Even with the error I was able to create a RaspberryPI image that did boot.
Error 122: The data area passed to a system call is too small.)įor Windows 10 Home, I am using version 0.9.5. This usually means something is currently accessing the device please close all applications and try again. ( An error occurred with querying properties. On Windows 10 Home, 21H1, OS Build 19043.1320, I get a different error. I have the same issue, but with Windows 10 Pro, 20H2, OS Build 19042.1348.