Hi,
Looks like your VM's logging settings are misconfigured.
From your snippet:
E:\Virtual Machines\vmware.log: rename of E:\Virtual Machines\vmware-0.log
Normally a log is written local to the VM so if your VM is "Windows 10" then all of the VM's files are in the "Windows 10" folder - including the log files!
The above line would then have looked like:
E:\Virtual Machines\Windows 10\vmware.log: rename of E:\Virtual Machines\Windows 10\vmware-0.log
IOW, I don't think it is the scoreboard -whatever that is- new feature.
edit: refinement of my conclusion: It might actually be the scoreboard feature that stops the VM, but it is triggered by a misconfiguration, not the feature itself. The scoreboard files on my VM's are also local to the VM folder, not in a general location.
--
Wil
