ObjectDock Cause of PC Slowness?

Not Supported on Windows 10?

https://forums.stardock.com/503933/page/1/#3804387

ObjectDock not supported on Windows 10? (see the link) Well, I guess that's right (listed for 8/7), but I'm a long time user, until yesterday. I've begun having lagging problems, particularly with YouTube videos sound, and with the cursor movement. So, I started hunting for causes/solutions.

I have noticed sometimes that ObjectDock fails to load after restarting PC, and instead then loads from a saved copy. Although a little sluggish at times, otherwise OD has seemed to work fine. But, when I killed OD from Task Manager, I found a definitely improved response from my PC, and lack of the YT audio stuttering. So, now I've set OD to not start on PC startup. I can live without it, but I'd rather still have it to use, as I've become to rely on it. I can start it when needed from a shortcut icon, then kill it. But is there another way?

I'm also running Start11, Fences, Groupy and CursorFx.

MB name    ASROCK 970A-G/3.1
Processor    AMD Phenom(tm) II X6 1055T Processor   2.80 GHz
Installed RAM    24.0 GB
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display
Edition    Windows 10 Home
Version    22H2
Installed on    ‎08/‎11/‎22
OS build    19045.2728
Experience    Windows Feature Experience Pack 120.2212.4190.

Windows is installed on a NVMe board, and I have other SSD and HD disks.

As I write this, Memory usage is 52%, CPU usage is 29- 48% without OD running. After starting OD, memory usage is still 52%, and CPU usage is about the same. OD is quite responsive. I've noted in the past that it becomes sluggish, particularly after hours of running.

Any suggestions?

Thanks.

4,318 views 1 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. But, it is known that ObjectDock will do strange things on not supported Windows system. What you can try to do is purge and reinstall steps as mention here : [Link]. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back.

Thank you,
Basj,
Stardock Community Assistant.