ClickOnce application does not open from shortcut

6,257

I was able to get this working again by uninstalling the v1511 update and letting it reinstall. Uninstalling the update by itself did not get it working again, but once the update installed again, my ClickOnce application seems to be working normally. Thanks @harrymc for your assistance.

Share:
6,257

Related videos on Youtube

dub stylee
Author by

dub stylee

Updated on September 18, 2022

Comments

  • dub stylee
    dub stylee almost 2 years

    After the most recent updates to Windows 10, an installed ClickOnce application will no longer launch from the taskbar shortcut.

    I can get the shortcut to work again by uninstalling/reinstalling the application and then pinning the application to the taskbar. Of course, this is very inconvenient, and I can not expect any other users in our domain to do this after every update of the ClickOnce application.

    It is not just the taskbar shortcut, the application also does not launch from the start menu either. I have tried searching the internet and haven't been able to come up with anything. Anyone else having similar issues or know what it could be?

    I considered the possibility that it could be anti-virus related, so I also tried disabling my anti-virus software to see if that makes a difference, and still no luck.

    EDIT:

    Here is a screenshot of the shortcut properties: enter image description here

    The full Location field reads: C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\<company name>

    • harrymc
      harrymc over 8 years
      Try the solution in the before-last entry of this thread. Take backup such as creating a system restore point, before updating the registry.
    • dub stylee
      dub stylee over 8 years
      Unfortunately, that did not help. I am able to get the application to run by running it from the deployment web site each time, but the start menu and taskbar shortcuts do not work.
    • harrymc
      harrymc over 8 years
      Please post the shortcut contents (it would be great if you could post it for before and after the application update). And which .Net version do you use and what type is your certificate?
    • harrymc
      harrymc over 8 years
      And which version of Visual Studio do you use?
    • dub stylee
      dub stylee over 8 years
      I have added a picture of the shortcut properties, which is currently not working. Unfortunately I cannot get the contents prior to the update without rolling back to pre-v1511. I am running VS2015 Community Edition and publishing the application with a self-signed certificate.
    • dub stylee
      dub stylee over 8 years
      Also, the application is a Windows Forms application targeting .NET 4.0.
    • harrymc
      harrymc over 8 years
      Please post (1) the entire contents of the Location field, (2) How do you Publish it in Visual Studio (and which version of Visual Studio)? (3) Try the latest .Net version.
    • dub stylee
      dub stylee over 8 years
      I have added the location field contents. I publish in Visual Studio 2015 Community Edition to a local IIS folder, then the program is installed via accessing that folder through Internet Explorer. I will try changing the .NET version and see if that helps.
    • dub stylee
      dub stylee over 8 years
      Unfortunately, I am limited to .NET 4.0, as some users are still running Windows XP. Hopefully in the near future I can get the last few people running operating systems from this century, and then I'll be able to switch to .NET 4.5 or newer.
    • harrymc
      harrymc over 8 years
      I have seen at least one report that says that .NET 4.5.1 is required for this to be solved (not just .NET 4.5).
    • dub stylee
      dub stylee over 8 years
      Could you post a link to that report? I have been looking for a fix for this for a few weeks now since my computer updated to v1511. The ClickOnce deployment does seem to still work fine on some other machines running v1511.
    • harrymc
      harrymc over 8 years
      See for example the last entry in this thread. This dates from before the 1511 update, and a newer .Net version now exists. Try it with the latest version - if it still doesn't work you can file a bug report.