39 replies to this topic

[JonF]

I've tried to install Internet Explorer 7 from AutoPatcher sfive or six times, always as part of a host of other updates, and it has always failed. AutoPatcher thought it worked but IE wouldn't start; in each case I had to uninstall IE7 and reinstall it from a download. So I don't do that anymore.

Anybody have different experience or thoughts on the issue?

[Erik Ramey]

I've personally used the IE7 in AP to update successfully a countless number of times.

When you say that it failed to install correctly, what are you seeing that tells you that IE7 didn't install correctly?

[JonF]

It's been some time, so I may not remember all details correctly. Certainly the most common symptom was IE7 crashing or freezing before dsiplaying the initial web page. After it fails to start several times in that manner (on one machine), you start thinking that the IE7 install got corrupted. Then when an uninstall and reinstall (from the web) works first time, I get convinced.

Edited by JonF, 24 March 2008 - 09:27 PM.

[EmuKing]

JonF, on Mar 24 2008, 05:26 PM, said:

It's been some time, so I may not remember all details correctly. Certainly the most common symptom was IE7 crashing or freezing before dsiplaying the initial web page. After it fails to start several times in that manner (on one machine), you start thinking that the IE7 install got corrupted. Then when an uninstall and reinstall (from the web) works first time, I get convinced.

Hi Jon,

Have never had any problems updating or installing IE. Just did a fresh install over the weekend and worked great!

King

[PsiMoon314]

Hi,

IE7 has stopped installing here when installed via APXP.

I have even manually set the run options to /passive and the IE7 installer does not seem to run when selected via AP.

I suspect that there is an installation order problem here; which seems to happen regularly with AP.

There is some dependency here for IE7 which is not getting installed before IE7 hence IE7 is not being installed.

For example the WGA addon is not run early on, which means than anything which needs a WGA check to install (such as IE7 or Windows Defender) will not install.

If the AP logging was better we might be able to track this down and fix it.

Kind Regards

Simon

[james.faction]

Since using APUP version of Autopatcher (for WinXP) I have used it to update IE to version 7 twice on two different machines (Dell Desktop and HP laptop). It succeeded, however in both cases IE7 is broken! It closes pretty much straight away when you start it, with no error message. It's possible DEP is killing it because it doesn't recognise the DLL or something? The problem goes away when I uninstall and go back to IE6.

[PsiMoon314]

Hi,

Occasionally I do get a strange install of IE7 where the engine and backend has updated to IE7 but the UI has not, it's still the IE6 front-end.

Uninstalling IE7, rebooting and Reinstalling usually fixes this outside of AP.

Again I would have to assume that the install order within AP is not correct.

I would suspect that IE7 needs to be installed early on. There seems to be little point in installing IE6 updates and then installing IE7 before you reboot.

Kind Regards

Simon

[Erik Ramey]

I'm talking to Antonis about creating conflicts with the main executable. Basically if you choose a, updates b and c will be grayed out since it conflcts. I was thinking the same thing personally PsiMoon314

[james.faction]

strangest thing... I tried reinstalling IE7 through Microsoft Update and it exhibited the same behaviour I mentioned above, closing almsot straight after opening, so I rolled back again. When I reinstalled IE7 again, this time I un-ticked the "download the latest updates" during the IE7 install - and all was well. *shrug*

*edit: I suggest the best workaround for now is to install IE7 first - it gets downloaded with autopatcher so might as well use the installer - in (autopatcher install directory)\modules\components\IE7_x86... install first, reboot as directed, then run autopatcher. I've now done this on a couple systems, it works fine and only adds an extra 5 mins or so to updating a system.

Edited by james.faction, 01 April 2008 - 02:35 AM.

[PsiMoon314]

Hi,

Would there be any merit to creating separate sections within AP for IE7 and WMP11 so that they can be selected and unselected as needed?

I would suggest that all of the updates relating to these two packages be grouped with them in their own sections.

Once SP3 has been released this would greatly simplify integrating this SP into APXP.

Kind Regards

Simon

[Cyrus]

I have not tried to install IE7 (I actually removed IE6 from my computers and use only Opera as a browser), but I have installed WMP11 on MANY computers with other updates and have had no issues as of yet.

[james.faction]

would that I could remove IE7 but we have browser-specific applications such as outlook web access that people can't do without... also unfortunately users are fussy and change-resistant... I'm able to say the upgrade to IE7 is necessary thankfully due to security concerns.

This does actually make it easier for them to change to other browsers since IE7 is much more similar to alternatives. Once they are used to IE7, switching to another better browser is much easier, a much smaller step.

[Angelico_Payne]

Never, allways had issues during or after install, finally had to integrate it into installation itself.

Dont get me wrong, net is full of people complaining about IE7 issues, so maybe problem is not in AP, but manual installation or integration method works, setting apart random crashes and IE7 bugs.

[PsiMoon314]

Hi,

I have created a modified version of the IE7_xp_x86_enu.apm file for installing IE7.

I have removed the registry detection portion of this .APM and so far this seems to be helping to resolve my "IE7 not installing from AP" issues.

The new .APM is as follows:

[AutoPatcher 5.6 Module]

[General]
Title=Internet Explorer 7 for Windows XP SP2
Description=Internet Explorer version 7.
Author=Microsoft
ModuleAuthor=Lyndon Brown
WebPage=http://www.microsoft.com/windows/ie/downloads/default.mspx
ReleaseDate=20041100

[Behavior]
ParentID=WINDOWS_COMPONENTS_PARENT
UniqueID=IE7_XP_X86_ENU
Critical=False
Recommended=True
AutoExpand=False
Depends=WGA_XP_X86_ENU
TimeToInstall=240
TimeToRemove=240
RequiresReboot=True

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=ie7.cat
FileVersion=ANY
FileMD5=

[DetectionRegistry]
RegistryPath=
KeyName=
KeyValue=

[OperatingSystem]
WindowsVersion=XP_SP2_X86,XP_SP3_X86,XP_MCE2005_X86
SystemLanguage=1033,2057

[SystemComponents]
InternetExplorer=ANY
WindowsMediaPlayer=ANY
DotNetFramework=ANY
WindowsInstaller=ANY
DirectX=ANY
MSNMessenger=ANY

[OfficeComponents]
Word=ANY
Excel=ANY
PowerPoint=ANY
Outlook=ANY
Publisher=ANY
Visio=ANY
Project=ANY
OneNote=ANY
FrontPage=ANY
InfoPath=ANY
Access=ANY
SharePointDesigner=ANY
Groove=ANY

[Installation]
"Module:\IE7-WindowsXP-x86-enu.exe" /passive /update-no /norestart

[Removal]
"windows:\ie7\Spuninst\spuninst.exe" /passive /norestart

[Slipstream]

My changes are in the ReleaseDate, DetectionRegistry, Installation and Removal sections.

I have not looked into why the DetectionRegisty section might be causing an issue with AP installing IE7.

Kind Regards

Simon

[Coldwind]

PsiMoon314, on Apr 7 2008, 06:44 AM, said:

Hi,

I have created a modified version of the IE7_xp_x86_enu.apm file for installing IE7.

I have removed the registry detection portion of this .APM and so far this seems to be helping to resolve my "IE7 not installing from AP" issues.

The new .APM is as follows:

[AutoPatcher 5.6 Module]

[General]
Title=Internet Explorer 7 for Windows XP SP2
Description=Internet Explorer version 7.
Author=Microsoft
ModuleAuthor=Lyndon Brown
WebPage=http://www.microsoft.com/windows/ie/downloads/default.mspx
ReleaseDate=20041100

[Behavior]
ParentID=WINDOWS_COMPONENTS_PARENT
UniqueID=IE7_XP_X86_ENU
Critical=False
Recommended=True
AutoExpand=False
Depends=WGA_XP_X86_ENU
TimeToInstall=240
TimeToRemove=240
RequiresReboot=True

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=ie7.cat
FileVersion=ANY
FileMD5=

[DetectionRegistry]
RegistryPath=
KeyName=
KeyValue=

[OperatingSystem]
WindowsVersion=XP_SP2_X86,XP_SP3_X86,XP_MCE2005_X86
SystemLanguage=1033,2057

[SystemComponents]
InternetExplorer=ANY
WindowsMediaPlayer=ANY
DotNetFramework=ANY
WindowsInstaller=ANY
DirectX=ANY
MSNMessenger=ANY

[OfficeComponents]
Word=ANY
Excel=ANY
PowerPoint=ANY
Outlook=ANY
Publisher=ANY
Visio=ANY
Project=ANY
OneNote=ANY
FrontPage=ANY
InfoPath=ANY
Access=ANY
SharePointDesigner=ANY
Groove=ANY

[Installation]
"Module:\IE7-WindowsXP-x86-enu.exe" /passive /update-no /norestart

[Removal]
"windows:\ie7\Spuninst\spuninst.exe" /passive /norestart

[Slipstream]

My changes are in the ReleaseDate, DetectionRegistry, Installation and Removal sections.

I have not looked into why the DetectionRegisty section might be causing an issue with AP installing IE7.

Kind Regards

Simon

[Coldwind]

JonF, on Mar 20 2008, 01:54 PM, said:

I've tried to install Internet Explorer 7 from AutoPatcher sfive or six times, always as part of a host of other updates, and it has always failed. AutoPatcher thought it worked but IE wouldn't start; in each case I had to uninstall IE7 and reinstall it from a download. So I don't do that anymore.

Anybody have different experience or thoughts on the issue?

Install Windows XP SP2 (What ever Flavor)
Get hooked up to the Internet just long enough to activate Windows (I'm getting pretty good at this - Less than 4 seconds)
OR if you are really paranoid about hooking to the grid, activate Windows by Phone.
Run AutoPatcher - Works everytime!

Without activation you will run into the problem you are having..

[Tekzel]

Coldwind, on Apr 15 2008, 03:33 PM, said:

Install Windows XP SP2 (What ever Flavor)
Get hooked up to the Internet just long enough to activate Windows (I'm getting pretty good at this - Less than 4 seconds)
OR if you are really paranoid about hooking to the grid, activate Windows by Phone.
Run AutoPatcher - Works everytime!

Without activation you will run into the problem you are having..

I always get the same issue, and always activate first. Besides, they removed the activation requirement from IE7 quite a while back. I just run AP, then immediately rerun the installer for IE7 directly from the modules folder. Its a minor pain in the butt, but it works. Lately, I have been having issues with DotNet 3.0 not updating after running AP. I have to run the cleanup tool and install all the dotnet stuff from windows update. So, it seems this is an issue that should be addressed for more than one product.

[JonF]

Well, everybody tells me it's supposed to work ...

So a friend bought a brand-new Dell and I updated it with AutoPatcher, created a week or two ago (after April's Patch Tuesday). For some reason the Dell came with IE6. So I selected pretty much everything including IE7.

After the reboot, the IE7 icon was on the desktop. Clicking it yielded a white window which immediately disappeared, and a new shortcut to IE7 on the destop.

It didn't show in Add/Remove programs, so I went into Windows\ie7\wherever the uninstall is, uninstalled it, and reinstalled it from the Web. No problems.

Maybe it would work if only IE7 were being installed ...

[frankenberrie]

IE7 never worked for me from AP and I tried on over 50 different machines.. I install IE7 first, reboot, the run AP-