Verison 1.0.0 will not launch

Bug #1672552 reported by David L. on 2017-03-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Image Writer
Tobin Davis

Bug Description

Win32 Disk Imager (WDI) v0.9.5 works on my two computers running Windows 10 64-bit.

I upgraded both to WDI v1.0.0 and neither of them work. WDI launches on both (I can see the process in task manager) but a window never opens and the process closes with no output.

Tobin Davis (gruemaster) wrote :

Can you give me some more details? Here are a few things to try:
1. Make sure it tries to run in Administrator Mode only.
2. Open a command prompt (Windows key/Start menu, search for cmd, right click and Run as Administrator then ce to the installation directory (C:\Program Files (x86)\Image Writer and run Win32DiskImager.exe and see what errors it gives you.

If these fail to give you any info, please let me know. Also, are you installing from the Win32DiskImager-1.0.0-install.exe or from the zip file?

I have tested this on a few different systems, but my testing environment is somewhat limited. I need to know if there is a missing library I need to include, or if there is some other issue I need to resolve.

Your help is greatly appreciated, thanks.

Changed in win32-image-writer:
status: New → Incomplete
David L. (derd100) wrote :

1. Installed v1.0.0.0 using installer
2. Started elevated cmd.exe (as Administrator)
3. Launched Win32DiskImager.exe

Win32DiskImager.exe appears in the process list for a short amount of time but then exits.
It does not produce any output.

Tobin Davis (gruemaster) wrote :

It sounds like you are missing a MSFT runtime library. I have tested this on several fresh installs of Windows 10 Premium, no issues.

What is the exact version of windows you are running?

Tobin Davis (gruemaster) wrote :

Can you also read this forum message and follow to see if this may be the issue?

Tobin Davis (gruemaster) wrote :

Another thing to try, check out this list of possible issues: See if any of that helps and please update your results here. Thanks.

David L. (derd100) wrote :

Using: Windows version 1607 (14393.953)

I don't get any missing DLL messages but I tried re-installing the runtime, as recommended and it made no difference. The "apps-wont-open" link appears to specifically deal with Windows 10 Apps (via the Windows Store), so this doesn't fall under that category.

I can try something else, if it will help. At the moment, I need to revert to 0.9.5, so that I can use the program. I will re-install 1.0.0, if there is something to test. Is the source code available? Maybe I could attach a debugger.

David L. (derd100) wrote :

Well, obviously the source code is available. Ignore that part.

Tobin Davis (gruemaster) wrote :

Heh. Consider it ignored. :P

On a side note, the release does not have debugging info for performance reasons, but you can download the QT tools and build a debug version and run it through their debugger. You'll have to launch QT Creator as admin to do this, but it is how I debug. Also, there is a similar sighting on SF ( that may be related. I haven't had time to trace through the code on this one yet. Your problem does sound similar though. Likely an issue during the drive detection routine on initial startup. Windows has multiple IO APIs depending on the medium being addressed, it could be that the IOCTL currently used is incompatible with these new corner cases (I haven't used assign or a ramdisk in at least a decade).

Tobin Davis (gruemaster) on 2017-04-04
Changed in win32-image-writer:
status: Incomplete → Confirmed
importance: Undecided → High
assignee: nobody → Tobin Davis (gruemaster)
Michael Johnson (johnsomor) wrote :

I am seeing the same behavior, it starts, but crashes. Event log entry:

Log Name: Application
Source: Application Error
Date: 5/7/2017 10:34:18 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <redacted>
Faulting application name: Win32DiskImager.exe, version:, time stamp: 0x58bdb94c
Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xa82cc161
Exception code: 0xc00000fd
Fault offset: 0x00042d9e
Faulting process id: 0x1da8
Faulting application start time: 0x01d2c7582401b9c2
Faulting application path: C:\Program Files (x86)\ImageWriter\Win32DiskImager.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 20c480c7-c1f8-46be-9881-cd7714cb1215
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2017-05-07T17:34:18.341868800Z" />
    <Security />
    <Data>C:\Program Files (x86)\ImageWriter\Win32DiskImager.exe</Data>

Tobin Davis (gruemaster) wrote :

Is this by any chance related to other issues people are seeing, like ramdisk or other drive letters assigned? I think I may have found the issue, but not sure based on the information here. If you are running a ramdisk, or mapping a drive letter to something other than basic drives, this may be the issue.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers