I'm really stuck trying to figure out how to configure FSLogix in our RDS environment. We're using FSLogix profiles, but we're running into a problem where neither Chrome nor Edge can install extensions. Every time they try to install, an error pops up saying it can't read a file after the CRX extension has downloaded. I've narrowed it down to FSLogix being the issue, because when I exclude accounts from FSLogix profiles, everything works fine.
To try and solve this, I've done the following:
- Created a redirections.xml file that excludes the Chrome and Edge 'User Data' paths from FSLogix.
- Adjusted the SetTempToLocalPath settings to keep temp paths local and include them in the FSLogix profile.
I'm looking for any suggestions or pointers to help resolve this problem, or advice on how to get useful logging info from Edge or Chrome to diagnose why the extension installation is failing.
3 Answers
Funny story—it turned out to be my own oversight! I was running an outdated version of FSLogix. After updating to the latest release, everything works perfectly. Just a reminder to always check the basics before escalating issues!
The problem with installation may stem from browser security features. When User Profile Disks are set up as links, browsers tend to reject access to these paths. Unfortunately, it appears there’s no fix for this issue; there's even a decade-old Chrome bug that’s still unresolved.
Have you checked where %temp% leads you in File Explorer? You know, depending on your SetTempToLocalPath setting, it could either be in 'C:Userslocal_USERNAMETemp' or 'C:UsersUSERNAMEAppDataLocalTemp'. It seems like the installation fails in both places.
Got it! So, the failure persists there too. That’s peculiar.
Is that the case? The nearest matching bug I can find mentions issues with dynamic disks, and it’s flagged as fixed. Could it be different?