# Initial Opus startup is very slow

**URL:** <https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142>\
**Category:** Help & Support\
**Created:** [November 18, 2010, 5:41pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142 "2010-11-18T17:41:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ron\_Hirsch](https://resource.dopus.com/user_avatar/resource.dopus.com/ron_hirsch/32/26343_2.png) [@Ron\_Hirsch](https://resource.dopus.com/u/Ron_Hirsch)\
**Post date:** [November 18, 2010, 5:41pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/1 "2010-11-18T17:41:08Z")

</div>

I'm running Opus 9 64 bit on a Win 7 64 bit system, with an SSD C drive, and several other HDD drives. Ths system is quite fast and responsive.

I keep an Opus icon in the task bar, and usually load it from there. when I want to use it

Lately, Opus 9 seems to take a long time to load the first time - as long a 20-30 seconds. It didn't used to be this way, in the recent past. Once it has loaded, and then is closed, it does reload within a small fraction of a second, via a single click of the taskbar icon. And all operations of Opus seem normal.

I checked my startup program listing, and "dopusrt.exe/dblclick" is in there and is enabled.

Any ideas why the initial loading is so slow?

Ron Hirsch

---

<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:** [November 18, 2010, 5:46pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/2 "2010-11-18T17:46:10Z")

</div>

Try the suggestions in this thread:

> [@Horrible slow first start!](https://resource.dopus.com/t/horrible-slow-first-start/6165/1):
>
> Hi, Whenever I start my system all other autorun programs start in a snap, but DO takes litteraly MINUTES to get the icon in the systray, and be ready for input ?!? I watched the startup using Process Monitor and see DOpus accessing/reading/writin…

Failing that, here's a list of ideas worth trying when there's not much else to go on:

> [@General slowdown or instability investigation steps](https://resource.dopus.com/t/general-slowdown-or-instability-investigation-steps/4618/1):
>
> See also: [Crash, exit or high CPU usage when viewing certain directories](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-viewing-certain-directories/1325/1)[Crash, exit or high CPU usage when right-clicking certain files](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-right-clicking-certain-files/1335/1)[How to find components causing high CPU usage](https://resource.dopus.com/t/how-to-find-components-causing-high-cpu-usage/14144)[How to find components causing memory leaks](https://resource.dopus.com/t/how-to-find-components-causing-memory-leaks/10135)[Crash dumps for bug r…](https://resource.dopus.com/t/crash-dumps-for-bug-reports/8861)

---

<div class="post-metadata">

**Author:** ![Ron\_Hirsch](https://resource.dopus.com/user_avatar/resource.dopus.com/ron_hirsch/32/26343_2.png) [@Ron\_Hirsch](https://resource.dopus.com/u/Ron_Hirsch)\
**Post date:** [November 18, 2010, 6:05pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/3 "2010-11-18T18:05:04Z")

</div>

Hi Leo,

Thanks for the reply. I've looked over the references you presented.

The "change" in Opus's startup could possibly be related to the fact that it now uses many of the QVP 11 viewer capabilities, and that's about the time that this all started. The slow startup is not a real problem, and I can just click on its icon when the system has booted up, and then mnimze or close it it when it loads. That way it'll re ready when I want to use it, as it reloads in about 1/3 of a second.

Right now, the command line for the Opus icon is ""C:\Program Files\GPSoftware\Directory Opus\dopus.exe" /autolister". Is there anything I can add to that string to have Opus open minimized. It would also be nice if I could add a command into the STARTUP listing, minimized so that I wouldn't have to do anything, as it would all be done in the background. Maybe there is something in the program's settings to do that - yes??

Ron

---

<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:** [November 18, 2010, 6:35pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/4 "2010-11-18T18:35:37Z")

</div>

> [@Ron Hirsch](#):
>
> The "change" in Opus's startup could possibly be related to the fact that it now uses many of the QVP 11 viewer capabilities

Use the ShellExView tool (linked from the FAQ in my post above) to see if QVP installs any shell extensions. If it doesn't it's unlikely to affect startup time as its preview handler would only be loaded when you view a file. (If it does install a shell extension it is worth checking out, though.)

> [@](#):
>
> and I can just click on its icon when the system has booted up, and then mnimze or close it it when it loads. That way it'll re ready when I want to use it, as it reloads in about 1/3 of a second.

Are you sure you're not confusing how long Opus takes to start with how long it takes to open a new window when it's already running in the background? Unless you've changed your configuration to make it auto-exit, Opus stays running even when all windows are closed, once launched for the first time.

> [@](#):
>
> Is there anything I can add to that string to have Opus open minimized. It would also be nice if I could add a command into the STARTUP listing, minimized so that I wouldn't have to do anything

Yes, go to the Launching Opus - Startup section of Preferences and set Opus to start but not open any windows.

---

<div class="post-metadata">

**Author:** ![michaelkenward](https://resource.dopus.com/user_avatar/resource.dopus.com/michaelkenward/32/12969_2.png) [@michaelkenward](https://resource.dopus.com/u/michaelkenward)\
**Post date:** [November 18, 2010, 7:22pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/5 "2010-11-18T19:22:15Z")

</div>

> [@leo](#):
>
> Use the ShellExView tool (linked from the FAQ in my post above) to see if QVP installs any shell extensions. If it doesn't it's unlikely to affect startup time as its preview handler would only be loaded when you view a file. (If it does install a shell extension it is worth checking out, though.)

Here at least QVP does nothing to alter the speed of Opus.

---

<div class="post-metadata">

**Author:** ![Jon](https://resource.dopus.com/user_avatar/resource.dopus.com/jon/32/12713_2.png) [@Jon](https://resource.dopus.com/u/Jon)\
**Post date:** [November 18, 2010, 7:35pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/6 "2010-11-18T19:35:18Z")

</div>

You could try using [Process Monitor](http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) to see what's happening during the startup.

Also, why not just run Opus on system startup? You can have it run without opening any windows - and then it is available immediately when you need it.

---

<div class="post-metadata">

**Author:** ![Ron\_Hirsch](https://resource.dopus.com/user_avatar/resource.dopus.com/ron_hirsch/32/26343_2.png) [@Ron\_Hirsch](https://resource.dopus.com/u/Ron_Hirsch)\
**Post date:** [November 18, 2010, 9:39pm UTC](https://resource.dopus.com/t/initial-opus-startup-is-very-slow/10142/7 "2010-11-18T21:39:42Z")

</div>

Thanks to all of you for the info offered. For some stange reason, the last new computer session brough up Opus back at its old quick load. And as I mentioned, once it has been loaded initially, and then shut down, the next time I click on the Opus taskbar icon - less than 1/3 second to display.

And thanks Leo for the path to load it at startup, with no lister opened. I looked for that option, but I guess I just missed it, even though I did remember seeing it in the past.

Ron
