Hello all, I'm running Windows 10 Home Edition, and after reading a number of posts about things going haywire after the Fall Creator's Update, I disabled Window Updates in the Services list. As I was warned, however, Windows is finally forcing an update this coming Tuesday night. I'm currently running Version 1703, Build 15063.909, and I assume I'm going to be updated to the latest version/build. The latest update I've done of Splat is the 2017.08 version. Other than the inevitable AD2 re-authorization, is there anything I should be proactively preparing myself for? I know people's issues have run the gamut from non-existent to completely debilitating, and so I understand it's a tough question to answer. I've heard about audio interface drivers maybe being messed up or switched around, not sure if there's anything else I should be looking at. Thanks in advance for any tips!

Joel

All that will happen is you might have to run XLN's on line installer and re authorize your computer. If you use iLock software the same might happen too. 
Other than that there's been nothing wrong with the last few W10 updates for me. Mine just updated last Wednesday I think. 
There's been some people complaining about certain setting changing in Windows stuff and sometime proper factory drivers get overwritten by a generic Windows driver. So just be aware of things like your Video card diver. 

If there is one thing I would suggest and that is to not allow Microsoft to touch hardware drivers in any way.  Do those manually by going to the manufacturer's websites for your various hardware.  I believe that, by far, the majority of issues that occur with Sonar after installing Windows updates is due to Microsoft choosing to install the wrong version drivers.

I am using the latest Sonar Platinum (Oct 2017) with a fully patched Windows 10 Pro 64bit machine and I have not had any issues.

I had this same problem, after 6 months of no updates, Updates came on by them self.
I pulled the plug when they started and rebooted, shut down updates again. Then came back on.
you need to remove the (update startup) from programs and features. I think there were two items.
It took a few tries to pull it back to no updating but I got there.
 

Promidi, you wrote "If there is one thing I would suggest and that is to NOT allow Microsoft to touch hardware drivers in any way." I most certainly would prefer that Microsoft not touch any drivers, but is there anything I can do to prevent them from doing so? Or just hope they don't and, if necessary, go through the process of figuring out what they changed if something's acting screwy?

After the Fall Creator update I had to reauth XLN stuff, re-disable Fast Start/Hybernate and re-disable auto optimize.  The optimize bit pizzed me off because I didn't realize it has been re-enabled until after Windows had defrag'd both of my SSDs.

After every Windows update I check Device Manager to see if Windows has re-enabled things I intentionally disabled, like HD audio and other features that could interfere with my audio settings. With the last couple of major updates Windows has left these things alone, but I still check just in case.

Windows 10 doesn't defragment SSDs, it runs trim. Trim erases deleted blocks to improve write performance and decrease the number of erase/write cycles on the disk. Trim makes SSDs faster and last longer.

toddbooster
Windows 10 doesn't defragment SSDs, it runs trim. Trim erases deleted blocks to improve write performance and decrease the number of erase/write cycles on the disk. Trim makes SSDs faster and last longer.

So if I choose the optimize tool for an SSD, it doesn't really do the defrag thing?
 
My SSDs have TRIM enabled.  A full backup immediately after the upgrade required a 30G incremental after the optimization ran.  That seems suspicious to me.

No, as far as I understand it, Windows will only defrag an SSD once a month if you have volume copy enabled (the old NT shadow copy) because it's necessary to keep the snapshots sane. Volume copy isn't default, so you probably don't have it on, in which case the storage service just runs trim when it's required.