Installed program missing from Programs and Features

[jvvong]

Squirrel version(s) 1.9.1

Description Created an installer following the getting started guide. Everything installed properly as expected except the program does no show up in "Programs and Features"

Steps to recreate

1. Create a basic installer.
2. Run Setup.exe to install the program
3. Go to Control Panel -> Uninstall a program

Expected behavior Program should be listed to uninstall

Actual behavior Program is not listed

Additional information Windows 10 install, desktop and windows shortcuts were created as expected. Also tried using custom events but that didnt work either SquirrelAwareApp.HandleEvents(v => mgr.CreateUninstallerRegistryEntry());

[anaisbetts]

Does the registry key that CreateUninstallerRegistryEntry try to create actually get created?

[jvvong]

No I dont think so, I couldnt find one.

[Bert-Proesmans]

I have the same issue. I'm deploying a SquirrelAware app and call the CreateUninstallerRegistryEntry method. The method is executed, but didn't have the desired effect.

"%localappdata%\SquirrelTemp\SquirrelSetup.log" shows no errors except

CheckForUpdateImpl: Couldn't write out staging user ID, this user probably shouldn't get beta anything: System.IO.DirectoryNotFoundException: Could not find a part of the path '[REDACTED]\packages\.betaId'.

Nothing new is created underneath HKEY_CU\Uninstall post install. There is no entry for my installed program within Programs and Features.

EDIT; Manually running Update.exe --uninstall makes my removal procedure crash because the Uninstall key doesn't exist.

[BitEnergy]

Same issue here. The assembly has "SquirrelAwareVersion". The setup creates the desktop shortcuts, the Program entry in the "start", and correctly places the program in the AppData/Local. However there's no entry in the "Programs and Features", no uninstall, and no errors in AppData/Local/SquirrelTemp/Squirrel-Install.log... any help would be really appreciated !

P.S. I'm using Squirrel v2.0.1 and I'm running the setup test under a Windows 7 machine.

[BitEnergy]

Ok, I found the culprit, and seems undocumented to me (If I'm wrong please somebody post the links). The point is that the name used for the installed package depends on the "Title" field of the Nuget Package, even though the documentation doesn't report using that field at all (at least on docs/getting-started/2-packaging.md). As a result, I had an "empty" name for the uninstall package.... Windows 7 reacion to empty name packet is to not-show the item at all. While Windows 10 shows an item with no name (but the version number). So, simply setting the "Title" field did the trick. I hope I helped someone else.