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

Nikola Jankovic | Reset 45 Reputation points
2024-03-11T15:29:10.53+00:00

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!

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,422 questions
{count} votes

22 answers

Sort by: Most helpful
  1. Josh Reaver 20 Reputation points
    2024-05-24T12:08:20.9233333+00:00

    Ok so I originally posted a fix which was down to OneDrive causing the issue, but then the issue came back and it was only when Outlook was open.

    I made a GPO which turns off Win11 Explorer and changes it back to Win10 if anyone is interested just amend the following keys and restart Explorer:

    Enable Win10 Explorer

    [HKEY_CURRENT_USER\Software\Classes\CLSID{2aa9162e-c906-4dd9-ad0b-3d24a8eef5a0}]

    @="CLSID_ItemsViewAdapter"

    [HKEY_CURRENT_USER\Software\Classes\CLSID{2aa9162e-c906-4dd9-ad0b-3d24a8eef5a0}\InProcServer32]

    "ThreadingModel"="Apartment"

    @="C:\Windows\System32\Windows.UI.FileExplorer.dll_"

    [HKEY_CURRENT_USER\Software\Classes\CLSID{6480100b-5a83-4d1e-9f69-8ae5a88e9a33}]

    @="File Explorer Xaml Island View Adapter"

    [HKEY_CURRENT_USER\Software\Classes\CLSID{6480100b-5a83-4d1e-9f69-8ae5a88e9a33}\InProcServer32]

    @="C:\Windows\System32\Windows.UI.FileExplorer.dll_"

    "ThreadingModel"="Apartment"

    Re-enable Win11 Explorer

    DELETE HKEY_CURRENT_USER\Software\Classes\CLSID{2aa9162e-c906-4dd9-ad0b-3d24a8eef5a0}

    DELETE HKEY_CURRENT_USER\Software\Classes\CLSID{6480100b-5a83-4d1e-9f69-8ae5a88e9a33}

    2 people found this answer helpful.

  2. Stéphane Côté 15 Reputation points
    2024-05-24T13:26:15.3933333+00:00

    So I can confirm that it is not related to the Windows virtual desktop client, Windows365 app client, or FSLogix.

    It just happened to me on regular RDP via VPN to a Windows 11 Multisession vdi host on a non fslogix admin profile.

    thank you @Josh Reaver for this alternate older file explorer, Microsoft is still clueless about what happens here and we have to be able to have a functionnal file explorer for our clients.

    1 person found this answer helpful.

  3. Stéphane Côté 15 Reputation points
    2024-04-03T13:16:07.98+00:00

    we have same problem and behavior here, cannot click file explorer menu but can navigate and use the menu with Tab, alt and enter
    Windows 11 multi-session, up to date from yesterday and freshly re-deployed.
    Windows App from Microsoft store, up to date as well,
    fslogix hotfix 3 applied,

    Same issue this morning again.
    random user
    random server.


  4. Peter Sundelin 16 Reputation points
    2024-04-10T12:17:12.76+00:00

    Same issue here on several AVD / FSlogix / Windows 11 multi session hosts.

    Sometimes the users are unable to use copy, or delete buttons in explorer. Also the Back button doesnt work. Really annoying, started with the new explorer version.


  5. Joost Martijn van Engelen 0 Reputation points
    2024-04-19T07:53:13.8866667+00:00

    We have a customer with exactly the same problem.

    FSlogix is up to date but I think this has nothing to do with it.

    In March we were be able to fix it by updating the Remote Desktop App on the client computers but It seems like some users are experiencing this issue again.

    0 comments No comments