Vmware workstation player ошибка

I have created a new test vm on a different path — C:TempVMWare1Test2.vmx, but still the. Restarted the VM services just in case. I looked also for the 4260062037 in registry but couldn’t find anything. Could it be in some config file?

2017-10-17T16:09:09.931-04:00| vmx| I125: VMMon_GetkHzEstimate: Calculated 2666389 kHz

2017-10-17T16:09:09.931-04:00| vmx| I125: HOSTINFO: Host doesn’t support constant rate TSC.

2017-10-17T16:09:09.931-04:00| vmx| I125: VMMon_RememberkHzEstimate: Calculated -34905259 kHz

2017-10-17T16:09:09.931-04:00| vmx| I125: TSC kHz estimates: vmmon 2666389, remembered 4260062037, osReported 2666000. Using 4260062037 kHz.

2017-10-17T16:09:09.931-04:00| vmx| I125: TSC first measured delta 228

2017-10-17T16:09:09.931-04:00| vmx| I125: TSC min delta 180

2017-10-17T16:09:09.931-04:00| vmx| I125: PTSC: RefClockToPTSC 0 @ 2603896Hz -> 0 @ 4260062037000Hz

2017-10-17T16:09:09.931-04:00| vmx| I125: PTSC: RefClockToPTSC ((x * 3350597356) >> 11) + -406660332475696204

2017-10-17T16:09:09.931-04:00| vmx| I125: PTSC: tscOffset -254531970031748

2017-10-17T16:09:09.931-04:00| vmx| I125: PTSC: using TSC

2017-10-17T16:09:09.931-04:00| vmx| I125: PTSC: hardware TSCs are synchronized.

At first I had an old VMWare Server 2.0 that was working, kind of, uninstalled it and then installed Workstation 14.  W14 didn’t work because of the CPU issue. Uninstalled it and then installed W12, which didn’t worked either. I then uninstalled/reinstalled W 12 a few times and after the last one clean all the registries and files left over using the following manual uninstall link, or a link that looks very close to it.

Cleaning up after an incomplete uninstallation on a Windows host (1308) | VMware KB

02.02.2011
1
10723

Если ваш любимый VMware player выдает ошибку «error while powering on internal error», то пришло время его переустановить. Не забудьте перезагрузить компьютер после установки!

P.S. Если у вас не получилось разобраться с ошибкой «error while powering on internal error«, обращайтесь в наш компьютерный сервис, либо закажите выезд компьютерного мастера.

В этой статье мы расскажем о возможных причинах, по которым не запускается виртуальная машина VMware Workstation. Мы рассмотрим самые распространённые ошибки, а также разберём, почему они возникают и как их исправить.

Ошибка VMware Workstation and Device/Credential Guard are not compatible

При включении VMware Workstation на Windows 10 может возникнуть ошибка со следующим текстом:

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Please visit http://www.vmware.com/go/turnoff_CG_DG/ for more details

Чаще всего эта ошибка возникает из-за того, что включено ПО Device Guard — оно помогает защитить систему от вредоносных файлов. Device Guard позволяет настроить список файлов, которые Windows будет считать безопасными. Если на компьютер попадут файлы, которые не входят в список, система автоматически удалит их. Работе VMware в таких случаях мешает компонент Hyper-V.

Как исправить

Чтобы исправить ошибку, отключите Hyper-V с помощью функционала «Выполнить».

Ошибка Cannot open the disk

Ещё одна распространенная ошибка при запуске виртуальной машины в VMware — Cannot open the disk. Её текст следующий:

An unexpected error was received from the ESX host while powering on VM.

На следующей строке будет указана одна из причин этой ошибки. Разберём, что означает каждая:

1) Failed to lock the file. Это значит, что процесс, который вы используете, не может открыть файл. При этом файл используется другим процессом. Что может привести к ошибке:

• при работе с ВМ вы пытаетесь запустить вторую ВМ, используя тот же VMX-файл,
• вы запустили ВМ с подключенным диском при помощи утилиты vmware-mount,
• вы добавили виртуальный диск к ВМ, которая уже используется.

2) The parent virtual disk has been modified since the child was created. Эта ошибка возникает, если повреждён снимок ВМ.

3) The destination file system does not support large files означает, что на целевом хранилище невозможно открыть файл ВМ того же размера.

4) Could not open/create change tracking file. Эта проблема может возникнуть, если файл filename-ctk.vmdk создавался ранее и не очищался перед созданием новой ВМ. Здесь filename — это название вашего файла.

5) Cannot allocate memory. Тот случай, когда в модуле VMFS не хватает места.

6) The file specified is not a virtual disk возникает в случаях, если повреждён .VMDK-файл дескриптора.

7) Insufficient permission to access file. Такая проблема может возникнуть при использовании хранилищ типа NFS. Она сообщает о том, что экспорт NFS работает неправильно, так как права на чтение и запись файла не даны либо даны некорректно.

Как исправить

Единого решения для этого типа ошибки нет. Чаще всего причина связана с локальными настройками компьютера. Рекомендации по исправлению ошибки описаны в официальной документации.

For many users, VMware is a go-to platform for creating and using Virtual Machine. It allows you to have multiple Operating Systems on a single host computer. But as of late, many users started complaining about VMware Internal Error and want to see some solutions to resolve the problem. That’s why we have accumulated and created some solutions that will help you in fixing the Internal Error in your VMware.

What causes the VMware Workstation Internal Error?

This error is caused when trying to open a VM in the VMware. So, the very obvious cause, in this case, would be the failure of the VMware authorization service. If it fails to start the VM won’t start and as a result, you will see the error question. Another reason that can cause this issue is your antivirus mistaking VM for a virus. This is not rare and sometimes, your antivirus or even the Windows Security system thinks that an app or a game is a virus and stops their working. There is a fix for this that we will talk about later in this article. There are some other reasons such as corrupted VM or VMware and some workaround that we will see hereinafter.

Let us start fixing VMware Internal Error by updating your system. You need to check for updates and install the latest one. If the issue is because of a bug then updating will resolve it. However, if installing the latest build is to no avail then you can try to follow solutions to resolve the issue.

1. Check VMware Authorization Service
2. Repair VMware
3. Check your antivirus
4. Restart VM Services
5. Reinstall VMware

Let us talk about them in detail.

1] Check Vmware Authorization Service

First of all, you need to check the VMware Authorization Service and make sure that it is enabled and has administrator privilege. As for the latter, you don’t need to do anything extra, if you are logged in as administrator then that’s enough. To check the Vmware Authorization Service you need to follow the given steps.

1. Open Services.
2. Look for Vmware Authorization Service, right-click on it and select Properties.
3. Make sure the Startup Type is Automatic and the service is running. If not you have to start the service.

You can also try restarting the service if it’s enabled, this will fix any glitch that the service may have. After doing that, see if the issue persists.

2] Repair VMware

If you are seeing the issue because of a corrupted VMware app then the best way to resolve it is by repairing the application. You can follow the given steps to do the same.

• Open Settings.
• Go to Apps.
• Look for VMware.
  • For Windows 11: Click on the three vertical dots and click Modify/Repair.
  • For Windows 10: Select the app and click Modify/Repair.

Then an installation wizard will pop up. There, you need to click Next and then Repair. Hopefully, this will resolve your issue.

3] Check your antivirus

If you are not dealing with a corrupted app then maybe your antivirus is blocking the VM from running on the system. This is not seldom and is an issue many computer apps are dealing with. So, if you have a third-party application, you can either disable the security or whitelist VMWare. You have to do the same with Windows Defender, either turn it off temporarily or allow VMware through the firewall.

4] Restart VM Services

Sometimes, the issue is because of a glitch, and in that case, restarting all the VM Services is the way to go. So, you need to execute some commands. Therefore, pull out Command Prompt as an administrator from the Start Menu.

Execute the following commands to stop the services.

NET STOP "VMware Authorization Service"

NET STOP "VMware DHCP Service"

NET STOP "VMware NAT Service"

NET STOP "VMware USB Arbitration Service"

taskkill /im vmware-tray.exe /f

taskkill /im vmware-tray.exe /f

Execute the following commands to restart the services

NET START "VMware Authorization Service"

NET START "VMware DHCP Service"

NET START "VMware NAT Service"

NET START "VMware USB Arbitration Service"

START C:Progra~2VMwareVMWARE~1vmware-tray.exe

START C:Progra~2VMwareVMWARE~1vmware-tray.exe

Finally, restart your computer and see if the issue persists.

5] Reinstall VMware

If nothing works then restarting VMware is your last resort. So, just uninstall VMware and then reinstall it to see if the issue persists.

Hopefully, you are able to resolve the VMware issue with the solutions mentioned here.

Related: Not enough physical memory is available to power on the virtual machine with its configured settings

How do I fix VMware not working?

VMware may not work because of many different reasons such as corrupted app clients or corrupted VMX files. But you need to know the exact error message and then search it on our website as all the different error messages mean different things. You should also execute the solutions mentioned here as they are more than capable to resolve almost all the VMware-related issues.

Why does my virtual machine fail to power?

Numerous things could be responsible for not powering up your virtual machine. You should start with the virtualization settings of your host computer. Then, you can verify the ISO file you selected for the virtual machine installation, restart the virtualization services, etc. If nothing happens, you can reset the virtual machine app as well.

Read Next:

• VMware Workstation Pro can’t run on Windows 10 computer
• Fix VMware operating system not found Boot error

What is ‘VMware Internal error while powering ON’ issue in Windows 10/8/7?

If you are facing ‘VMware Internal error while powering ON’ or ‘VMware Internal error’ issue while trying to start virtual machine in VMware in your Windows 10/8/7 computer, then you are in right place for the solution. Here, you will be guided with easy steps/methods to resolve the issue. Let’s starts the discussion.

‘VMware’: VMware is cloud computing and virtualization Technology Company. VMware offers VMware desktop software for Microsoft Windows OS, Linux and MacOS, while its enterprise software hypervisor for servers, VMware ESXi, is bare-metal hypervisor that runs directly on server hardware without requiring underlying operation system.

VMware software allows you to run multiple guest operating systems or virtual machines at same time on single host. It has many versions available like VMware Player – free VMware Workstation which is paid version with additional features. So if you want to run multiple OS in your Windows computer then VMware software can be one of the solution for this.

However, several users reported that they faced ‘VMware Internal error while powering ON’ or ‘VMware Internal error’ issue while they tried to start virtual machine in VMware software on their Windows 10/8/7 computer. This issue is usually caused by VMware Windows Authorization service when fails to start. You should make sure this service is properly running in your computer otherwise, you may face the error forever.

This issue can also be occurred due to required administrator permissions are not given for VMware Authorization service. You can provide administrative permission to VMware software in Windows computer and check if it works toward resolving. Another possible reason behind the issue is the interference of third-party antivirus/firewall program installed in your computer. In such case, you can disable your third-party antivirus/firewall program in order to fix the issue.

VMware Internal error can also be occurred due to corruption in VMware Workstation or VMware Player software itself. You can uninstall and then reinstall VMware WorkStation or VMware Player software in computer in order to fix the issue. This issue can also be occurred due to Game.exe Virus that is blocking VMware’s functions from running virtual machine. You can see this virus in Task Manager if it is running. You can remove this malware from computer in order to fix the issue. Let’s go for the solution.

How to fix VMware Internal error while powering ON in Windows 10/8/7?

Method 1: Run VMware Authorization Service with Administrator permissions

One possible way to fix the issue is to run VMware Authorization Service with Administrator permission.

Step 1: Press ‘Windows + R’ keys on keyboard, type ‘services.msc’ in ‘Run’ window and hit ‘Ok’ button to open ‘Services’ window

Step 2: Find and double-click on ‘VMware Authorization Service’ service to open its ‘Properties’

Step 3: Select ‘Automatic’ option from ‘Startup Type’ dropdown and hit ‘Start’ button under ‘Service Status’ section, and then hit ‘Apply’ and ‘Ok’ button to save the changes. Once done, check if your virtual machine again VMware.

Method 2: Reinstall VMware software with Repair option

Another possible way to fix the issue is to reinstall VMware software in order to remove corruption.

Step 1: Open ‘Control Panel’ in Windows 10 via Windows Search Box and go to ‘Uninstall a Program > Programs & Features’

Step 2: Find and right-click on ‘VMware’ software from the list of programs, and select ‘Repair’ option

Step 3: Follow on-screen instructions to finish repair process and once done, please check if the issue is resolved.

Method 3: Run VMware software with Administrative permission

This issue can also be occurred if VMware software is not running with administrator permission. You can run the VMware software with Administrator in order to fix the issue. To do so, you need to right-click on VMware software icon and select ‘Run as Administrator’, and check if it works for you.

Method 4: Stop and restart all VMware services

Another possible way to fix the issue is to stop all VMware services and then restart them.

Step 1: Type ‘cmd’ in Windows Search Box and press ‘SHIFT + ENTER’ keys on keyboard to open ‘Command Prompt as Administrator’

Step 2: Type the following commands one-by-one and hit ‘Enter’ key after each line to execute

NET STOP “VMware Authorization Service”

NET STOP “VMware DHCP Service”

NET STOP “VMware NAT Service”

NET STOP “VMware USB Arbitration Service”

taskkill /im vmware-tray.exe /f

taskkill /im vmware-tray.exe /f

Step 3: The above commands will stop all VMware relating services in your computer. Once executed, type the following commands one-by-one and hit ‘Enter’ key after each after each line to execute

NET START “VMware Authorization Service”

NET START “VMware DHCP Service”

NET START “VMware NAT Service”

NET START “VMware USB Arbitration Service”

START C:Progra~2VMwareVMWARE~1vmware-tray.exe

START C:Progra~2VMwareVMWARE~1vmware-tray.exe

Step 4: Once executed, try re-launching VMware software and check if the error is resolved.

Fix Windows PC Issues with ‘PC Repair Tool’ [Recommended Solution]

‘PC Repair Tool’ is easy & quick way to find and fix BSOD errors, DLL errors, EXE errors, problems with programs/applications, malware or viruses issues, system files or registry issues, and other system issues with just few clicks.

⇓ Get PC Repair Tool

Conclusion

I hope this post helped you on How to fix VMware Internal error while powering ON in Windows 10/8/7 with several easy steps/methods. You can read & follow our instructions to do so. If the post really helped you, then you can share the post with others to help them. That’s all. For any suggestions or queries, please write on comment box below.