moeburn Posted May 6, 2004 Share Posted May 6, 2004 (edited) Whenever i download an install program that has been compiled with the Wise Installation Wizard, the program opens, a blue box comes up that says ""initializing wise installation wizard", and then just hangs there eating up 100% of my cpu. So far, 3 programs do this. Any solutions? Edited May 6, 2004 by moeburn Link to comment Share on other sites More sharing options...
Bold_Fortune Posted May 6, 2004 Share Posted May 6, 2004 I never tried this before, but it kind of made sense to me when I saw it posted, so I saved it. I guess if it's not working for you, it's worth a shot. A method to try to fix Windows Installer... Per mediaplaya: 1. Click START, and then click RUN. 2. In the OPEN box, Type msiexec /unreg, and then click OK 3. When this process is complete, click START, and then click RUN. 4. In the OPEN box, type msiexec /regserver, and then click OK. Link to comment Share on other sites More sharing options...
jhaygood86 Posted May 6, 2004 Share Posted May 6, 2004 That fix will only work with Windows Installer and InstallShield (which uses Windows Installer) Link to comment Share on other sites More sharing options...
+virtorio MVC Posted May 6, 2004 MVC Share Posted May 6, 2004 I would clear out my temp directory and disable my virus scanner. Link to comment Share on other sites More sharing options...
moeburn Posted May 6, 2004 Author Share Posted May 6, 2004 windows installer works fine, and i cleared out my temp dir. As a temporary fix, i installed everything on a different comp then copied over. Link to comment Share on other sites More sharing options...
Joe User 99 Posted May 6, 2004 Share Posted May 6, 2004 That fix will only work with Windows Installer and InstallShield (which uses Windows Installer) Actually, Wise has Windows Installer based products also, but I do think he is referring to the old fashioned ones. Kinda like the old Installshield installers, the installer copies various dependency files to locations on the HD. Might try looking for some of them, maybe they are corrupt, or incompatible withe the ones from the installer you are trying to run. I don't know them off hand, but I know Unwise (the uninstaller) was one of them, and there are probably more. IF you can't find them, maybe something like filemon from sysinternals would help you determine what the installer is trying to access. Link to comment Share on other sites More sharing options...
Recommended Posts