IconPackager causing corruption

Hello all. I'm having some serious trouble with IconPackager_3.20.128_04.19.2007. It has caused me to reformat my drive TWICE, but now I'm 99% it is IconPackager (that or either WindowFX) after going through many system restores. When I unarchive my copy of IconPackager, it installs and says activation fails, have no idea why, but when I go into the program I enter in my email and serial number and activation works. (Might be because my serial number expired in June of 2007?) Anyways on to the real problem. It installs successfully and changes all the icons I want, great. But when I restart, I can no longer run msconfig, mspaint, defragmenter, or GenuineCheck.exe from Microsoft.com for download, and who knows what else cannot run. All I get is a working in background cursor and no window ever appears. I look in processes tab and the program is however running. Upon logoff/shutdown I receive Memory Instruction Errors on the apps I tried to open that fail to do so. After some more experimentation and lots of google searches, I tried ending explorer.exe and running those apps from Task Manager, and they work! Anybody have any idea what could be causing this? I can no longer update because my OD serial number has long since expired. I would appreciate any help as I would really like to change my icons to complete my theme! Thanks :)

Also I would like to take the time to ask how to fix corrupt default EXE icons just incase it happens again. Once when editing properties to an EXE all default icons became Unknown/Missing File type icons (under use of IconPackager). Rebuilding the cache/repairing did not succeed. EXE icons with custom icons displayed correctly, but ones with no supplied icons did not.

Thanks in advance for any advice.
3,002 views 3 replies
Reply #2 Top
Looks like you're going to have to go directly to Stardock Support with this, here:

WWW Link


Way bizarre - don't think I've ever seen anything on here like this.
Reply #3 Top
Update: Searching around in the forums, I noticed there was some temp fix for another problem by renaming iprepair.dll, so I decided to try it. After renaming it to iprepair.bak and logging off and back on and the problem was gone... With iprepair.dll, the problem exists. Very strange.

File Info: iprepair.dll 64.0 KB (65,536 bytes) Created on: Wednesday, December 14, 2005, 6:47:26 PM Version 3.1.0.0

Yeah I think I may contact them, just wanted to see if I could get any help from here first. Thanks!