The PrivacyAgent.exe service takes a long time to fully start when WSL is enabled

[offhub]

On my system, PrivacyAgent.exe starts with an 8-minute delay when Windows Subsystem for Linux (WSL) is enabled. This issue could also be linked to network sharing.

[offhub]

Deleting the program containing the WSL path from the program list resolves the problem.

[DavidXanatos]

I don't think it is feasable to speed the network check up, hence I'll change the code to skip all checks on network files during startup

[Nidvogr]

@DavidXanatos Could the network check become async? One of the things I find valuable would be to gain insight into what the heck wsl is doing, but from the host. I've had malware attacks where a container was running a payload, so there's value in being able to differentiate what is actually trying to connect from wsl, instead of the bad windows default of wsl something wants to connect to foo ip. It tells the user nothing about the legitimacy of the connection.

[DavidXanatos]

I'll look into it we can always run stuff in a separate thread but then other things would be delayed.