Two weeks ago I was happily running a dual boot system (Win 7 on one SSD, Win 10 Home on another SSD) but Win 7 for 99% of the time.
 
Then one of the 1709 Win 10 updates made the Win 7 SSD no longer boot  To cut a long story short no amount of fiddling with Boot files, BCD etc would bring the Win 7 SSD back to life so I have resigned myself to running with Win 10. To be clear I didn't lose any data as I have everything backed up, it's just the time spent getting Win 7 to where it was in terms of software and configurations etc.
 
After a lot of time doing software re-installation, re-authorisation etc Win 10 is now running most of my Audio Production software so the prospect of the 1803 update breaking it again is worrying. Still I am now keeping daily Acronis Trueimage backups of the Win 10 SSD but it does force you to do updates eventually.
 
I might even try a restore of a Win 7 backup I had to the other SSD once I have retrieved any recent files from it although Win 10 cannot access the drive so I have to boot into a Win 7 recovery environment to get to it. 
 

ZincT.  If you haven't done it, disable Fast Startup in Win 10.  That can cause some of the Win 7 problems.  Many are still running dual boot systems, even with 1803 version and no problems.  
 
Here is the tutorial from the tenforums.com site
https://www.tenforums.com...rtup-windows-10-a.html

I have seen this behavior as well, but on an earlier W10 update. Maybe sometime back in January, I think.
 
That's when I noticed that the internal audio interface had been de-disabled, very surprising and likely a mistake on Microsoft's part. Even if the outboard interface had been turned off, it should still be acceptable to boot into Windows without any audio. My guess is some junior engineer couldn't imagine what use a computer might have without Pandora, but was subsequently overruled in the next build by someone more senior. Perhaps someone old enough to remember when computers didn't make any sound other than beeps, and yet were still somehow useful.
 
At that time, I simply re-disabled the integrated audio and have had no issues since, including this most recent update. Sounds like you never disabled the onboard audio so that you could use it as an alternate reference. Windows probably replaced some file that needed to guess your device, and guessed the first one on the list. This might not be an acceptable solution to you, but I think disabling the onboard audio would probably prevent this from happening again.
 
 

I use the on-board audio so disabling is not an option.  I use my PC for general PC use including the web (I'm entering data with it now) and for Sonar. 
 
Windows only allows one default audio playback device.  Up till point "x" a recording interface unit could work independent of the Windows default audio play back device with a DAW program (e.g. Sonar, Studio One 3, ProTools or whatever) but the regular PC audio would work for all PC applications.  I heard audio from the recording interface unit on my studio monitors and PC audio on my PC speakers - the way it should work.
 
I submitted feedback to Microsoft about this on the Windows Insider feedback link.  Maybe others did too and they took action to correct it???
 

fireberd
ZincT.  If you haven't done it, disable Fast Startup in Win 10.  That can cause some of the Win 7 problems.  Many are still running dual boot systems, even with 1803 version and no problems.  
 
Here is the tutorial from the tenforums.com site
https://www.tenforums.com...rtup-windows-10-a.html

Thanks fireberd; I already disabled Fast Startup a while back.  I had been running the dual boot since early on when they were giving the Win 10 update for free. I thought I would get it while it was free, even though my intention was to carry on with Win 7 as long as possible.
 
It had been running fine for a long time until the 1709 update last year which caused the Win 7 build to auto run chkdsk on startup. After that it started OK but I made a mental note to disconnect the Win 7 SSD for future Win 10 updates (which of course I remembered too late for the update a couple of weeks ago). I might still try and reinstall Win 7 though so that I have something to fall back on if (when?) Win 10 updates itself into oblivion!

Jerry,

Don't know if the problem with Boss Tone Studio has resolved. I lost the ability to connect to both the Gt 100 and GT1B tone studio after W10 1803 update. solved my problem. Basically, Settings>Privacy>App permissions>Microphone>TURN ON " Allow apps to access your microphone", you can turn off all the individual buttons, both of my tone studios reconnected immediately.

Hope this helps
LSC

joakes
Yes, it hosed my Boss GT 100 set up (I uninstalled, re-installed drivers, plus Tone Central but the latter will not connect) and also, to a lesser degree, it hosed ExpressVPN (and even support are stumped here).
 
The resulting MS KB fix didn't do anything, but I have a theory - I think its limited to W10 Pro.
 
My laptop with W10 Home, updated perfectly and both the GT 100 and Express VPN work perfectly. Go figure !
 
If anyone has any tips, for the GT 100 they are more than welcome.
 
Cheers,
Jerry

Jerry,

Don't know if the problem with Boss Tone Studio has resolved. I lost the ability to connect to both the Gt 100 and GT1B tone studio after W10 1803 update. solved my problem. Basically, Settings>Privacy>App permissions>Microphone>TURN ON " Allow apps to access your microphone", you can turn off all the individual buttons, both of my tone studios reconnected immediately.

Hope this helps
LSC

KATANA - 50 / 100 / HEAD / ARTIST: CONNECTION ISSUE WINDOWS 10 UPDATE is the article I found.

LSCowles
Jerry,

Don't know if the problem with Boss Tone Studio has resolved. I lost the ability to connect to both the Gt 100 and GT1B tone studio after W10 1803 update. solved my problem. Basically, Settings>Privacy>App permissions>Microphone>TURN ON " Allow apps to access your microphone", you can turn off all the individual buttons, both of my tone studios reconnected immediately.

Hope this helps
LSC

KATANA - 50 / 100 / HEAD / ARTIST: CONNECTION ISSUE WINDOWS 10 UPDATE is the article I found.

Yes, i also found that solution on the net, applied it and it worked !

Cheers,
Jerry

My studio desktop was 1803'd a couple of hours ago.  Nothing weird to report, my Hammerfall DSP is still the audio device.