| 4 | | ''Avast is causing issues with Virtualbox versions newer than 7.0.18 r162988 when Guest Additions are installed. Although the Guest Additions themselves, when scanned, don't show up in a report, Avast is injecting itself in the threads created by the VBoxTray.exe process and it causes them to go into an infinite loop. In a 4c/4th VM, you would see 25% usage which means that 1 core is cycling at 100%. Inserting the C:\WINDOWS\system32\VBoxTray.exe under the exception in all shields doesn't help and if a stack trace is performed we can see that aswArPot.sys and aswSnx.sys are there. To confirm that this is the case, uninstalling avast make |
| | 4 | ''Avast is causing issues with Virtualbox versions newer than 7.0.18 r162988 when Guest Additions are installed. Although the Guest Additions themselves, when scanned, don't show up in a report, Avast is injecting itself in the threads created by the VBoxTray.exe process and it causes them to go into an infinite loop. In a 4c/4th VM, you would see 25% usage which means that 1 core is cycling at 100%. Inserting the C:\WINDOWS\system32\VBoxTray.exe under the exception in all shields doesn't help and if a stack trace is performed we can see that aswArPot.sys and aswSnx.sys are there. To confirm that this is the case, uninstalling avast makes the VBoxTray.exe process execute normally with all its threads. There's nothing from the Virtualbox side that could cause any lockup, so this needs to be addressed on the Avast side. Please release a new definitions update in which the Virtualbox Guest Additions are whitelisted so that they won't cause an issue on Windows Guests.'' |
