Installing IconPackager 3.00a breaks Microsoft Reader
from
Stardock Forums
Setup:
======
Windows 2000 SP4 + all the latest updates
Microsoft Reader 2.1.1 (latest version)
IconPackager Enhanced v3.00a
Symptoms:
=========
Installed IconPackager. A day or two later, I rebooted my computer. When I tried to launch Microsoft Reader later, I got this error:
msreader.exe - Application Error : The application failed to initialize properly (0xc0000005). Click on OK to terminate the application.
I went as far as to reinstall SP4 and all the updates since. Nothing worked.
Solution:
=========
At a command line, type:
regsvr32 /u _path_to_iconpackager_folder_\iprepair.dll
I discovered this by tracking and comparing modules loaded by my MSReader and one installed on another computer that happens not have IconPackager installed. Once I unregistered iprepair.dll, MSReader worked again.
iprepair.dll does not appear to cause problems with any of my other apps.
Additional Info:
================
iprepair.dll version is 3.0.0.1, date Jan 10 2005
Thank god for Dependency Walker, otherwise I'd never have fixed this bug. So what exactly is going on?
======
Windows 2000 SP4 + all the latest updates
Microsoft Reader 2.1.1 (latest version)
IconPackager Enhanced v3.00a
Symptoms:
=========
Installed IconPackager. A day or two later, I rebooted my computer. When I tried to launch Microsoft Reader later, I got this error:
msreader.exe - Application Error : The application failed to initialize properly (0xc0000005). Click on OK to terminate the application.
I went as far as to reinstall SP4 and all the updates since. Nothing worked.
Solution:
=========
At a command line, type:
regsvr32 /u _path_to_iconpackager_folder_\iprepair.dll
I discovered this by tracking and comparing modules loaded by my MSReader and one installed on another computer that happens not have IconPackager installed. Once I unregistered iprepair.dll, MSReader worked again.
iprepair.dll does not appear to cause problems with any of my other apps.
Additional Info:
================
iprepair.dll version is 3.0.0.1, date Jan 10 2005
Thank god for Dependency Walker, otherwise I'd never have fixed this bug. So what exactly is going on?