Iconpackager v3.09b(b).002

Unable to load explorer upon reboot

Hi guys.

just thought you should know that on my machine the new IP Beta (Iconpackager v3.09b(b).002) causes the windows explorer to hang on initialisation. This also cannot be uninstalled as Stardock Central will not list installed files in "Safe Mode".

You may already have heard of this but if you need more info let me know.

Jon
9,823 views 20 replies
Reply #1 Top
I'm also having the same troubles with the latest IconPackager.
Reply #2 Top
Ditto on this end. I posted this issue regarding WB5 since I presumed it was the culprit. After a few more XP installs, I narrowed it down to IP Beta as well. It'd be ---REAL--- handy for Stardock to post a few hints regarding how to nuke a faulty installation or issue of this nature that results in a hang to the OS in such a fundamental way. Could never get past this without a wipe & re-install.
Reply #3 Top
I'm with you on an uninstall tool... I reinstalled 2 times before I found the problem. Good thing for Norton Ghost is all I can say


Posted via WinCustomize Browser/Stardock Central
Reply #4 Top
Add another to the list-I can not boot into windows nor can I rool back to the previous version. Thanks Stardock, clue us in as to how to get our PC's back up and running. Fix this NOW
Reply #5 Top
Writing from my laptop PC BTW, since my main rig is now screwed.
Reply #6 Top
Iconpackager should be uninstalled through the Stardock Central Browser.

If a program in the SDC list can't be uninstalled - try the ODNT zapper: Link
Reply #7 Top
Stardock, clue us in as to how to get our PC's back up and running. Fix this NOW


IP Beta (Iconpackager v3.09b(b).002)


The word beta should tip you off that there may be issues.

IP is a great app but its integration into Windows in beta has always been . . . problematic . . . for me at least.


Posted via WinCustomize Browser/Stardock Central
Reply #8 Top
Acknowledged as to the beta; I'm always prepared for something to not be quite right with one, but not being able to finish starting windows raises the bar to a new level. I'm a huge fan of their stuff, but I don't think I'll ever try another Beta from Stardock for anything. I was understandably a little pissy last night but I did manage to rectify the problem by starting up in safe mode and removing IP through SDCentral. Once I was back in, I went to re-install the previous archived version, and even though I selected the older version SDCentral proceeded to reinstall the 3.09 beta again. Everything seems to be happy, so I didn't have to try the ODNT Zapper, but thanks for the link!
Reply #9 Top
I have only had that kind of trouble with IP betas. Enhanced Dialog was a bit goofy . . . but IP betas and my production systems . . uh-uh, no way, lesson learned.

WindowBlinds or DesktopX on the other hand . . I'll install thoses betas any day.


Posted via WinCustomize Browser/Stardock Central
Reply #10 Top
Yeah, you have a point-WB betas have never given me a problem-I'm with you there.
Reply #11 Top
Well, the release that came out today cleared my problems.
Reply #12 Top
The release that came today cleared my issues.
Reply #13 Top
The release that came today cleared my issues.
Reply #14 Top
Excuse the above 3 multiple postings. Also I spoke too soon. My system has become unstable. I've had to restore to a backup I took prior to installing the latest IP.
Reply #15 Top

Can you please try updating to the latest beta of IconPackager 3.09d[b].002 and see if the problem has been resolved.

Thanks.

Reply #16 Top
Explorer still abends at startup.
Reply #17 Top
Icon Packeger installs an autorun for iprepair.dll at startup. It resides in the registry category ShellServiceObjectDelayLoad. Use something like "autoruns" to remove this at load time and your problem will go away.... until you re-install from an update or something... was hard to figure out. Hope this helps.

Posted via WinCustomize Browser/Stardock Central
Reply #18 Top
or rename iprepair.dll fixes the problem as well. FWIW, the problem only seems to occur when WB 5 is installed (at least on my rig).
Reply #19 Top
The 12-13-2005 version seems to have worked except that Stardock Central even after updating continues to not recognize the update.
Reply #20 Top
Tried downloading the 12-13-2005 vervion yet a 4th time and all is good in the western world.