RE: Problems Before/After Uninstalling .Net Framework 1.1 - Please

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm running winXP sp2 and having this problem. I tried the firs command
prompt commands and that didn't work. Reading further down it gives more,
but you lost me as what to do. Rename, delete from command prompt? I'm
Stupid, please help.

"Steven Cheng[MSFT]" wrote:

> Hi Troy,
>
> Thanks for your followup. I'm sorry to hear that the problem became rather
> worse. Then, have you installed some of the updates on windowsupdate before
> your installer engine broken down?
>
> Since you're not able to intall any programs now, there must be some
> underlying settings got currupted , you can have a look at the following
> info I've found in some kb and threads:
>
> If still no one helps, I'm afraid the your sys enviorment may encounter
> some serious damage. Would you consider reinstalling the system?
>
>
> ====================================
> If the Windows Installer does not install successfully, one of the
> following may be the cause:
>
>
>
> - If an environment variable is empty, you receive the following error
> message:
>
> Error 1631: Windows Installer Service failed to start. Contact your
> support personnel.
> After you add a value or you remove the empty environment variable, the
> engine installs successfully.
>
> For additional information, click the article number below
> to view the article in the Microsoft Knowledge Base:
>
>
>
> KBLink:251274.KB.EN-US: Error Message When You Attempt to Install
> Program Using Windows Installer
>
> - On Windows NT 4.0, if the Sfc.dll file exists in the system folder, the
> engine may not install successfully.
> For additional information about a cause and workaround for this problem,
> click the article number below
> to view the article in the Microsoft Knowledge Base:
>
>
>
> KBLink:264652.KB.EN-US: BUG: Unable to Install or Upgrade Windows
> Installer Service
>
> - On Windows 2000, version 1.2 of the Windows Installer does not
> install. The Windows Installer files are protected files under System
> File Protection (SFP) and cannot be replaced. Running version 1.2 of
> Instmsi.exe has no effect on the computer, and version 1.1 remains on
> the system.
> ==============================
>
> ===================================
> Installer Succeeded, But You Cannot Run an .msi File
> ----------------------------------------------------
>
>
>
> If the Windows Installer does install successfully, but you cannot run an
> .msi file, one of the following may be the cause:
>
> NOTE: If the engine does not install correctly, you cannot run any .msi
> files.
>
>
>
> - The registration of the engine may be corrupted, so that an attempt to
> run an .msi package fails. If this is the case, all attempts to run an .msi
> package fail. If only a single .msi package does not complete successfully,
> contact the vendor of that package for support on that particular product's
> installation.
>
>
> To correct the registration of the Windows Installer, unregister and
> reregister the Installer service. This shuts down and reregisters the
> service, which assures that the Windows Installer engine will function
> properly. To do this, run the following commands from a command prompt:
>
>
> "msiexec /unregister" (without the quotation marks)
>
> "msiexec /regserver" (without the quotation marks)
> This corrects most situations in which the Windows Installer is not
> responding or in which you suspect corruption. This does not affect any
> application that is currently installed on the computer that is using the
> Windows Installer.
>
>
>
> - If correctly registering the engine does not resolve the problem and you
> want to remove the engine files and reinstall clean, follow these steps.
>
> NOTE: On Windows 2000 and on Microsoft Windows Millennium Edition, you
> cannot remove the Windows Installer engine because the files are protected.
>
> 1. Run the following command from a command prompt:
>
> "msiexec /unregister" (without the quotation marks)
>
> 2. Delete the Msi.dll, Msiexec.exe, and Msihnd.dll files from the system
> folder. You must rename these files from the command prompt.
>
> 3. Restart Windows.
>
> 4. Run the Instmsi.exe program to install and register the engine files
> again.
>
> =============================================================
>
> Thanks & Regards,
>
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
.

Quantcast