"The network firewall is not functioning properly" [Merged Threads]

[Guest]

[Searinox]

Sadly it's true. The new version may fix the issue from occurring, however if you already have broken CFP Miniports there is NO WAY to uninstall them. PERIOD.

I wish Comodo would look into this because it's quite a puzzling issue. No matter how much of Comodo you clean away there is simply no way to remove the miniports, and I mean NO WAY. I've tried 2 driver cleaners, one registry cleaner, a manual and dangerous search-and-delete operation of anything in the registry referring to the miniports... nothing. Nothing will remove them.

[gibran]

Sadly it's true. The new version may fix the issue from occurring, however if you already have broken CFP Miniports there is NO WAY to uninstall them. PERIOD.

I wish Comodo would look into this because it's quite a puzzling issue. No matter how much of Comodo you clean away there is simply no way to remove the miniports, and I mean NO WAY. I've tried 2 driver cleaners, one registry cleaner, a manual and dangerous search-and-delete operation of anything in the registry referring to the miniports... nothing. Nothing will remove them.

If you didn't attempt to use devmgr_show_nonpresent_devices please try to manually remove them and report back any results.

How to uninstall hidden devices, drivers, and services
Works with Windows 2000, XP, Server 2003, all SP levels.

Ever have those drivers or devices that just won't go away even though you're sure you've uninstalled them? Or, say you replace your old 100Mbps network card with a faster Gbps adapter. But, you can't re-assign it the same IP address because your system insists there is still an adapter installed with that same IP address and you forgot to remove the driver before removing the old card (which is now in your little brother's pc)?

To get rid of that unwanted driver, device, or service:
1) Open the "Start" menu and choose "Run..."
2) Type in "cmd" (without the quotes) and click "ok".
3) At the cmd prompt, type in "set devmgr_show_nonpresent_devices=1" (without the quotes) and press enter. (Note that nothing seems to happen--this is ok. We are actually setting an environment variable which is going to help us to see hidden devices)
4) On the next cmd prompt line, type in "devmgmt.msc" (without the quotes) and press enter. This will launch the Windows Device Manager Console.
5) In the Device Manager Console, from the "View" menu, select "Show Hidden Devices".

Now, as you expand the different drivers and devices in device manager you will see not only the items that Windows currently detects as installed on your pc (these are the usual items displayed), but you will also see drivers, devices, and services which have been loaded in the past but were not uninstalled or are not currently started. You can find your offending device, right-click, and choose "uninstall" to remove it from the system completely.

Be careful though; you should note that non-loaded devices, drivers, and services are "grayed" out, but that doesn't necessarily mean that you should delete all of them. Only remove items you know you don't need. And, be careful that you don't change too many devices or you might need to re-activate your Windows installation.

Last thing, if you accidentally exit the Device Manager Console you will need to start over again at the cmd prompt. To close the cmd prompt window, type "exit" (without the quotes).

[Searinox]

That did not help. Upon clicking "uninstall" the devices list does a refresh and the devices are STILL there. There is no way to get rid of the miniports without system restore.

[gibran]

That did not help. Upon clicking "uninstall" the devices list does a refresh and the devices are STILL there. There is no way to get rid of the miniports without system restore.

Searinox thanks for posting the results.

As things stands out system restore is the only safe method.

A more risky way would be to manually remove those devices using regedit but if I remember correctly
those devices reference more than one registry branches in

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Anyway I cannot gurantee this method will success.
I guess only people who don't have any useful restore point could possibly want to give it a try before reinstalling windows.

[EricJH]

The broken Miniport can be uninstalled after uninstalling Comodo. In my case I didn't restart the computer after uninstalling. I am on Vista SP1.

[Searinox]

A SOLUTION FOUND AT LONG LAST

HKLM\SYSTEM\CurrentControlSet\Enum\Root\NT_INSPECTMP is the culprit! the entries 0001, 0002 etc. each refer to Miniport components listed in Device Manager. The PERMISSIONS for these keys are severly screwed up. There is no owner, no one is allowed to access them, and so on. Ownership must be taken and then inheritable permissions systematically removed from every key which is TEDIOUS work. Then the permissions can finally be changed and once the user is given write privilleges, the keys can finally be deleted, along with the whole NT_INSPECTMP. After that, a mere refresh of Device Manager will show that the Miniports are indeed gone! If you intend to uninstall only the faulty devices, their names can be found in the FriendlyName DWORD value right inside the 000# key. Just identify them by name and proceed with the treatment...

The privilege system for those keys can probably be reset using Subinacl, I have not tried. Even with my WORKING devices, if I go to NT_INSPECTMP/000#/Properties I am told immediately upon merely clicking the key that the data cannot be displayed, access is denied. Under Permissions, these keys have no displayable owner etc.. Their existance impedes the deletion of any whole 000# key, which represents a Miniport device. This is what causes CFP Miniport uninstalls to fail silently, as NOT EVEN THE SYSTEM HAS PRIVILEGES TO MODIFY THOSE KEYS.

I hope this proves of use to all those who have shared my frustrations. And I believe that if you are providing users with a tool to do a clean uninstall of CFP it too should perform a reset on the permissions of said registry keys before attempting to delete them.

[3xist]

Bump.

[sprac]

Hi there!

I have installed Comodo for the first time (3.0.25.378 64-bit). I get the "network firewall is not functioning properly" message, and cannot make it disappear (=> cannot get the product to work at all).

- Diagnostics shows no errors
- Defense+ doesn't seem to do anything either (have disabled it now anyway)
- Vista 64bit
- "Comodo Firewall Driver" shows up for the relevant LAN controller

As a side effect, bcveserv.exe (part of Bestcrypt Volume Encryption, which otherwise seems to continue to work fine) crashes every boot with a memory protection fault. I've been using BCVE for years without any problems, and now this.

[WTH]

Hi there!

I have installed Comodo for the first time (3.0.25.378 64-bit). I get the "network firewall is not functioning properly" message, and cannot make it disappear (=> cannot get the product to work at all).

Is your disk type dynamic or basic? On WinXP the firewall won't work under dynamic disks. This might be the same problem as under vista. Sounds strange, but it can be reproduced. A fully working comodo firewall will stop working when converting the disk type from basic to dynamic.

[sprac]

No dynamic disks - but encrypted using Bestcrypt Volume Encryption ( www.jetico.com ).

[3xist]

No dynamic disks - but encrypted using Bestcrypt Volume Encryption ( www.jetico.com ).

That might be the problem then.

Uninstall that prog and see if it solves anything.

[sprac]

If I "uninstall the program" nothing will work, as my disks will stay encrypted.

I will not decrypt all my drives just to get a firewall working. I have been using Bestcrypt for years and never experienced ANY application incompatibility (even tools like drive imagers and defrag work).

[3xist]

Then I guess we can only wait for a fix.

Josh

[msdomino]

i am yet another victim of the no matter how clean my system is or how i install cfp3 it will not work on dynamic discs under winxp and winmce.

2 questions, does anyone know approximately when we can expect an update or fix?  has anyone figured out which version we need to install if we want to stick with cfp (a link would be really handy for this)??

btw, this way this problem is being handled does seem to remind me of the hal.dll error.  love the products when they work.  this really bites that i just got my fresh install finished and can't put my chosen firewall or antivirus on it

 

[panic]

2 questions, does anyone know approximately when we can expect an update or fix?  has anyone figured out which version we need to install if we want to stick with cfp (a link would be really handy for this)??

These two questions are best directed to the development team, as they are probably beyond the scope of a user forum (the former - definitely, the latter - probably).

Go to http://support.comodo.com and register to lodge a suport ticket. You weill need to re-register, as your forum credentials do nto carry through to the official Support Centre.

Hope this helps,
Ewen :-)

[Tags:]