Hanging delays (Win 7, 10)

Hanging delays (Win 7, 10)

I've noticed a couple of similar complaints of Object Dock, slow/hanging & lag. I currently am using Windows 10 but this 'hanging-lag', which comes after launching an app from Object Dock, or attempting to launch an item with Object Dock not responding, like it's writing to itself or something is just not correct.

This lagging started quite a while back with Windows 7 (64bit). I use both a tabbed dock at top of screen and a quick launch dock at screens bottom. Both remain off screen/hidden till the cursor initiates, which is also at times a painful delay or lag.

Sometimes the lag is minimal, yet at times it's painfully long. I thought just maybe it wasn't getting enough cpu priority (above normal) so I even tried upping it's priority with no luck.

If I didn't depend on this menuing system so much I would have left it on the backburner 3 years ago... I noticed people have some Windows 10 issues, yet weirdly enough the lag and delays are somewhat less with Windows 10 then they were with Windows 7, but the lag is still here, and I know because I know how just how fast and snappy Object Dock could be while (over) loaded down with many, many (many!!!!) programs & folders spanning 2 disks.

At first I thought my OS was glitchy (Win 7) till I did a clean fresh install which changed nothing. I wish I recorded exactly when this performance issue started.

Hoping this someday gets resolved. Cause even with everything not being copasetic, I'm still a Stardock fan.

not sure if this will help you but stopped dock64.exe and dock64.dll from running by renaming it to dock64.exe.old and dock64.dll.old and it stopped being slow and hanging in windows 10. Im not sure what impact that will have on the program but it seems to be working just fine.

not sure if this will help you but stopped dock64.exe and dock64.dll from running by renaming it to dock64.exe.old and dock64.dll.old and it stopped being slow and hanging in windows 10. Im not sure what impact that will have on the program but it seems to be working just fine.

I have tried your suggestion of stopping those 2 files dock64.exe and dock64.dll. It does show improvement, less lag, but the lag is still there. If I didn't remember how instantaneous Object Dock can be after launching programs and with even more shortcuts this would be less obvious to me. I just know how great this Dock app can be.

For the time being I'm leaving those 2 files stopped. Have not yet seen any negative impact.

Stardock - renaming those dock64.exe and dock64.dll files also worked for me. What I was noticing is when I would close a program and go to ObjectDock to pick a new one, I'd get a spinning cursor for a few seconds - like ObjectDock was busy. Taking out the 64 bit files absolutely stopped that and the dock is still working. I'm running Win10. Can we get some feedback on this?

Big shame as tried this and although improved my issue it only dropped from 34 seconds to start down to 30 seconds. You guys arent having to wait this long are you? Ive tried disabling a few things in my startup which I dont need but 30 seconds is the fastest I can get it to go which considering with Win 7 it only took a couple of seconds im pretty disappointed. Even tried getting rid of my old free version and buying the latest paid for one and doing a fresh install but still slow...

Am using W7 and object dock and when I click on a program it brings it up in 3-5 seconds. I've done none of the above fixes, straight out of the box as they say. I can click program after program and its still 3-5 seconds. As I'am an old man I don't need it any faster.

For me the rename of the x64 files just corrected the bit of clocking when closing items launched from the dock (and some minor delay in starting apps from the dock). However, upon boot it does take my Win10 system much longer to display the dock than it did under Win 7. I'd say the 30 secs. sounds about right. Under Win7 I'd see the dock very soon after boot. Under Win10 there is a very noticeable delay. I just thought it was something on my system, but after looking around, and removing anything that isn't needed in startup land I see no change. I thought it was just me...

I am using windows 10 pro x64 and not having any delays at all. Im not a computer expert or anything i just tinker around abit thats why i came up with the renaming of files so they would not run at boot which helped my system 100%

I'm running Win Pro 10 x64 with 8G of memory, RAID array and an Intel I5 processor. After login, everything comes active but there is a delay before I see the Dock at the bottom. I also have a few flyout menus on the Dock - not sure if that adds anything to the mix. Randy, do you shutdown your computer or put it to sleep or hibernate? I'd be interested from a cold boot and login, how long after login before you see the Dock?

I'm running Win Pro 10 x64 with 8G of memory, RAID array and an Intel I5 processor. After login, everything comes active but there is a delay before I see the Dock at the bottom. I also have a few flyout menus on the Dock - not sure if that adds anything to the mix. Randy, do you shutdown your computer or put it to sleep or hibernate? I'd be interested from a cold boot and login, how long after login before you see the Dock?

Since Win8 and beyond, Microsoft changed their boot sequence to give the impression of a fast-loaded desktop, however all third-party applications were left to the end of the sequence which gives the impression [only] that there is a delay for such things as Object Dock loading.

The reality is that the overall boot time is not much different from Win7 and earlier - it only looks that way.

Only real gauge of load times is watching drive activity. When that stops the sequence is complete...

Jafo - I take that point about Windows now relegating 3rd party apps to start after it - having said that I have like 20 items in my system tray they all load pretty soon after login. In addition I recently installed Rainmeter to watch my drive and processor. Even that loads way before ObjectDock comes active - and I just installed it so that isn't causing any more load. It is still a solid 15-20 seconds after Rainmeter loads on the screen before I see OD. It is just curious, not the end of the world. I just unloaded it after boot and started. Took like 10 seconds, so that doesn't seem all that bad. I'm guessing part of the reason is that it starts from the Startup folder and not as a service - but that is how Rainmeter loads too.

oh I'm sorry. I was thinking people were talking about when you clicked on the objeckdock menus of being slow. because some times before i renamed those files mine would freeze for a few seconds and sometimes stop responding all together.

Yea, we have a couple of different things going on this thread. I didn't have a delay launching but did have one closing apps. The Dock would clock. Renaming those files did stop that. I do hope Stardock is looking at some performance improvements in the next release...