This is a large part of why I haven't been able to do much development on this app in a while. Windows keeps changing little things that are devastating to this app, and it takes a lot of time and effort to reproduce the issue, then debug it.
>From the start, I have wanted to keep the code clean and functional across Windows releases. By clean, I mean no code that looks like this:
~~~
If Windows XP do XPfunction(custom params)
else if Windows Vista do Vista(custom params)
else if Windows 7 ...
~~~
You get the idea.
---
** [tickets:#73] Windows 10 update causing old error in a new way**
**Status:** open
**Release:** 1.0
**Created:** Tue Jun 26, 2018 11:06 AM UTC by mmortal03
**Last Updated:** Tue Jun 26, 2018 11:06 AM UTC
**Owner:** nobody
A recent Windows driver update seems to be causing an old error to occur in a new way in win32diskimager with certain hardware.
I noticed it this past evening, after trial and error, that an update to the Windows 10 Renesas USB 3.0 extensible host controller driver (or something related to it) seems to be causing imaging to fail midway through. I don't know whether or not there's a way for win32diskimager to detect this configuration and work around it, but I'm mentioning it because others may run into it.
I started getting the error this past evening while writing a raw Linux disk image to a thumb drive. The image contains two partitions (it's a fresh, bootable Linux Mint install). I'm using the same hardware that I've always used with win32diskimager for this purpose, and I've previously had no issue: a USB 3.0 PCIe two port expansion card which uses the NEC/Renesas USB 3.0 Host Controller, and a 32 GB SanDisk Ultra Fit thumb drive.
The error is: "An error occurred when attempting to write data to handle. Error 2: The system cannot find the file specified."
I googled the error, and saw that it had been reported elsewhere five years ago regarding SD card imaging, but that doesn't fit what I'm experiencing.
For me, it's specifically happening around the 51% mark of the imaging process. The image I'm writing contains two partitions, with the first partition much smaller than the second, so I don't think the failure point is between the two partitions. I actually don't know what the low level cause is.
This issue seems to have started after a recent Windows 10 update, possibly the Windows 10 April 2018 Update, but it may have been due to an update prior to that. I'm currently on Windows 10 version 17134.1.
After tracking down an older, Windows 7 version of the NEC/Renesas USB 3.0 Host Controller driver (3.0.23.0) and installing that, I am able to write the images successfully again.
To rule out disk image or thumb drive corruption, I first rebuilt the disk image from scratch and tested that, which still had the same issue, so then I tested writing the images on Linux with a different utility to the same thumb drive, and those imaged properly; this confirmed that there was nothing wrong with my images or the thumb drive. After installing the older driver, win32diskimager wrote the same images perfectly fine.
---
Sent from sourceforge.net because win...@li... is subscribed to https://sourceforge.net/p/win32diskimager/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/win32diskimager/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |