Brice........i had exactly the same problem this week and for this reason i have now dumped DX2 out of my system until it is more stable. I do not think it is anything to do with the Windowblinds update.
[Message Edited]

Hmm, I don't have that problem with either program. There are many ways to explain it though. One foremost is conflicts. Conflicts with other programs or the same program loading different versions of certain old files being cross referenced. Updating programs can be tricky. Especially, when the program doesn't update or remove older dll's that continue to load. Most dangerous when those files are placed in other directories such as the window directory and, aren't updated or removed when no longer neccessary, but there reference is still present in the registry, and windows tries to load them which would corrupt the updated version of the same program. Sometimes the best solution is "If it ain't broke, why fix it?"

Also, SDC and CM, by default, loaded programs in different directories. If you have a old version still present from CM and the new version from SDC, both versions are still active and may conflict. So that, DX and WB maybe loading older files or dll's still referenced in the registry from the old CM, WB or DX install.

One solution maybe to ask Stardock for every file used in the program. Old and new versions. Then, clean every WB and DX file, from the program and system folders and every reference in the registry. But, it may also be referenced in other locations too.
I had to do that with my Soundblaster drivers.

The best solution maybe to do a clean install of windows, and apply the new versions via SDC. That way, every trace of any old registry references won't exist.

I did this once and it worked. I had shareware versions on my system and they crashed my full versions. So, I uninstalled windows, wiped my hard drive and reinstalled the full versions and I have never had a problem since then.

But, I had a similar problem and I noticed that DX and WB was somehow installed in two different places. So, I removed Windowblinds completely, I removed the older windowblind folder which I don't know why it was still there after the uninstall, and then I defragged and restart my system fresh before I reinstalled. As another saying goes, "Sh*t Happens" or better stated "Sh*t lingers"

Thanks Chas for your explanation and thoughts. The one thing i do recall when i was updating DX and other Stardock programmes via Stardock central during the week is that i took my eye off the updating for about 10 minutes and when i returned to the machine the install of the DX had stopped half way through and was giving me an error message (cannot recall what error) but i clicked on it and then it carried on. This may have been the cause. Shorly after a restart i noticed that some of the icons in my system tray were not showing and then i found that the iconpackage i had installed with my skin was playing up. I guessed this must have been caused by the DX update so after this and seeing another couple of warnings recently i decided i was not going to put my system in jeopardy as it had been running like a dream so i uninstalled and wiped DX completely out and thankfully everything went back to normal. I think i will wait a while now and come back to DX in a couple of weeks.

And I also encountered an error during the DX download. I'll try again

Aqua - change server in SDC settings and DX will install without errors...