squidowl
Win11 Error message during install - property for shortcut could not be set
Windows 11, fresh install 2025.9 using halloy-installer.msi
Warning 1946.Property 'System.AppUserModel.ID' for shortcut 'Halloy.lnk' could not be set.
Will take a look.
@darienm Which W11 build exactly you installed? Additional question: You got PowerToys or anything like that installed? For example W11+PowerToys trigger this type of error.
Windows 11 Pro, 24H2, build 26100.6584. Installed 2025.9 release halloy-installer.msi Yes, am running PowerToys.
I think this is related to PowerToys and not an issue of Halloy Installer. See: https://github.com/microsoft/PowerToys/issues/34391
It should be fixed in PowerToys. Could you check that you have the latest version installed: https://github.com/microsoft/PowerToys/releases
Yes, I've been running the latest PowerToys 9.42.2 since it was released a few weeks ago. And I don't use PowerToys.PowerLauncher.exe running (I only have a very few PowerToys modules active.)
It seems that something is interfering while the installation is running. I cannot reproduce this warning on a fresh and clean Windows system, but under certain circumstances having Scope="perMachine" might trigger it.
I’m considering changing the installer to use perUser scope, which is generally more appropriate nowadays. However, I need to check for possible side effects first, especially regarding existing Halloy installations. I’ll update this issue once I decide whether to change the scope.
In the meantime, this warning should be harmless — Halloy should install and run without any problems.
Thanks a lot!
I have looked into the "perMachine" and "perUser" scopes in detail. Although I would personally prefer "perUser" (for example, for security reasons), I would recommend keeping the installer as it is for now. The reason is that with a "perUser" installer we lose some features we currently have — most notably the URL handling (Microsoft no longer supports this for "perUser" installers... for security reasons, keyword: URL hijacking).
I do have a working "perUser" installer and can provide the code for it if needed, but it lacks the URL handling functionality. In current Windows 11 versions, this can no longer be changed manually unless the software is distributed via MSIX, for example through the Microsoft Store.
Whether we want to support MSIX and drop MSI altogether is something we can discuss separately.
As for the issue itself: I’ve tested various scenarios but haven’t been able to reproduce it so far. I’m also convinced that the problem is not caused by the installer.
regards Kai