{"id":183196,"date":"2016-10-29T23:12:24","date_gmt":"2016-10-29T21:12:24","guid":{"rendered":"http:\/\/www.borncity.com\/blog\/?p=183196"},"modified":"2022-06-26T18:30:27","modified_gmt":"2022-06-26T16:30:27","slug":"wartungs-update-fr-vmware-workstation-12-5-1-und-player","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2016\/10\/29\/wartungs-update-fr-vmware-workstation-12-5-1-und-player\/","title":{"rendered":"Wartungs-Update f&uuml;r VMware Workstation 12.5.1 und Player"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2013\/09\/VMware_thumb.jpg\" align=\"left\"\/>Im September hat VMware die bereits im August angek\u00fcndigten neuen Versionen der VMware Workstation 12.5 und des VMware Player 12.5 freigegeben (siehe <a href=\"https:\/\/borncity.com\/blog\/2016\/09\/19\/vmware-workstation-12-5-und-vmware-player-freigegeben\/\">VMware-Support f\u00fcr Windows 10 Anniversary Update<\/a>). Nun gibt es bereits ein Update dieser Versionen von VMware Workstation und Player.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/e80db7f4d82745feb7afb2b38d35088b\" width=\"1\" height=\"1\"\/>Es handelt sich um ein Wartungs-Update, welches einige Fehler beseitigt sowie eine Sicherheits-L\u00fccke schlie\u00dft. Problem ist die beschissene Webseite von VMware, wo man bei <a href=\"https:\/\/web.archive.org\/web\/20170924212803\/https:\/\/www.vmware.com\/products\/workstation.html\" target=\"_blank\" rel=\"noopener\">VMware Workstation<\/a> und Player zwar viel Blah, Blah serviert bekommt. Aber man muss schon sehr genau suchen, um auf die Release-Notes zu sto\u00dfen. Wenn man gezielt nach der Versionsnummer 12.5.1 sucht, werden einem die Release-Note zu den Versions-Updates angezeigt. <\/p>\n<blockquote>\n<p>Ich selbst setze die \u00fcberfrachtete VMware Workstation 12.5.1 nicht ein und werde auch nicht kostenpflichtig upgraden, da ich nicht absehen kann, ob die Entwicklung weiter l\u00e4uft. Da ich VMware Workstation 10.0.7 verwende, habe ich auch auf die Installation des VMware Player 12.5 verzichtet. Daher bekomme ich solche Updates nicht mehr mit. Dankenswerter weise haben die Kollegen von deskmodder.de <a href=\"https:\/\/www.deskmodder.de\/blog\/2016\/10\/29\/vmware-workstation-12-5-1-player-und-pro-mit-einem-update\/\" target=\"_blank\" rel=\"noopener\">einen Lesertipp bekommen<\/a>. <\/p>\n<\/blockquote>\n<p>Die Release-Notes zu VMware Workstation 12 Pro Version 12.5.1 vom 27. Oktober 2016 <a href=\"https:\/\/web.archive.org\/web\/20170623224532\/http:\/\/pubs.vmware.com:80\/Release_Notes\/en\/workstation\/12pro\/workstation-1251-release-notes.html\" target=\"_blank\" rel=\"noopener\">finden sich hier<\/a>. <\/p>\n<h4><font style=\"font-weight: bold\">Known Issues<\/font><\/h4>\n<ul><a name=\"1750948\"><\/a> <\/p>\n<li><strong>Using multiple monitors does not work on Ubuntu 16.10 virtual machines<\/strong>\n<p>When using multiple monitors with an Ubuntu 16.10 virtual machine, you may see a black screen or all the displays on one monitor. This issue can occur when you cycle through three or more monitors. The issue can occur when you are using VMware Tools or open-vm-tools.  <\/p>\n<p><strong>Workaround<\/strong>: Reboot the virtul machine and cycle through the monitors again.  <\/p>\n<p><a name=\"1750615\"><\/a><\/p>\n<\/li>\n<li><strong>Virtual machines running Linux kernel version 4.7 or above may crash or hang on hosts with Intel CPUs<\/strong>\n<p>Virtual Machines running Linux kernel version 4.7 or above may crash during installation or during power-on with a crash in the intel_powerclamp driver. This issue has been reported with Ubuntu 16.10, but it is a generic Linux kernel issue.  <\/p>\n<p><strong>Workaround<\/strong>: VMware is working with the OS vendors to have them fix their respective kernels. Until a fix is available, you can blacklist the intel_powerclamp driver so that the buggy code doesn't get loaded.  <\/p>\n<p>To blacklist the driver:  <\/p>\n<p>Add the kernel command-line option <code>modprobe.blacklist=intel_powerclamp<\/code> to the guest OS's default grub configuration or add it directly at the grub menu during boot.  <\/p>\n<p><a name=\"1748315\"><\/a><\/p>\n<\/li>\n<li><strong>VMware Tools service is not started in Ubuntu 16.10 guest<\/strong>\n<p>After installing VMware Tools in an Ubuntu 16.10 guest, the VMware Tools service is not started. As a result, functionality provided by the VMware Tools service, for example, shared folders, is not available.  <\/p>\n<p><strong>Workaround<\/strong>: In the guest operating system, manually start the VMware Tools service.  <\/p>\n<p>Log in to the guest machine and enter the following command: <code>sudo systemctl start vmware-tools.service<\/code>.  <\/p>\n<p><a name=\"1725785\"><\/a><\/p>\n<\/li>\n<li><strong>Some driver files are not deleted after uninstalling VMware Workstation from a Windows host operating system<\/strong>\n<p>After VMware Workstation is uninstalled, the following driver-related files remain on the Windows host operating system:<br \/>In <code>C:\\Windows\\System32\\drivers<\/code>:<br \/><code>hcmon.sys<\/code><br \/><code>vmci.sys<\/code><br \/><code>vmx86.sys<\/code><br \/><code>vmkbd.sys<\/code> in case Enhanced Keyboard Driver was installed.  <\/p>\n<p><strong>Workaround<\/strong>: Navigate to <code>C:\\Windows\\System32\\drivers<\/code> and delete <code>hcmon.sys<\/code>, <code>vmci.sys<\/code>, <code>vmx86.sys<\/code>, and <code>vmkbd.sys<\/code>.<\/p>\n<\/li>\n<\/ul>\n<h4><font style=\"font-weight: bold\">Resolved Issues<\/font><\/h4>\n<ul><a name=\"1751513\"><\/a> <\/p>\n<li><strong>Bridged networking not working<\/strong>\n<p>If you delete VMnet8 and VMnet1 in the Virtual Network Editor, then bridged networking is no longer available after the host is restarted. This issue could appear after upgrading to Workstation 12.5.  <\/p>\n<p>This issue is resolved.  <\/p>\n<p><a name=\"1751511\"><\/a><\/p>\n<\/li>\n<li><strong>vmrun commands fail on RHEL 6.8 and CentOS 6.8 hosts<\/strong>\n<p>Trying to execute vmrun commands on a RHEL 6.8 or CentOS 6.8 host machine, results in errors.  <\/p>\n<p>This issue is resolved.  <\/p>\n<p><a name=\"1751512\"><\/a><\/p>\n<\/li>\n<li><strong>hostd server does not start on RHEL 6.8 host<\/strong>\n<p>If you install Workstation 12.5 on a RHEL 6.8 host machine, vmware-hostd cannot start. As a result, shared virtual machines are not available.  <\/p>\n<p>This issue is resolved.  <\/p>\n<p><a name=\"1751076\"><\/a><\/p>\n<\/li>\n<li><strong>A virtual machine using EFI firmware sometimes crashes when it is powering on<\/strong>\n<p>When powering on a virtual machine that uses EFI firmware instead of BIOS, the virtual machine sometimes crashes witha <code>0xc0000374 (Heap Corruption)<\/code>exception.  <\/p>\n<p>This issue is resolved.  <\/p>\n<p><a name=\"1725785_b\"><\/a><\/p>\n<\/li>\n<li><strong>Some driver files are not deleted after uninstalling VMware Workstation from a Windows host operating system<\/strong>\n<p>After VMware Workstation is uninstalled, the following driver-related files remain on the Windows host operating system:<br \/>In <code>C:\\Program Files\\Common Files\\VMware\\Drivers\\vmci\\device<\/code>:<br \/><code>vmciver.dll<\/code>  <\/p>\n<p>This issue is resolved<\/p>\n<\/li>\n<\/ul>\n<p>Die Release-Notes f\u00fcr den VMware Player 12 Version 12.5.1 vom 27. Oktober 2016 <a href=\"https:\/\/web.archive.org\/web\/20170623224532\/http:\/\/pubs.vmware.com:80\/Release_Notes\/en\/workstation\/12pro\/workstation-1251-release-notes.html\" target=\"_blank\" rel=\"noopener\">finden sich hier<\/a>.  <\/p>\n<ul>\n<li><strong>Virtual machines running Linux kernel version 4.7 or above may crash or hang on hosts with Intel CPUs<\/strong>\n<p>Virtual Machines running Linux kernel version 4.7 or above may crash during installation or during power-on with a crash in the intel_powerclamp driver. This issue has been reported with Ubuntu 16.10, but it is a generic Linux kernel issue.  <\/p>\n<p><strong>Workaround<\/strong>: VMware is working with the OS vendors to have them fix their respective kernels. Until a fix is available, you can blacklist the intel_powerclamp driver so that the buggy code doesn't get loaded.  <\/p>\n<p>To blacklist the driver:  <\/p>\n<p>Add the kernel command-line option <code>modprobe.blacklist=intel_powerclamp<\/code> to the guest OS's default grub configuration or add it directly at the grub menu during boot.  <\/p>\n<p><a name=\"1725785\"><\/a><\/p>\n<\/li>\n<li><strong>Some driver files are not deleted after uninstalling VMware Workstation Player from a Windows host operating system<\/strong>\n<p>After VMware Workstation Player is uninstalled, the following driver-related files remain on the Windows host operating system:<br \/>In <code>C:\\Windows\\System32\\drivers<\/code>:<br \/><code>hcmon.sys<\/code><br \/><code>vmci.sys<\/code><br \/><code>vmx86.sys<\/code><br \/><code>vmkbd.sys<\/code> in case Enhanced Keyboard Driver was installed.  <\/p>\n<p><strong>Workaround<\/strong>: Navigate to <code>C:\\Windows\\System32\\drivers<\/code> and delete <code>hcmon.sys<\/code>, <code>vmci.sys<\/code>, <code>vmx86.sys<\/code>, and <code>vmkbd.sys<\/code>.<\/p>\n<\/li>\n<\/ul>\n<h4>Resolved Issues<\/h4>\n<ul><a name=\"1751509\"><\/a> <\/p>\n<li><strong>VMware VIX API files installed to the incorrect location<\/strong>\n<p>When you install the VMware VIX API files, some files install to <code>C:\\<\/code>, even when you select the default install path of <code>C:\\Program Files (x86)\\VMware\\VMware VIX<\/code>.  <\/p>\n<p>This issue is resolved.  <\/p>\n<p><a name=\"1751511\"><\/a><\/p>\n<\/li>\n<li><strong>vmrun commands fail on RHEL 6.8 and CentOS 6.8 hosts<\/strong>\n<p>Trying to execute vmrun commands on a RHEL 6.8 or CentOS 6.8 host machine, results in errors.  <\/p>\n<p>This issue is resolved.  <\/p>\n<p><a name=\"1725785_b\"><\/a><\/p>\n<\/li>\n<li><strong>Some driver files are not deleted after uninstalling VMware Workstation Player from a Windows host operating system<\/strong>\n<p>After VMware Workstation Player is uninstalled, the following driver-related files remain on the Windows host operating system:<br \/>In <code>C:\\Program Files\\Common Files\\VMware\\Drivers\\vmci\\device<\/code>:<br \/><code>vmciver.dll<\/code>  <\/p>\n<p>This issue is resolved.<\/p>\n<\/li>\n<\/ul>\n<p>Wer die Produkte lizenziert hat, kann die Updates auf dieser VMware-Webseite f\u00fcr <a href=\"https:\/\/web.archive.org\/web\/20171004145135\/https:\/\/www.vmware.com\/products\/workstation-for-linux.html\" target=\"_blank\" rel=\"noopener\">Linux<\/a> und <a href=\"https:\/\/web.archive.org\/web\/20170924212803\/https:\/\/www.vmware.com\/products\/workstation.html\" target=\"_blank\" rel=\"noopener\">Windows<\/a> herunterladen.  <\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/><a href=\"https:\/\/web.archive.org\/web\/20210613235557\/https:\/\/borncity.com\/blog\/2016\/02\/05\/vmware-fusion-und-workstation-vor-dem-aus\/\">VMware Fusion und Workstation vor dem Aus?<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2016\/09\/19\/vmware-workstation-12-5-und-vmware-player-freigegeben\/\">VMware Workstation 12.5 und VMware Player freigegeben<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2016\/03\/12\/vmware-legt-fokus-auf-profitable-produktlinien\/\">VMware legt Fokus auf profitable Produktlinien<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Im September hat VMware die bereits im August angek\u00fcndigten neuen Versionen der VMware Workstation 12.5 und des VMware Player 12.5 freigegeben (siehe VMware-Support f\u00fcr Windows 10 Anniversary Update). Nun gibt es bereits ein Update dieser Versionen von VMware Workstation und &hellip; <a href=\"https:\/\/borncity.com\/blog\/2016\/10\/29\/wartungs-update-fr-vmware-workstation-12-5-1-und-player\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[4299,5570,5569],"class_list":["post-183196","post","type-post","status-publish","format-standard","hentry","category-virtualisierung","tag-virtualisierung","tag-vmware-player-12-5-1","tag-vmware-workstation-12-5-1"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/183196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=183196"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/183196\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=183196"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=183196"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=183196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}