You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md
+29-1Lines changed: 29 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -744,7 +744,7 @@ Once added to the `docker` group, restart your machine. For more information, se
744
744
745
745
### Verify the Docker context
746
746
747
-
Make sure you're using the correct Docker context that is managing your containers. You can check your current context by running:
747
+
Make sure you're using the correct Docker context that's managing your containers. You can check your current context by running:
748
748
749
749
```bash
750
750
docker context ls
@@ -838,6 +838,34 @@ docker run \
838
838
mcr.microsoft.com/azure-storage/azurite
839
839
```
840
840
841
+
## Storage Explorer doesn't run within FSLogix session
842
+
843
+
If FSLogix manages your user profile, Storage Explorer might be unable to run due to an `EEXIST` error. The error occurs due to a known issue with recent versions of FSLogix. If you encounter the error, you can work around it by following these steps:
844
+
845
+
1. Open the Group Policy Management Console (gpmc.msc).
846
+
847
+
2. Create or edit a Group Policy Object (GPO) that targets your AVD session hosts.
848
+
849
+
3. Navigate to: Computer Configuration > Preferences > Windows Settings > Registry.
850
+
851
+
4. Add a new Registry Item with the following settings:
0 commit comments