The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Base Filtering Engine service won't work

    Discussion in 'Networking and Wireless' started by Schubatis1, Jun 15, 2008.

  1. Schubatis1

    Schubatis1 Notebook Enthusiast

    Reputations:
    0
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    15
    Whenever I try to start the windows firewall or the Internet Connection Sharing services, I get an error saying that they cannot start because they cannot start their dependencies. I've been looking into this and it appears to be an error with a service called Base Filtering Engine.

    Whenever I try to start the Base Filtering Engine service, I get the following error:

    " Windows could not start the Base Filtering Engine service on local computer.

    Error 15100: The resource loader file failed to find the MUI file."

    I have this service configured to automatically start up when Windows boots up. I'm running Windows Vista Home Premium on a Dell XPS M1530. One post I read led me to believe that security software can cause this issue. In case that is so, I have the latest version of McAfee. How can I solve this problem?
     
  2. nizzy1115

    nizzy1115 Notebook Prophet

    Reputations:
    2,557
    Messages:
    6,682
    Likes Received:
    1
    Trophy Points:
    205
    I don't have any experience with McAfee, but it might be that it is not allowing it to be run. Most firewalls ask or require you to have the windows firewall disabled so they do not conflict one another. Remember, 2 host based firewalls are worse than 1 and same goes for 2 host based antivirus programs.

    If i were to do anything in the trouble shooting it would be to remove McAfee and see if this solves the problem.