-
Notifications
You must be signed in to change notification settings - Fork 162
MS store update doesn't work on PowerShell core #656
Comments
Interesting. The step uses the Windows Powershell on purpose, regardless if Powershell Core is installed. We can also see the the output that it didn't use Powershell Core but used the Windows Powershell. I also use Powershell Core myself and don't experience this issue. What happens if you run |
If I run
|
Apparently Edit: Yup, it's missing in PS 7: https://powershell.org/forums/topic/powershell-7-is-missing-get-wmiobject/ |
@MCOfficer yes, it is. However, Topgrade explicitly runs this command in Windows Powershell. We can even see that in @blackcat-917 's output:
I also run Topgrade from Powershell Core and I don't experience this issue. I'm not sure what am I missing here |
I guess gsudo is the problem, that's the only difference I see between my system to the @r-darwish one. |
I'm fairly sure i have sudo from psutils instead of gsudo, but I'll check when I'm home. |
I use |
Mine is from psutils, but here's a new find: Scoop creates 2 shims for every application, one
But the .ps1 works!
that cmd file seems to do a bit of magic with the arguments:
|
Thanks @MCOfficer. With that insight I could finally figure out what's wrong. |
What did you expect to happen?
Topgrade upgrades MS store apps correctly.
What actually happened?
Topgrade throws an error and asks to retry.
Additional details:
Windows 10
Via
cargo install topgrade
command (currently on Topgrade version 6.6.0, this issue affects all versions of Topgradeincluding the latest)
sudo
on Windows?Because I use this
Run
topgrade --dry-run
to see which commands Topgrade is running. If the command seems wrong and you know why please tell us so.If the command seems fine try to run it yourself and tell us if you got a different result from Topgrade. (yes, I got a different result)
topgrade --only microsoft_store --dry-run -v
topgrade --only microsoft_store --dry-run
topgrade --only microsoft_store -v
The text was updated successfully, but these errors were encountered: