Hello frustrated IT tech,
It is excellent that you are proceeding with the local profile isolation, as identifying whether the UI refresh failure is restricted to a corrupted user hive or is a machine-wide shell fault is the definitive next step. If your test environment exhibits the exact same pinning delay, the root cause is almost certainly a rogue third-party shell extension or cloud storage overlay intercepting the File Explorer refresh threads rather than a native OS bug. In that systemic scenario, download Sysinternals Autoruns, navigate directly to the Explorer tab, and temporarily disable all non-Microsoft context menu and overlay handlers(paying special attention to OneDrive, Dropbox, or antivirus integrations).
After clearing those third-party hooks, explicitly restart the explorer.exe process via Task Manager to verify if the dynamic Quick Access UI refresh is restored. If systematically re-enabling those extensions identifies the culprit, or if your local profile isolation successfully allows you to pinpoint the data corruption, tell me the result. I'm waiting a good new!
Tracy Le.