I can definitely confirm that all the internal USB hubs 3.1 and 2, and ALL my USB gear are working nicely since turning off the 'Fast Start' and hibernate in WIN10.  Microsoft should think about renaming that function 'Fast, but not so great, you'll think you're going crazy, Start.'
 
I have found that
 http://www.blackviper.com/
 
has some good suggestion to turning some other functions off.  It appears it was most recently updated last week, so I should also go through it to see if there are other suggestions he has made since I reviewed it about 6 weeks ago.  I will need to see if he mentions the 'fast start' issue on his web site.  I wasn't looking closely for that before.     
 

Thank all. I actually loaded ASIO4ALL for the first time in a long time, but am getting issues where those drivers will not release to allow the Saffire to run. I just disabled Fast Start and rebooted and the Saffire came online as expected, but have not tried shifting between them very much at this point.

My desktop music computer updated to WIN10, version 1803 today.  Then everything started acting a bit screwy.  CbB crashed 3 times, a control surface wasn't reported, and several other USB hub issues noticed including the power options to turn off USB hubs had been reactivated.  Plus terrible drop outs on a simple project that worked just fine before.  Then I noticed that the 'hybernation' option and the 'fast, but stupid, startup' options had been reinitialized.  Those are not compatible with my machine.  So I turn those off, and things are closer back to normal. 
 
So if you allow updates to WIN10 be aware that an update may or may not change a number of these settings.  Or perhaps in my sleep I changed all this, just to get one more post!  

Some privacy settings will change, Fast Startup will be re-enabled, power-management for USB hubs can be re-enabled, etc.  After a significant update, you'll want to check those things.

The major Windows "upgrades" such as the latest Spring Creator's Upgrade (V1803) resets most to like it was a new Windows installation.  Thus you have to reset most customized items such as the Fast Startup.  
 
You will have to reauthorize some plug-ins, too, as they think its a new PC or OS.   I had to do that on Melodyne as it thought I had installed it on too many computers (the same computer was listed twice in the authorizations) when it has only ever been installed on one.  With Melodyne, I had to have their support reset my account so I could reauthorize it for my Win 10. after the latest creators upgrade.

I am getting pretty fed up with Windows 10 borking with my machine.  Two days ago, it was the SECOND time a Win10 update changed my BIOS settings. Don't ask me how, but it did...again.  My SSD Win10 drive was missing from the boot options despite it always being connected to the SATA1 port. Fortunately, having been through this before, I immediately knew what to do after my computer failed to restart (i.e. no boot drive). I reinstalled the BIOS from a USB drive, and viola, the computer works again!
 
And just now, yet another Win update and I constantly have to reset my audio settings from Windows' default of 96000Hz back to 44100Hz!

I've never heard of a Windows update changing the BIOS settings, and I do PC support.
 

fireberd
I've never heard of a Windows update changing the BIOS settings, and I do PC support.

 
It's been reported by a few in other forums and support sites around the web, though it's not common. I think the issue is caused by the fact that BIOS's are more plug-n-play than they were before. I have no other explanation for it, but it indeed has happened twice to me so far (same motherboard though).
 

File sharing is broken again.  Even mapped drives did not work. This has been common in W10. They need to can developers who can't get this right.  Never had issues with W7.  I noticed the also removed Computer browser in Services which has to be installed again. (didn't work) I reverted back to previous version and everything works again.
 
http://www.infopackets.com/news/10330/how-fix-win10-april-update-rdp-mapped-drives-broken
 
The solutions here was not something I would be willing to try since some where a rocket science to me.
 
I'd like to meet those developers responsible and punch them in the nuts.

They completely got rid of homegroup this time around. Luckily, it doesn't seem to have broken my shared folders (yet that I can tell). The way Windows has always handled file/folder sharing has been so ass backwards and a pain to deal with.