search

microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
111.14k stars 6.54k forks source link

Fresh / firsttime installation of v0.23.0 fails, but upgrading from 0.21.1 works #7008

Closed jhb closed 4 years ago

jhb commented 4 years ago

ℹ Computer information

📝 Provide detailed reproduction steps (if any)

  1. Have a (relatively) new windows, where powertoys was never installed before
  2. Download exe from github
  3. Click install as normal user
  4. Wait very, very long - the install never finishes.

✔️ Expected result

Have a quick install experience, with powertoys being available after the install.

❌ Actual result

A very slow install notification in the message pane (or whatever its called), which finally will stall at 99%.

Workaround

Fix this by installing 0.21.1 first, and then upgrade from there

ghost commented 4 years ago

@jhb If you have winget try:

winget install powertoys

Winget is package manager for Windows

jhb commented 4 years ago

@alannt777 I have it installed by using the the described workaround.

ghost commented 4 years ago

@jhb Ok

enricogior commented 4 years ago

@jhb

Wait very, very long - the install never finishes.

This doesn't provide enough information to be able to do any investigation. At what point during the installation did it stop?

jhb commented 4 years ago

@enricogior as I wrote, it never finishes, but stalls at 99%. Ok, I didn't wait for eternity, but waited for maybe 20mins or so, then rebooted.

enricogior commented 4 years ago

@jhb PowerToys was not present in the StartMenu?

jhb commented 4 years ago

@enricogior nope

enricogior commented 4 years ago

@jhb did the .msi part of th einstallation start?

image

if it started, did it reach the end?

image

jhb commented 4 years ago

@enricogior no, the msi part did not start. Just the message in the message pain / notification area

enricogior commented 4 years ago

@jhb OK, so it stopped while downloading or installing .NET Core, it might have been just a glitch during that part. So it's not that 0.21.1 "fixed", very liked it would have worked as well just running the 0.23 installer again. The only way to know it, would be to uninstall 0.23 and .NET Core and reinstall 0.23 again.

jhb commented 4 years ago

@enricogior I tried the installer about 3 or 4 times, before installing 0.21.1. Every single time the same problem. I also tried manually installingthe .NET Core 3.1 Desktop Runtime, but couldn't, because I had a newer one.

So, the only fix that worked for me was installing 0.21.1. As I have written :-)

In regards to uninstalling everything etc. - I am quite happy with it finally running now. I just wanted to help with the bug report, not do a full debugging session - I would hope that m$ has enough resources for that :-)

enricogior commented 4 years ago

@jhb

In regards to uninstalling everything etc. - I am quite happy with it finally running now. I just wanted to help with the bug report, not do a full debugging session - I would hope that m$ has enough resources for that :-)

I understand that, but this is an open source project with limited resources, so no, we don't have the resources to investigate all issues ourselves.

jhb commented 4 years ago

@enricogior fair enough. I trust in the power of google to find this bug report, if anyone else encounters the issue. Thanks for you looking into it!.

enricogior commented 4 years ago

Closing this as duplicate of https://github.com/microsoft/PowerToys/issues/5545