DesktopX Problems
Cannot Load More Than One Wiget At A Time
Saturday, May 30, 2009 by The-Reaper-Man | Discussion: DesktopX
There has been a recent problem for me with DesktopX widgets. I am using Windows Vista SP1 OS, it was working perfectly before but now every time I try to load a widget, I first get the stupid Vista securtiy crap asking me for permission to run it and then if I try loading a second widget DesktopX will not respond, period. No error message, no Windows asking for permission message, nothing. This all started the other day, when I upgraded to Service Pack 2. I first noticed the DX "welcome" widget no longer worked and then the other problems started. I have since tried uninstalling DX and re-installing it, as well as downgrading back to Service Pack 1 but this did not do the trick either. It's as if Windows turned off some of it's multi-tasking features and that's why it will only allow one widget to run at a time. Has anyone else experienced this? And if so, I'd be delighted to know if you have found a fix for it. Thank you.
Reply #3 Thursday, June 18, 2009 5:37 AM
Doc, you were absolutely right! It seemed so simple that I actually didn't try it until now. I'd been corresponding back and forth between Stardock Technical Support and trying this and trying that, including running batch files and downloading patches and whatnot but finally I got around to trying your suggestion and it worked incredibly well! Thanks a bunch! 
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 Sunday, May 31, 2009 6:29 AM
Just off the top of my head, is UAC enabled? (User account control) If it is, it can inhibit many functions. I might be off the mark, but it's where I'd start looking. If it's turned on, turn it off, reboot and then see what happens.
-Doc