# Directory Opus holds on to \*.rar files

**URL:** <https://resource.dopus.com/t/directory-opus-holds-on-to-rar-files/35829>\
**Category:** Help & Support\
**Created:** [June 9, 2020, 7:44pm UTC](https://resource.dopus.com/t/directory-opus-holds-on-to-rar-files/35829 "2020-06-09T19:44:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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 9, 2020, 8:52pm UTC](https://resource.dopus.com/t/directory-opus-holds-on-to-rar-files/35829/4 "2020-06-09T20:52:25Z")

</div>

One thing that might reveal what's happening is a Process Monitor log:

> [@Process Monitor instructions](https://resource.dopus.com/t/process-monitor-instructions/27806):
>
> Download Microsoft's [Process Monitor](https://docs.microsoft.com/en-us/sysinternals/downloads/procmon) and extract the zip somewhere. (No installation is required.) Double-click Procmon.exe to launch it and accept the default filters. Make sure it is logging filesystem events. It should be by default, by ju…

That would show which code or component is opening and closing the archive. It can be a pain to work out which thing failed to close it, but it might be worth a look, if you want to make one and send it to us.

If you do send a log, please include details of the archive file name so we can filter on it.

---

_[View the full topic](https://resource.dopus.com/t/directory-opus-holds-on-to-rar-files/35829)._