![]() However if I included the term 64bit in the VM name then the VM icon changed to indicate 64bit. I installed my first 64bit VM the other day (Win7), and I noted at the time that when selecting the guest type from the dropdown there was no specific choice of 32bit vs 64bit. Why go through all this trouble? Having one more shield running seems like a good idea.Actually Perry, I have to say the same thing, and it puzzled me too until I realized that it meant nothing. So, you might want to try enabling Anti-Rootkit Shield, disabling Anti-Exploit Shield, rebooting, then running your VMs. Disabling Anti-Exploit Shield will still result in the VMs failing until a reboot is done. For example, in this case, running the VMs with Anti-Exploit Shield enabled will cause the VMs to fail. One thing I've learned (for me, anyway) is that once Avast has loaded the shields and an app (like a browser or email client) that would utilize these shields has been run, then changing the shield settings in the Avast UI doesn't have any effect on the VMs until a reboot. Perhaps in my previous attempts, I tried disabling the Anti-Exploit Shield after having already running the VMs with it enabled. I don't know what I did differently, but just now I tried leaving the Anti-Rootkit Shield enabled, but disabled the nested Anti-Exploit Shield. ![]() I have reported my findings to Avast, but have not heard anything back yet. I tried leaving the Anti-Rootkit shield enabled, but disabling the nested Anti-Exploit Shield, and my VMs still crashed. I believe the Anti-Rootkit Shield is the source of my issues, and not the nested Anti-Exploit Shield. Having done this, I can now run my VMs without errors. This will also disable the nested Enable Anti-Exploit Shield. Scroll down, and uncheck Enable Anti-Rootkit Shield.In the Avast user interface, click the 3-bar Menu in the upper-right corner, and select Settings.After several iterations, I was able to isolate a single shield that is causing my VMs to crash. In the course of reporting this issue to Avast, they asked me to narrow down the options I need to disable in order to be able to use my VirtualBox VMs. I'll report back if I get a working solution from Avast. They have a beta available now which attempts to fix this problem, but it did not fix it for me. I've reported this problem directly to Avast, but haven't heard anything back. This helps me a little bit, as I least I can read my email while I have a VM open. I did find that in my case, if I disable all the Core Shields *except* the Mail Shield, then I can run my VMs without error. I believe this is because Avast will activate one or more of the shields when I open the email client. If I open my email client *before* disabling the Core Shields, and then disable them, the problem occurs in my VMs. If I disable all the Core Shields before running any app, then I can use the VMs without a problem. So, on my system at least, apparently the Core Shields is the only feature I'm using. I just went through the Protection item in the user interface, and checked the items that are available in the free version: Email Guardian, Firewall, Ransomware Shield, and Network Inspector. I haven't spent any time in customizing Avast (even though I've been using it for years), so all the settings are default. VBoxlogs.zip (106.9 KiB) Downloaded 7 timesįth0 wrote:If you have time and like to help, could you identify all Avast settings that lead to the crash? Log Files: Both are attached to this post. VB Version: 6.1.32 + Expansion pack installed ![]() Is there anything i can do to really solve it once and for all? It also happened again while i was running a Zoom session and one virtual machine running Ubuntu 20.04 LTS. I eventually got back and installed the expansion, but since i thought adding 8GB of RAM + updating my graphicsĭrivers would have solved the problem for good - i'm starting to get frustrated with it. ![]() While installing the expansion for VB it occurred again! :O ![]() (the part above is for anyone who encounters the same situation. Now i was able to install the OSes on the virtual machines and have them running. Initially i thought its a problem with not enough RAM, so i added 8GB to the PC (host) and got it to 16GB RAM.Īfter several attempts of installing the OS on the guest machine i also got the blue screen of deathĪnd realized i need to update my graphics drivers - it looked like it worked! My PC had the resources for it, the error kept popping up and kill the installation processes. I started getting this error when i tried to install any type of OS on either of the virtual machines,Īfter checking that i did allocate the correct amount of RAM and number of CPUs, and that I'm having a recurring "critical error" -> meditation guru problem with my Virtualbox and in need of guidance please. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |