My dilemma now, is will a future update fix the issue the last update caused with UWP drivers. So am I better allowing updates to find out?

I just got a decent size Windows update just now, after my Fall Creators update last week. Lets see if the ASIO and sound driver issues get better.....

mudgel
After informing my self on the state of the Fall Creators update, 2 weeks ago I downloaded the iso for my laptop and installed it..after 2 weeks of running smoothly I decided to install it on my DAW where it is also running fine, though I did have to go into Sonar and select my ASIO driver again.

Why oh why do people get so negative?

It is as it ever has been with Windows updates. For some reason, people with very little computer security knowledge are pretty sure they know better than Microsoft what they need. Likewise one person will report a problem, a problem that was often as not partially their issue, and everyone amplifies it and takes it as an example of how evil Microsoft is.
 
A good example would be the "Vista's DRM doesn't allow high resolution audio." You probably heard it, it still kicks around online. It all traces back to an article by Peter Gutmann who installed Vista on a system with an old soundcard that then didn't work properly (full duplex mode didn't work right in Vista). Sonar, of course, worked great on Vista doing 24/96 multi-channel audio no issue.
 
I have seen it with audio pros, I have seen it with gamers, I have seen it with IT pro, people that are convinced that updates are an evil, evil thing and will break everything. Personally, I am all in on updates, not just Windows updates. At home and at work I make sure that OSes, applications, switches, storage arrays, BIOSes, etc all get updated. End result? Things work well and we largely avoid getting screwed by security issues.
 
Personally I've seen very little issue with Windows 10 feature updates. I've seen zero on my primary desktop/DAW system. We have had an occasional system at work with an issue, one laptop last week got 1709 and its net stopped working... so we told it to roll back to 1703 and not apply 1709, it'll skip to the next release when it comes out.
 
You always want to test and check updates before they go on critical systems, of course, and a DAW certainly qualifies for sound pros. But the idea that they are evil and will screw you up is just silly.

Installed the W10 Creator Edition 1709 B16299.98 last night - abt 2 hrs.  Went smooth, SPLAT runs good and the only thing I've seen is the usual switching of audio playback device to an NVidia HD device.  
I must say that the method of monthly MS Updates have gone well over the past couple of years, compared to the awful method of loading/upgrading the OS (ie, 8 to 10).  I have noticed a couple of updates that tried to load and were not successful, but it kept trying and was later fixed by a follow-on update.  It caused no issues during that time.

Not a big issue in the audio device switching, I know, but frustrating to say the least.
Other than that, I’ve mostly been very happy with Win 10 since public offering.
Call me crazy, but I don’t think you should have to reload drivers and reconfigure things that were working before for an update.
Not everyone is computer savvy, and shouldn’t have to be these days. I can’t imagine my parents dealing with this kind of stuff and not have me around to help fix it. To me, that’s bull, but hey, much worse things in the world to be dealing with for sure.
Of course guys that know computers like driving will think that is a reciculous statement, but it’s true for the 95% rest of the market share that expect, dare say need, things to just work!

Currently supporting 60+ computers for individuals and very small organizations.
Depending upon what these people do determines how i set the auto-update settings for their computers.
 
For at least half of the machines, the WINDOWS UPDATE service is stopped and disabled. 
This is the ONLY way to control w10 auto-updates. (Other concerns are all the telemetry crap.)
 
(The Store also has auto update settings for games and other worthless crap. It is disabled when the update service is disable. But if not, it will update gigabytes for the start menu,...)
 
For other client's, whom i seldom visit, updates are set to auto. And when an update is imminent i try to prepare everyone. Some clients do not want to pay for maintenance. The will pay for fixing.
 
Last week, I let one of my main work computers get updated. I have 5 TXT files that are loaded from shortcuts in the startup folder. The update not only deleted the shortcuts, it deleted ALL 5 files from the documents' folder. (Backups are my friend.)
 
The update also removed all EVENT logs before the time of the update. (Losing this history is beyond annoying.)
 
I know the EULA indicates that the MS gods will remove whatever they deem dangerous to their network,... But my TXT files were none of their concern.
 
(NONE of the computers i support are allowed to use MS logins. The EULA is clear: use an MS login and the computer, and everything on it, belongs to MS.)
---------------------
 
During the past two years, updates have: nuke USB ports, lose printer connections (12 times, including for me), video cards defuncting, audio drivers lost, ... And lots of settings changed, that have resulted in extra connection charges.
 
Now, a standard practice for me is to create a disk image before installing any big update. And then another after verifying all works, and full disk cleaning. I do not trust the roll-back function, since it is on the same disk, and gets updated by the update.
 
Because of the updates this past 6 months, I now am faced with at least 4 versions of the w10 interface, privacy settings (new and changed), STORE update ****, cortana crap, different task scheduled telemetry, and auto-maintenance,...  (Once had the defragger start during a late night recording session. Now such tasks are disabled.)
 
AND::: There is usually NO indication that an update is pending a restart. Just the computer gets less and less responsive. And some of these updates can take hours to install. 
 
I don't give a **** about MOST USED on the start menu. But I now have to endure that stupidity, otherwise the RUN box history is not retained. Stooooopid.
 
And replacing the CONTROL PANEL link on the right-click windows menu with SETTINGS: idiocy. 
 
-------------------
Last year when attempting to install a tascam interface, my main audio computer responded by not starting. And since the w10 recovery options are worthless, had to use an image.  So, now I have two computers configured for audio. Almost clones. I synchronize files after every session. I update one to test.
-----------------
 
 

Don't know if it will be better, but I installed w8.1. I re built my main studio DAW over the weekend and I still had the disk I bought when I first built it. I actually never wanted W10 but of course it just happened one night when I was sleeping and forgot to turn things off. 
 
At least W8.1 has the update feature" Tell me about updates but let me deside when to downoad and install" 
So I now have 2 more or less identicle DAW's, one with W 10 kept up to date  and one with 8.1. We'll see which one keeps going and gives me no greif. 

It definitely doesn't "break" AD2.  You just have to remove the license from the "Old version" of Windows to the new version.  Takes all of 3 seconds.  

So, last week I stopped the Windows Update service and set it to disabled.  A few days later, some event or elapsed number of day...not sure which, the Windows Update service was re-enabled (not by me) and a MS update got applied.  I did NOT restart the service.  If appears that stopping and disabling the update service in NOT effective in totally stopping Windows Updates permanently.
 
Is there another method that is effective?

Midiboy
It definitely doesn't "break" AD2.  You just have to remove the license from the "Old version" of Windows to the new version.  Takes all of 3 seconds.  

I shouldn't even have to do that.
If it was working before the update...it should still be working after the update. I shouldn't have to re-install drivers, remove this, tweak that..,so yeah...It did break AD2.
It may have been an easy fix, but it should have never happened in the first place.