<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>RU5 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>RU5 Tracker</description>
    <pubDate>Fri, 17 Nov 2023 17:50:33 GMT</pubDate>
    <dc:date>2023-11-17T17:50:33Z</dc:date>
    <item>
      <title>Re: Can't update to Workstation 17.0.1</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-update-to-Workstation-17-0-1/m-p/2965847#M40398</link>
      <description>&lt;P&gt;I notice in the release notes this has been fixed going forward:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;&lt;STRONG&gt;Cannot close Workstation Pro while upgrading Workstation Pro&lt;/STRONG&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;If you try to upgrade Workstation Pro from version 17.0.0 or 17.0.1, you cannot close the Workstation application after the upgrade installer appears. The issue is expected to appear when you upgrade Workstation Pro from version 17.0.0 or 17.0.1 to 17.0.2.&lt;/P&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;This issue is resolved now in this release and is not expected to appear when you upgrade Workstation Pro from version 17.0.2 to a higher version.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 27 Apr 2023 08:06:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-update-to-Workstation-17-0-1/m-p/2965847#M40398</guid>
      <dc:creator>RU5</dc:creator>
      <dc:date>2023-04-27T08:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: Can't update to Workstation 17.0.1</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-update-to-Workstation-17-0-1/m-p/2952398#M40132</link>
      <description>&lt;P&gt;By bottom right, do you mean the system tray? I don't have the system tray icon enabled for Vmware.&lt;/P&gt;&lt;P&gt;Killing in task manager is all well and good if you have no VMs running, but I did when the updater first popped up, so what then? There's a serious risk of data loss then.&lt;/P&gt;&lt;P&gt;For the record, I too killed it via Task Manager in the end. But not very user friendly.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 12:28:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-update-to-Workstation-17-0-1/m-p/2952398#M40132</guid>
      <dc:creator>RU5</dc:creator>
      <dc:date>2023-02-03T12:28:55Z</dc:date>
    </item>
    <item>
      <title>Can't update to Workstation 17.0.1</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-update-to-Workstation-17-0-1/m-p/2952387#M40130</link>
      <description>&lt;P&gt;How do I resolve this chicken/egg situation? I launch the updater from the Help menu, the installer wants me to close vmware.exe but all controls on the original window are locked out.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2023-02-03 113131.png" style="width: 999px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/99760iDF745164B1A77516/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2023-02-03 113131.png" alt="Screenshot 2023-02-03 113131.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 11:34:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-update-to-Workstation-17-0-1/m-p/2952387#M40130</guid>
      <dc:creator>RU5</dc:creator>
      <dc:date>2023-02-03T11:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 KB5019959 crashes into BSOD</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Windows-10-KB5019959-crashes-into-BSOD/m-p/2942980#M179068</link>
      <description>&lt;P&gt;Hello all. I would just like to add that although this issue is supposed to be fixed in 17.0, it is not for me (Windows 11 host, 2xWindows 10 guests, one 64-bit and the other 32-bit). Just putting this out there as others may also be (un)affected after purchasing an upgrade to VMWare.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2022 17:27:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Windows-10-KB5019959-crashes-into-BSOD/m-p/2942980#M179068</guid>
      <dc:creator>RU5</dc:creator>
      <dc:date>2022-12-08T17:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unsupported Processor error running Windows 10 guest OS on vmware workstation pro 16.2.4</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Unsupported-Processor-error-running-Windows-10-guest-OS-on/m-p/2942978#M179067</link>
      <description>&lt;P&gt;I've just upgraded to Windows 11 and hit this problem. Purchased an upgrade to 17.0 and it still does not resolve it.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2022 17:21:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Unsupported-Processor-error-running-Windows-10-guest-OS-on/m-p/2942978#M179067</guid>
      <dc:creator>RU5</dc:creator>
      <dc:date>2022-12-08T17:21:45Z</dc:date>
    </item>
  </channel>
</rss>

