GPO "Global Connected Script" is beeing ignored

[doctari]

I'm trying to configure a global script, running after the client has connected. The GPO "Global Connected Script" seemed to be the right way to do it. So I'd build a BAT-file, tested it, placed it on a networkshare with public access an wrote the path in to the user GPO. the problem is, the script is beeing completly ignored by the windows client

I'd checked:

-The GPO is beeing processed by the client and writes the path to "HKEY_CURRENT_USER\SOFTWARE\Policies\SparkLabs\Viscosity" -> globalConnectedScript
-User has access to the script, a manual execution works fine
-The script path has no spaces, but to ensure i'd tried the path with quotations and without
-Viscosity version 1.10.5
-When I put the script into the connection, it works just fine ... but that should not be the way to deploy it to 250 computers
-any other GPO setting works fine.

Any ideas?

regards
doctari

[doctari]

Hm okay, seems to be a bug in 1.10.5. 1.11 works as expected :\

unfortunatly, i've got to rollout .net 4.8.1 on every win10 client now :\