I now have the same problem with 17.4.3014 (Last update May 18, 2017) and VMWare Workstation 12. Previous to this last update VMWare was usable (and I mean right up until because all I did was close down the VMs which we working normally and do the AVG requested reboot) After the requested reboot, VMWare is unusable. The only thing that happened was the AVG update and reboot. My system has 12 cores and 32G of memory. The VMs are running off SSDs. There is no reason for this other than an AVG problem.
Same problem happens in AVG latest paid version (ver 17).
In addition, I found that all TCP connection to the VMWare guest was blocked after AVG had updated itself to ver. 17 no matter the requests came from the VMWare host or the VMWare guest locally. I cannot confirm that if it's caused by new AVG version but it's the only software updated in the past 2 month. Disable AVG or uninstall AVG does not solved the problem. The VMWare guest image is dead.
My machine is for commercial used. It extremely affects my business.
Have you tried turning off Hardware-assisted Virtualization under settings>troubleshooting?
I just worked on a Windows 7 laptop with XP mode. The user uses XP mode for a legacy app on a regular basis. All of a sudden, in the last week or so, the virtual machine (XP mode) will not launch. When I dug into the event log, it had error 108: "fatal processor error". I searched that and found a thread about an Avast setting that killed virtual processes.
After disabling this feature in AVG and rebooting (did not work before rebooting), the XP mode worked like a charm. Now that Avast and AVG are on the same team, I guess they are developing the same bugs.
Any response from AVG on this glitch?
Yo Young - Thank you for this thought - it is a good one. Before seeing it, I've gone down the path of cleaning out to reinstall AVG in the host (Win7) machine and run into a new & different problem (below).
Sreedevi - Apology accepted and I'm grateful for your interest. However, the two statements in your reply both miss the point and each would be avoided with a more careful reading of my original post.
1. VMware 12 Player worked (note past tense) fine with AVG enabled in both Win7 host and XP client until the reboot after enabling AVG. VMware 12 Player is not (present tense) working fine since then…and I am mystified why you ask me this, since it is the problem I was reporting to you in my post.
2. You ask for a screenshot - and I wonder what am I to take a screenshot of? I did not mention an error message - the problem is crippled performance of VMware player in running the VM so that it functions, but…each…painful…menu…step…takes many minutes. It is so slow that when a highlighted button changes colour, I can see the new colour filling the button from left to right over a few seconds.
Since the problem arises from AVG's behaviour in the host machine I've tried to clean AVG out of the Win7 host for a fresh install. However (Sreedevi note - the new problem is about to be outlined) both AVG uninstall (run through Win7) and AVGremover have failed. After their use:
1. Win7 reports 'AVG Protection' remains in program list (but no longer 'AVG')
2. AVG uninstall fails (Error 0xe0010002)
3. AVG remover fails to detect an AVG installation and then Win7 reports it to have crashed when it is 'run anyway'
4. AVG remover despite giving the OS the impression it has crashed, reports it has completed
5. Following reboot, there is still AVG software (avguix.exe) starting and reporting errors (0x80000003)
6. Following reboot, two unstoppable AVGui processes remain running - processes which are started in the registry by run entries, but which cannot be removed even by Administrators because Windows security prevents deletion of the values either directly or by changing permissions for the key.
The numbers above correspond to the sequential screenshots I have taken which include all error messages for this new problem, but which I cannot attach because of a third problem - a glitch in AVG's BB software.
Sreedevi, could you please apply your and your team's skills to the first two problems, which I have laid out in detail? I can email you separately the screenshots, but don't want this thread messed up by a side discussion on the behaviour of the BBS. Thanks in anticipation.
NB, in semi-desperation and before taking time to report all this I rang AVG support. After initial language difficulties in which I was unconvinced the man understood the nature of the problem, I was offered a remote login during which he would 'fix all my problems using special software'. For 65GBP.
The thought occurred to me that if someone put software on my PC without asking (and AVG's Zen updates are exactly that)…and that software damaged my PC and then the perpetrator wanted money to recover my machine for me…I would normally call it Ransomware.
Hello Stephen,
Please accept our genuine apology for all the issues you had with AVG program.
We realize the issue with AVG Zen conflicting with VM ware.
Please let us know if VM ware 12 player is working fine when AVG enabled in your system.
It would be easier for us to analyze the issue with the screenshot of the error message if any while running AVG in system.
Thank you.
I first stumbled into this, but have now reproduced it after reinstalling entire system from backup.
System is i7 4712-MQ 16GB running Win7 Pro and WinXP Pro in VMware12 Player. AVG AV Free in both.
1. First (and unbidden) a message from Win7 AV 'AVG is in passive mode - another AV product is running' (no it isn't). Only option is 'Fix now' with no intimation of what this entails. At this point, the VM and AV in it work fine, with WinXP opening to the desktop in <6 secs.
2. This (high performance of VM) remains after pressing the 'Fix Now' but after the obligatory subsequent reboot, the Win7 machine works fine but the VM is crippled, taking 4+mins to boot - ie 10-100x slower, though still functioning. The first time this happened, it was not clear whether AVG in the VM, or a Win Update were the culprits, but this time it is absolutely clear that it is AVG in the main machine has crippled its operation of the VM.
I've lost a day to this problem already and will have to take a couple of hours more reinstalling from the backup again. Perhaps I am throwing good money after bad to have spent more time here in laying out this problem for no-one other than AVG's benefit. I onsole myself with the thought that this will be my last contribution in return for use of a free product - I don't think there's any way back for AVG after this, with the relentless pushing of the unneccessary Zen and the gradual and the intentional obfuscation of the update/upgrade process that has happened recently.
Hi Stephen,
We understand your concern, please Download and run AVG Clear tool: https://share.avg.com/steam/PSP/AVG2017/AVG_Clear.exe . This tool will help with removing antivirus component of AVG 2017 and its traces.
Open tool
User Account control - click "Yes"
Windows safe mode - click "No"
Choose installed version (AVG Free, AVG Internet Security)
Click "Uninstall"
Click "Restart computer"
After that please try reinstalling AVG Anti Virus FREE from : http://www.avg.com/us-en/download
If issue persists, please get back to us and we will assist you further.
Thank you!
Samuel,
Sorry for the inconvenience. It seems that the issue still persists even after you have disabled or uninstalled AVG, it confirms that the issue is not caused by AVG. We request you to contact your VM Ware support for further assistance. Thank you!
Same problem happens in AVG latest paid version (ver 17).
In addition, I found that all TCP connection to the VMWare guest was blocked after AVG had updated itself to ver. 17 no matter the requests came from the VMWare host or the VMWare guest locally. I cannot confirm that if it's caused by new AVG version but it's the only software updated in the past 2 month. Disable AVG or uninstall AVG does not solved the problem. The VMWare guest image is dead.
My machine is for commercial used. It extremely affects my business.
Thank you very much for this, Akash. Summary of where things now stand:
- Problem originally reported is confirmed: AVG cripples VMware Workstation 12 Player so that it is approx 50x slower and an XP VM run in a Win7 host took 11.5min to boot (cf 17secs without AVG) - even with Hardware Assisted Virtualisation (Yo Young's comment) switched off. In addition, all the processor cycles allocated to the VM were consumed, so that the VM reported 100% processor use, even if extra processor power was allocated it through VMware.
- AVG_Clear worked (where AVG Remover did not) to clean out the remains of AVG. I note that your support has offered both Remover and AVG_Clear (the latter with an Avast splashscreen) to do the same job, and surmise this must reflect the unfinished integration of the companies.
- Even after AVG_Clean, CCleaner found 17 registry anomalies referring to AVG, and a manual search found about 20 more. I suggest this means it's not a finished article.
- The conflict may be specific to the combination of AVG AV 64b, Win7 Pro SP1and VMware Workstation 12 or it may well be wider. Removal of AVG a further time restored the speedy functioning of VMware and the VM.
- The competitor Bitdefender, when installed to this (once more working) system had a negligible effect on VMware - an extra 4sec taken to boot the same VM.
- The recent noxious increase in pressure, both overt and covert, to move to paid versions,
- The current availability of two removal tools,
- The recent move to thrust Zen on all users, whether it is wanted or not,
- The release of software updates without regression testing to confirm their compatibility with major third party software such as VMware...
Since I have now lost two working days to this problem, I will be staying away from AVG until others at the bleeding edge report that the problem has gone away. In the interests of balance, and for anyone reading this and yet to form an opinion, I should say I am heartened by the responsiveness and utility of one of the 3 support contacts I received (Thank You again Akash). The other email response was less useful and the phone response was positively alarming.
I now have the same problem with 17.4.3014 (Last update May 18, 2017) and VMWare Workstation 12. Previous to this last update VMWare was usable (and I mean right up until because all I did was close down the VMs which we working normally and do the AVG requested reboot) After the requested reboot, VMWare is unusable. The only thing that happened was the AVG update and reboot. My system has 12 cores and 32G of memory. The VMs are running off SSDs. There is no reason for this other than an AVG problem.
Have you tried turning off Hardware-assisted Virtualization under settings>troubleshooting?
I just worked on a Windows 7 laptop with XP mode. The user uses XP mode for a legacy app on a regular basis. All of a sudden, in the last week or so, the virtual machine (XP mode) will not launch. When I dug into the event log, it had error 108: "fatal processor error". I searched that and found a thread about an Avast setting that killed virtual processes.
After disabling this feature in AVG and rebooting (did not work before rebooting), the XP mode worked like a charm. Now that Avast and AVG are on the same team, I guess they are developing the same bugs.
Any response from AVG on this glitch?