Applications only connecting to JACK if run as Administrator

[hockinsk]

Describe the bug

Applications not able to connect to jackd.exe unless they are set to run as Administrator

Environment

• JACK Version: Which version of jack2 are you using? (e.g. the output of jackd --version or a git commit checksum) 1.9.21
• Operating System: What operating system or distribution in which version are you using? (e.g. Linux, macOS, Windows) Windows 10
• Installation: How did you install jack2? (e.g. package manager, from source) Installer from github

Steps To Reproduce

Run qjackctl > start jack > open application to connect to Jack without Adminstrator priveledges

Expected vs. actual behavior

I would expect an application to be able to connect to Jackd.exe without itself having to be running with Administrator priveldges. Is this a bug or expected behavior? The problem with some applications running in Administrator mode is, things like drag and drop break from the application, because explorer.exe cannot run as Admin, so the application isn't permitted to drag and drop. e.g. Bitwig displays this exact behavior, but I have to run bitwig in Admin mode in order to get Jack to work with Bitwig

[satchnut]

Is JACK being run with admin privileges? Check to see if both JACK/QjackCtl and the ASIO app are run using the same privileges (Task Manager -> Details tab; both should be either elevated or not elevated).

[hockinsk]

The latest updated to Windows seem to have fixed this issue on a new PC I installed JACK onto. iirc, all I had to do was take Jack out of read only default install state and it worked rather than have everything running as Admin.