The earlier thread (https://community.roonlabs.com/t/raatserver-exe-not-launching-on-clean-install-of-roon-build-952/203687) has been closed, but I wanted to make mention of the solution, in case anyone else experiences similar issues.
I should point out that everything – OS, Roon, ASIO4ALL, &c – is up-to-date. I did, subsequent to resolving this issue, have some issues with ASIO4ALL, but have managed to get them sussed out.
I’m using Bitdefender, both AV and VPN. It turns out that the issue that made it impossible for RAATServer.exe to launch, thereby making it likewise impossible to configure anything other than the Roon Tested AirPlay audio output, was Bitdefender’s VPN. Turning it off made it possible to install and add Roon Ready audio outputs (e.g., ASIO4ALL v2). Similarly, turning it back on when running Roon will eventually cause Roon to stop streaming.
This is obviously an issue with my VPN and I will broach it with Bitdefender support to try to find a resolution, because not being able to use VPN kinda defeats the point of, you know, having VPN.
This is a new issue for me, within the past week or so. I had previously had no issues with Bitdefender conflicting with RAATServer.exe.
I hope this is will help others who might experience similar issues.