dotnet installers cannot be started elevated on windows

[stephanbertl]

When trying to launch any of the dotnet installers from an elevated windows cmd or powershell, simply nothing happens. I have oberved the behaviour on multiple windows 10 PCs. It simply does not open any windows and does nothing:

The only way to install them is by running them as a normal user and then clicking the install button.

This creates some problems, because it's not possible to install the runtime through automation scenarios like "Windows Software Center".

I have observed similar installer behaviour with other packages like Visual C++:

It this by design? Why? Is this even the right place to log this issue?

[joeloff]

Can you provide a log from when you launch from the elevated prompt? It's possible there are policy settings that prevent this because running from an elevated prompt would bypass UAC.

Let's start with the log. I'd also suggest checking the Windows Event Viewer to see if anything related issues were logged.

[stephanbertl]

I believe you are right. It seems to be a problem with AppLocker and the specific kind of installer. We will investigate - still might be interesting what the results are.

[joeloff]

If you can get logs from the installer it would help. I've tried this on a couple of machines and the installer works as expected when launched from an admin prompt. It's possible there's a policy configuration that's excluding the installer, but something should get logged when you launch the process. Might be worth it to also check the event viewer logs in case the policy completely blocks the application from even starting up.

[joeloff]

If you open the Local Security Policy console, do you see an rules defined for Windows Installer or Executables?

[marcpopMSFT]

Old issue triage: closing as not repro