288125 - Uninstall 1.0.1 after update to 1.0.2 can't uninstall 1.0.2 or reinstall

Status: VERIFIED DUPLICATE of bug 247884

(Firefox :: Installer, defect)

Description

[Andrew]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 1.0.2

I downloaded the upgrade from 1.0.1 to 1.0.2 when I went into the Add/Remove 
programs section of Windows XP I saw that both versions where displaying. I 
then uninstalled 1.0.1.   1.0.2 still shows in the programs installed, but the 
shortcuts and the file directory are no longer showing. I then downloaded 
1.0.2 fully and tried to install it. It gave me an error message 
saying "unspecified error" and gave the option of "OK"

I then tried to uninstall 1.0.2 but it gave the following error

0: Uninstall log folder not found:

HKEY_LOCAL_MACHINE\Software\Mozilla\Mozilla Firefox\1.0.2(en-US)\Uninstall Log 
Folder

OK


I can not install or uninstall 1.0.2

Reproducible: Always

Steps to Reproduce:
1.See Summary
2.
3.

Actual Results:  
See Summary

Expected Results:  
1.0.1 should have uninstalled and 1.0.2 should have installed sole so that no 
Registry values would be missing

I don't have anything else to report that will help with this. I do have a 
screen shot of the second error message though.

Comment 1

[Andrew]

Attachment: .doc Contains a screen shot and brief description of problem

Comment 2

[Simon Paquet [:sipaq]]

The root cause here is bug 247884, so duping against that one. When you
uninstalled 1.0.1 you really uninstalled 1.0.2 because of this bug.

*** This bug has been marked as a duplicate of 247884 ***

Comment 3

[Andrew]

This doesn't solve the issue of not being able to install Firefox, as of this 
point Firefox cannot be installed. Firefox is not able to be used at all, 
ever. I'd like to be able to use it, but short of a clean install, I cannot 
use Firefox.

Comment 4

[Asa Dotzler [:asa]]

This is a symptom of bug 247884. To install Firefox, download the installer from
mozilla.org and run it.

*** This bug has been marked as a duplicate of 247884 ***