Vista_x64: VMware Workstation 6.5.2 fails to run with CIS 3.10.101801.529 again

[Guest]

[ledge]

Hi,

Vmware Workstation 6.5.2 fails to start any virtual machine once I upgraded to CIS 3.10.101801.529.
The error received is:

"Could not get vmx86 driver version: The handle is invalid.
You have an incorrect version of driver "vmx86.sys". Try reinstalling VMware Workstation.
Failed to initialize monitor device."

Followed by a message box saying:

"Cannot find a valid peer process to connect to."

Installing CIS 3.8.64739.471 fixes the problem.

    * CPU: 64 bit

    * Windows Vista Ultimate 64-bit, sp1

    * Actively-running security and utility applications:
        CIS 3.10.101801.529 and Eset Nod32 Antivirus 3.0

    * Specific symptoms of the bug, and steps you can take to reproduce it (step by step).:
        Install CIS 3.10.101801.529, Start Vmware workstation.  Start any virtual machine.  Error message indicated above appears.

    * Specific steps you have taken to try to resolve it:
        1.  Install CIS 3.8.64739.471
        2.  Run VMWare Workstation 6.5.2 "As Administrator"

    * Brief description of your Defense+ and  Firewall+ mode (Custom, Train with safe) plus mention if you modified any setting in ADVANCED section of D+ and F+ (Optional if you post a  Comodo Firewall Pro Configuration Report):
        Did not modify any Defense+ or Firewall option.  Firewall is in "Safe Mode".  Defense+ is in "Clean PC mode".  No Antivirus in CIS.

    * If you pc reboots or you have a BSOD post in  BSODs: Please add your minidump files here:
        N/A.

    * Report if you are using an Administrator account Or a Limited User account. Vista users please Report if you have UAC Disabled or Enabled (Optional if you post a  Comodo Firewall Pro Configuration Report):  
        Using Administrator account.  UAC Enabled.

Running VMWare Workstation "As Administrator" is a workaround, but a proper fix to CIS needs to be made.

I hope this bug can be fixed as I need to have VMware Workstation functional with a firewall.
I also hope Comodo can get this fixed as it's an awesome program!

Cheers,
Ledge.

Edit: added clarification that Antivirus is not running in CIS.
Edit2: Updated CIS version to 3.9.95478.509 and VMWare Workstation version to 6.5.2.  Same problem!
Edit3: Updated CIS version to 3.10.101801.529.  Same problem still present.

[LaserWraith]

I have the latest version of VMware Workstation, and CIS is installed on a VM and it runs smoothly...

But I have 32bit, not 64.

[John Buchanan]

I think the problem has to do with a conflict with NOD 32.  Try disabling that and try again.

[ledge]

Hi,

Thanks for your quick reply.
I've been running VMware Workstation 6.5.1 and Eset Nod32 Antivirus together with CIS 3.5 and earlier without any problems.  Even running them both with CIS 3.8.64739.471, Vmware Workstation is fine.  It's just CIS 3.8.65951.477 that causes the problem.  However, I will reinstall CIS 3.8.65951.477 tomorrow and test the theory.

Cheers,
Ledge.

[LaserWraith]

It is never good to run two real-time anti-virus/malware scanners at the same time.  Even if you don't see any major things going wrong, there still probably are at least some small negative effects.  It's like a bomb waiting to go off.

So, the best advice I can give is to turn off the real-time scanner of either NOD or CIS.

[ledge]

Hi,

Thanks all for your posts.

To clarify, I have never installed the antivirus component of CIS.  I always only install the Firewall and Defense+ components.  I leave the antivirus part to Eset Nod32 Antivirus.  I have updated my original post to reflect this.

However, that being said, I uninstalled my existing CIS, reinstalled CIS 3.8.65951.477 (Firewall and Defense+ only) and disabled Nod32.  VMware Workstation still reports the same error.

Any further advice greatly appreciated 

Cheers,
Ledge.

[LaserWraith]

I'm a bit blank right now, but try this:

Try using the instructions here to turn off the FW/D+ and while it is off try again with VMware.

Remember to return back to whatever settings was enabled when you are done.

[ledge]

Thanks again for your suggestion.
VMware Workstation still gives the same error even when the Firewall and Defense+ is disabled as indicated in your post.
However, VMware Workstation works when CIS 3.8.65951.477 is uninstalled.

Cheers,
Ledge.

[John Buchanan]

Do any of the Devs have a suggestion on this?

[LaserWraith]

Like John said, it could be that CIS and NOD are "fighting".

I wonder if everything would work if you uninstall/disable NOD.

[AcoSys]

Hello Guys,

i have exact the same problem. Ich update my CIS today to the new version and my virtual machine in VMWorkstation don't work striting this moment with the same error message like ledge. The uninstall of CIS fixed the problem, but this ist not a solution.

System:
* Vista 64bit Business
* only CIS, without AntiVirus installes (only Firewall + Defense+)
* no AntiVirus program

Where I can get older versions of CIS?

cheers,
Aco

[ledge]

Hi,

Thank you for the suggestions.
I uninstalled Eset Nod32 Antivirus and installed CIS 3.8.65951.477 (Firewall and Defense+ only) and VMware Workstation still generates the abovementioned error message.

Any further assistance is welcome!

Cheers,
Ledge.

[olddane]

I have had the same problem some time ago. Just start VMware elevated with "run as administrator".

cheers
René

[ledge]

Thanks olddane for the suggestion.
Running VMware as Administrator does indeed work. 
However, with all due respect, CIS should be fixed by the Comodo development team so such a workaround isn't required.

Is it possible for the "root cause" of this problem to be fixed in CIS?

Cheers,
Ledge.

[olddane]

Hi

Well I don´t think it has anything to do with  CIS. I was running an earlier version when I encountered the problem after updating vmware to 6.51.

Since the problem appeared, vistax64, avast, CIS and many other programs have been updated on my computer. Updates of almost any program for security reasons are frequent now a days.

One day (about  2 weeks ago) I discovered, that it was no longer necessary to "run as administrator". The problem had mysteriously disappeared by it self !

I don´t know if it has do with program updates, or the fact that, I once a while use a systemcleaner (IObit advanced..) to remove all clutter and sanitize the registry.

Maybe you will get lucky too

/René

[Tags:]