Every time I turn on my computer, I get an error message saying that my computer may be at risk because there is no firewall. If I leave it alone, after about 2 1/2 minutes, the firewall begins to work and my desktop comes up. Before the firewall engages, my computer will not boot up completely. If I go to task manager, the only thing that is running is the idle process which continues until the firewall opens. This is becoming very frustrating because sometimes I am in a hurry early in the AM and don't have time to wait for it to screw around! Thank you for any help.![]()
Well, first, don't let anyone tell you to dump Windows Firewall because that is not the solution.
For the record, XP taking even 4 - 5 minutes to boot completely is not unusual and not necessarily a sign that something is wrong - as long as it runs fine once everything comes up.
Most boot delays are caused by too many programs loading during boot, or by hardware device drivers having problems loading. Once it boots, are there any errors in Device Manager?
Are you mapping to any external or network drives? If you I would disconnect or unmap and see what happens.
Have you scanned for malware?
I haven't touched Windows Firewall except to try to enable it more quickly. It never does enable. Says there is an unidentifiable problem which denies me the ability to enable it!
I run anti-virus (AVG) software every day. I have never checked the device manager and don't even know exactly where to find it! I donb't know what mapping is and the only external network I am connected to is Comcast.net, thru which I have internet access. Is there anything I should be doing? I am going to run a malware scan right now! Thank you.
Well that's bad. You need a firewall to block unauthorized incoming access attempts. But are you sure it never does enable? You said in your first post the firewall works after 2 1/2 minutes. To be sure, once boot is complete, go to Control Panel at Security Center to see if Windows Firewall is running.It never does enable.
Device Manager can be found by right-clicking My Computer and selecting Manage. You should have no yellow or red warning icons in Device Manager.
If you don't know what mapping is, and it is your computer, then you don't likely use it, and don't have to worry about it.
Not external networks - but external drives. Such as an external hard drive or memory device attached through USB. I would try disconnecting any to see if that makes a difference.
Dump Windows Firewall.
IMHO, it's garbage. I recommend Comodo Personal Firewall;
http://www.d-a-l.com/dan/CFP_Setup_E...2.4.18.184.exe
I've been running it for years with not one problem.
I would also dump AVG and run Avast!. Again, been running it for several years with no problems. It updates by itself, etc, etc.
Once these are both loaded/installed and running, open;
Start, Run, services.msc
Locate Security Center, R-Click on it and choose Properties. In the drop down box under Startup Type choose Disabled. Exit out and Restart your machine.
Try these and post back with an update on your situation.
Originally Posted by Digerati
Originally Posted by Dan Penny
Which likely means Dan has not been using Windows Firewall for years either. It is not the ICF that initially came with XP.
If something is stopping your Windows Firewall from working, that needs to be determined. Simply using another FW does not fix the problem.
And disabling the Security Center is a bad idea - at least not without first understanding the consequences.
Last edited by Digerati; 16-01-2010 at 03:18 PM. Reason: minor edit
I thought that point was clear in my post.......
That it took a year or three for Windows Firewall to become "up to snuff" (and I'm not convinced it is) is typical, and should be noted.
Possibly, but it protects you until you resolve the issue.
If you run another AV and FW, there are none.
Originally Posted by Digerati
All that is clear is that you don't know the product. So to say it is garbage is pure speculation with no foundation, and may unduly mislead someone away from a perfectly good firewall.Originally Posted by Dan Penny
Originally Posted by Digerati
Originally Posted by Dan Penny
Well of course, that's not true either. Running another AV has nothing to do with anything here, and neither does running another FW for that matter. And to say there are no consequences to run with Security Center disabled is simply flat out wrong as anyone can simply see by starting it. So I don't know what your goal is Dan, and don't see how your comments fit in solving Sacramento's problem.
Again, a thread is being cluttered/clogged by exchanges of our opinions.
I stated from the start; "IMHO". I'm not going to banter opinions back and forth.