the slow performance could have to do with the 8 GB memory that you have. Are the 8 GB for the VM or this your total memory? What version of AS6 are you using?
A little bit more RAM would be nice but it should not impact stability. Sounds like your issues are randomly. See if you can find a pattern when the crashes happen then we can take a look at it.
Hashmith Rajcoomar reported that Automation Studio 6 (AS6) running on a Windows 10 VM with 8GB RAM and 8-core CPU is slow and occasionally crashes. Stephan questioned whether the 8GB RAM is allocated to the VM or total system memory and asked for the AS6 version; Hashmith confirmed it’s for the VM and mentioned using a demo license, wondering if that could be a factor. Stephan clarified that the demo license doesn’t affect performance or stability, recommended upgrading to AS6 v6.3.4, and suggested that while more RAM would help, it’s unlikely to cause crashes — advising to look for crash patterns. Corne Geerts added troubleshooting tips: check if projects are stored in shared folders or copied locally, and ensure antivirus software isn’t scanning AS6 project folders — providing screenshots of exclusion settings. Jaroslav Kovar later asked Hashmith to update the thread if a solution was found. The issue remains unresolved as of the last post, with suggestions focused on configuration, version, and environment optimization.
From experience using Automation Studio (AS) installed on virtual machine (VM), I run these settings for Windows Host system (7,10,11), 32GB RAM:
-VMs are installed in the primary partition of the host system (C:),
-the folder where the VMs are installed (C:\VM for example) is excluded from firewall, antivirus, … checks
-the host machine always has at least 80 GB of free space of the primary partition C:;
-VMs are configured with 16GB of RAM.
On the guest machine:
-start AS as administrator,
-space on the primary partition of at least 50 GB,
-disable firewall,
-disable folder controls,
-at the end of the day do not pause the VM but turn it off.
Despite these configurations, it happens that the pre-installed performance optimization software, especially in windows 11, slows down the execution of the
virtualization software. In such cases on notebooks with a removable battery I turn off the notebook and unplug the battery for 5-10 minutes.
If the battery is not removable, I avoid putting the notebook to sleep and if the VM is very slow I turn off the notebook by keeping it off for at least 10 minutes by disconnecting the power supply.
Giusto per chiudere il cerchio, ho notato differenze nell’uso della stessa VM con VMWare (player) e VirtualBox; con VMWare workstation pro a uso gratuito (di cui broadcom rilascia aggiornamenti regolarmente) mi pare si siano allineati.