Mitch Richters

I feel it's a fixable oversight that doesn't break demo compatibility, but will leave it with the powers that be 😁

Do you have a log or any screenshots or anything to help the devs out?

Agreed with DanGough, there's zero difference between escaping a double quote in a double-quoted string with another double quote, or by using a backtick.

Was something missed in the PR?

Unfortunately so, for both Windows PowerShell and PowerShell 7:  The repair command is essential because Windows images often ship with ludicrously out of date WinGet versions.

Windows PowerShell support is very inconsistent as well. Take `Get-WinGetPackage`, under SYSTEM it throws saying Windows PowerShell is not supported, however the cmdlet works fine under non-SYSTEM contexts: 

I'm currently using WinGet via the CLI while running as SYSTEM presently, it's just a cumbersome (albeit reliable) solution due to all the text parsing I have to do from...

I've been experiencing this myself and am yet to determine the circumstances. Have had it on Windows 10 and 11 machines, both of which are 22H2, both of which have...

> Experienced similar issue. After deploying the [Visual C++ Redistributables](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022) the WinGet starts normally as `SYSTEM` user. @kugelbit, this is the solution.

Wouldn't it be better on your side to use `[System.Security.SecureString]` objects rather than passing plain-text passwords around in RAM and then trying to mask them out?