Verison 1.0.0 will not launch

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.

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

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

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?

Can you also read this forum message and follow to see if this may be the issue?
https://windowsforum.com/threads/how-to-fix-msvcp110-dll-is-missing-in-windows-10.212064/

Another thing to try, check out this list of possible issues: http://windowsreport.com/windows-10-apps-wont-open/. See if any of that helps and please update your results here. Thanks.

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.

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

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 (https://sourceforge.net/p/win32diskimager/tickets/47/) 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).

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>
Description:
Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, 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="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-05-07T17:34:18.341868800Z" />
    <EventRecordID>3328</EventRecordID>
    <Channel>Application</Channel>
    <Computer><redacted></Computer>
    <Security />
  </System>
  <EventData>
    <Data>Win32DiskImager.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>58bdb94c</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.15063.0</Data>
    <Data>a82cc161</Data>
    <Data>c00000fd</Data>
    <Data>00042d9e</Data>
    <Data>1da8</Data>
    <Data>01d2c7582401b9c2</Data>
    <Data>C:\Program Files (x86)\ImageWriter\Win32DiskImager.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>20c480c7-c1f8-46be-9881-cd7714cb1215</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

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.

I had the same issue.

In my case it was cause by an 'inconventional' drive. I had mounted drive from pCloud service.

I disabled it and then Win32 image writer ran again!

Hope this helps as a workaround.

The problem is understood and has been fully debugged. I jut haven't had time to work on this project in a while, but will before the end of the year (fingers crossed).

Check if you have done any recent change like installed new apps then uninstall it. Despite, this also update the drivers installed in your system.
Source: http://www.pcerror-fix.com/how-to-repair-ntdll-dll-error-messages-in-windows-8-1

I just installed Win32DiskImager on my Windows 10 machine.

On the first machine I tried, Win32DiskImager would not start.

On the 2nd one, it did.

Looking at differences between the machines (same build of Win 10) I realized that on the first machine I had 3 disk images mounted via VeraCrypt, a program which allows a simulated disk to be mounted from an encrypted disk file, or to mount a complete disk with encryption. Since I keep customer information on my disk, I am required to keep that data encrypted and password protected. When I dismounted all of the VeraCrypt disks, Win32DiskImager started properly.

Now that I know how to make it work, I will be using it this weekend to create a backup image of a microSDCard that will arrive this weekend.

I am experiencing the exact same behavior. Win32DiskImager doesn't start properly (no gui) when I have a VeraCrypt volume mounted. With no VeraCrypt volumes mounted, it seems to work normally. Any more ideas why this would be? It's a bit annoying. Anyway, thanks for discovering this incompatibility.

Same problem here with VeraCrypt!

@Dev: You really need to inform the people about this issue!
I almost gone mad trying to start Win32DiskImager with a mounted veracrypt image!

Same problem here - the cause was "Google File Stream" that mounts your Google Drive as a "physical drive" into the explorer.

As soon as I stopped the service, Win32DiskImager started up in less than a second.

+1 Google File Stream was the issue on my PC. I uninstalled and it worked. Thanks for posting this, it was the only place I found that had this discussion regarding veracrypt and Google File Strea.

+1
Shutting down Google File Stream and Google Drive app did the trick.
I did not need to uninstall or restart.