Fresh install via WinGet fails to launch

[nikosalonen]

Pixelorama version: 4.4.1.stable.official.49a5bc7b6

Where did you download Pixelorama from? Installed via Windows Package Manager (WinGet) using command: winget install OramaInteractive.Pixelorama

OS/device including version: Microsoft Windows 11 Pro 10.0.26120

Issue description: After installing Pixelorama via WinGet, the application fails to launch and displays the following error message:

Error: Couldn't load project data at path ".". Is the .pck file missing?
If you've renamed the executable, the associated .pck file should also be renamed to match the executable's name (without the extension).

This appears to be a packaging issue where the .pck file (containing the application's data) is either missing from the WinGet package or not properly associated with the executable during installation. This is a fresh installation with no user modifications.

Steps to reproduce:

1. Open Command Prompt or PowerShell as administrator
2. Run: winget install OramaInteractive.Pixelorama
3. Wait for installation to complete successfully
4. Launch Pixelorama from the prompt
5. Observe the error message about missing .pck file

Expected behavior: Pixelorama should launch normally after a fresh WinGet installation.

Additional information:

• This appears to be specific to the WinGet distribution method
• The error suggests a packaging/distribution issue rather than a user configuration problem
• Other installation methods (GitHub releases, manual download) may work correctly

[Variable-ind]

Hy 👋, The .pck file seems to be missing/renamed

Can you check the installation folder and tell which files are showing in pixelorama folder

[nikosalonen]

Hi @Variable-ind

• The .pck file is present in the installation directory (%LOCALAPPDATA%\Microsoft\WinGet\Packages\OramaInteractive.Pixelorama_Microsoft.Winget.Source_8wekyb3d8bbwe\Pixelorama-Windows-64bit\Pixelorama.pck)
• Pixelorama does work when run directly from its installation directory
• The issue is that the executable looks for the .pck file in the current working directory instead of relative to the executable's location as I'm trying to launch it from the current project folder in the command prompt.

[Variable-ind]

@nikosalonen Embedding the pck in the executable might fix this. i generated some builds for testing (with pck embedding enabled) could you:

• Download the windows build https://github.com/Variable-ind/Pixelorama/actions/runs/16463152258
• Remove old pixelorama.exe and pixelorama.pck
• Add the pixelorama.exe file from the build to the installation folder.
• Try running it again

[OverloadedOrama]

Hmm, embedding the pck in the executable sounds like a good idea. Unfortunately we're not the ones maintaining this package and I'm not really sure how it works, so we probably can't be of much help here. I assume the maintainers would have to generate their own builds with the pck embedded.

[nikosalonen]

@Variable-ind I'll try after I get back to computer in the evening.

@OverloadedOrama winget is pretty straightforward. Basically a PR to Microsoft's winget repo on every version update is enough and it can be done via GHA automatically. It should be possible to "take over" the current maintainer if the initial submit haven't been done by the team and you want to have control of the winget versions. During the initial submit the submitter needs to accept CLA to affirm they have permission to do so, so I assumed you're somewhat involved.

@cjmaxik seems to be the original submitter https://github.com/microsoft/winget-pkgs/pull/170556

[cjmaxik]

Hey, there is no "maintainer" per se, everyone is free to make PRs.

[nikosalonen]

@Variable-ind with embedded .pck it works 👍

And now that I can search properly, @damn-good-b0t is keeping the winget up to date. Probably if you just create a build with embedded .pck file, it'll update it.