Forum Discussion
Photos App not working "Invalid Value For Registry"
I've had this problem reoccur for multiple Azure Virtual Desktop customers throughout the last years (multi-session Windows 10 and 11). When a user tries to open a .jpeg or any other photo-file,...
Our WorkAround is to open the Photos App (search for it in the search field), close it again. Then it works - for some time.
Ditto, we just get people to open and close the Photos app but it is a utter pain, we are 99% sure this is to do with the app updating and either different hosts ending up with different versions of the same apps or the registry referencing the old build version number.
To be honest having just had a load of issues with AppX deployments with FSLogix on Windows 10 hosts recently due to a regression in an update in July, and having been looking at the FSlogix logs I do have to question the logic in making everything retched modern apps updated via the app store and then basically re-deployed into each user session every login; I was looking and at each login our hosts report they process like nearly 70 AppX packages, none of which are third party packages, all are Microsoft in-box apps or there dependencies - can anyone explain to me what was wrong with say calc.exe, a file that is about 1MB and statically installed on the host at machine-wide level and why something bloated to 21x the size is an improvement!
To be honest having just had a load of issues with AppX deployments with FSLogix on Windows 10 hosts recently due to a regression in an update in July, and having been looking at the FSlogix logs I do have to question the logic in making everything retched modern apps updated via the app store and then basically re-deployed into each user session every login; I was looking and at each login our hosts report they process like nearly 70 AppX packages, none of which are third party packages, all are Microsoft in-box apps or there dependencies - can anyone explain to me what was wrong with say calc.exe, a file that is about 1MB and statically installed on the host at machine-wide level and why something bloated to 21x the size is an improvement!
This again started yesterday. Opening the photo app and closing did not solve it. Running the powershell command to disable development mode has but the file icon has not been restored. It is just ridiculous that this even happens.
