Installing the EasyFlash 3 Driver in Windows 10

I finally decided to purchase an EasyFlash 3 cartridge from RETRO Innovations.  As is typical the documentation was nonexistent, so it was time to dig and figure out how to load .crt images onto the cartridge.  Didn’t take me long to find this website.  All the directions seemed easy enough, obviously the first thing that I needed to do was get the drivers installed, which is detailed on this page.  If everything had gone as documented I would not be writing this post!

Following the Directions (sort of)

Plugging in the EasyFlash did not bring up a driver installation dialog it just auto installed something unspecified.  I figured I would check the Device Manager to see what it had done and if it was anything close to correct.

Well I don’t know what correct is, but this is very likely not correct.  Ok, well I will download the driver from here and update the driver by hand.  Once the drivers are unzipped somewhere, I just put them in “Desktop\EF3-driver-windows”.  Right click the EasyFlash 3 device in the Device Manager and select “Update Driver Software…”.

Select a “Browse my computer for driver software”.

Navigate to where you downloaded the driver, click “Next” and that should be that!

Swing and a miss!  This error message came up.

Ok if you have ever dealt with Windows 10 drivers you know now a days every driver has to be digitally signed for “security” and Windows no longer lets you install unsigned drivers at all.  Well this is very bad news.

What Now?

Searching the internet I found this post.  This lead me to this post on how to disable driver signature verification.  For me this was a non-starter, for a variety of reasons, so what are my other options.  I happen to notice the below image on the driver install page.

The image shows that the EasyFlash 3 is a “libusb (WinUSB)” device.  Lately I have been dealing with the intricacies of the ZoomFloppy, which is story I will tell in a separate post.  With the ZoomFloppy you have to use a third-party tool to install a signed libusb-based driver.  The tool also allows for the installation of a signed WinUSB driver.  Lets see if we can make it work!

Trying Zadig

The driver installation tool is call Zadig and can be downloaded from here.  So I downloaded and ran it.

It recognizes that the EasyFlash doesn’t have a driver.  So I select the “WinUSB” driver and hit “Install Driver”.  Lets check the Device Manger again.

This looks promising!  So I hooked it all and tried transferring a crt image as described here.

SUCCESS!!  So there it is.  How to install the EasyFlash 3 driver in Windows 10 without disabling driver verification.  Any questions, just let me know.

7 Replies to “Installing the EasyFlash 3 Driver in Windows 10

  1. A very late reply:

    You can actually have Windows install it without using any .inf files.

    Go to device manager, right-click on the EasyFlash device, and select Update Driver. Then choose to Browse for drivers, and “Let me pick from a list…”

    From there, choose Winusb device, and click Next. Say Yes to the warnings, and you’re done. The device is installed, no weird 3rd-party signing packages needed.

  2. (Same situation) Unfortunately tried bypassing digital signature and still needed complained on needing one. Then, with this method I also tried setting it up as WinUSB (Successfully), but still EasyFlash 3 did not recognize the FTDI connection.

    Any thoughts for possible issues or debugging…
    Using Windows 10, and I validated all EF3 prerequisites

    1. Well I can definitely repro the problem. Newest version of Win10 and I cannot upload anything either. I will look into the problem and see what I can find.

    2. What did you get in the programming window. Was it:
      Send PRG file: Filename.crt
      Send command: EFSTART:PRG

      or was it:
      Send PRG file: Filename.crt
      Send command: EFSTART:PRG
      Got response: “WAIT”.
      Send command: EFSTART:PRG
      Got response: “LOAD”.
      (LOAD) Start to send data.


      I am getting both and once it actually programmed the file.

    3. One more question. When you do try does anything happen on the C64? nothing happens in the first case and in the second case it goes to a blank blue screen. I am just trying to see if I can repro your issue.

    4. Also have you tried the command line tool in the easytransfer folder? Running the command line it worked everytime, in the GUI it was really hit or miss.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.