Thread: Windows installer

So, the last few days since I reinstalled my Creative drivers and software, everytime I open xfire and then expand it (it starts minimized) or when I start up Azureus Vuze (like Bit Torrent), the windows installer pops up, saying preparing to install. This goes away eventually, but I can't do anything with either program until it does.

Does anyone know what's going on?

Well, nothing new was in the msconfig version of what starts up with my computer, BUT there was a AudioDrvEmulator in the registry. This would make some sense since recently when playing Deus Ex: Invisible Wars, the game would randomly CTD.

Registry Entry:

Code:

"C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" -AudioDrvEmulator "C:\Program Files\Creative\Shared Files\Module Loader\Audio Emulator\AudDrvEm.dll"

Now, when I started my AV (Nod32) up just to make sure it wasn't a virus or anything, the Windows Installer thing came up again.

If the emulator above is the problem, how should I get rid of it?

--edited for clarity
---I looked at the event viewer, and apparently (I use that word a lot don't I), it's trying to install Microsoft Office Small Business Edition 2003. I have to say, wtf?

There's a couple of possibilities...

You can setup installation packages to verify/repair the package whenever the program is invocated. It may be there's another program on your machine that has a DLL conflict with Azureus, and when you run the two they each repair themselves. It could also be the 'service' that XP has that protects system files and it's overwriting the DLL file when you boot, and then Azureus tries to repair itself when it starts.

It's more than just Azureus though. Currently, I've seen it when using xfire, Azureus, and Nod32 (my AV).

I can't see anything else that could be the problem. I did find this, however, here.

Windows Installer Appears Every Time I Start an Application

Intended For
Windows XP
Windows 2003
Windows 2000
The Windows Installer is a global application used to install many Microsoft products, including Office 2000 and Office XP, and is even available to third-party developers to include with their programs.

Unfortunately, it's fraught with bugs, one of which is its tendency to appear every time you start Office (or some other programs) and begin a reinstallation or reconfiguration process. All you'll see is the "Please Wait" screen, followed by a progress bar. The problem is related to the This feature will be installed when required option (sometimes called "Install on Demand"), used when installing some applications. In essense, Windows Installer starts to install a "feature" when it is needed, even though it may be already installed.

Unfortunately, but not surprisingly, Microsoft will not acknowledge that there is a serious flaw in thier installer software. Here are the solutions we've come up with so far:

Solution #1:

* Reinstall the application in question, and don't choose the This feature will be installed when required for any of the optional components.

However, this may not solve the problem (which is the very bug we're talking about). We're currently looking for a way to fix the problem properly, but in the mean time, here's how to turn off the "feature:"

Solution #2

* Open the Group Policy Editor by selecting Run from the Start Menu, and typing gpedit.msc. (If the file is missing, run mmc.exe instead. Then, select Add/Remove Snap-in from the Console menu, click Add, and double-click Group Policy. Click Finish, then Close, then Ok.)
* Expand the following branches:
Local Computer Policy \ Computer Configuration \ Administrative Templates \ Windows Components \ Windows Installer
* Double-click Disable Windows Installer to your right, click Enabled, and choose Always from the list. Click Ok when you're done.
* The change will take effect immediately. If you added a snap in, as described above, you don't need to "save changes to the console."

* Note: If you encounter an error about the Administrator Policy the next time you try to install an application, you'll have to re-enable the Windows Installer temporarily.

Solution #3 (for Office 2000 only):

* Run the Registry Editor (REGEDIT.EXE).
* Expand the branches to HKEY_CURRENT_USER\ Software\ Microsoft\ Office\ 9.0\ Common.
* Delete the UserData value on your right, and close the Registry Editor.
* The next time you start an Office application, it will ask for your username, but shouldn't bother you again.

Since I don't have my Office disks with me, option #2 seems the best. The question is: should I do this?