That's because there are many different versions of Sonic Studio 3 by ASUS/A-Volute people have installed...
Generic short replies in this thread won't help.
Users must specify what version of Sonic Studio 3 and Sonic Radar 3 they have installed, if they use the UWP or normal "desktop" versions, if SS3svc32.exe was launched under AutorRun, if they had 2 tasks in Task Scheduler and what was the execution command
contents in there etc. etc. Moreover some users don't use UAC (!!) or keep at default settings while others use UAC at max level ( = confirm ALL admin actions)...
No offense, but reading that some users to solve UAC prompt do force the exe to run as Admin (!?) is also nonsense and show poor knowledge of what UAC is and why it does pop-up ( = exactly to gain higher token privileges as Admin
because SS3svc32.exe actually needs them for some reason after KB4517211...).
ATM from my analysis, on my default installation of desktop version of Sonic Studio 3 (3.6.42.51937) on a gaming laptop ASUS GL703GS, with UAC at max level, my clues show that
ss3svc32.exe needs Admin rights because at every launch (e.g. from 'Sonic Studio 3' Start menu icon the command line for me is: "C:\Program Files\ASUSTeKcomputer.Inc\Sonic Suite 3\Foundation\SS3Svc32.exe" /command SonicStudioSystray OpenUI /start SonicStudioSystray)
it re-creates two tasks in Task Scheduler named SS3svc32Run (and SS3svc64Run) that seem to be a workaround for ss3svc32/64.exe themselves to be automatically elevated to higher privileges (without prompting UAC) using parametric arguments at launch
(the command line for SS3svc32Run, using "highest privileges", for example is: "C:\Program Files\ASUSTeKcomputer.Inc\Sonic Suite 3\Foundation\SS3Svc32.exe" $(Arg0) $(Arg1) $(Arg2) $(Arg3) $(Arg4) $(Arg5) $(Arg6) $(Arg7)), but for some reasons
a) this workaround doesn't work anymore
b) as I mentioned ss3svc32.exe tries to re-create the above tasks in Task Scheduler at every single run after KB4517211 (???) and this alone could be the cause of UAC prompt...
One thing is sure: it all started after KB4517211, and users with this problem who removed that Windows Update confirmed they solved this minor yet annoying issue and everything went back to normal, so MS/ASUS should investigate WHY...