Icon Pacager problem!

Every time I try to open up IP it starts to look for the themes, then it stops. And a window comes up and says Icon Pacager needs to close now! do you want to send this information to Microsoft? It worked good until I downloaded the Nordagan theme. Any help would be great! I,m stuck on one theme. Would it help if I uninstalled it and re-installed it with Object Desktop?
9,667 views 13 replies
Reply #1 Top
Here is a picture seeing what it says.

Reply #2 Top
installing these programs via SDC has always worked best for me.
you could try an uninstall, then move that package out of the folder prior to reinstall and see if IP is still acting up.

There have been issues with some packages done on a computer using language other than eng. (don't know if that applies in this case).

Reply #3 Top
Uninstalling it worked.Somthing must have been corrupt in there. i went and put all files in the IP folder in a temp folder.to my supprise after I uninstalled IP I still had the theme setup on my desk top.After I moved the config files to the temp they all went to nothing. this could be a night mare to a noob,and Stardock should repair this! After uninstalling it should revert back to the windows default Icons!
Reply #4 Top
I don't recall seeing any desktop customization software that puts everything back just like it was upon uninstall. Doesn't mean there's none out there, I just haven't seen any.

Best case scenario is you set everything back to default prior to uninstall.

People like me could benefit from a 'go back to default upon uninstall', but then I wouldn't be learning as much as I am.
Reply #5 Top
For whatever it's worth, I just went through something similiar. I had to uninstall IP which I tried using SDC and the unistall failed to complete and SDC crashed also. Eventually after some considerable work, I got the remainder of the IP folder down to my Icon Packages Folder and 1 last IP file - iprepair.dll. When I tried to delete it Windows wouldn't let me. No uninstall program, file shredder program or anything else I had available would allow me to remove/uninstall this 1 last file. I eventually found a solution to the problem which took some more work. I then downloaded a fresh version of IP with SDC and the same problem happened again. I thought sure the problem was becoming unsolvable. IP would start to load and bomb before displaying the Icon Packages in the library. The solution was to remove the library from the IP subdirectory completely. This allowed IP to display only the WindowsXP default Icons and it worked!. I reset everything and now I have been slowly moving my Icon Packages one at a time into the IP library and everything seems fine.

The reason why I am posting this is 3 things had to happen to get things going again. Uninstall and reinstall IP using SDC. Make sure IP installs into a fresh directory without any Icon Library since there is a corrupt Icon Package that is causing the problem. I also after moving all my Icon Packages to a temporary folder did a file registry maintenance to clean up any registry problems at which point I downloded IP. That's when everything started working again and the iprepair.dll file was at last gone.
Reply #6 Top
I tried all that. Moved every thing to a "temp" file,themes and all. after reinstalling everything worked great. today after work I tried to open up IP and had the same problem. i got a support ticket from Mike @ stardock. ran a file to see whats wrong I hope. I work odd hours so when I get off work he's probably at home. LOL
Reply #7 Top
Not sure if your problem was identical to mine but, it sounds very similar. When you tried to de-install IP did you have any difficulties? Did a file called iprepair.dll remain stuck in the IP subdirectory, it did on mine. Everytime I tried to eliminate it (before the fresh install) Windows would refuse to allow it to be deleted reporting it was "in use" by another active process. At the time I had already unloaded all customizing software and rebooted. It was at this point I went to Microsoft's Live OneCare web site for a free system maintenance (file registry cleanup). When Live OneCare was done iprepair was gone. This leads me to believe on my machine I had developed some type of system cache and/or file registry problem. I also did not put my full Icon Package library back into my IP themes folder. I've been re-installing those one at a time. So far no glitches. Anyway, good luck dwax.  
Reply #8 Top
pls. help me... i cant make my iconpackager work for my x64????

can any1 help me walk me through the process of makin it work.. thnx
Reply #9 Top
This thing is getting old! I did the uninstall,removed all the old files and did a clean install. Put the icons rhat I had back in "new install" And now have the same problem! Stardock support is about non helpfull unless they are busy. Have not seen a word from them for three days!! Mike.... If you read this...HELP!!!!!!
Reply #10 Top
moshmosh you need to start your own post or contact support.
Reply #11 Top
dwax I went through the same problem. Try just moving all of your Icon Library out of your IP theme directory. Then try to restart IP. If that works you will see just the Windows default icons available in IP library display. It also means you have 1 or more corrupt Icon themes in your library. Do not move them back to your IP theme directory all at once. You will have to reload them one at a time until you find the problem theme package. I hope this helps.
Reply #12 Top
For the pesky file that wont remove because it is "being used by another person or program" ...google for "unlocker assistant" ...it's a handy little [free] app that will unlock a file that is causing this message to appear.

Install it, reboot, then do exactly what you did before [when you got the cannot remove file message] ...this time, however, unlocker assistant will pop open and give you access to unlock the file so you can delete it.

Then try what was described above, after you have gotten rid of the iprepair.dll file.

You should [by now] be rid of all your previous IP files, and will be downloading a completely fresh copy.

Like to hear if this worked for you...

Good luck.