<?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: Adding existing vmdk to encrypted (VM) not possible. in Fusion 2023 Tech Preview Discussions</title>
    <link>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989844#M530</link>
    <description>&lt;P&gt;I've also been able to edit the vmx directly, both to remove and add virtual disks. &amp;nbsp;Not for the fainthearted, but it works without all the hoops (which surprises me that the UX is more restrictive).&lt;/P&gt;</description>
    <pubDate>Thu, 05 Oct 2023 15:37:03 GMT</pubDate>
    <dc:creator>ColoradoMarmot</dc:creator>
    <dc:date>2023-10-05T15:37:03Z</dc:date>
    <item>
      <title>Adding existing vmdk to encrypted (VM) not possible.</title>
      <link>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989721#M527</link>
      <description>&lt;P&gt;When installing Windows 11 in Fusion, i choose to just "ecnrypt vm files" instead of virtual disk..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I then got corrupted windows after complete shut down and could not repair, (see my other post).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I then thought, in order to post log to Microsoft community, and i was doing troubleshooting in WinPE, i thought i could just :&lt;/P&gt;&lt;P&gt;- add a known good working .vmdk from backup, and boot to that.&lt;/P&gt;&lt;P&gt;- add the corrupted .vmdk as 2nd, so i can access and copy log..&lt;/P&gt;&lt;P&gt;so i removed 1st hd, added known good backup vmdk, then re-added the corrupted one as a 2nd&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However when i tried to "Apply" I got "can't add encrypted hard drive" so effectively, i was stuck..&lt;/P&gt;&lt;P&gt;Which is false.... The vm files were only encrypted, not the vmdk disk... so why can't i add it?&amp;nbsp; The known-good one is also not encypted. as i only ever prefer encrypting vm fils, not disk.. So i know that's not the issue.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 02:57:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989721#M527</guid>
      <dc:creator>TECH198</dc:creator>
      <dc:date>2023-10-05T02:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: Adding existing vmdk to encrypted (VM) not possible.</title>
      <link>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989730#M529</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#565656"&gt;I just tried this out. &lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;FONT color="#565656"&gt;Start with a working Windows 11 ARM VM - otherwise you might have to mess around with the EFI boot strings and that isn't going to be pretty.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="inherit" color="#000000"&gt;Make a backup copy of the working &lt;/FONT&gt;&lt;FONT color="#000000"&gt;&lt;SPAN&gt;Windows&lt;/SPAN&gt;&lt;/FONT&gt;&lt;FONT face="inherit" color="#000000"&gt;&amp;nbsp;11 VM by copying it elsewhere.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;On this working VM:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Remove the TPM device (unless you're using BitLocker, you won't have a problem with removing and re-adding a TPM device).&lt;/LI&gt;&lt;LI&gt;Decrypt the VM.&lt;/LI&gt;&lt;LI&gt;Now go to the VM's settings and click "Add Device...". From there, select "Existing virtual disk".&amp;nbsp;&amp;nbsp;Navigate to the old VM and select its virtual disk, and specify that you want to make a copy. Leave the original alone.&lt;/LI&gt;&lt;LI&gt;Re-encrypt the VM&lt;/LI&gt;&lt;LI&gt;Add the TPM device back into the configuration&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;On your next boot, Windows may ask you to reset your PIN if you've configured Windows Hello. That's an artifact of losing the TPM device, (I had to reset my PIN - thank heavens that Microsoft Authenticator on my iPhone tied to my Microsoft account made that super easy.)&lt;/P&gt;&lt;P&gt;Upon login, my other VM's hard drive is now seen as the E drive.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It does seem a bit strange that the VM won't allow you to add a disk that doesn't have any component of it encrypted. Perhaps that's a remnant of the older fully encrypted disks worked. Paradoxically, Fusion allowed me to remove that second virtual disk without decrypting the VM. Go figure.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 04:53:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989730#M529</guid>
      <dc:creator>Technogeezer</dc:creator>
      <dc:date>2023-10-05T04:53:51Z</dc:date>
    </item>
    <item>
      <title>Re: Adding existing vmdk to encrypted (VM) not possible.</title>
      <link>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989844#M530</link>
      <description>&lt;P&gt;I've also been able to edit the vmx directly, both to remove and add virtual disks. &amp;nbsp;Not for the fainthearted, but it works without all the hoops (which surprises me that the UX is more restrictive).&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 15:37:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/Adding-existing-vmdk-to-encrypted-VM-not-possible/m-p/2989844#M530</guid>
      <dc:creator>ColoradoMarmot</dc:creator>
      <dc:date>2023-10-05T15:37:03Z</dc:date>
    </item>
  </channel>
</rss>

