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,...
do you use fslogix? I have the same problem and i'm starting to wonder if it is related to fslogix being in the mix. I might do a simple test without fslogix in the picture today.
Yes, we are also using FSLogix. I have noticed that it isn't very friendly to Windows Apps, so that might be logical. We cannot ditch FSLogix however.
- It is also very possible that sysprep is screwing this up as well. Either fslogix or sysprep. But here's the update from my tests this morning. I basically could NOT reproduce it because the photo app was in a "working state" from the get go. I don't currenly know of a broken user either.
BUT i tested combinations of having the InstallAppxPackages fslogix reg key set to 0 and 1 and saw no difference in behavior, either deleting the profile container and trying logging in wiht both settings AND keeping the same profile in place and toggling the setting, restarting the fslogix app service each time.
So yeah, inconclusive testing so I can't reliably reproduce this at all.
maybe the latest fslogix build resolved this issue. - Maybe upgrading FSLogix to the latest release, includes the added feature from FSLogix 2210 (2.9.8361.52326) that may include a fix for it. We'll be deploying the latest to production soon and see if it makes any difference.
Feature: Added a new process during the sign out phase, which creates an AppX package manifest for the user. This manifest is used at sign-in to re-register the AppX applications for an improved user experience. This work is on-going as AppX packages and applications continue to evolve. The focus for this work has been on the built-in Windows apps (inbox apps).- btw I'm also doing these tests with the latest release of fslogix: 2.9.8612.60056
- Its almost like when this feature was added is when we started having the issue. When was the feature introduced? I'm currently on build 2.9.8440.42104.
I'm going to test with FSLOGIX completely disabled first
then i'll test by DISABLING this setting:
https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=profiles#installappxpackages
InstallAppxPackages
Type: DWORD
Default Value: 1
Data values and use:
When enabled (1), this setting reads the AppxPackages.xml manifest file from the user's profile and installs / re-registers the list of applications. The AppxPackages.xml file can be found at: %APPDATALOCAL%\FSLogix\AppxPackages.xml.
and to tomdw, I'm not saying to ditch it. Its a narrowing down process. Then if we can say fslogix is causing it we open a ticket with Azure support. Then wait 3 weeks for them to actually work on it after trudging through all the inferior techs they try to throw at us since MS is being cheap and laying off mostly support staff.- Has anyone had opportunity to try this Registry Key? We're experiencing this with a few different environments using Windows 10 and we narrowed it down to FSLogix but haven't got any further as we went begrudgingly down the third-party route.
