Connected when updating the escribe executable not the fw, that's how I read it, but could be wrong.[/QUOTE] Yes, EScribe was already updated. The failed update was of the firmware. Sorry for the confusion.[/QUOTE] Sorry my bad, you know what they say about assumption, sometimes Windows is too slow assigning drivers and can do it if it is a known device just on a different port.[/QUOTE] Windows can sure be wonky that way... Since I'm a Mac user, had to dig out an old netbook of mine to run the software so that just adds to the slowness. I wanted to run it natively and not through parallels or bootcamp.