Don't forget the important issues that your work PC had as reported in your other post - https://forums.wincustomize.com/406597/page/1/#2920486

There could be other issues with the setup of XP Professional that your company help desk would know about that could be causing the issue with Impulse.

Actually - I have resolved many of those issues on my work PC - in fact, after running that SubInACL I got my WindowBlinds working great again. I am enjoying a beautiful desktop again after so many weeks of the Fisher Price WinXP theme.

I'm wondering if maybe there is something in my .NET drivers that need to be upgraded/repaired. But instead of just installing stuff willy-nilly, I would like to review an install log for Impulse to know why it doesn't want to work.

-= Einy =-

I upgraded my .NET to 3.5 - that seemed to fix it. So far no crashes.

I am having the same problem, but my .Net components are all up to date.

Anyone have any other ideas?

Could be a bad download of Impulse, you might try uninstalling it, running a clean up program and then reinstalling from the Stardock site.

Thanks, but I already tried that, to no avail.

I have a case in with Stardock support, but was hoping to find a quicker solution here.

EDIT:

On a hunch, I updated the .NET 1.1 framework and that is what, I think, fixed the issue.

I was already up to date on the 3.5 version, but there seem to be some dependencies in Impulse for 1.1.

Go figure. I really wish that Stardock were not so in bed with MS.

I disagree - how else can a third party create applications that are so lacking in default Windows installs unless they have intimate knowledge of how the OS does what it does? I have seen some "ahem ... attempts" at skinning and tools to enhance Windows, but nothing I have tried comes as close as native functionality as provided by Stardock.

Sleep away Stardock, make sure Microsoft gives you a nice back rub.