Cmdlets working in powershell with no elevated (admin) rights are no longer working after azure cli installation

[asimeonov]

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name
``

Errors:

After install of Azure CLI most powershell cmdlets stopped working if not started as admin

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• Just installed CLI, also looks like there is an issue with Asus laptops with Ryzen 7 because after restart computer goes in endless restart and it is enabled to load the OS again regardless of mode (this happens 3rd time in row with the same laptop after Azure CLI install)
• ``

Expected Behavior

To not kill powershell nor Windows on Ryzen

Environment Summary

Windows-10-10.0.22000-SP0
Python 3.10.5
Installer: MSI

azure-cli 2.40.0

Additional Context

I have no idea how the CLI shows windows 10 I'm with Windows 11 pro. I can give some scr shots from powershell and how it stopped working. When this is not scary for most of the automation that we use on our internal systems because we can migrate to scripts that run-in administrator powershells it looks like it kills laptops with Ryzen that maybe have some registered cmdlets that can no longer be executed on startup.

As shown clearly EF is installed and this was working without admin rights before installation of CLI

Powershell run as admin, no issues.

[asimeonov]

Maybe there is some other issue but after the installation of CLI user defined PATH is no longer loaded in powershell sessions. User defined variables are now only loaded when powershell is running under elevated permissions.

[yonzhan]

@jiasli for awareness