Skip to content

Commit 1b61dbf

Browse files
Merge pull request #10322 from craxal/dev/cralvord/se-fslogix
AB#8604: Inform of FSLogix update fixing issue
2 parents 1cc2bf6 + 53bded8 commit 1b61dbf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -479,7 +479,7 @@ If you accidentally attached by using an invalid shared access signature URL and
479479
Storage Explorer comes packaged with all dependencies it needs to run on Windows.
480480

481481
> [!NOTE]
482-
> Some components need command line access. If it's restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
482+
> Some components need command line access. If restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
483483
484484
## [macOS](#tab/macOS)
485485

@@ -840,7 +840,7 @@ docker run \
840840

841841
## Storage Explorer doesn't run within FSLogix session
842842

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:
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 certain versions of FSLogix. If you encounter the error, make sure you're using the latest version of FSLogix. If the issue still occurs, you can work around it by following these steps:
844844

845845
1. Open the Group Policy Management Console (gpmc.msc).
846846

0 commit comments

Comments
 (0)