Has anyone come accross a fix for this other than downgrading? We've installed Player 3.1.0 but recieved this error on some machines. Downgrading to 2.5.2 (the last release our organization allowed before 3.1.0) seems to fix this error. We want to upgrade to 3.X but need to find a solution to this problem!
Running Win XP Prof SP3 as host and VM.
this error ???
Come on - which one ?
VMplayer 3 has massive issues with USB-devices - is that what you are talking about ?
Part of those issues can be fixed - but we need input
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
I figured it was self explanatory to the thread I was replying on....
"Error while powering on: internal error"....
The VM doesn't start at all, it resides in a folder on C:; RAM varies between 1GB-4GB depending on the user; VMs are standardized so it's not a VM a user created
can you run other VMs ?
can you run VMs if you disable USB for the VM ?
can you start VMs if you disable the vmusbarbservice on the host ?
what driver does your GM device use ? - is it a USB-device ?
what driver is used for the USB-root-hubs on your host ?
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
Hi!
Ok, so after some troubleshooting and testing I've come up with the following:
1) VM's are all stored locally in a folder on C:
2) Can't run other VMs (even new VMs)
3) Can't run VMs if USB is disabled
4) Can't run VMs if vmusbarbservice is disabled on the hose
5) No USB drivers are being used
6) USB-root-hubs is the Windows built-in
Uninstalling, doing a /clean and then re-installing VMware Player seems to fix the errors.
Errors seem to happen when VMware Player is pushed through SCCM and installed.
SCCM is updating from 2.5.2 to 3.1.0
Could modifying VMware Player's dislay name reg key have anything to do with the errors?
Could modifying VMware Player's dislay name reg key have anything to do with the errors?
please explain that
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
We've modified the display name in the Control Panel to include a tracking number we use for each software release.
As the display name is saved in the registry, the regustry is thus modified.
sorry - which registry key do you talk about ?
the only registry keys used by vmplayer that have a key DisplayName are used by drivers
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
I have identical problem from 3.1.2, I can normaly downgrade to 3.1.1. and continu to use.
today I test 3.1.4 build-385536, 8184 MB, Windows 7 Ultimate, 64-bit 6.1.7601, Service Pack 1
and now I will downgrade again, problem is only time I lose for up and downgrade
I hope someone find why this error ocures
Regards, ve
I have added some logs, compresed with 7zip