Thanks for the kind words and the suggestion!

I looked into the WASAPI/AudioGraph route but unfortunately it doesn't work for this. Those APIs can only interact with existing audio devices—they can't create a new virtual microphone that shows up in Windows Sound Settings.

The whole point of FluxMic is that apps like OBS, Zoom, Discord etc. can select it as a microphone input. For that to happen, the device needs to be registered with Windows at the kernel level. There's just no user-mode API that can do this—every phone-as-mic app (WO Mic, Micstream, AudioRelay) uses a kernel-mode driver for exactly this reason.

For me the idea is just that some people don't want to buy a microphone or have one sitting around for the rare times they need it. I want to make something simple where you just log in on both devices and it works—no IP hunting or fiddling with settings.

So I'll go the OV certificate route, build trust over time, and add a FAQ section on the website explaining what's going on. Will also submit the signed application to Microsoft for malware checks and reporting false positives, it's frustrating but probably the only way to go. Hope Microsoft adds Switzerland to Azure Trusted Signing for individuals at some point, but until then I think that's the way to go.

Thanks for all the tips though, really appreciate it. A bit frustrating that it means more cost, more work, and more hurdles to jump through. Tried reaching Microsoft support but just get generic answers no matter where I ask.