K
Ken1943
Anyone else getting a second update today ? It installed ok yesterday.
KenW
KenW
N
NQ
Yes I did but because they are both listed as KB890830 I assumed thatAnyone else getting a second update today ? It installed ok yesterday.
KenW
even though it showed that it successfully installed yesterday that it
probably hadn't installed correctly.
K
Ken1943
I stopped the install. I am checking for updates now to see what happens.Yes I did but because they are both listed as KB890830 I assumed that
even though it showed that it successfully installed yesterday that it
probably hadn't installed correctly.
KenW
K
Ken1943
Just got no updates available.Yes I did but because they are both listed as KB890830 I assumed that
even though it showed that it successfully installed yesterday that it
probably hadn't installed correctly.
KenW
F
Fokke Nauta
Here as well.Anyone else getting a second update today ? It installed ok yesterday.
KenW
It installed correctly yesterday. Status = succesful.
Today it (KB890830) came again. I let it install itself, to see as to
what will happen. It installed correctly, status = succesful. It's twice
on the update history list.
Perhaps NQ is right and it did not install correctly the first time.
Fokke
S
SC Tom
Maybe it's an update to itself? It could be that Microsoft found they forgotKen1943 said:Anyone else getting a second update today ? It installed ok yesterday.
something and released it again. They wouldn't necessarily change the
number; it might be like the MSE definition updates that all have the same
KB number but different Definition numbers. Who knows what evil lurks in the
minds of MS ;-)
F
Fokke Nauta
Windows 8.1?Maybe it's an update to itself? It could be that Microsoft found they
forgot something and released it again. They wouldn't necessarily change
the number; it might be like the MSE definition updates that all have
the same KB number but different Definition numbers. Who knows what evil
lurks in the minds of MS ;-)
Fokke
B
Bert
In Fokke Nauta
Or it's just living up to its name and is being malicious.Perhaps NQ is right and it did not install correctly the first time.
E
Ed Cryer
If you look at the log in Sytem32/debug/mrt.log you might find somethingKen1943 said:Anyone else getting a second update today ? It installed ok yesterday.
KenW
interesting. Mine has a run for yesterday and one for today; both found
no malware, but the versions of the program are different.
Microsoft Windows Malicious Software Removal Tool v4.22, July 2013
Started On Wed Jul 10 12:08:52 2013
Microsoft Windows Malicious Software Removal Tool v5.2, July 2013 (build
5.2.9201.0)
Started On Thu Jul 11 13:57:11 2013
Ed
J
John K.Eason
From memory, the one with the other updates was around 5 Meg, whereas the later*From:* "SC Tom" <[email protected]>
*Date:* Thu, 11 Jul 2013 08:10:21 -0400
Maybe it's an update to itself? It could be that Microsoft found
they forgot something and released it again. They wouldn't
necessarily change the number; it might be like the MSE definition
updates that all have the same KB number but different Definition
numbers. Who knows what evil lurks in the minds of MS ;-)
one was 19 Meg, so it does look as if the later one was a complete program update.
Why MS didn't do the whole lot in one go is another question...
Regards
John ([email protected]) Remove the obvious to reply...
K
Ken1943
Guess August update will tell.From memory, the one with the other updates was around 5 Meg, whereas the later
one was 19 Meg, so it does look as if the later one was a complete program update.
Why MS didn't do the whole lot in one go is another question...
Regards
John ([email protected]) Remove the obvious to reply...
KenW
C
charliec
I had posted another message on this updated before I saw thisGuess August update will tell.
KenW
message. I'm guessing it is safe to install and does not impact other
Antivirus programs (I run Norton Antivirus). How does it impact the
operations of you system?
charliec
R
Robin Bignall
So, SC Tom's explanation sounds reasonable.If you look at the log in Sytem32/debug/mrt.log you might find something
interesting. Mine has a run for yesterday and one for today; both found
no malware, but the versions of the program are different.
Microsoft Windows Malicious Software Removal Tool v4.22, July 2013
Started On Wed Jul 10 12:08:52 2013
Microsoft Windows Malicious Software Removal Tool v5.2, July 2013 (build
5.2.9201.0)
Started On Thu Jul 11 13:57:11 2013
G
gufus
I got a error with v4.22, maybe thats why M$ released a bug fix.If you look at the log in Sytem32/debug/mrt.log you might find something
---------------------------------------------------------------------------------------
Microsoft Windows Malicious Software Removal Tool v4.22, July 2013
Started On Wed Jul 10 23:54:58 2013
->Scan ERROR: resource process://pid:1628 (code 0x00000490 (1168))
Results Summary:
----------------
No infection found.
Microsoft Windows Malicious Software Removal Tool Finished On Wed Jul
10 23:56:34 2013
Return code: 0 (0x0)
---------------------------------------------------------------------------------------
Microsoft Windows Malicious Software Removal Tool v5.2, July 2013
(build 5.2.9201.0)
Started On Thu Jul 11 13:22:16 2013
Results Summary:
----------------
No infection found.
Microsoft Windows Malicious Software Removal Tool Finished On Thu Jul
11 13:24:00 2013
Return code: 0 (0x0)
J
Johnny
I got two malicious software removal tool updates. One installed, andAnyone else getting a second update today ? It installed ok yesterday.
KenW
the other is waiting to be installed. They are the same number.
I don't know why the first one installed, because I'm supposed to decide
whether or not to install updates.
G
gufus
Strange, my 32bit box has 1 update v4.22, my 64bit has 2 v4.22 - v5.2I got two malicious software removal tool updates. One installed, and
the other is waiting to be installed. They are the same number.
E
Ed Cryer
No, that error you got is very common; common enough to ignore.gufus said:I got a error with v4.22, maybe thats why M$ released a bug fix.
---------------------------------------------------------------------------------------
Microsoft Windows Malicious Software Removal Tool v4.22, July 2013
Started On Wed Jul 10 23:54:58 2013
->Scan ERROR: resource process://pid:1628 (code 0x00000490 (1168))
Results Summary:
----------------
No infection found.
Microsoft Windows Malicious Software Removal Tool Finished On Wed Jul
10 23:56:34 2013
Return code: 0 (0x0)
---------------------------------------------------------------------------------------
Microsoft Windows Malicious Software Removal Tool v5.2, July 2013
(build 5.2.9201.0)
Started On Thu Jul 11 13:22:16 2013
Results Summary:
----------------
No infection found.
Microsoft Windows Malicious Software Removal Tool Finished On Thu Jul
11 13:24:00 2013
Return code: 0 (0x0)
The second KB890830 (notice they're always the same KB no; going back
years) was a major program update.
Here's a possible scenario for what happened in an MS office.
Programmer A: I haven't quite got it ready yet. I'll do my best.
Programmer B: It's almost time to release the monthly updates.
Programmer A: Damn. I'm doing what I can.
Programmer B: Release the monthlies.
...........
Programmer A: Here's the new MSRT.
Programmer B: Too late, old chap. The Kraken's been released.
Programmer A goes to boss; boss tells programmer B to release it on its
own. Programmer B does just that.
Ed
C
charliec
I went ahead and installed the update today. But, how do you tell itNo, that error you got is very common; common enough to ignore.
The second KB890830 (notice they're always the same KB no; going back
years) was a major program update.
Here's a possible scenario for what happened in an MS office.
Programmer A: I haven't quite got it ready yet. I'll do my best.
Programmer B: It's almost time to release the monthly updates.
Programmer A: Damn. I'm doing what I can.
Programmer B: Release the monthlies.
..........
Programmer A: Here's the new MSRT.
Programmer B: Too late, old chap. The Kraken's been released.
Programmer A goes to boss; boss tells programmer B to release it on its
own. Programmer B does just that.
Ed
is running and where do you find the result of scan? Just want to
check and see if it is active?
charliec
P
Paul
The MRT runs once, when it is "installed" on a monthly basis. At leastI went ahead and installed the update today. But, how do you tell it
is running and where do you find the result of scan? Just want to
check and see if it is active?
charliec
that is what mine does, on an older OS.
A user can also run it manually, at any time.
http://en.wikipedia.org/wiki/Windows_Malicious_Software_Removal_Tool
"It records its results in a log file located at %windir%\debug\mrt.log.
To run it manually at other times, users can start "mrt.exe" using the
Command Prompt or Run command in the Start Menu.
With Windows 2000 going out of support in July 2010, Microsoft stopped
distributing the MSRT tool to Windows 2000 users via Windows update.
Download and usage of the current versions up to 4.20 (May 2013) was
still possible. Starting with version 5.1 (June 2013) Windows 2000
is not supported anymore."
So I guess that's a difference, between the two versions being discussed.
Loss of Win2K testing, even though Win2K is very close to WinXP
in terms of design concepts.
HTH,
Paul
N
Nil
It's only "active" for a short time. It appears as an update, it getsI went ahead and installed the update today. But, how do you tell
it is running and where do you find the result of scan? Just want
to check and see if it is active?
downloaded and installed, it runs once and exits, and supposedly tells
you if it found anything of note. Pretty stupid of it not to provide
you with any feedback, if you ask me. Maybe it makes an entry in one of
the Event Logs.
You can run it manually by typing "MRT" in the "Run..." box.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.