Thanks for confirming that.
This seems like a different issue from the one you originally reported. The first time, the updater could detect the device is a Cure 2 but could not communicate with it. Now it seems the connection was unhandled.
We can continue looking into it on our side. It might help to get the full logs, starting at the time you run the updater.
Will do. I’ll send the logs in a PM as this thread doesn’t need that cluttering it up.
@smerret Oh, please make sure you update to the latest PreForm 3.55.1
Here’s a relevant part of the release notes:
Fixed issues with printer USB connectivity due to Another version of PreForm is using this printer and/or Unavailable Printer Detected errors
I am experiencing the same thing. FormWashCureUpdater.exe will close down after I plug in USB. If I don’t plug in USB it will sit and wait. So something is triggering it to close once USB is connected to Cure/Computer.
Hi all, can you please confirm using Windows Device manager’s Driver by type feature that the formlabs usb drivers are installed on this machine? The msi package could install successfully but the drivers may still have issues.
Thank you for this guidance. I have the following.
I note that you highlight the Form Cure L V2 (I think) but I have the Cure V2. Not sure if that makes a difference. Both drivers of the kind your arrow points to seem to be installed on my machine/account.
My default view shows the Cure V2 as “other devices”
Hi there, looks like the device is not picking up the right driver (hence the 
icon). We managed to reproduce a similar issue in-house, we are still investigating the root cause.
Sorry for the inconvenience, we will report back as soon as we find a fix or a workaround.
The workaround from @jesus.rubio to manually assign the libusbK driver seems to have been successful. Thanks
This isn’t a Cure V2 vs Cure L V2 issue — it’s a libusbK driver binding problem.
if the Form Cure V2 shows under “other devices” with a warning icon, the FormWashCureUpdater can’t enumerate it, so it just closes.
manually forcing the libusbK driver fixes it because that’s what the updater expects. until the installer consistently binds the right driver, this is basically a usb driver association bug.
How do you actually realize this driver workaround? I have the same problem where the updater closes and the Cure V2 shows up under Other Devices in Device Manager.
EDIT: Some further googling + installing and running Zadig fixed this
I received a DM from @jesus.rubio which admittedly would have been sensible for FL to put into a post on this thread. Here’s what he said and I was able to follow this to resolution.
So if you go to Other devices > Form Cure V2 DFU, it will likely tell you there’s no driver for it but you have the option to select one from your computer. Click that and select libusbK USB Devices > formlabs_form_cure_v2_dfu.inf.
After this, the Cure 2 finally showed up on the updater.
I’m sure it wouldn’t take FL community or software support members of this forum to put something a bit more structured and illustrated out here.
Can confirm this is still present. Received a brand new Form Cure V2 today, and have exactly the same issue. Ran the driver install from the support page, but the Cure V2 still shows in ‘Other Devices’.
For some reason, I don’t have the option to view ‘drivers by type’ in Device Manager either, it’s not in the menu as an option.
Yes, unfortunately the issue still exists but there is a workaround, as mentioned in previous comments. You can find more detailed steps in the Troubleshooting section of the firmware update instructions here.
