Kasper Johansen
Kasper Johansen
This is interesting I have started a cmd.exe in system context, I have verified that it is indeed running in system using the whoami command. When I go the the...
OK, so I tested the same thing in a Windows 10 machine same issue. I have also tested on an Windows 11 machine, that is not enrolled in my Intune...
Have you seen this: https://github.com/microsoft/winget-cli/issues/3049
> > OK, so I tested the same thing in a Windows 10 machine same issue. > > I have also tested on an Windows 11 machine, that is not...
Your suggestion seems to work. Compared to what I have tested earlier, the Set-Location is new. Is that already a part of your winget wrapper script?
I spoke too soon: 
End result is the same as before:  Remember I am executing this i SYSTEM context. It's working perfectly fine in both non-admin and admin context.
Here is the script being run from ISE as SYSTEM 
> Hi, > > I have the exact same issue, was a resolution found for this? Hi Jazzy I have not yet found a solution. It's a problem with winget...
I am having the same issue and getting this error message: Element not found. (Exception from HRESULT: 0x8002802B (TYPE_E_ELEMENTNOTFOUND)) I have not tried the KIR workaround.