Not launching in windows 10 pro x64

Bug #1685077 reported by Randy Bell on 2017-04-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Image Writer
High
Tobin Davis

Bug Description

Win32diskimager latest version 1.0 downloaded and installs just fine. However when launching the executable it never comes up. No splash screen no nothing. Not sure where to look for it. I have several USB and SD cards plugged in. I can write a file just fine using the etcher program so I know my PC can see and write the retropi images just fine with that but love all the features of this program.

brand of micro sd card - SanDisk Ultra 32GB HC 1
image trying to write is a raspberry pi of course i never get that far.

I did find this in the event log
Log Name: Application
Source: Application Error
Date: 4/20/2017 11:04:18 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Bell-Media
Description:
Faulting application name: Win32DiskImager.exe, version: 1.0.0.0, time stamp: 0x58bdb94c
Faulting module name: AcLayers.DLL, version: 10.0.14393.953, time stamp: 0x58ba5d8a
Exception code: 0xc00000fd
Fault offset: 0x0001923e
Faulting process id: 0x2374
Faulting application start time: 0x01d2ba65189cdfa6
Faulting application path: C:\Program Files (x86)\ImageWriter\Win32DiskImager.exe
Faulting module path: C:\WINDOWS\AppPatch\AcLayers.DLL
Report Id: 8d04eea5-6ebd-4ee2-afca-e9c7ace2e77b
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-04-21T06:04:18.424645200Z" />
    <EventRecordID>41920</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Bell-Media</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Win32DiskImager.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>58bdb94c</Data>
    <Data>AcLayers.DLL</Data>
    <Data>10.0.14393.953</Data>
    <Data>58ba5d8a</Data>
    <Data>c00000fd</Data>
    <Data>0001923e</Data>
    <Data>2374</Data>
    <Data>01d2ba65189cdfa6</Data>
    <Data>C:\Program Files (x86)\ImageWriter\Win32DiskImager.exe</Data>
    <Data>C:\WINDOWS\AppPatch\AcLayers.DLL</Data>
    <Data>8d04eea5-6ebd-4ee2-afca-e9c7ace2e77b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

as well as this entry
Log Name: Application
Source: Windows Error Reporting
Date: 4/20/2017 11:04:19 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Bell-Media
Description:
Fault bucket 108794295219, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Win32DiskImager.exe
P2: 1.0.0.0
P3: 58bdb94c
P4: AcLayers.DLL
P5: 10.0.14393.953
P6: 58ba5d8a
P7: c00000fd
P8: 0001923e
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F8.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Win32DiskImager._a02655e6b7f4d354176fd15d18af73fd70ce482_cb50a873_2c7a04e6

Analysis symbol:
Rechecking for solution: 0
Report Id: 8d04eea5-6ebd-4ee2-afca-e9c7ace2e77b
Report Status: 0
Hashed bucket: 4fd3c18dcac4d41bafc947a6972ca3c9
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-04-21T06:04:19.399753900Z" />
    <EventRecordID>41921</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Bell-Media</Computer>
    <Security />
  </System>
  <EventData>
    <Data>108794295219</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>Win32DiskImager.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>58bdb94c</Data>
    <Data>AcLayers.DLL</Data>
    <Data>10.0.14393.953</Data>
    <Data>58ba5d8a</Data>
    <Data>c00000fd</Data>
    <Data>0001923e</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F8.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Win32DiskImager._a02655e6b7f4d354176fd15d18af73fd70ce482_cb50a873_2c7a04e6</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>8d04eea5-6ebd-4ee2-afca-e9c7ace2e77b</Data>
    <Data>0</Data>
    <Data>4fd3c18dcac4d41bafc947a6972ca3c9</Data>
  </EventData>
</Event>

Randy Bell (pappabees12) wrote :
Tobin Davis (gruemaster) wrote :

First, do you have any drive letters assigned to network shares , ramdisks, or using the ASSIGN to reassign a folder to a drive letter? This appears to be a common issue that I am looking into. If that is the case, I already have several bug reports both here and on Sourceforge.

If you have a software raid, this may also be causing an issue.

If this is not the case, can you try removing all USB/SD drives and relaunching? If it still fails, then there is really something odd happening.

Thanks for testing and reporting. Your help is greatly appreciated.

Changed in win32-image-writer:
importance: Undecided → High
assignee: nobody → Tobin Davis (gruemaster)
Randy Bell (pappabees12) wrote :

Ok I do indeed have a ramdrive running. I have disable the drive and the software now comes up. Thanks for the heads up. I am using softperfect RAM disk the full purchased version. I now at least can disable it when I want to use win32diskimager. Let me know if you need me to test anything out happy to help but also understand this is your spare time thing so no pressure from me. However thank you for your response, Big thank you for your product, Cheers mate.

Tobin Davis (gruemaster) on 2017-04-25
Changed in win32-image-writer:
status: New → Confirmed
Tobin Davis (gruemaster) wrote :

I root caused this to a race condition and have uploaded code to the git tree to work around it. This may not be the final solution, but at least I can add this to my testing. This will be fixed in the next release.

Changed in win32-image-writer:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers