CursorFX drags down the system after standby
Monday, May 12, 2008 by eznoh | Discussion: CES 2007
After returning from standby on an XP system the system is slowed down to a crawl by CursorFX. It is using around 50% of the CPU. After a while it settles down.
Mike
Mike
jnyb
Reply #2 Sunday, January 11, 2009 9:14 AM
Reply #2 Sunday, January 11, 2009 9:14 AM
I am currently having this same problem in Vista - can't explain why...
when I come out of standby cursor fx is slowing down the system ( like 25+ cpu ) rendering the computer unoperable - so every time I come out of standby, before I can start using my computer, I have to kill cursor fx in task manager, opern up cursor fx control panel, fish on a cursorless system to click on a cursor fx theme, quit cursor fx control panel, and minimize the task manager. This occurs in my plus version, the free version... i have tried all attempts with deleting and reistalling and trying in safe mode which didn't work, because i got a message that said the windows installer couldn't be accessed.
da_zman20
Reply #3 Sunday, January 11, 2009 10:08 AM
Reply #3 Sunday, January 11, 2009 10:08 AM
just a tip you can press Ctrl Shift and C this turns off cursor FX without having to do the whole Ctrl Alt Delete thing... I've had to disable it many time... and in your situation it should work in pinch... just till you get an answer from stardock 
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Monday, May 12, 2008 1:18 PM
And what does it settle down to?
(both answers might assist dev that stops by and sees this)
Aslo, you might want to email [email protected]
I've not seen this reported by the community so you might not get a response from anyone who has had (and solved) this issue.