Applications do not start

URGENT fix needed!

I have got problems with the following applications after having done the latest updates (Jul 28,) on Desktop Central of the major apps as Desktop X, WindowBlinds, IkonX etc: iMatch; photo manager, not skinnable Dantz Retrospect 6.5; back-up utility, not skinnable Pinnacle Studio 9; not skinnable I have tried to exclude them from being skinned in WindowBlinds, but no luck. When starting the apps the .exe files show up in the Processes tab in the Task Manager but not in the Application tab. I really like the Stardock products and I have never had any problems before, but this time something has gone seriously wrong with one of the updated apps. The worse is that I have spent the an entire day to roll-back my computer to an earlier image and try to pin down the problem and everything worked fine until I did the Stardock update so I have no doubt that one or more of those apps are the culprit. The last doubt I had disappeared when I saw this post in the forum. I would like to add that I have tried to uninstall and re-install both iMatch and Retrospect and they still do not work after re-install. Stardock, please fix EXTREMELY fast!! See also: https://forums.stardock.com/?ForumID=166&AID=79365 /PerLink
7,707 views 8 replies
Reply #1 Top
The solution to this has been in at least 4 different threads on this board for several weeks:

"Please make sure there is not an iprepair.dll in the IconPackager directory. If there is, attempt to delete it. If it won't go: Start / Run

regsvr32 /u "C:\program files\stardock\object desktop\iconpackager\iprepair.dll" and reboot. Then remove it.

Uninstall the enhanced dialog beta as well if you're running it.

Without physical access to the machines, the symptoms sound like the iprepair.dll issue from early this month."
Reply #2 Top
"Please make sure there is not an iprepair.dll in the IconPackager directory


werewolf, Does this need to be done to all versions of IP, or just the latest one? Thanks!
Reply #3 Top
clwoods, interesting question. The very latest update doesn't include iprepair.dll at all, so, if iprepair.dll appears in your IP folder, I would get a command window open in that directory and do the old 'regsvr32 /u iprepair.dll' and then reboot. You can then delete the file.

I believe that you might lose 'some' functionality in the Enhanced Dialog menus and some other minor things, but it's better than all the other fuss and bother
Reply #4 Top
I think they where talking about taking iprepair out due to the high number of problems it caused.
Reply #5 Top
Hi thomassen, you're right. They did take out iprepair in the latest version for just that reason.
Reply #6 Top
Thanks alot, werewolf. I really appreciate it. I do have it in my IP folder, but I don't have any problems that I know of. I have been scared to update anything lately.
Reply #7 Top
Thanks werewolf. I found an answer that was posted after I asked my question in another very recent thread. The problem is that it took me a day of systematic investigations to figure out that Object Desktop and was the culprit. When I understood that it was time to go to the forums here. It's not really "intuitive that" it was a dll-file in IconPackager that was the problem.

Now I am happy again!!

/Per