Browsing OneDrive dossiers avec Explorer on Windows 11 Lent

Windows Client (10, 11, 12) Performance & Dépannage
,
1

Browsing dossiers that are synced by OneDrive is extremely lent. Every navigation action takes a 10+ second delay, even si le dossier is empty. J’ai trouvé a similar problème description sur le Microsoft Forums sans fix.
Common is that the problème occurs depuis the upgrade to Windows 11. When monitoring Explorer J’ai remarqué that during the delay a massive amount of registry queries is performed by explorer dans le *HKCU\Software\Classes* space.
See Screenshort Sysinternals Process Monitor

Strange is that when navigating the same dossiers using the tree sur le left part of Windows Explorer écran the problème ne occur. Same for fichier open/save dialogues, they ne suffer depuis le performances problème.

J’ai déjà tried enabling the old Ribbon in Windows explorer sans any success.

Running latest version of OneDrive (22.248.1127.0001)

Anyone who has a solution to this problème?

Mise à jour
The problème has disappeared sur mon laptop. Je ne peux pas pinpoint to a specific mise à jour, but my current OS is Windows 23H2 Build 22631.4317 and OneDrive version is 24.186.0915.0004.

2

J’ai essayé de solve the problème by uninstalling OneDrive, removing all OneDrive Application and Data dossiers depuis le ordinateur using the following script.

:: Removing remaining OneDrive folders.
rd "%UserProfile%\OneDrive" /s /q
rd "%LocalAppData%\Microsoft\OneDrive" /s /q
rd "%LocalAppData%\OneDrive" /s /q
rd "%ProgramData%\Microsoft OneDrive" /s /q
rd "%systemdrive%\OneDriveTemp" /s /q

:: Removing remaining  OneDrive registry keys.
REG DELETE "HKCR\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f
REG DELETE "HKCR\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f
REG DELETE "HKCR\Software\SyncEngines\Providers\OneDrive" /f

Did a reinstall of latest OneDrive version avec /allusers parameter.

Après configuration and syncing OneDrive I started adding également SharePoint dossiers that J’étais syncing. Initially it looked ok, but après a number of dossiers the problème is back again. Will continue to zoom in on what SharePoint location is causing the problème. Maybe removing them un par un is enough to solve the problème and track down the root cause…