Malfunction after Windows Update

[Drew]

I tried using the Windows update feature a few hours
ago to download a couple of critical updates and some
updates for Outlook Express.

Bad idea.

After installing, I could not boot the system.

I would get a blue screen before the login screen
that said something like STOP (it flashed so fast
you could not read the full message) and then reboots.

I used the Win 2000 CD and did a repair and was
able to get the system to boot, but things are not
right.

I get this "Windows Installer" window that pops up
when I boot the system or launch Internet explorer

Should I do an in-place upgrade?

Drew

 

[Jason Hall [MSFT]]

--------------------

From: "Drew" <[email protected]>
Subject: Malfunction after Windows Update
Date: Wed, 9 Jun 2004 22:03:43 -0500

I tried using the Windows update feature a few hours
ago to download a couple of critical updates and some
updates for Outlook Express.

Bad idea.

After installing, I could not boot the system.

I would get a blue screen before the login screen
that said something like STOP (it flashed so fast
you could not read the full message) and then reboots.

I used the Win 2000 CD and did a repair and was
able to get the system to boot, but things are not
right.

I get this "Windows Installer" window that pops up
when I boot the system or launch Internet explorer

Should I do an in-place upgrade?

Drew

----------------------

If you fully describe the current problem you are experiencing we will be
able to help you better
....or you can just do an in-place upgrade ; )

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Drew]

If you fully describe the current problem you are experiencing we will be
able to help you better
...or you can just do an in-place upgrade ; )

I thought I did describe the problem.

Anyway, I disabled the Windows Installer in the Group policy editor
and now things seem to be working. This is not what I wanted to
do, however. I suspect I will have problems in the future.

Microsoft: This is messed up. The update should not have caused
this problem. And there does not appear to be a easy fix for
this annoying "Windows Installer" dialog that pops up.

Drew

 

[Torgeir Bakken \(MVP\)]

I thought I did describe the problem.

Anyway, I disabled the Windows Installer in the Group policy editor
and now things seem to be working. This is not what I wanted to
do, however. I suspect I will have problems in the future.

Microsoft: This is messed up. The update should not have caused
this problem. And there does not appear to be a easy fix for
this annoying "Windows Installer" dialog that pops up.

Hi

Most likely it is Windows Installer doing an on-demand installation...

See "Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand installation?"
in the FAQ at

http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx

To access the Application Log in the Event viewer,
run the following command from Start/Run:

eventvwr.msc


If you are running Windows XP (or have access to a Windows XP computer,
you can copy MSIZAP.EXE over to your Win2k computer):

If a product code is listed there and this product is not really installed,
MSIZAP.EXE is maybe able to fix this issue, it is included as a utility in
the support tools installation package (on your WinXP CD) with some additional
documentation included in suptools.chm (installed by suptools.msi).

It will remove all Windows Installer entries for a product key that you feed
it with.

Note that if MSIZAP.EXE is used incorrectly it can affect other applications
on the machine.

Based on the documentation in
http://msdn.microsoft.com/library/en-us/msi/setup/msizap_exe.asp

this is what you should run:

msizap T {product code}

an example:
msizap T {FFB37294-1155-17D3-A809-0250BAAFB1AB}


Alternatively, for a more user friendly interface to MSIZAP.EXE ,
take a look at this article:

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

 

[Drew]

Most likely it is Windows Installer doing an on-demand installation...

See "Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand installation?"
in the FAQ at

http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx

To access the Application Log in the Event viewer,
run the following command from Start/Run:

eventvwr.msc

Thanks for the info.

I was able to get rid of the Windows Installer popup by reinstalling the offending
program.

However, I now I get this long pause before the desktop shows up on booting.

I just looked at the Application Log in the Event Viewer, and there are quite
a few error messages going on. Most of them come from "WinMgmt":
WMI ADAP was unable to create object index 1848 for Performance Library RSVP because no value was found in the 009 subkey

WMI ADAP was unable to process the PerfDisk performance library due to a time violation in the open function

Unable to read IO control information from NBT device.

Drew