In the command prompt, commands like ipconfig, ping, tracert, etc cannot work unless the full path was typed in , eg, c:\windows\system32\ipconfig. It Seems like the path was not correct
On typing in path in the command prompt i got the following:
Computer A with CPF
PATH=%systemroot%\system32;%systemroot%;%systemroot%\System32\Wbem;C:\Program Files\QuickTime\QTSystem;C:\Program Files\Comodo\VEngine\
Computer B without CPF
Thus on computer A, i right click on my computer Icon on the desktop-> choose properties → advanced → environment variables → under system variables → path → i changed all %systemroot% to C:\windows and rebooted the machine.
After that, windows was able to detect and list the firewall in windows security centre. I tried with computer B as well and had the same problem and needed to change the settings before windows can detect the firewall.
Is this a bug? Hope that this bug can be fixed in future versions .
Excellent post, Cavey! I will be trying this tonight.
In my case, the firewall reported by Windows Security Center is currently NAV 2006’s “worm control” firewall (yes, I am using Norton Antivirus 2006 on my machine). That has always bothered me, but I figured NAV was so intrusive that somehow it had taken control.
Windows Security Centre recognises security components through WMI, not through the path variable. It may help, but it’s not the primary means that Windows uses to communicate and acknowledge these components.