Thank You, Microsoft and Steve Dodson

[Guest]

Thank you, guys. Apparently with todays Defender updates, the McAfee task
scheduler (mcmnhdlr.exe) is now classified as "allowed" software. My
scheduled virus scan ran tonight without interference from Defender, right
after I noticed the classification change. Hats off to all of you!

 

[Guest]

Whoops! Apparently the problem is not entirel solved. There are other
people reporting that Defender still classified their McAfee task handler as
Not Yet Classified. The one I noticed as this version of that file:
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask

File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10

My file version is different: version 10,0,0,20 and is is classified as
Allowed and Spynet voting not applicable. The same Allowed status shoud be
given to all versions of that mcAfee software.

 

[Steve Dodson [MSFT]]

I wonder if they have the latest updates.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

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.

 

[Guest]

Steve,

Yes I believe I have the latest updates, I've pasted below.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1395.2

I still have the issue w/ Defender Spynet "not yet classified". Rebel was
speaking of me in his message. His McAfee "mcmnhdlr" program was finally
classified. Mine never has been "classified". I'll paste it again below.
The only difference we could find is his McAfee Virus Scan version is 10 and
mine is 9. The file paths are identical.

File Name: mcmnhdlr.exe
Display Name: McAfee VirusScan
Description: McAfee VirusScan Command Handler
Publisher: McAfee, Inc.
Digitally Signed By: NOT SIGNED
File Type: Application
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
Date Installed: 1/1/2005 6:13:15 PM
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
Ships With OS: No
SpyNet Voting: In Progress

Kevin

I wonder if they have the latest updates.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

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.

 

[Guest]

Hello Kevin,

I notice, you are running v. 1.1.1051.0, today was release of v. 1.1.1347.0

Can you go to Windows Update, do an Express scan, and apply all offered
updªtes
http://update.microsoft.com

Once that is finished, can you verify the update installs? There are many
pre-requisite files which are needed from windows update and signature
update with windows defender will fail until you have these files.

Go here for 1.1.1347.0 and install on top of the old one.
http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

Bill Sanderson sugest.- Users who normally select advanced Spynet membership
should be aware that the install process will set you back to basic
membership, so it's a good idea to revisit both the Spynet membership area of
Tools, and the Options area--to see what's different, and check that your old
choices have been
preserved.

I hope this post is helpful.
Let us know how it works ºut.
Еиçеl

Steve,

Yes I believe I have the latest updates, I've pasted below.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1395.2

I still have the issue w/ Defender Spynet "not yet classified". Rebel was
speaking of me in his message. His McAfee "mcmnhdlr" program was finally
classified. Mine never has been "classified". I'll paste it again below.
The only difference we could find is his McAfee Virus Scan version is 10 and
mine is 9. The file paths are identical.

File Name: mcmnhdlr.exe
Display Name: McAfee VirusScan
Description: McAfee VirusScan Command Handler
Publisher: McAfee, Inc.
Digitally Signed By: NOT SIGNED
File Type: Application
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
Date Installed: 1/1/2005 6:13:15 PM
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
Ships With OS: No
SpyNet Voting: In Progress

Kevin

I wonder if they have the latest updates.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

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.

Whoops! Apparently the problem is not entirel solved. There are other
people reporting that Defender still classified their McAfee task handler
as
Not Yet Classified. The one I noticed as this version of that file:
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
My file version is different: version 10,0,0,20 and is is classified as
Allowed and Spynet voting not applicable. The same Allowed status shoud
be
given to all versions of that mcAfee software.
--
Old Rebel: Too Old to Rebel; Too Young to just take it!


:

Thank you, guys. Apparently with todays Defender updates, the McAfee task
scheduler (mcmnhdlr.exe) is now classified as "allowed" software. My
scheduled virus scan ran tonight without interference from Defender,
right
after I noticed the classification change. Hats off to all of you!

 

[Guest]

Engel,
OK did the version upgrade, all patches that were released on Patch tuesday
were automatic but I did go to update website just to verify and none
available. Now all of my programs under Defender software explorer are
showing "Not yet Classified". Before upgrade the only problem I had w/
classification was a McAfee program that Spynet did not recognize. What's
really funny is under startup programs, Windows Defender itself showing up as
"Not yet Classified". Imagine that, that's like me forgetting my name. I'm
kind of bashing Defender here but I think the real culprit is Spynet Voting,
This voting is like the Florida polls - I don't think it works. It's Beta
though, I know.

Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1303.0
Definition Version: 1.14.1396.12

File Name: MSASCui.exe
Display Name: Windows Defender
Description: Windows Defender User Interface
Publisher: Microsoft Corporation
Digitally Signed By: Microsoft Code Signing PCA
File Type: Application
Startup Value: "C:\Program Files\Windows Defender\MSASCui.exe" -hide
File Path: C:\Program Files\Windows Defender\MSASCui.exe
File Size: 777424 Bytes
File Version: 1.1.1347.0
Date Installed: 4/3/2006 6:12:24 PM
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
Ships with Operating System: No
SpyNet Voting: In Progress

Kevin

Hello Kevin,

I notice, you are running v. 1.1.1051.0, today was release of v. 1.1.1347.0

Can you go to Windows Update, do an Express scan, and apply all offered
updªtes
http://update.microsoft.com

Once that is finished, can you verify the update installs? There are many
pre-requisite files which are needed from windows update and signature
update with windows defender will fail until you have these files.

Go here for 1.1.1347.0 and install on top of the old one.
http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

Bill Sanderson sugest.- Users who normally select advanced Spynet membership
should be aware that the install process will set you back to basic
membership, so it's a good idea to revisit both the Spynet membership area of
Tools, and the Options area--to see what's different, and check that your old
choices have been
preserved.

I hope this post is helpful.
Let us know how it works ºut.
Еиçеl

Steve,

Yes I believe I have the latest updates, I've pasted below.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1395.2

I still have the issue w/ Defender Spynet "not yet classified". Rebel was
speaking of me in his message. His McAfee "mcmnhdlr" program was finally
classified. Mine never has been "classified". I'll paste it again below.
The only difference we could find is his McAfee Virus Scan version is 10 and
mine is 9. The file paths are identical.

File Name: mcmnhdlr.exe
Display Name: McAfee VirusScan
Description: McAfee VirusScan Command Handler
Publisher: McAfee, Inc.
Digitally Signed By: NOT SIGNED
File Type: Application
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
Date Installed: 1/1/2005 6:13:15 PM
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
Ships With OS: No
SpyNet Voting: In Progress

Kevin

I wonder if they have the latest updates.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

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.
Whoops! Apparently the problem is not entirel solved. There are other
people reporting that Defender still classified their McAfee task handler
as
Not Yet Classified. The one I noticed as this version of that file:
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
My file version is different: version 10,0,0,20 and is is classified as
Allowed and Spynet voting not applicable. The same Allowed status shoud
be
given to all versions of that mcAfee software.
--
Old Rebel: Too Old to Rebel; Too Young to just take it!


:

Thank you, guys. Apparently with todays Defender updates, the McAfee task
scheduler (mcmnhdlr.exe) is now classified as "allowed" software. My
scheduled virus scan ran tonight without interference from Defender,
right
after I noticed the classification change. Hats off to all of you!

 

[Guest]

Hi Kevin,

I read one o two posts with the same problem, since the upgrade is 2 days
old, and this is a wekend, we have to wait until next week for somebody from
HQ to supply the solution, I don't have nothing to offer with this problem,
maybe somebody else come with your solution.

Sorry Kevin
Еиçеl
---

Engel,
OK did the version upgrade, all patches that were released on Patch tuesday
were automatic but I did go to update website just to verify and none
available. Now all of my programs under Defender software explorer are
showing "Not yet Classified". Before upgrade the only problem I had w/
classification was a McAfee program that Spynet did not recognize. What's
really funny is under startup programs, Windows Defender itself showing up as
"Not yet Classified". Imagine that, that's like me forgetting my name. I'm
kind of bashing Defender here but I think the real culprit is Spynet Voting,
This voting is like the Florida polls - I don't think it works. It's Beta
though, I know.

Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1303.0
Definition Version: 1.14.1396.12

File Name: MSASCui.exe
Display Name: Windows Defender
Description: Windows Defender User Interface
Publisher: Microsoft Corporation
Digitally Signed By: Microsoft Code Signing PCA
File Type: Application
Startup Value: "C:\Program Files\Windows Defender\MSASCui.exe" -hide
File Path: C:\Program Files\Windows Defender\MSASCui.exe
File Size: 777424 Bytes
File Version: 1.1.1347.0
Date Installed: 4/3/2006 6:12:24 PM
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
Ships with Operating System: No
SpyNet Voting: In Progress

Kevin

Hello Kevin,

I notice, you are running v. 1.1.1051.0, today was release of v. 1.1.1347.0

Can you go to Windows Update, do an Express scan, and apply all offered
updªtes
http://update.microsoft.com

Once that is finished, can you verify the update installs? There are many
pre-requisite files which are needed from windows update and signature
update with windows defender will fail until you have these files.

Go here for 1.1.1347.0 and install on top of the old one.
http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

Bill Sanderson sugest.- Users who normally select advanced Spynet membership
should be aware that the install process will set you back to basic
membership, so it's a good idea to revisit both the Spynet membership area of
Tools, and the Options area--to see what's different, and check that your old
choices have been
preserved.

I hope this post is helpful.
Let us know how it works ºut.
Еиçеl

Steve,

Yes I believe I have the latest updates, I've pasted below.

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1395.2

I still have the issue w/ Defender Spynet "not yet classified". Rebel was
speaking of me in his message. His McAfee "mcmnhdlr" program was finally
classified. Mine never has been "classified". I'll paste it again below.
The only difference we could find is his McAfee Virus Scan version is 10 and
mine is 9. The file paths are identical.

File Name: mcmnhdlr.exe
Display Name: McAfee VirusScan
Description: McAfee VirusScan Command Handler
Publisher: McAfee, Inc.
Digitally Signed By: NOT SIGNED
File Type: Application
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
Date Installed: 1/1/2005 6:13:15 PM
Startup Type: Registry: Local Machine
Location: Software\Microsoft\Windows\CurrentVersion\Run
Classification: Not yet classified
Ships With OS: No
SpyNet Voting: In Progress

Kevin



:

I wonder if they have the latest updates.

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

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.
Whoops! Apparently the problem is not entirel solved. There are other
people reporting that Defender still classified their McAfee task handler
as
Not Yet Classified. The one I noticed as this version of that file:
Startup Value: "c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe" /checktask
File Path: c:\PROGRA~1\mcafee.com\vso\mcmnhdlr.exe
File Size: 143360 Bytes
File Version: 9, 1, 0, 10
My file version is different: version 10,0,0,20 and is is classified as
Allowed and Spynet voting not applicable. The same Allowed status shoud
be
given to all versions of that mcAfee software.
--
Old Rebel: Too Old to Rebel; Too Young to just take it!


:

Thank you, guys. Apparently with todays Defender updates, the McAfee task
scheduler (mcmnhdlr.exe) is now classified as "allowed" software. My
scheduled virus scan ran tonight without interference from Defender,
right
after I noticed the classification change. Hats off to all of you!