Glitch in the installation sript?

[Winfried]

I am working on migrating from Win 10 pro to Win 11 pro.
For this purpose I bought a refurnished Dell Precision 7503 to have a playground for the migration of my "production" Desktop.
The Dell is quite a big and heavy "iron" (Intel i7-8850H, 64 GB RAM, 1024 GB SSD, NVDIA Quadro P1000). It might be an overkill for a playground, but life is so short and the toy runs quite well. Playgriund doesn't mean gambling.
So I installed the system and created a microsoft account and two local accounts (one for my and one for my wife), with no administraion rights..
I installed PWP from my personal account (non Admin). During installation I was prompted for the Admin password, normal procedure:
After installing the missing Visual C++ Runtime everything was ok... PWP runs fine under my personel account.
But for the admin and my wifes account, the files from docments\Picture Windows Pro are msissing. So PWP does not run from this accounts.
Okay, to solve this should be no big deal for me, but maybe you can have a look into the installationscript an solve this glitch.

[jsachs]

Yes, there is a problem with having more than one account. The workaround is to do a portable installation for the secondary accounts (Help/Create Portable Install).

[jsachs]

I discovered the problem with installing PWP for multiple users. To make this work, settings and other files must be stored in C:\users\<user name>\AppData\Local\Picture Window Pro and not in Documents\Picture Window Pro. Currently I use AppData only for certain files that are closely tied to a particular computer such as Color Management and Preferences settings. I prefer to use the Documents folder for settings files as it is easier to back up, but Microsoft really does not want me to store the files there even though every user gets their own Documents folder.

For the next release, I have made the necessary changes to relocate the settings folder, but it is a little tricky since accumulated settings you have created over time are stored (e.g. saved scripts and snippets, default settings for each transformation, saved settings files, etc.) in the old folder must be copied to the new folder to become available to the new version. I believe I can mostly automate this process however.