XYplorer Beta Club

I built my own custom PC with multiple internal drives. My operating system is installed on a fast M.2 SSD, and I have a few other SSDs and one 14TB HDD for storage.

Since I installed the HDD, it's been slow to respond after being inactive for a while, causing a couple of seconds of freezing in my XYplorer when I first try to access it. After that, it works fine. From what I understand, this is totally normal. The HDD goes to sleep after inactivity and when trying to access it again, it takes a few seconds to spin up.

Recently, my XYplorer has become extremely laggy whenever I open a folder or change tabs, even when I'm not accessing the HDD. I tried restarting my computer and adjusting some XYplorer settings, but the issue only resolved when I disconnected the HDD SATA Cable from my motherboard.

Oddly enough, I tried downloading XYplorer portable to see if the issue persisted but the portable version worked just fine with the HDD connected. Maybe there's a setting that is causing this but I haven't changed any settings recently so I'm not sure why this suddenly started happening.

Any help would be greatly appreciated!

No, I don't think there is a valid pattern that connects the presence of a hard drive with delays in XYplorer. Windows can be funny, and a reboot is too often the solution.

Update: Several hours after disconnecting my HDD, the issue came back and now anytime I try changing directories or tabs, XYplorer freezes up for at least 5 seconds. So strange considering disconnecting my HDD temporarily solved the issue when nothing else did. Multiple reboots have not resolved the issue either.

Another update: The issue seems to be stemming from Dropbox Desktop. I quit out of the application and suddenly XYplorer is working without issue. Unfortunately, I need Dropbox always running since I use it for work and work from home. Any suggestions?

See if disabling auto-refresh makes a difference: Configuration | General | Refresh, Icons, History | Auto-Refresh | Auto-refresh

This appears to be an issue with the latest Dropbox release and the way it handles Adobe temporary lock files. I found some others with similar issues and all agree this is on Dropbox.

https://www.dropboxforum.com/t5/Integra ... m-p/780233

Thanks for the help anyways! Hopefully Dropbox fixes the issue soon.

Thanks for the info!