Windows Update causing errors and re-boots system

This week Windows send a number of updates for Powerpoint, Word and Malicious
Software Removal Tool. The update attempts to begin the installation of the
items and before it can start the computer will re-boot. Once it re-boots an
error report is presented.
I followed the Microsoft error report recommendation yet once the update
attempts to begin the computer will re-boot.
I manually installed Powerpoint and Word individually. This was successful
without any re-boot errors. When I tried to manually update the Malicious
Software Removal Tool the computer errors and re-boots before the install
begins.
I went to the Microsoft webste and ran the Malicious Software Removal Tool
with no problems. I had hoped this would cancel out the update, however, I
was wrong.

Please advise me on what is happening with the Malicious Software Removal
Tool Update and what can I do to either remove the update or fix the error
causing the computer to re-boot.

Are running VIsta? if so here is a Knowledgebase article with all updates
and known issues as well as fixes..... For Vista as this is a Vista
Newsgroup!!

921583

"MAC" wrote:

> This week Windows send a number of updates for Powerpoint, Word and Malicious
> Software Removal Tool. The update attempts to begin the installation of the
> items and before it can start the computer will re-boot. Once it re-boots an
> error report is presented.
> I followed the Microsoft error report recommendation yet once the update
> attempts to begin the computer will re-boot.
> I manually installed Powerpoint and Word individually. This was successful
> without any re-boot errors. When I tried to manually update the Malicious
> Software Removal Tool the computer errors and re-boots before the install
> begins.
> I went to the Microsoft webste and ran the Malicious Software Removal Tool
> with no problems. I had hoped this would cancel out the update, however, I
> was wrong.
>
> Please advise me on what is happening with the Malicious Software Removal
> Tool Update and what can I do to either remove the update or fix the error
> causing the computer to re-boot.

Chris,
Thank you for the quick reply. I am running Windows XP.

"Chris {MSVB Beta Support}" wrote:

> Are running VIsta? if so here is a Knowledgebase article with all updates
> and known issues as well as fixes..... For Vista as this is a Vista
> Newsgroup!!
>
> 921583
>
> "MAC" wrote:
>
> > This week Windows send a number of updates for Powerpoint, Word and Malicious
> > Software Removal Tool. The update attempts to begin the installation of the
> > items and before it can start the computer will re-boot. Once it re-boots an
> > error report is presented.
> > I followed the Microsoft error report recommendation yet once the update
> > attempts to begin the computer will re-boot.
> > I manually installed Powerpoint and Word individually. This was successful
> > without any re-boot errors. When I tried to manually update the Malicious
> > Software Removal Tool the computer errors and re-boots before the install
> > begins.
> > I went to the Microsoft webste and ran the Malicious Software Removal Tool
> > with no problems. I had hoped this would cancel out the update, however, I
> > was wrong.
> >
> > Please advise me on what is happening with the Malicious Software Removal
> > Tool Update and what can I do to either remove the update or fix the error
> > causing the computer to re-boot.

"MAC" <> wrote in message
news:F395F4DD-9C1B-4901-9640-...
> This week Windows send a number of updates for Powerpoint, Word and Malicious
> Software Removal Tool. The update attempts to begin the installation of the
> items and before it can start the computer will re-boot. Once it re-boots an
> error report is presented.


Details?


> I followed the Microsoft error report recommendation yet once the update
> attempts to begin the computer will re-boot.


Please be more precise about your symptoms.
It is unclear whether you have a loop (e.g. due to automatic restart)
or if it is just a repeatable problem.

In case it is the former (loop due to automatic restart) which is preventing
you from capturing any diagnostics, see this recent post from MVP
Maurice N~

http://groups.google.com/group/micro...9ccd1250da213e

(Google Groups search for
prevent automatic reboot XP (MSFT OR MVP) group:microsoft.*
- sorted by date to try to capture current thinking
)



> I manually installed Powerpoint and Word individually. This was successful
> without any re-boot errors. When I tried to manually update the Malicious
> Software Removal Tool the computer errors and re-boots before the install
> begins.
> I went to the Microsoft webste and ran the Malicious Software Removal Tool
> with no problems. I had hoped this would cancel out the update, however, I
> was wrong.
>
> Please advise me on what is happening with the Malicious Software Removal
> Tool Update and what can I do to either remove the update or fix the error
> causing the computer to re-boot.


Again, it is unclear what is happening or what you can do.

Read the articles which this KB search turned up.
Notice that the first one is an example of the new
"Guided Help" service:

http://support.microsoft.com/search/...=20&1033comm=1

Hmm... have you seen this yet: <w>

<title>A diagnostic program may immediately close and you may receive a
&quot;STOP 0x00000050&quot; or &quot;STOP 0x0000000A&quot;
error message in Windows Server 2003, Windows 2000, or Windows XP</title>
http://support.microsoft.com/kb/897079/en-us


HTH

Robert Aldwinckle
---

When I submit the error report the following information is presented:

A message appears on a blue screen with error code information:

STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
- or -
STOP: 0x100000EA THREAD_STUCK_IN_DEVICE_DRIVER_M

I followed the recommended action to updated video drivers. After I updated
drivers is when I realized it was linked to the Windows Malicious Software
Removal Tool - June 2006 (KB890830).

I can't remove the install. Please let me know if this is possible.




"Robert Aldwinckle" wrote:

> "MAC" <> wrote in message
> news:F395F4DD-9C1B-4901-9640-...
> > This week Windows send a number of updates for Powerpoint, Word and Malicious
> > Software Removal Tool. The update attempts to begin the installation of the
> > items and before it can start the computer will re-boot. Once it re-boots an
> > error report is presented.
>
>
> Details?
>
>
> > I followed the Microsoft error report recommendation yet once the update
> > attempts to begin the computer will re-boot.
>
>
> Please be more precise about your symptoms.
> It is unclear whether you have a loop (e.g. due to automatic restart)
> or if it is just a repeatable problem.
>
> In case it is the former (loop due to automatic restart) which is preventing
> you from capturing any diagnostics, see this recent post from MVP
> Maurice N~
>
> http://groups.google.com/group/micro...9ccd1250da213e
>
> (Google Groups search for
> prevent automatic reboot XP (MSFT OR MVP) group:microsoft.*
> - sorted by date to try to capture current thinking
> )
>
>
>
> > I manually installed Powerpoint and Word individually. This was successful
> > without any re-boot errors. When I tried to manually update the Malicious
> > Software Removal Tool the computer errors and re-boots before the install
> > begins.
> > I went to the Microsoft webste and ran the Malicious Software Removal Tool
> > with no problems. I had hoped this would cancel out the update, however, I
> > was wrong.
> >
> > Please advise me on what is happening with the Malicious Software Removal
> > Tool Update and what can I do to either remove the update or fix the error
> > causing the computer to re-boot.
>
>
> Again, it is unclear what is happening or what you can do.
>
> Read the articles which this KB search turned up.
> Notice that the first one is an example of the new
> "Guided Help" service:
>
> http://support.microsoft.com/search/...=20&1033comm=1
>
> Hmm... have you seen this yet: <w>
>
> <title>A diagnostic program may immediately close and you may receive a
> "STOP 0x00000050" or "STOP 0x0000000A"
> error message in Windows Server 2003, Windows 2000, or Windows XP</title>
> http://support.microsoft.com/kb/897079/en-us
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>

MAC <> wrote:

> I realized it was linked to the Windows
> Malicious Software Removal Tool - June 2006 (KB890830).
>
> I can't remove the install. Please let me know if this is possible.

The Windows Malicious Software Removal Tool cannot be uninstalled because it
was not installed in the first place. It is not now present on the system.
During the Windows Update process, the MSRT is downloaded, does its work,
and is then deleted.

--
Robin Walker [MVP Networking]

"MAC" <> wrote in message
news:026A65A2-FA73-4C17-89A8-...
> When I submit the error report the following information is presented:
>
> A message appears on a blue screen with error code information:
>
> STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
> - or -
> STOP: 0x100000EA THREAD_STUCK_IN_DEVICE_DRIVER_M
>
> I followed the recommended action to updated video drivers.


I think that defective "video drivers" are just the most common causes
of this stop code. You would need to capture and analyse your stop code
info in more detail to check if that is really the case.

Even after the fact, if the crash created an event in the system event log
you could perhaps get more details from it (e.g. via Run... eventvwr)
or if you have a .dmp file associated with a crash you can run dumpchk
against it to see the stop info. (ref. KB314084)

BTW I would expect that this stop code would allow you to initiate
an Online Crash Analysis (OCA) incident. Did you see any sign of
that opportunity during a reboot?


> After I updated
> drivers is when I realized it was linked to the Windows Malicious Software
> Removal Tool - June 2006 (KB890830).
>
> I can't remove the install. Please let me know if this is possible.


As Robin indicated I think that this stop code should have nothing to do
with the MSRT. However, depending on how the malware had its hooks set
it's possible that there was a problem with its removal which could cause
even more bizarre symptoms than are inherent with it in the first place.

So, I think you should check whether in fact the MSRT did try to remove
any malware. E.g. search for its report, mrt.log (ref. KB891717)


HTH

Robert
---