Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Create WinUtil Shortcut" not working properly with latest release. #2487

Closed
Squtzy opened this issue Jul 30, 2024 · 8 comments · Fixed by #2488
Closed

"Create WinUtil Shortcut" not working properly with latest release. #2487

Squtzy opened this issue Jul 30, 2024 · 8 comments · Fixed by #2488

Comments

@Squtzy
Copy link

Squtzy commented Jul 30, 2024

Describe the bug

When trying to create a shortcut for winutil on the latest release it creates the shortcut but when going to open winutil using the shortcut it only opens "This PC" in my File Explorer. When right clicking the shortcut it does not give me any "open with" option either. Shortcuts made before current release has worked flawlessly on 2 of my Windows 11 Systems.

To Reproduce

Steps to reproduce the behavior:

  1. Go to "Tweaks" tab in winutil.
  2. Click on "Create Shortcut"
  3. Attempt to open shortcut in saved location.
  4. Met with file explorer being opened on the "This PC" tab.

Expected behavior

When clicking/opening the shortcut I expect Winutil to open like it has done with "older" shortcut versions before.

Screenshots

Adding screenshots that show steps of issue.

Additional context

Wanted to make a new shortcut as I had cleaned up my secondary PC and removed the old shortcut without realising. After attempting to make a new shortcut I am met with this issue.
System is Windows 11: Version 23H2 (OS-version 22531.3880)
image
image
image

@Squtzy
Copy link
Author

Squtzy commented Jul 30, 2024

Apologies for my Windows being in Swedish. Hope the screenshots are still of some help

@MyDrift-user
Copy link
Contributor

MyDrift-user commented Jul 30, 2024

Hey @Squtzy, tested it on my end using the Full-Release:

image

Will look into this, thanks for reporting!

EDIT: made a PR and linked it to the issue that will fix the issue.

@Squtzy
Copy link
Author

Squtzy commented Jul 30, 2024

Hey @Squtzy, tested it on my end using the Full-Release:

image

Will look into this, thanks for reporting!

EDIT: made a PR and linked it to the issue that will fix the issue.

Oh wow that was some quick work :D Glad I could be of help :)

@Monodark86
Copy link

I'm still having the same issue with the shortcut creation link just opening up this pc with latest update

@MyDrift-user
Copy link
Contributor

MyDrift-user commented Aug 1, 2024

Yes @Monodark86 , I have created the Pull Request. Chris now has to merge this PR wh3n he accepts the changes and make a release after.
Sorry for the inconvenience.

@Squtzy
Copy link
Author

Squtzy commented Aug 1, 2024

Yes @Monodark86 , I have created the Pull Request. Chris now has to merge this PR wh3n he accepts the changes and make a release after. Sorry for the inconvenience.

Question on the topic, is it possible to manually fix a/the shortcut for the moment? :)

@NotYourAverageGamer
Copy link

Question on the topic, is it possible to manually fix a/the shortcut for the moment? :)

Yes.
I couldn't fix the shortcut WinUtil made, but I found I can manually create the shortcut by doing the following:
(this is for win10 but win11 should be the same)

  • Right-click on your desktop and go to New -> Shortcut
  • It should ask for the location of the item, copy and paste the following:
"C:\Program Files\PowerShell\7\pwsh.exe" -ExecutionPolicy Bypass -Command "Start-Process pwsh.exe -verb runas -ArgumentList '-Command "irm https://christitus.com/win | iex"'
  • Press Next/Enter
  • It should ask what you want to name the shortcut, enter WinUtil
  • Right-Click the new WinUtil shortcut on your desktop, and select Properties
  • In the Shortcut tab, select Advanced...
  • Tick the box for Run as administrator
  • Press OK then press OK again.

You should now be able to run WinUtil from that shortcut.

To fix the missing icon try:

  • Right-Click the shortcut -> Properties -> Change Icon...
  • Below "Look for icons in this file:", replace everything there with:
%USERPROFILE%\AppData\Local\winutil\cttlogo.ico

Press Enter twice, then click OK

You should now have a manually created version of the shortcut that WinUtil would usually make. :)

@sergiodevelop78
Copy link

Question on the topic, is it possible to manually fix a/the shortcut for the moment? :)

Yes. I couldn't fix the shortcut WinUtil made, but I found I can manually create the shortcut by doing the following: (this is for win10 but win11 should be the same)

* Right-click on your desktop and go to `New -> Shortcut`

* It should ask for the location of the item, copy and paste the following:
"C:\Program Files\PowerShell\7\pwsh.exe" -ExecutionPolicy Bypass -Command "Start-Process pwsh.exe -verb runas -ArgumentList '-Command "irm https://christitus.com/win | iex"'
* Press Next/Enter

* It should ask what you want to name the shortcut, enter `WinUtil`

* Right-Click the new `WinUtil` shortcut on your desktop, and select `Properties`

* In the `Shortcut` tab, select `Advanced...`

* Tick the box for `Run as administrator`

* Press OK then press OK again.

You should now be able to run WinUtil from that shortcut.

To fix the missing icon try:

* Right-Click the shortcut -> Properties -> Change Icon...

* Below "Look for icons in this file:", replace everything there with:
%USERPROFILE%\AppData\Local\winutil\cttlogo.ico

Press Enter twice, then click OK

You should now have a manually created version of the shortcut that WinUtil would usually make. :)

HI, this worked great.
The only thing that I failed was the icon.
I can't find cttlogo.ico on de folder %USERPROFILE%\AppData\Local\winutil\cttlogo.ico

Where can I find the ico file?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants