# DO becomes unresponsive for folder that contains 800,000 files

**URL:** <https://resource.dopus.com/t/do-becomes-unresponsive-for-folder-that-contains-800-000-files/35893>\
**Category:** Help & Support\
**Created:** [June 18, 2020, 2:16am UTC](https://resource.dopus.com/t/do-becomes-unresponsive-for-folder-that-contains-800-000-files/35893 "2020-06-18T02:16:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)\
**Post date:** [June 18, 2020, 8:55am UTC](https://resource.dopus.com/t/do-becomes-unresponsive-for-folder-that-contains-800-000-files/35893/2 "2020-06-18T08:55:11Z")

</div>

A couple of quick things to check:

- Does it still happen without the Owner and/or Status columns?

- If you look in Task Manager, is dopus.exe or anything else (e.g. antivirus) using a lot of CPU when this starts happening?

- What type of drive is this happening on? e.g. Local drive, Windows network drive, or non-Windows network drive.

If you can send us some process snapshots so we can see what's happening while the program is unresponsive, we may be able to see what's going wrong from those:

> [@Manually generating process snapshots](https://resource.dopus.com/t/manually-generating-process-snapshots/34071/1):
>
> If you find Directory Opus is hanging, using a lot of CPU, or otherwise exhibiting unexplained behaviour, one important diagnostic tool is the generation of manual process snapshots (often called "dumps"). These snapshots capture the state of the Op…

---

_[View the full topic](https://resource.dopus.com/t/do-becomes-unresponsive-for-folder-that-contains-800-000-files/35893)._