aidanodr is correct, if you do the gpedit trick, it will not come back. Obviously, one has to be sure about disabling AV, but if one is comfortable, that will work.
 
I've done it on about 50 machines, and none have had Defender come back.

OK.
 
I have now added back AVAST. This time I used another tip I saw elsewhere re avast. Some say its best to download the OFFLINE install file for avast. These are found in the AVAST FORUMS .. obvious location / sticky when you go there. Using the website download buttons downloads the online install app. Apparently that can sometimes not install avas properly.
 
Since doing this I have avast running fine so far. In avast I have EXCLUDED all my audio folders from Avast shields via setup / exclusions over right.

All seems well in my Sonar world again :D

Here is another one for y'all. I looked at processes and fround "Microsoft Compatibility Telemetry" was giving constant 90%+ High Disk Usage. So using GPEDIT once again you can disable this. The minute I did so the disk usage dropped like a stone.
 
Check procedure out here:

https://www.drivereasy.com/knowledge/windows-10-microsoft-compatibility-telemetry-high-disk-usage-solved/
 

aidanodr

Here is another one for y'all. I looked at processes and fround "Microsoft Compatibility Telemetry" was giving constant 90%+ High Disk Usage. So using GPEDIT once again you can disable this. The minute I did so the disk usage dropped like a stone.
 
Check procedure out here:

https://www.drivereasy.com/knowledge/windows-10-microsoft-compatibility-telemetry-high-disk-usage-solved/
 

You can also disable the related tasks via Task Scheduler > Task Scheduler Library > Microsoft > Windows > Application Experience.
 
Also note that Gpedit is only available in Windows Pro, not Home.

How ever I have found my most satisfying experience with fastest Sonar was that breif moment when I had Defender disabled and no other AV installed ... Ah well :D
 
 

I was faced this issue many time but thanks to really solved very easily.  
 
 

I've had some frustrations with USB midi controllers that I can reasonably nail down to the Creators update, as I'm sure they were OK the day before the install happened. 
Of course I did just have surgery under general anesthetic 3 days before it installed, so it could be the morphine talking 
 
I have a Roland FA06 keyboard, an Nektar Impact LX25 and an AKAI MPK mini Mk2, all of which I use at various times as a midi controller. I'm currently running Sonar on a Macbook Pro via a bootcamp Windows 10 ( I do have a PC as well but this is at my studio and I can't drive at the moment to check it out there).
 
Outside of Sonar, they can all drive my virtual instruments via midi without any problems. Inside its a different issue.
The LX25 and the MPK mini appear as valid midi inputs / outputs but can the virtual instruments get triggered when I play them? Nope. Not a whisper.
The FA06 does seem to work, but even that has been a bit flaky - once I was working on it, went away for an hour or so and when I came back it no longer worked - had to reboot to get it started again. Another time it worked if I created a new project and inserted a virtual instrument, but not on an old one (which has subsequently started to work again). Also had one point where the midi playback was triggering a continuous note on the FA06 and I had to switch it off to shut the thing up.
Haven't had time to try dusting off the 5 pin midi cables and plugging in via my desk's midi input (a Yamaha N8 which then comes in over firewire) but that would only work for the FA06 anyway.
 
Has anyone else had these kind of problems? Looking at the standard USB audio drivers that Windows uses for this they do appear to have been updated in the Creator's update. I tried re-installing drivers for Nektar / Akai but they are older and don't seem to be related to the core USB midi transport - more the additional control functions.

Ok, weirdness continues. Just used the ancient MIDI-OX  app to check the midi flow for the AKAA MPK, which seemed fine. Loaded up Sonar with MIDIOX opened and as expected if I tried to apply the MPK midi inputs / outputs got a message saying 'not enough memory', which is what happens if two separate apps try to hog the same midi devices like this. 
Then I close MIDIOX, re-apply the MPK midi inputs in Sonar and Hey Presto! It works!
 
OK, so seems I have at least one way around it, but seems awfully ropey to me
 

Never had a problem with Windows Defender.
If you have, it's better to temporarily deactivate it while doing music, and reactivating it afterward. There is no need to gpedit your computer into malware.
 
 

You can fix it very easily with Using Group Policy Editor.

• Press windows + R Key now
• Type gpedit.msc cmd and hit enter.
• Now just find "Data collection and Preview Builds”
• And Disable t.

You follow complete way for further steps.
"https://www.howtoseeks.org/microsoft-compatibility-telemetry/

Thanks

No problems here. As suggested you can run it when surfing the net, then turn it off when disconnected and running SONAR.