Closed Bug 303343 Opened 19 years ago Closed 17 years ago

Mozilla is not a valid Win32 Application, Install error:

Categories

(SeaMonkey :: Installer, defect)

x86
Windows XP
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: flyboydale, Unassigned)

Details

(Whiteboard: H'n'C)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511

With both the Mozilla 1.7.8 and the new Mozilla 1.7.11 I get an install error
and Mozilla will not install because it says Not a Valid Win32 Application. 
This is after I installed XP Professional Clean and did all the Windows Updates.
 Congradulations to Microsoft, they just made your Mozilla Browser uninstallable
on XP as a result of their new security download updates.  What a bunch of ****,
and I was just bragging to all my friends on how good Mozilla is compared to IE.
 Now everyone is stuck with IE whether they like it or not.

Reproducible: Always

Steps to Reproduce:
1.Download Mozilla 1.7.11 and create a folder in My Documents, then click on RUN
and chose the install file.  Error Not a Valid Win32 Application.
2.Download Mozilla 1.7.8 and create a folder in My Documents, then click on RUN
and chose the install file.  Error Not a Valid Win32 Application.
3.Everything was fine with Mozilla until I wiped the hard drive and reinstalled
XP Professional and downloaded all the Windows Updates.
4.Firefox 1.0.6 gets the same results too.

Actual Results:  
Mozilla would not install.  Neither version would install, nor would firefox
1.0.6 either, which I also tried.

Expected Results:  
Installed like it used to do.
Additional notation:  The Mozilla 1.7.8 works flawlessly on my other computer
that has XP Professional on it that has not had the updates done, but bear in
mind that anyone who reinstalls XP and Downloads All the Windows Updates is in
for a rude awakening if they think they are going to install Mozilla back onto
their computer with XP, it is not going to be allowed by the operating system,
thanks to Bill Gate's Motley Crew.
Did you download the installer from scratch or did you use one from your
harddisk, maybe the installer is just corrupted (also unlikely that all three
installers are broken)?
By mail (Dale, you can just comment in this bug here, no need to write me this
per mail) i got this info: He downloaded all three installers from scratch.
Maybe it was just a temporary glitch of the ftp server since that error message
means that app is corrupted? Maybe you could give me the md5sum of the installer
file(s) you downloaded (this is some some kind of checksum)? You can do this by
downloading the zip file from http://www.pc-tools.net/win32/md5sums/, extract it
somewhere and then drag&drop each installer file over the md5sums.exe icon. This
should open a new window with the md5sum in it. Paste these md5sums together
with the file name in the bug here. Then i can tell you if your downloaded
installer files are correct.
Per an email, suggesting I do some checksum checking and use a downloaded
program to see if the installer is corrupted.  I have Mozilla on a CD that
installs just fine as long as the Windows Newest Updates have not been
downloaded and installed, so I will try to install from that known working copy
of the CD I have burned and see if it will install from the fresh install and
updates of XP Pro.  If not, I will repost it here as an additional comment.  Do
not expect a result until after this weekend.
I have secured the last set of updates that have caused the problems installing
either Mozilla or Firefox on any computer that has had these following Microsoft
Updates for WinXP.  The error is "Not a Valid Win32 Application".  Mozilla is
not the only software that will not install.  There are a lot of programs I used
to use that would install and work fine as long as these last updates listed
below have not been performed!

Cumulative Security Update for Internet Explorer for Windows XP (KB896727)
Security Updates for Windows XP:
-KB893756
-KB896423
-KB899587
-KB899588
-KB899591
Update For Windows XP (KB894391)
Windows Malicious Software Removal Tool August 2005 (KB890830)

After you allow this series of updates to be installed, forget installing a lot
of your programs you used to install and use without problems, because you will
not be allowed to, due to the error, "Not a Valid Win32 Application".  

Bill Gates will have the control of what programs he will allow you to install
and use after doing the above updates if you have Windows XP.  So many of the
programs you bought or downloaded and used flawlessly in the past, may prove to
be worthless.

If you doubt my findings, just do a Google Search for "Not a Valid Win32
Application" and see all the hits you will get, but you will not find 1 solution
for each and every program that people are complaining about, and you certainly
will not find a solution to Mozilla or Firefox's inability to install after
doing the above downloads.  

Mozilla, Firefox, and many, many other good working programs, are now defunct
and worthless.  So, lets see if there is anyone who is working on Mozilla
Project that can come up with a real solution to this problem.
QA Contact: bugzilla → general
Is this still a problem ?
I am installed all Updates Available for Win XP SP2.

Mozilla 1.7.11 Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.11) Gecko/20050728 - OK
Mozilla 1.7.13 Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.13) Gecko/20060414 - OK
SeaMonkey 1.1b Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.8.1) Gecko/20061016 SeaMonkey/1.1b - OK
SeaMonkey 1.5a Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9a1) Gecko/20061016 SeaMonkey/1.5a - OK
This is still happening with Firefox 2.0.0.4! This is now 2 years! 
WFM - This is very likely due to a corrupted download or some other file corruption issue. I've personally seen this problem some time ago with some broken RAM cells.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Whiteboard: H'n'C
You need to log in before you can comment on or make changes to this bug.