Glitch in the installation sript?
Posted: June 8th, 2025, 9:51 am
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.
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.