Navigation buttons in File Explorer doesn't work for some users in Windows 11 | Azure Virtual Desktop

Nikola Jankovic | Reset 35

Hey Everyone,

We have a customer that is using Azure Virtual Desktop. They use in total 3 VM's running Windows (Windows 11 Enterprise multi-session). Since recently they are complaining about not being able to navigate back and forth in the File Explorer. This option is not greyed out neither they get a error. Simply nothing happens... Sometimes the search bar is not even working, users cannot click on it. If you use 'Tab' on your keyboard then it works.

I've tested this with a brand new user account and for the first time I logged in e.g. vm1. On this account and on the vm it works fine with the navigation pane of the File Explorer. When, I log in to vm2 and test it. The navigation pane doesn't work anymore. When, I go back to vm1 then it works again...

They are using FSLogix profiles.

If there is more info needed, please let me know!

Prrudram-MSFT 22,486 Reputation points

2024-03-13T12:29:27.98+00:00

Hi @Nikola Jankovic | Reset

This is an unusual behavior. Do you allow concurrent logon with the FSLogix config (a user can log on to multiple VMs at the same time using the same profile)?

Can you please check if you use the latest FSLogix version and have the latest Windows cumulative updates installed on the VMs?
Dustin McPhillips 0 Reputation points

2024-03-19T15:32:08.8766667+00:00

I have also seen this in our environment. It has been an ongoing issue for months and we are on the latest version of FSLogix and do not allow multiple logons.
Josh Reaver 0 Reputation points

2024-04-24T10:04:23.4366667+00:00

I have made a further discovery. If you have explorer fullscreen the back button always doesn't work. If you have it in windowed mode but have it aligned on the left it also doesn't work.

It's like theres a deadzone on the top left of the screen within the session blocking mouse input, but only for explorer. So if the deadzone is there i can still interact with desktop items for instance.

I really need someone else to confirm if they are experiencing this same behaviour on their systems.

16 answers

Josh Reaver 0 Reputation points

2024-04-22T14:42:36.4733333+00:00

Ok so having the same issue on our end. I have it logged with MS support but who knows if/when they will get back to me.

Some things I have found that snap it out of it is running anything as admin on the users session. Why this works I have no idea but it seems to.

I found this out when I was attempting to run ExShell which requires elevated rights, upon running it with my admin creds. Upon doing so I went to test and was surprised to see the issue was gone, a little annoyed as I wanted to test...

I then tried on another machine and ran ExShell as admin but had the same thing happen where the issue fixed itself.

A third session had the issue so I decided to run CMD as admin and the issue was fixed in Explorer!

This was earlier today so I don't know if the issue will come back on this session or just a fresh session but this has to be some kind of indicator of the cause I just cannot figure out what.

Can some of you test this yourselves and see what you find?
Please sign in to rate this answer.
Josh Reaver 0 Reputation points

2024-04-23T12:22:00.68+00:00

Right so I found the cause, its OneDrive. Close OneDrive and the issue goes away. This is obviously a workaround but please try it and confirm. In the meantime I'm going to think of some tests I can do.
Sign in to comment
Jelle Bos 0 Reputation points

2024-04-23T06:42:14.31+00:00

We have also the same problems. Only with Windows 11 in combination with Dell Latitude 3540.
Please sign in to rate this answer.
Josh Reaver 0 Reputation points

2024-04-23T12:44:05.94+00:00

If you close OneDrive does it fix the problem?
Sign in to comment
Travis Lamming 1 Reputation point

2024-04-23T21:08:27.44+00:00

Our first client on 22H3 is having the same issue here. We will open a ticket with MS, but please update if you guys run into a fix.
Please sign in to rate this answer.
Josh Reaver 0 Reputation points

2024-04-24T07:26:10.32+00:00

What happens if you close OneDrive? This seems connected as for me it fixes the issue. Then you reopen OneDrive and the issue returns.

Travis Lamming 1 Reputation point

2024-04-24T18:37:03.77+00:00

We dont run Onedrive on this particular client, so maybe Onedrive isnt the cause but triggers whatever is happening to all of us.
Sign in to comment
Josh Reaver 0 Reputation points

2024-04-24T13:05:00.1066667+00:00

Ok I have the fix.

Delete the file %USERPROFILE%\AppData\Local\Microsoft\OneDrive\Resources.pri
Please sign in to rate this answer.
Travis Lamming 1 Reputation point

2024-04-24T13:35:34.71+00:00

Josh, any context on this? For every user? Does the problem come back?

Josh Reaver 0 Reputation points

2024-04-24T13:39:43.3666667+00:00

@Travis Lamming yes its for every user, so I have done it via GPO to just delete that file. It never comes back unless you reinstall OneDrive and the issue itself has completely disappeared.

I couldn't tell you why it works except that the file itself seems to be some kind of resource index so something inside it must not get along with the environment.

However - I have done extensive testing with 20 users and all of them have had no issues and OneDrive functions exactly as expected. It'll likely be that this is just "one of those fixes" until Microsoft sort their side out. So far I have been ignored by them for a week with me constantly chasing.

Travis Lamming 1 Reputation point

2024-04-24T16:06:31.59+00:00

This is strange, because we have the issue but arent running onedrive.

Dustin McPhillips 0 Reputation points

2024-04-24T18:46:45.4466667+00:00

I am unable to locate the file above in our User (FXLogix) profiles, in either their local_(username) or (username) folder appdata

Simon 0 Reputation points

2024-04-26T07:58:01.88+00:00

@Dustin McPhillips same here, unable to locate the file, our users do use Onedrive.

Are you able to locate the "resources.pri" somewhere else?

I did a search and found the following:

"C:\Users\username\AppData\Local\Microsoft\Teams\Resources.pri"

"C:\Users\username\AppData\Local\Microsoft\Teams\current\resources\Resources.pri"

"C:\Users\username\AppData\Local\Microsoft\Teams\previous\resources\Resources.pri"

Will check when the user reports the problem again if deleting these files solves anything.

Albert He 0 Reputation points

2024-04-29T00:39:35.06+00:00

Hi Simon, any update on this? Did it fix this issue by deleting these files?
Sign in to comment
Travis Lamming 1 Reputation point

2024-04-24T13:56:28.3866667+00:00

Josh, any context on this fix? Does the problem return? Does it have to be removed from every user profile? What does this file do? We don’t use one drive and the file is not there for folks having the issue.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

Navigation buttons in File Explorer doesn't work for some users in Windows 11 | Azure Virtual Desktop

16 answers