OneCare Firewall failed while executing the following method: GetPolicy. Error Code: 0x8E5EFBBE RRS feed

  • Question


    Event Type: Error
    Event Source: MSFWSVC
    Event Category: (2)
    Event ID: 1080
    Date:  7/14/2008
    Time:  8:12:54 PM
    User:  N/A
    Computer: BANANA2
    OneCare Firewall failed while executing the following method: GetPolicy. Error Code: 0x8E5EFBBE, Error Message: Unknown Error.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    MS and google searchs come up with zilch.  Just started happening today after my live one care updated itself. I rebooted then this started showing and my Live one care is red, won't turn on (hangs when I attempt to...)

    Tuesday, July 15, 2008 3:26 AM


All replies

  • I assume that you are seeing these errors in the Event Viewer. I would generally not be concerned with that, though in relationship with a red status, it may be of concern.

    When you open OneCare, is it advising that the firewall is off? And clicking turn on hangs? Hangs for how long? Does it return an error at that point?

    I would recommend the Firewall repair tool - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2468376&SiteID=2

    If that doesn't resolve it, since it began with the update, run the cleanup tool - 


    And then reinstall OneCare from http://onecare.live.com, activating with your subscription LiveID.

    Or, contact support.

    How to reach support (FAQ) - http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2421771&SiteID=2



    Tuesday, July 15, 2008 1:21 PM
  • Thank you for your response.  Although your response doesn't answer my question 'what is error xxxxx' it does give good advice to resolve.


    I tracked it down myself to a corrupted file on the hard drive.  Ultimately, a reinstall fixed the issue.  It sure would be nice to have an actually error message in english to go with the code!  I thought that in 2002-3 MS pushed for all developers internally to document these... oh well.


    Jim Shimota

    Thanks Steve. 

    Wednesday, July 16, 2008 5:23 AM
  • Glad to read that you managed to resolve it with the reinstall. What file was actually found to be corrupt? That might be good information to have....

    Sorry that I couldn't specifically provide the answer for what the error meant. Many of these cryptic errors are pretty useless to us, the users. I would hope that the errors are documented, but this information isn't widely available. For example, I have a list of the Installation errors and their general meanings based on the first 4 digits, but the secondary part of the error is a mystery to me in most cases.



    Wednesday, July 16, 2008 2:30 PM
  • I realized afterwards it might have been useful info for this thread but alas, no, I didn't make note.  I had started up a diags disk with a generic Vista OS then run the disk check routine (A tool called Activeboot - very useful!).  In the disk check a number of files where doc'd as 'corrupt', and were then reindex, etc. (basically a chkdsk /r).  On reboot, the system status changed from the red 'can't start' to non-existent.  ie; the icon for OneCare was nolonger there.  I uninstalled and reinstalled and poof. I was back up and running - all my previous settings still intact.




    Wednesday, July 16, 2008 6:17 PM
  • Thanks for that information and once again, glad it is working fine now.



    Wednesday, July 16, 2008 6:23 PM