iprepair.dll and IP 3.00.089

from WinCustomize Forums
iprepair.dll is not being installed with the download of IP 3.00.089 on Stardock Central and, consequently, icons in the shell are not being skinned.

Please fix this!
iconpackager
12,575 views 20 replies
Reply #1 from WinCustomize Forums Top
You may have already done so, Lazlo, but iprepair.dll is posted in the iconpackager.binaries newsgroup and can be downloaded from there & placed in the Program Files\Stardock folder. Don't know why the installer isn't giving it up.

Cheers,
Daiwa
Reply #2 from WinCustomize Forums Top
Don't know what made me look, but I found a second, newer instance of iprepair.dll with a different file size (40k vs 32k) in the Program File\Stardock\Object Desktop\IconPackager folder which must have been installed by one of the interim IP updates. The one posted in the newsgroup is the 32k version.

I'm having no problems with IP, but I haven't changed packages or fiddled with my existing one for several updates. I'm now uncertain which version of the .dll is the "right" one and exactly where it should reside. Also not sure what having two different versions resident will do if/when I decide to run IP & change icons (which I plan to do once Mormegil's Icon-a-Day package is done).

Cheers,
Daiwa
Ashes of the Singularity II
Reply #3 from WinCustomize Forums Top
iprepair.dll is not being installed with the download of IP 3.00.089 on Stardock Central


Same issue here.
iprepair.dll is posted in the iconpackager.binaries newsgroup


Hey Daiwa how do I get to this.
Reply #4 from WinCustomize Forums Top
I have a 44kb iprepair.dll that Brian emailed to me on request once, but it doesn't do anything anymore. I have saved it into the IP folder, registered it (regsvr32.exe iprepair.dll) successfully, rebooted, and then upon opening xplorer² Windows default icons appear. Clearly iprepair.dll is NOT doing the job it used to do, for some reason.
Reply #5 from WinCustomize Forums Top
Cavan1 -

If you have OE or another newsreader, just add news.stardock.com to your News tab of the Accounts dialog. It will prompt you to download the NG's - you can subscribe or not, but go to the stardock.iconpackager.binaries newsgroup and do a search for iprepair.dll.

Cheers,
Daiwa
Reply #6 from WinCustomize Forums Top
Thanks Daiwa, I added to newsgroup in OE, will have to just keep seeing if can get thru, when downloading newsgroups server is not responding.
Reply #7 from WinCustomize Forums Top
Just a side note -

I updated on June 9, to the IconPackager 3.00.089 version on top of the old 2.50h.087 with no issues.

I just looked in the IP sub-directory and did a subsequent search for "iprepair.dll" which resulted in it not being present.

I saw mention of it in the "History" text file in IP sub-directory, but that was it.

Perhaps it is no longer utilized for repair functions and the "cache.dll" now does it all?

Just a thought.
Reply #8 from WinCustomize Forums Top
Thanks Corky, you may be right as you always are.
Reply #9 from WinCustomize Forums Top
Perhaps it is no longer utilized for repair functions and the "cache.dll" now does it all?


The fact that I had cache.dll and no shell icon skinning would seem to destroy that hypothesis.
Reply #10 from WinCustomize Forums Top
Lazlo,

I am not a coder, so I am not sure which ".dll" would be responsible for the shell icon - though "shellext.dll" would be a good candidate as well.

I have the following ".dll" files in my IP sub-directory:

1 - "cache.dll"
2 - "common.dll"
3 - "inetconfig.dll"
4 - "shellext.dll"

I am currenlty running Utopia 'Canvas' by Mormegil, and my system shell icons are being replaced by the relevant package icons that exist in the package.

No Internet Explorer shell icon change is made, but if I am not mistaken, the Utopia series was created with IP 2.5 which I do not think supported changing IE shell icon - though I could be mistaken.

Just a list of ".dll" files for reference in an update that works.
Reply #11 from WinCustomize Forums Top
Now that you mention it, it is very possible that iprepair.dll's functionality was integrated into another .dll or the executable code in IP3. As I recall, the .dll was provided for download some time after 2.5 was released and, while I don't recall it being mentioned specifically as such, I got the feeling that it was intended as a temporary bandaid until IP3 was released.

That wouldn't account for Lazlo's issue, but it may explain why iprepair.dll appears to be "non-functional" - could be the .exe doesn't call or load it now.

Cheers,
Daiwa
Reply #12 from WinCustomize Forums Top
Corky,

I had a completely fresh install of IP 3.00.089 from Stardock Central, and it was NOT skinning shell icons. Something was clearly wrong! Using iprepair.dll fixed the issue.
Reply #13 from WinCustomize Forums Top
Laz -

What did you do to get it to "do the job"? Did you have to move it to a different folder? Just curious since yesterday you indicated iprepair.dll was there but not "working".

Cheers,
Daiwa
Reply #15 from WinCustomize Forums Top
That's what's known in the military as an ESO issue - Equipment Smarter than Operator.

Cheers,
Daiwa
Reply #16 from WinCustomize Forums Top
On the subject of the iprepair.dll - it's have me tearing my hair out for three days trying to find a virus or spyware that dian't exist!

I even installed SP2 - just to see if it was some system dll problem!

So - if you are having problems with programs not running when you double click on their icon, or their exe file, try unregistering iprepair.dll using this:

go to the start menu and choose 'Run' and in the box type this:

regsvr32.exe /u "c:\program files\stardock\object desktop\iconpackager\iprepair.dll"

and hit enter. Then you might want to run Stardock Central and update IconPackager.
Reply #17 from WinCustomize Forums Top
hey everybody...
seem to be having the same problem as many of you have had...mine just does't want to download (icon packager) i did try the last thing that essorant tried and just said that the specified module could not be found...i downloaded this last week and everything seems to be working fine except the ip...i tried to uninstall the whole kit and kaboodle, but computer did not let it happen...sent email to stardock and they sent me a bunch of stuff to do plus an uninstall (https://www.stardock.com/files/odnt_zapper.exe)...didn't work either...

again, new at this, i must be missing something simple...help, i sometimes need to have my hand held!

thanks, tony

Posted via WinCustomize Browser/Stardock Central
Reply #18 from WinCustomize Forums Top
what do you mean by the whole kit and kaboodle?
you shouldn't have to deregister the dll if IP isn't installed (why it couldn't be found).

are you downloading with SDC?
Reply #19 from WinCustomize Forums Top
I updated to 3.00i[b].002 a couple of days ago (from 3.00a.091) & can't get shell icons to change anymore. I've unregistered & re-registered iprepair.dll with reboots in between, reloaded & applied the IP package & still no go.

I also have an older version of iprepair.dll (2.0.0.1) sitting in the C:\Program Files\Stardock folder but I unregistered that as well & left it that way. It was also sitting there with the prior version working fine so I don't think it's presence per se is an issue.

Any thoughts other than reverting to the previous working version?

Thanks,
Daiwa
Reply #20 from WinCustomize Forums Top
For any others who may wander here - fix is to use "Tools/Repair Shell Icons" & select "Repair icons for all processes". Shell icon replacement is now off by default and overt action is required to enable it.

Cheers,
Daiwa