jbraner
UPDATE:
MOTU support thinks that me and one other person (maybe you Rob?) are the only ones seeing this problem. I don't think anything is going to happen too quickly with this - esp if they can't reproduce the problem.

that could well be the case - if we are the only ones who bought the AVB to be used with windows ;-)
 
joking aside, this could also be a win 10 / USB controller issue ... BUT I have 3 different machines (totally different hardware) and I have seen this on either one (when using this particular driver i.e. there were occasions when the device was not recognized until after a DAW reboot and device reboot)
 
anyway, I keep researching as there are some other minor oddities (that occasional error code 0x80070426 and that 2nd ESI MIDI device that also does not always show up)

John, Steve,

I think I figured out a way to fix this whenever it happens using a simple double click on a shortcut that executes a one line script...

In case one of you wants to try this, please PM me. As the problem happens like 1 out of 30 times it's hard to reproduce and before I post the quick fix, I'd like to make sure it works (I just did a ton of reboots to get the problem twice and both time the script fixed it without requiring any reboots etc )

I just PMd you - I'll try it.

I'd say if I reboot 10 times I'll get at least one "bad" one ;-)

I've just changed over from a Intel USB port to a ASMedia one - but I don't think that will change anything...

jbraner
I just PMd you - I'll try it.

Did it work for you? Seems to be a feasible workaround here (fixed it again this morning) ...
 
BTW, just got a note from MOTU that they may have identified the problem, and I'm supposed to get a beta driver to check it out.
 
Meanwhile there also appeared a new driver version on http://motu.com/avb/index.html: MOTU AVB Installer v4.0+71271 (Release Date 2016-09-20) but I think this pre-dates their most recent troubleshooting (release news are identical to the Sep. 1 driver, so they might just have hiked build number and release date to match the most recent Mac version???)

I got your PM - I'll try to play around with it today.

I got the batch file going - but it's not working reliably.
 
It does not take me long to get a failure - once every 3 or 4 boots
 
The devcon command doesn't work with the full device ID - so I had to use a wildcard, and it restarts my MOTU MIDI interfacs as well as the Ultralite. That's OK though.
 
I used "devcon restart USB\VID_07FD*"
 
I've tried the new driver - and if anything it is *worse*.
Before - after a few times where the Control Panel default device was set for Out 1-24 rather than Out 1-2, and the devices were set at 48KHz rather than 44.1 KHz (I don't know if it matters much - but when I fixed them, it made things work) - then the batch file worked sometimes, and other times I had to run it twice.
 
I updated the batch file to restart the device, pause then do it again - but now with that new driver, even this does not work! No devices.
It seems like each new driver version gets worse for me!
 
I got a message from MOTU about new beta drivers and maybe a fix - so we'll see.
I wish this batch file was working all the time - because it's muxh easier than rebooting and pulling cables.
 
I can't play much now until next week - but I'll keep in touch...

jbraner
I got the batch file going - but it's not working reliably.
 
It does not take me long to get a failure - once every 3 or 4 boots

Sorry to hear. I had hoped it would work in your case, too, but it looks like your system is more affected by this than my DAW. I don't get the problem as often, and the script pretty much cured it for the time being.
 

jbraner
I've tried the new driver - and if anything it is *worse*.

Thanks for trying but I didn't expect that to be of much help as the release date of that driver pre-dates our support enquiries ...
 

jbraner
I got a message from MOTU about new beta drivers and maybe a fix - so we'll see.

Me too. I'll let you know once I got my hands on it ...
 

Sorry for the delay in replying to the thread. I  will be reporting this to MOTU today. I am having similar symptoms and the only things I know is that it never seems to happen when the interface and computer are up and running. I can work all day either in a DAW or just playing music, YouTube etc and I never get the failure. It's a reboot that makes things sick, at least for my system.
And like others have said, it takes various methods to get it back working again. The same method may not work two times in a row.
 
Very weird.
One question, anyone with this problem running an iLok?
I am. The original blue version with the latest drivers.
 

Steve,
Your symptoms are exactly the same as mine.
I'm running ilok - but it's a ilok 2.

Same symptom - no iLok here, though.
 
This must be a win10 / AVB driver issue.  Good thing is that MOTU is indeed on this, so please report this, Steve, and they'll probably also give you access to a driver update which "may" fix this (should be available soon)...