Impulse crash on start up wehn I want to update elemental

I have 2 computer. I have sucessfully updated Elemental to 1.09 on my Netbook with win XP a few days ago, now I am trying to update my Windows Vista PC. I first tried to run impulse and they say that they have encountered an unknown error. If I try to send a report it fails.

If I run elemental, it tells me that there is an major update to the game and ask me if I want to update. If I select yes, it launch impulse and crash the same way.

First, I was thinking impulse was dead, but since elemental can detect there is a newer version that should not be the case.

I tried reinstalling and repairing impulse and it does not work. Still, I have installed it over the old Impulse, Maybe I need to uninstall everything and reinstall from scratch?

Does anybody have any Idea of what can cause this problem.

2,711 views 4 replies
Reply #1 Top

If you're having issues with Impulse, please contact support@stardock.com and they should be able to help.

Reply #2 Top

I had Impulse crashing my Vista computer as well, i resolved the problem by updating Vista.

Also i had to copy the game over to my laptop so i can put my main computer in for repair. I did not install Impulse on my laptop but i did copy the impulse folder across. When i tried to run the game for the first time on my laptop, it asked me to register the game - and i was able to open a folder in the impulse folder and see my game number and i could activate it on my laptop. then the game was telling me to update to version 109 when it was already version 109 but i ignored that because i know Impulse is not installed. The game runs fine, a good temporary solution until i get my main computer back.

Reply #3 Top

It seems I have solved the problem. Buy looking at the error log, it was something with the .net frame work. I had version 3.5 and 4 installed. I uninstalled 3.5 and it now seems to work. Maybe there was some conflict between both versions.

 

Reply #4 Top

By re-looking at the log file, there still seems to be errors like "Unrecognized configuration section system.serviceModel", but the software does not crash on start up, so it's a good sign.