Because the slowdown happens only in the standard account and not in the administrator account on the same PC and same folders, the problem is most likely profile-specific rather than disk, hardware, or the Windows installation.
A practical way to troubleshoot it is:
- Confirm it is profile-specific
- Test the same folder from another local account.
- If the other account is fast, that points to per-user Explorer state.
- Restart Windows Explorer
- Open Task Manager with Ctrl + Shift + Esc.
- In Processes, select Windows Explorer and choose Restart.
- This is a quick check for a stuck Explorer process.
- Clear Quick Access history
- Open Run and go to:
-
shell:recent\AutomaticDestinations -
shell:recent\CustomDestinations
-
- Delete the contents of both folders.
- Then restart the PC.
- This removes Quick Access shortcuts, but not the actual files.
- Open Run and go to:
- Check for Windows updates and restart
- Go to Start > Settings > Update & Security > Windows Update > Check for updates.
- Install available updates and restart.
- Run the System Maintenance troubleshooter
- Open Control Panel.
- Set View by to Large icons or Small icons.
- Select Troubleshooting > View all > System Maintenance.
- Select Next > Try troubleshooting as an administrator.
- Check system files
- Run System File Checker as described in Using System File Checker in Windows.
- If File Explorer itself is unstable, run Startup Repair
- Go to Start > Settings > Update & Security > Recovery.
- Under Advanced startup, select Restart now.
- Then choose Troubleshoot > Advanced options > Startup Repair.
- This is more invasive than the earlier steps, so use it after the simpler checks.
- Focus on the user profile if the issue remains
- A similar case showed that when Explorer is slow only in one account, the issue can be tied to per-user shell state in the profile.
- Since the same files in the Public folder are fast under the administrator account, that strongly supports a user-profile cause.
- The most direct confirmation is testing with a fresh local account.
If the fresh account is fast, the supported conclusion is that the slowdown is tied to the affected user profile rather than the files themselves.