[Solved] Clicks, Pops, and Other Hazards

This is an accumulation of wisdom from other posts, and some peculiar zigs and zags. And something I just went through.
 
Happy Times:
 
1. I had four audio interfaces (Line 6 KB37, three Focusrite Scarlett 1st Gen interfaces (two 18i6s, and one 2i2)).
2. Everything was working - no glitches.  Latency was a bit slow on the Focusrites, all was well otherwise.
3. Focusrite 2nd Gen stuff came out touting marked improvements in avoiding latency.
4. Sold my three Focusrite 1st Gen units on Craigslist, essentially got my money back, bought the 2nd gen units (now have two 18i8s and one 2i2 - all 2nd Gen).  Essentially just traded up with almost no cost.
5. All was well.  KB37 was great, 2nd Gen Focusrites were great, no glitches, and latency issues gone.  Big improvement.
6. KB37 doesn't have a MIDI connector, so using Focusrite 18i8 for MIDI input for Roland TD-12 Drums.  Addictive Drums now works amazingly well for recording/tracking, TD-12 performance, Focusrite 18i8 is the MIDI receiver and the audio interface.
 
Plot Complication:
 
7. Windows 10 automatic update rolls in.
8. Pops, clicks, glitches at the lower buffer sizes in my Focusrite units.  KB37 still worked fine.
9. No longer could capture TD-12 drums due to the pops, glitches.  Not to mention guitars, vocals, etc at faster latencies.
9. Researched the forum and elsewhere, tuned my Windows 10 settings, downloaded DPC Latency Monitor.
10. DPC Latency Monitor, even when not running any audio program like Sonar, said my laptop had issues and would suffer from audio dropouts and pops and clicks.  Pointed to my bios and networking connections. My DPC Latency charts were ugly and in the red.
11. Tried ASIO4ALL.  Nice tool, but didn't help with glitches.
12. Tried reinstall of all my Focusrite drivers etc.  No change.
13. Visited my bios and there were no settings that would help.
 
Zigs, Zags, and Solutions
 
14. Called Sweetwater Support (where I had obtained the Focusrite 2nd Gen units).
15. Sweetwater Tech Support is fantastic!  In a nutshell, they logged in remotely to my system, verified I had tuned my Windows in all the right places.  Examined the whole schmeer, and pointed to the obvious thing I needed to fix.
16. Sweetwater demonstrated that I needed to turn off my network devices through Device Manager in the Control Panel (both the wireless and LAN ones). 
17. After following this procedure, the DPC Latency Monitor showed I had no issues in the system.  Pretty green graphs. Yeah!
18. After following this procedure (of disabling my network devices in Device Manager), I had no clicks, pops, glitches with either my KB37, or any of my Focusrite Scarlett audio interfaces - even at the lowest buffer settings. Amazing!  Just that one trick - before tracking/recording in Sonar, just pop open Device Manager, disable the network devices.  When finished with tracking, then just re-enable them.  Easy two clicks.
 
The Plot Thickens!
19.  Happy with my new settings, I open a regular, tricked out Sonar file (with my Network devices disabled). Tricked out meaning I had lots of tracks and effects.
20.  I get an error message that says My Waves licenses are gone. Like gone, gone. Ugly gone.
21. Researched the Web, found several ideas for this including using the Waves Recover option (which can be used once a year).
22. Found one obscure post that said they had talked with Waves support, and Waves suggested toggling the disable/enable several times for the network devices in Device Manager and it might find the licenses again. Otherwise, the user could buy a whole bunch of WUP.
23.  Tried that, and indeed after several attempts I was able to get my Waves licenses once again to be found by Waves. Whew!
24. The discovery is that Waves Central, if you store your licenses on your machine, stores all the Waves licenses related to your Network adapter.  So if it's disabled Waves throws an error message that your licenses are gone. Even more disconcerting is that after re-enabling the network adapter you still see the same message. It's only by repeat toggling that you can try to get them to come back like I did.
25. So, I had three options: 
  A. live with the glitches and pops and not disable the network adapters, in order to keep the Waves plugins alive
  B. disable the network adapters, no longer use Waves (toss them in the trash)
  C. The winner!  Buy a new mini USB flash drive (essentially a Waves dongle), transfer my Waves licenses to that, then disable the network adapters when tracking. Always keep my USB dongle attached (at least when I'm in Sonar).
 
Option C above works great. 
 
Final Result:
26. Focusrite Scarlett devices work with extremely low (like none) latency, with no pops or clicks.  Waves plugins are working.  Everything works fantastic again - actually better than before. In order to get to this state of Nirvana, I open Device Manager and disable my network adapters (both LAN and wireless) before opening Sonar.
 
End of this long post.  Hope it helps someone.

Any clues or tips to get past these snags are helpful. I think in my case DPC Latency Monitor points to my network devices as being resource hungry, likely regardless of audio interface or driver. I have a reasonably modern laptop, pretty fast, but not the fastest. I think PC processing speed is also a factor.

It's good to find ways around obstacles and still be able to keep the focus on creating and mixing in Sonar, rather than being frustrated.

I hope if anyone else has similar issues this might provide some clues to help them.