windows installer telling me to install photo gallery

hi hope someone can help me i had some software on my computer which i removed from my computer as i didn't use it much but now every time i turn on my computer i get windows installer boxes coming up on my screen telling me to install photo gallery (which I've removed) i went into my search box to try and find this photo gallery in case i didn't uninstall it properly but the search came back as windows can not find any file or program so its driving me nuts as i cant seem to stop widows installer from popping up all the time

please help

 

Annoying Installer popups

I have a similar problem to ravens...

I uninstalled an older version of an application to install a newer version, had some issues, did a Restore and did the uninstall/install again. Now on every boot/login/logout/shutdown of Windows, and periodically when accessing applications I get MSI popup saying it's preparing to install (and no other information). On startup, it remains long enough for me to hit cancel. After login, it comes and goes rapidly 6-10 times or so. If I can cancel it, it stops the Service, but it will restart the next time SCM calls it. I'm not sure why SCM keeps sending the start control.

Event Viewer has Warning for Event 1001 regarding MSI (31 times this morning).

I have already run Windows Installer Cleanup Utility; it did nothing for me. ;(

Hope you can provide some help.

WinXPProSP2. Version 5.1.2600.2622, Build 2600.xpxp_2_gdr.050301-1519
Dell Inspiron 6000, 60G HD, 512M RAM, Intel Pentium M 1.6GHz, 1800 MHz max CPU

Thanks,

LM

 

Method #1: Find the Startup Entry and Remove it
I would use Microsoft/Sysinternals AutoRuns:
http://www.microsoft.com/technet/sysinternals/utilities/Autoruns.mspx

Method #2: Reinstall the Application, then Uninstall it.
Sometimes you beat the bear. Sometimes the bear beats you. This method works quite often to "fix" the issue.

Method #3: Answer the Windows Installer Prompts in the Affirmative
Sometimes letting it do an "installation ", even if it fails, will resolve the issue. After using this method, check with the Windows Installer Cleanup Utility again, as the entry of interest may now be visible.

 

Annoying Installer popups

I've used Autoruns. However, I don't know what app/service/driver/etc is creating the SCM call to MSI. SCM has to run, so I can't stop that. MSI is supposed to be a Manual startup, so it can be called to run if needed. What I need to know is what's triggering SCM to call MSI.

Agreed. I've done that, too. No luck there, either. In fact, the developers gave some specific regkey(s) to delete after uninstalling. Didn't make any difference.

Agreed. I've done that, too. If I don't choose "cancel" the installer window stays for about 30 seconds, then disappears (prior to login; this occurs while Windows is starting up). It never displays any information or prompts other than it is preparing to install, and the cancel button. After login to Win, as stated b4, the installer popup flashes on & off several times b4 disappearing for a while. It usually reappears when opening apps, logging off, or locking Windows.

My initial response was that it was related to the uninstallation of the old app and installation of the new. Since going thru the steps taken thus far , I'm more inclined to think that something (perhaps associated, perhaps not) occurred during the Restore process and subsequent reinstall of the original program. I think there's some sort of "ghost" installer package that has a startup or registry key that's being activated; I just don't know what it is. I had thought the problem might've been with MSI becoming corrupted somehow, so I dl'd and installed fresh copies of msiexec.exe and msi.dll (didn't help).

Is there a way to tell what is triggering SCM to create the MSI call?

TNX,

LM

PS: I have not done the sfc /scannow thing, although I may try that, just in case (I'll have to reinstall my unlocked uxtheme.dll afterwards, I guess)

 

If you look at the details of the MSI/1001 errors they should be in the form:
Detection of product '<product GUID>', feature '<feature name>' failed during request for component '<component GUID>'.

It would help if you posted back both GUIDs.

First step: enable verbose logging:
http://support.microsoft.com/default.aspx?scid=kb;en-us;223300

Some workarounds that have proven useful for others:

Try setting permissions properly (for Office programs): http://support.microsoft.com/default.aspx?scid=kb;en-us;911682
Also for Office: http://support.microsoft.com/default.aspx?scid=kb;en-us;290139
Also for Office: Add two Reg entries under :
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\common
"UserData" (DWORD) = 1
"UserData" (DWORD) = 1

(Modify the "9.0" when you navigate in regedit to reflect your Office version)

If MSI v. 2, use Methods 1,3,4, and 5: http://support.microsoft.com/default.aspx?scid=kb;en-us;319624

Upgrade to MSI v.3: http://www.microsoft.com/downloads/...70-b259-4733-a914-a956122e08e8&DisplayLang=en

Use ORCA to examine the MSI package to determine components that are required. One may be missing. (ORCA from the Windows Installer SDK should be used to load the MSI and look up the components required. You may find a missing file that did not get installed for some reason).

Clean all TEMP folders!

 

Here's the Viewer info:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 11/9/2006
Time: 3:15:45 PM
User: WCPLAPTOP\xxx
Computer: WCPLAPTOP
Description:
Detection of product '{6617B209-C45E-4ED7-86A6-5055D17BFBEE}', feature 'DefaultFeature' failed during request for component '{E79E3ED7-50A7-49F7-8C11-EF43F5650180}'

I have followed the instructions to create the registry key for MSI logging.

Hope this helps,

LM

 

Commodo Antivirus?

Ask in their Forum. This is a case where ORCA could help as discussed above. But the feature may in fact have been missing from the installation to begin with.

(At least there are reports on the web suggesting that this is the case).

Since this is a Beta product, you would benefit looking at these freeware AV alternatives:

AVG by Grisoft
AntiVir
Avast 4 << -- would be my choice

 

What in the keys relates it to CAVS? And how/what is that relation?

This issue occurred some in the first iteration of the beta, which they related to a faulty install mechanism. They changed installers and no longer had the problem. They've provided regkeys to delete, and a command line uninstall, which I did, but it hasn't changed this issue.

We're working thru it in Comodo's forum as well, and their development team is doing some more research based on information I've provided them; I'm trying to cover all bases, as it seems to relate to products other than theirs (ie, the installer).

What is ORCA (obviously not the sea creature...)? Where do I get it/use it? I've done checksum on the MSI download; everything's good in that respect...

LM

 

Your error message referred to two GUIDs. These GUIDs are related to the install of Commodo Antivirus. That is how I knew what application it was, by its GUIDs.

ORCA is available from the Windows Sofware SDK as I said above. Documentation: http://msdn.microsoft.com/library/d...mponents_for_windows_installer_developers.asp

Your issue is not a checksum issue. Your issue is that there are missing components from the original installation:

Nor is this an installer failure.
Something is wrong with how the installer instructions were written, and the components included (or not) in the image.

 

I downloaded and installed the SDK for WinXP. Error towards the end of installation:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 11/10/2006
Time: 12:31:06 PM
User: WCPLAPTOP\xxx
Computer: WCPLAPTOP
Description:
Product: Microsoft Platform SDK (3790.1830) -- Error 25130. The file C:\Program Files\Microsoft Platform SDK\SetEnv.cmd could not be open for read/write.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 42 41 39 36 41 36 39 {BA96A69
0008: 35 2d 45 39 43 45 2d 34 5-E9CE-4
0010: 42 32 41 2d 39 31 39 41 B2A-919A
0018: 2d 35 34 30 42 37 33 45 -540B73E
0020: 37 41 37 38 45 7d 7A78E}

Also, regarding the registry component entries for CAVS, this one {6617B209-C45E-4ED7-86A6-5055D17BFBEE} showed 8 entries in the Registry, which I backed up and removed. This one {E79E3ED7-50A7-49F7-8C11-EF43F5650180} returned no results. Editing, compacting and rebooting did not result in any changes - the popup still appears, and Viewer still gives the exact same Warning message for Event ID 1001.

LM

 

The SDK for Windows XP is not the right SDK.

You want the SDK for Windows Installer Developers:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/orca_exe.asp

I don't recall asking that the GUID entries be removed from the registry. I am not suprised that this did not help.

 

Sorry, Bill; not trying to get ahead of you or cause other problems. I had a moment so I thought I'd check to see; didn't work, and I replaced the originals.

I dl'd the setup.exe for SDK for WID. On running it, Windows says it will take 9+ hours to download the 968MB file. For what is needed in this situation, do I need the whole thing (since it allows you to select components to download). If not, which ones specifically?

Thanks,

LM

 

orca.msi

But consider what you are going to do with this utility.
What it allows you to do is to dis-assemble an .MSI package.

Your faster approach to this would lie with the folks at Commodo, as you are not the only one that had problems with Commodo Antivirus.

Also, have you considered using System Restore to a point prior to the installation?

Two last thoughts:

Do you have Ewido/AVG antispyware installed? You may have to uninstall Ewido as it has known conflicts with Commodo.

Redo any Windows Installer 3.1 installation:

• Download a fresh copy of the 3.1 Redistributable
  http://www.microsoft.com/downloads/...familyid=889482fc-5f56-4a38-b838-de776fd4138c
• Do not install yet!
• Start, Run, cmd
  cd \windows\system32
  ren msi.dll msi.old
  ren msihnd.dll msihnd.old
  ren msiexec.exe msiexec.old
  exit
• Reboot.
• Now re-apply the 3.1 redistributable

 

I thought I laid the situation out in my initial post; perhaps not (or not well enough...) I'll explain in more detail:

I had CAVS Beta1.x installed (there were known issues with the MSI installer not completely uninstalling in some circumstances, and Comodo created their own installer for future versions).

CAVS Beta2.x was released; it required an uninstall of Beta1.x prior to install of Beta2.x. I completed the uninstall thru Add/Remove Programs, installed Beta2.x.

Experienced a glitch causing a system freeze with an explorer.exe error (it's a Beta, after all), and had to manually power off (this is w/Beta2.x installed). I rebooted in Safe Mode, and rather than try to debug it, I thought to just Restore and start over; maybe the install of Beta2.x wasn't good. So I restored to my Pre-Beta2.x Restore Point.

On reboot to Windows with the Restore, Beta1.x automatically reinstalls. Fine. I uninstalled it again. That's when this annoying popup started. Also at that point, Beta2.x refused to recognize/accept the uninstall of Beta1.x, even tho' add/remove programs showed the program to be gone.

I ran two utility packages provided by Comodo, to "manually" remove the system files, LSP hook, and restore the registry backup created at install of Beta1.x. This did not fix the installer popup issue or Beta2.x's saying that Beta1.x needed to be uninstalled.

I manually removed the associated file folders for Beta1.x, ran RegSeeker to clean out the registry, edited the Startup to remove CAVS applications.

Finally Beta2.x agreed that Beta1.x was gone, and was successfully installed. (I Restored several times during this whole process, to reverse changes.) However, the MSI popup keeps occurring. It's not interfering with any application function, but it just won't go away...

I think most users have either moved on, or reformatted. I can't blame them, but I don't want to do either. Plus, I'm stubborn.

Inasfar as conflicting AVs, no I do not. I use non-resident AV scanning to keep from having conflict and make sure the system's clean. I am using Spybot S&D for other malware scanning, and haven't seen any conflicts. Since Beta2.x has HIPS I don't use any HIPS-type of product that could cause conflict, either.

I will redo the Windows Installer 3.1 in accordance with your instruction.

LM

 

Bill, renaming the three files and reinstalling the 3.1 did not resolve the MSI popup issue (you probably didn't expect it to...).

Also, (and probably no surprise here, either) whatever is causing this installer call runs in Safe Mode as well. At one point I rebooted into Safe Mode just to see, but that didn't help (I hoped it would, so I could take a snapshot of what ran both ways, to compare).

LM

 

And do you have Ewido/AVG anitspyware installed?

 

No, I do not have Ewido/AVG antispyware installed.

 

Create a new folder and install HijackThis into the new folder.
Download HijackThis here
www.merijn.org/files/hijackthis.zip
or here
www.castlecops.com/downloads-file-328.html

Then, Open Hijackthis and instead of scan choose *Open Misc Tools Section*
Then, in the top section marked "Startup List ", checkmark the two boxes to the right and then press the *Generate StartupListlog* button.

Please post back only this section of the HijackThis log:
Enumerating Active Setup stub paths:


Have you considered uninstalling Commodo Antivirus, as this is what is kicking the Installer error message.

Avast 4 and AntiVir are my two current favorite free AV applications. I currently am very disappointed with AVG and no longer recommend it.

 

Here is the Hijack This log section, as requested.

Enumerating Active Setup stub paths:
HKLM\Software\Microsoft\Active Setup\Installed Components
(* = disabled by HKCU twin)

[<{12d0ed0d-0ee0-4f90-8827-78cefb8f4988}] *
StubPath = C:\WINDOWS\system32\ieudinit.exe

[>{22d6f312-b0f6-11d0-94ab-0080c74c7e95}]
StubPath = C:\WINDOWS\inf\unregmp2.exe /ShowWMP

[>{26923b43-4d38-484f-9b9e-de460746276c}] *
StubPath = C:\WINDOWS\system32\ie4uinit.exe -UserIconConfig

[>{60B49E34-C7CC-11D0-8953-00A0C90347FF}] *
StubPath = RunDLL32 IEDKCS32.DLL,BrandIE4 SIGNUP

[>{60B49E34-C7CC-11D0-8953-00A0C90347FF}MICROS] *
StubPath = RunDLL32 IEDKCS32.DLL,BrandIE4 SIGNUP

[{2C7339CF-2B09-4501-B3F3-F3508C9228ED}] *
StubPath = %SystemRoot%\system32\regsvr32.exe /s /n /i:/UserInstall %SystemRoot%\system32\themeui.dll

[{44BBA842-CC51-11CF-AAFA-00AA00B6015B}] *
StubPath = rundll32.exe advpack.dll,LaunchINFSection C:\WINDOWS\INF\msnetmtg.inf,NetMtg.Install.PerUser.NT

[{6BF52A52-394A-11d3-B153-00C04F79FAA6}] *
StubPath = rundll32.exe advpack.dll,LaunchINFSection C:\WINDOWS\INF\wmp.inf,PerUserStub

[{7790769C-0471-11d2-AF11-00C04FA35D02}] *
StubPath = "%ProgramFiles%\Outlook Express\setup50.exe" /APP:WAB /CALLER:WINNT /user /install

[{89820200-ECBD-11cf-8B85-00AA005B4340}] *
StubPath = regsvr32.exe /s /n /i:U shell32.dll

[{89820200-ECBD-11cf-8B85-00AA005B4383}] *
StubPath = C:\WINDOWS\system32\ie4uinit.exe -BaseSettings

[{89B4C1CD-B018-4511-B0A1-5476DBF70820}] *
StubPath = C:\WINDOWS\system32\Rundll32.exe C:\WINDOWS\system32\mscories.dll,Install

The version of Comodo AntiVirus/AntiSpy associated with this MSI popup is Beta 1.x. It is no longer on my machine; it was uninstalled, and all associated files & registry keys (that I could find) physically removed, since the installer (MSI) did not remove them. I do have CAVS Beta 2.x installed; it has a completely different installer designed by Comodo to eliminate the problems associated with the Beta 1.x installer.

TNX,

LM