<?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>topic Re: VT-x/EPT is not supported on this platform in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VT-x-EPT-is-not-supported-on-this-platform/m-p/2967560#M181213</link>
    <description>&lt;P&gt;I was able to "fix" this issue by disabling VBS in the boot image.&amp;nbsp; The steps to do this appear to have originated with a VMware KB article that has since been updated to remove them.&amp;nbsp; Fortunately(?), The Internet Is Forever™.&amp;nbsp; &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@677206E94727C39F3BB2721E5A55F2C1/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;One article that persists the steps is &lt;A href="https://superuser.com/questions/1124753/what-are-these-vmware-instructions-actually-doing-disabling-device-guard-and-r" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;And I also learned that Microsoft has actually built a workaround into Windows for Hyper-V via the 'Set-VMSecurity' command.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anybody know if it's possible to set a similar policy opt out for VMware Workstation or VMware VMs?&amp;nbsp; (I doubt it.)&lt;/P&gt;</description>
    <pubDate>Tue, 09 May 2023 15:00:54 GMT</pubDate>
    <dc:creator>gediam</dc:creator>
    <dc:date>2023-05-09T15:00:54Z</dc:date>
    <item>
      <title>VT-x/EPT is not supported on this platform</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VT-x-EPT-is-not-supported-on-this-platform/m-p/2967396#M181190</link>
      <description>&lt;PRE&gt;Virtualized Intel VT-x/EPT is not supported on this platform.&lt;BR /&gt;Continue without virtualized Intel VT-x/EPT?&lt;/PRE&gt;&lt;P&gt;I am encountering the above on a Microsoft Surface Pro 9 running Windows 11 Pro 22H2 / 22621.1635 while trying to run a VM with nested virtualization (specifically, to run Docker Desktop on Ubuntu).&lt;/P&gt;&lt;P&gt;The tablet's processor - an i7-1255U - absolutely supports VT-x.&lt;/P&gt;&lt;P&gt;This issue has been posted - and answered - here many times over. I am aware of &lt;A href="https://kb.vmware.com/s/article/2146361" target="_blank"&gt;https://kb.vmware.com/s/article/2146361&lt;/A&gt; and other articles like &lt;A href="https://www.makeuseof.com/windows-11-disable-vbs/" target="_blank"&gt;https://www.makeuseof.com/windows-11-disable-vbs/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;And... I am also confident that this is actually a Microsoft issue. I have opened a support case with them, but I'm not holding my breath for a solution.&amp;nbsp; &lt;STRONG&gt;Nested virtualization works under Ubuntu&lt;/STRONG&gt; (unfortunately, running Windows in a VM won't work for my use case, or I'd be all over it.)&lt;/P&gt;&lt;P&gt;So I'm posting here.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;I have followed all of the steps outlined in the given articles &lt;U&gt;and still VBS continues to run&lt;/U&gt; &lt;/STRONG&gt;&lt;/EM&gt;and VMware Workstation continues to report that VT-x is not supported.&lt;EM&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;How can I kill VBS?!&lt;/P&gt;&lt;P&gt;Thanks in advance!!!&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 19:54:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/VT-x-EPT-is-not-supported-on-this-platform/m-p/2967396#M181190</guid>
      <dc:creator>gediam</dc:creator>
      <dc:date>2023-05-08T19:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: VT-x/EPT is not supported on this platform</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VT-x-EPT-is-not-supported-on-this-platform/m-p/2967560#M181213</link>
      <description>&lt;P&gt;I was able to "fix" this issue by disabling VBS in the boot image.&amp;nbsp; The steps to do this appear to have originated with a VMware KB article that has since been updated to remove them.&amp;nbsp; Fortunately(?), The Internet Is Forever™.&amp;nbsp; &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@677206E94727C39F3BB2721E5A55F2C1/emoticons/1f609.png" alt=":winking_face:" title=":winking_face:" /&gt;&lt;/P&gt;&lt;P&gt;One article that persists the steps is &lt;A href="https://superuser.com/questions/1124753/what-are-these-vmware-instructions-actually-doing-disabling-device-guard-and-r" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;And I also learned that Microsoft has actually built a workaround into Windows for Hyper-V via the 'Set-VMSecurity' command.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anybody know if it's possible to set a similar policy opt out for VMware Workstation or VMware VMs?&amp;nbsp; (I doubt it.)&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2023 15:00:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/VT-x-EPT-is-not-supported-on-this-platform/m-p/2967560#M181213</guid>
      <dc:creator>gediam</dc:creator>
      <dc:date>2023-05-09T15:00:54Z</dc:date>
    </item>
  </channel>
</rss>

