I have yet to install this update but I'm sure I will eventually . Has anyone done so and if you have has it caused problems with Cakewalk? Or anything?
Thanks
WSS

The only problem I've come across is the default audio playback device issue that I documented on another thread.  If you only use the PC for DAW work its not a problem.    Until V1803, whatever was set as default audio playback device (e.g. the PC sound) stayed as default when a recording interface unit was plugged in.  But, with 1803 it now automatically assigns the recording interface as the default audio playback device. 
 
This "problem" is corrected in later OS builds.  Its back to the "old" way in the latest Windows Insider advanced OS build release.  Maybe someone realized the error (Hopefully).
 

Some impact but easily fixable. Had to re-associate addictive drums via the xln installer. A couple of my Daw optimizations were reversed. Audio options other than my dedicated audio interface that I had disabled were re-enabled. Frustrating, but I am getting used to the fix it routine now after Microsoft drops their OS update bombs.

I am watching this, too. I run Windows 10 pro and have not gotten the 1803 version yet...still on 1709. I hope the issue is ironed out before I get the update.
 
One advantage to having Windows "Pro" is that (they claim) the updates are delayed in comparison to folks running "Home". Hope this helps me this time.

I'm current and having no issues.

I've installed Windows 10 (version 1803 / build 17134.48) and haven't noticed any operational problems. In saying that, it's worth noting that the privacy settings are reset to Microsoft's preferred 'invasive' mode as are any custom 'services and scheduled tasks' settings.

Messed up my networking.  Shared and mapped drives no longer work.  The settings in Windows 10 file sharing is constantly broken with each update.

Westside Steve Simmons
I have yet to install this update but I'm sure I will eventually . Has anyone done so and if you have has it caused problems with Cakewalk? Or anything?

I had to uninstall and reinstall my modified Windows 8.1 PCR-800 driver for Windows 10. 

After the update, the PCR-800 showed as working properly in device manager, but no MIDI was being received via its USB.

The migration to the new driver management paradigm in this update to not take place correctly.

Installing the driver over the was not enough.  I had to do the complete uninstall and reinstall on the modified Windows 8.1 PCR-800 driver.

Other than that everything was smooth.

I had a few issues on the initial upgrade to 1803:

• "folders as drive" mappings gone
• focusrite audio driver needed re-installing... 4 times before it took hold!!
• AD2 needing re-authorised - this happens every major win update, so it's kind of expected now

 
Since then, there's been 2 maybe 3 updates to 1803. I have had no issues with those whatsoever.
 
M.

Actually, there was one other problem I had I totally forgot about.
 
I run VirtualBox on my Studio PC running a 32-bit Windows XP VM, mainly for some old 16 bit apps (like Korg X5D / NX5R synth editors), and some other old apps I find useful.
 
VirtualBox requires vt-x to run, which clashes with Microsoft's Hyper-V. I had Hyper-V disabled, but after 1803 it seemed to think it was back, even though the system claimed otherwise. 1803 must have partially installed it again somehow, as the services were all back.
 
If anyone else has this setup, to fix it you need to fully enable Hyper-V and disable it again:
 
Run powershell as administrator, and type:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
 
Let your machine restart etc.
 
Once you've rebooted, run powershell as administrator again and type:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
 
M.