Windows 10 and USB Gadget

did you install nomad? that should install the gadget drivers as well.

I have it running on Windows 10 with Eos v2.3.2 Nomad. I don't recall having to do anything special to get it to work.

AFAIK, UpdaterAtor doesn't update Gadget or Nomad.

Is there any chance you've got the wrong Nomad installer?

https://www.etcconnect.com/Products/Consoles/Cobalt-Family/Nomad/Software.aspx

https://www.etcconnect.com/WorkArea/DownloadAsset.aspx?id=10737482473

Thanks. Have downloaded the right installer. Installed Nomad before plugging in the dongle, as specified in the set-up guide. When I go into Device settings for the PC it says that drivers are unavailable for the gadget. Have tried a clean install and a different laptop (also running windows 10 though) but the same problem. Installed on my macbook and it works good as gold.
Thoroughly confused!

I am having the same problem on a new windows 8.1 computer. I have installed and uninstalled Nomad PC many times. I even went back to build 44 from the beta. The gadgets(I have 2) do not show up in the I/O tab of the shell, they don't show up in the About System screen in Nomad, and in Tab 99 , when I plug them in, they give me an error 50 and they are never identified as being a gadget. My gadgets work fine on Mac and have worked fine on an older windows 8.1 laptop. I have full administrative privs and I see the same thing that Natalie is seeing in the device settings. Computer is Asus All-in-one 19.5" Touchscreen. Intel Core i5 2.2ghz 64 bit, 8gb ram

Can you tell me the exact nomad installer you downloaded and installed with so I can attempt to reproduce this?

I used the latest released Nomad PC installer from the ETC Website. I was able to re-install the drivers manually from the device manager and that worked. The drivers were in the ETC Program folder, but didn't install when the gadgets were plugged in.

So I think what is happening is that the InstallShield Version that the driver package was built with doesn't support Windows 10 fully. I confirmed that I the drivers didn't show up for me by installing the 2.3.2 Nomad version on my Windows 10 VM. I then took the driver installer package as built by our new version of InstallShield and the driver seemed to push into the system as expected. This is something that we will address in a future release.

In the mean time, as jpgagnon mentions you should be able to manually install the device driver through device manager from the Program Files\ETC\HighSpeed_Pipeline_Drivers location. If you need assistance with this process, please don't hesitate to reach out. We have an installer package that we could potentially make available as well to see if the new installer package would work for you.

worked fine under win10 for me, but had a problem with win7 professional...

Can you tell me more about the Win10 install that worked and the Win7 install that doesn't please?

installed 2.3.2 under win10, nomad dongle worked (although there was a problem with the permission for a certain part of the safenet drivers), gadget was recognized fine. no need to manually or re-install.
on a client's win7 professional setup, nomad installation of 2.3.2 looked like it was working. no error message (at least not a visible one). dongle was recognized, nomad would start. but it had no library. and when connecting a gadget i would get the error of unknown device. checked the hard drive and could find the pipeline driver in the ETC directory. installed manually, worked fine. for the missing library i downloaded the most recent library patch and installed it through the shell. worked fine after that.

there have been other reports about library missing after installtion of 2.3.2. don't know if here in the forum or in the facebook group

ETCnomad_Eos_PC_v2.3.2.9.0.45 was used on both?

Yes. On the win 10 PC I had a previous nomad version (not sure which, probably 2.3, but might have been a beta), but on the win7 PC no nomad had been installed before

I don't suppose you have dates for when these both were initially installed?

win10 (successful) nov 19
win7 (semi-successful) nov 4