Results 1 to 15 of 15
  1. #1
    New Lounger
    Join Date
    Dec 2009
    Location
    UK
    Posts
    5
    Thanks
    2
    Thanked 1 Time in 1 Post

    Turn Off MS Security Essentials End of Support Nag Notifications

    Windows XP users: To Remove the annoying nag and restore the green house status for Microsoft Security Essentials, just extract this executable overwriting the one in typically in C:\Program Files\Microsoft Security Client. The easiest way is to rename msseces.exe to msseces.exx before copying this previous version of the notification icon. Cheers from Mike
    Attached Files Attached Files
    Cheers from Mike

  2. Subscribe to our Windows Secrets Newsletter - It's Free!

    Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!

    Excel 2013: The Missing Manual

    + Get this BONUS — free!

    Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!

  3. The Following User Says Thank You to msun For This Useful Post:

    alziz (2014-05-10)

  4. #2
    Star Lounger
    Join Date
    Dec 2010
    Location
    Scotland
    Posts
    74
    Thanks
    0
    Thanked 2 Times in 2 Posts
    Why would you want to do that?

    The flag serves a purpose in different colour states, overriding is ridiculous, you'll think all is good when it may not be.

    Plus of course, ehy would anyone download a file like this from an unknown provider.

  5. #3
    3 Star Lounger bassfisher6522's Avatar
    Join Date
    Jul 2013
    Location
    NC
    Posts
    270
    Thanks
    39
    Thanked 28 Times in 27 Posts
    Quote Originally Posted by mandarin View Post
    Why would you want to do that?

    The flag serves a purpose in different colour states, overriding is ridiculous, you'll think all is good when it may not be.

    Plus of course, ehy would anyone download a file like this from an unknown provider.
    I totally agree....that defeats the purpose of the warning/notifier system it all together.

  6. #4
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    2,820
    Thanks
    19
    Thanked 108 Times in 102 Posts
    Why not uninstall MSE and install a free antivirus program which still supports XP? Like Avast! ?
    BATcher

    If it wasn't for the weather, Great Britain would be a silent nation.

  7. #5
    New Lounger
    Join Date
    Jan 2014
    Posts
    12
    Thanks
    0
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by bassfisher6522 View Post
    I totally agree....that defeats the purpose of the warning/notifier system it all together.
    I can think of one possible reason. I have XP installed in Virtual Mode on my Windows 7 Professional. I have MSE installed in the Virtual Machine also. Since support has ended for XP, I get the "red house" MSE. BUT if you read the MSE home page, it says my virus definitions are up to date and real-time protection is on. The "nag" makes it red (because XP is no longer supported), in spite of the fact that MSE is actually working as an anti-virus (and will be supported until July 2015).

    While I just ignore the red house MSE, it would be nice to be able to opt out of the XP nag (red) and have the MSE be green IF MY DEFINITIONS ARE UP-TO-DATE. As it is now, I have to click the update tab and check. Can no longer rely on the older color coding schemes, since the fact that XP is no longer supported defaults everything to red.

    However, I am not irritated enough to install a download from an unknown provider....

  8. #6
    Super Moderator CLiNT's Avatar
    Join Date
    Dec 2009
    Location
    California & Arizona
    Posts
    5,380
    Thanks
    127
    Thanked 481 Times in 442 Posts
    Uninstall MSE and go with another AV that supports XP.
    MSE is on it's way out as far as XP is concerned & you're going to have to dump it sooner or later.
    Now is just as good a time as any.
    DRIVE IMAGING
    Invest a little time and energy in a well thought out BACKUP regimen and you will have minimal down time, and headache.

    Windows 8.1, 64 bit
    Motherboard: DX58SO2*Chipset: X58 Express/Intel ICH10*BIOS: SOX5820J.86A.0888.2012.0129.2203*Processor: Intel Core i7 CPU X 990
    GPU: Nvidia GTX 580*Memory: Corsair 12 GB, 4x3@1600*PSU: Corsair HX1000*Hard drives: REVO X2 160GB*OCZ VERT X3 120GB*5 mechanical storage drives (12 TB) total.

  9. #7
    New Lounger
    Join Date
    Dec 2009
    Location
    UK
    Posts
    5
    Thanks
    2
    Thanked 1 Time in 1 Post
    The msseces.exe is not from an unknown provider; it is just the notifier from the previous release of MSE i.e. one without the nags and scare tactics. It should work as intended, notifying you if the definition files are out of date or if there is any other issue to be addressed.

    We were promised that MSE support should continue for another year at least, so I do not think a red warning here is appropriate.

    Also, the task scheduler includes popups at regular intervals to remind you that Windows XP support has ended. That should suffice but even those could be deleted if preferred.
    Last edited by msun; 2014-04-13 at 18:35.
    Cheers from Mike

  10. #8
    New Lounger
    Join Date
    Jan 2014
    Posts
    12
    Thanks
    0
    Thanked 2 Times in 2 Posts
    Thanks, Mike

  11. #9
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    2,361
    Thanks
    14
    Thanked 234 Times in 187 Posts
    FWIW

    I personally don't need a reminder that XP is no longer supported. So I don't need or want the big reminder popping up to tell me that. I mounted a drive image using TBI View, copied msseces.exe from the image file, then overwrote the file in Microsoft Security Client.

    Microsoft is still issuing updates for MSE for XP, and will continue for a while. Using the old executable returns to the color scheme with which we are all familiar. I'm not really using XP online other than on my home network, so I'm not really worried. My home network is protected by the hardware firewall in my router, and I can update MSE just by opening it and clicking on "Update".

    YMMV
    Create a new drive image before making system changes, in case you need to start over!

    "Let them that don't want it have memories of not gettin' any." "Gratitude is riches and complaint is poverty and the worst I ever had was wonderful." Brother Dave Gardner "Experience is what you get when you're looking for something else." Sir Thomas Robert Deware. "The problem is not the problem. The problem is your attitude about the problem. Do you understand?" Captain Jack Sparrow.
    Unleash Windows

  12. The Following User Says Thank You to bbearren For This Useful Post:

    msun (2014-04-28)

  13. #10
    New Lounger
    Join Date
    Nov 2009
    Posts
    22
    Thanks
    2
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by msun View Post
    The msseces.exe is not from an unknown provider; it is just the notifier from the previous release of MSE i.e. one without the nags and scare tactics. It should work as intended, notifying you if the definition files are out of date or if there is any other issue to be addressed.

    We were promised that MSE support should continue for another year at least, so I do not think a red warning here is appropriate.

    Also, the task scheduler includes popups at regular intervals to remind you that Windows XP support has ended. That should suffice but even those could be deleted if preferred.
    Mike,

    By "unknown provider", the whingers don't mean Microsoft. They mean YOU!

    I did compare your msseces.exe with the one that I extracted from version 4.4.304.0 of the MSE installer (mseinstall.exe), which is the version that was available just before Microsoft decided to scare the living bejeebers out of (some) people by making that nice comforting green MSE icon turn permanently red.

    I also find that red icon annoying and unhelpful so I have fixed it using a slightly different approach reported on Superuser:
    http://superuser.com/questions/73813...-on-windows-xp
    This approach also means you can keep Automatic Updates on - not sure why that is needed now - because it doesn't matter if MS overwrites or updates msseces.exe because the registry patch tells MSE to use the old version of msseces.exe which is renamed msseces2.exe.

    I suppose if I were Microsoft, I would immediately issue another update that deleted all files matching msseces*.exe, just to foil the workaround. But that would be even too devious for MS, wouldn't it? Maybe I'll rename my msseces2.exe to some random name... just in case.

    A friend of mine also fixed the problem using another variant of your approach: he uninstalled the update that caused the red icon, copied the version 4.4.304.0 of msseces.exe back into the Microsoft Security Client folder and turned off Automatic Updates to stop msseces.exe being "updated". After all, if MS aren't giving any more security updates, why have that function on?

  14. The Following User Says Thank You to Khun Roger For This Useful Post:

    msun (2014-04-28)

  15. #11
    Star Lounger
    Join Date
    Jan 2010
    Location
    Los Angeles, California, USA
    Posts
    95
    Thanks
    0
    Thanked 1 Time in 1 Post
    for all you XP users out there, check the version of Microsoft Security Essentials installed on your machines.
    If the msseces.exe file and their DLL files are version 4.5.216.0 or higher, you need to completely uninstall MSE, reboot and install version 4.4.304.0 from this Filehippo.com page.

    Far better than just copying an EXE file with an older one that has full features for Windows XP and have mis-matched versions of the EXE/DLL files for the Microsoft Security Essentials program. XP users should stay with version 4.4.304.0 of MSE, period!

    And as Khun Roger has said, shut off Automatic Updates to prevent MSE from being upgraded from 4.4.304.0 and also dump Microsoft Update and revert to the plain Windows Update feature on XP.
    Last edited by np-7930; 2014-04-30 at 12:41.

  16. #12
    4 Star Lounger
    Join Date
    Feb 2010
    Location
    Fairfax County, Virginia
    Posts
    435
    Thanks
    8
    Thanked 41 Times in 33 Posts
    Figuring out which button to click on File Hippo took awhile. It is the one in the top right corner of the page, that says
    Download Latest Version (10.61MB)
    Now Microsoft Security Essentials Reports that my PC status is Protected, and everything is green, but the Windows Security Center shield in the notification area is red, because Automatic Updates is turned off.

  17. #13
    New Lounger
    Join Date
    Dec 2009
    Location
    Bloomington, MN, USA
    Posts
    23
    Thanks
    1
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by bassfisher6522 View Post
    I totally agree....that defeats the purpose of the warning/notifier system it all together.
    With RED indicating 'all systems are "Go"', and
    with RED indicating you haven't downloaded virus signatures for a while, and
    with RED indicating your machine is infected,

    I don't really see the value of this 'warning/notifier system'.

  18. The Following User Says Thank You to JNygren For This Useful Post:

    alziz (2014-05-10)

  19. #14
    New Lounger
    Join Date
    Nov 2009
    Posts
    22
    Thanks
    2
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by np-7930 View Post
    for all you XP users out there, check the version of Microsoft Security Essentials installed on your machines.
    If the msseces.exe file and their DLL files are version 4.5.216.0 or higher, you need to completely uninstall MSE, reboot and install version 4.4.304.0 from this Filehippo.com page.

    Far better than just copying an EXE file with an older one that has full features for Windows XP and have mis-matched versions of the EXE/DLL files for the Microsoft Security Essentials program. XP users should stay with version 4.4.304.0 of MSE, period!

    And as Khun Roger has said, shut off Automatic Updates to prevent MSE from being upgraded from 4.4.304.0 and also dump Microsoft Update and revert to the plain Windows Update feature on XP.
    Yes, that's exactly what I ended up doing as I couldn't always get the green icon to appear in the "System Notification Area" on the task bar using the "msseces.exe" method in my previous post.

    So with automatic updates turned off, I disabled the Internet, uninstalled MSE completely (using "Revo Uninstaller"), installed MSE version 4.4.304 and re-enabled the Internet. Now, no more red icon or nag screen from MSE.

    Version 4.4.304 of MSE is also available from several links here, in the section labelled "Download links": http://superuser.com/questions/73813...-on-windows-xp

  20. #15
    Lounger ruosChalet's Avatar
    Join Date
    Dec 2009
    Location
    Seattle WA
    Posts
    28
    Thanks
    26
    Thanked 3 Times in 3 Posts
    I have a much simpler solution. MSE still functions and updates on XP without the notification ICON -- you can separately disable it.
    I simply unchecked the Start-Up item "C:\Program Files\Microsoft Security Client\msseces.exe" -hide -runkey.
    I use CCleaner's Start-up tool, but you can also Run ... msconfig or use AutoRuns.

    Since I have MSE set to "Auto" on all actions, the notification never told me when viruses were quantined anyway. Now, with RED all the time, it's even less useful.
    When I do periodically check up on MSE, I simply use the Program Menu to launch MSE. It still displays the out-of-support warnings, but it also shows that the definitions are up to date AND the last time a scan was run.

    I also have Windows Update set to "notify but don't download." That way, MS won't re-establish the MSE start-up item for mssecs.exe. Even if it happens, I'd just uncheck it again. MSE is still working -- RED flags hidden. Easy! ~RonR

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •