tweebs
Active member
- Local time
- 3:54 PM
- Posts
- 1
- OS
- Windows 10 LTSC 1809
I think I already know my answer but maybe someone can confirm my suspicions...
My work laptop was provided with Windows 10 Enterprise but has been extremely locked down to the point where I can't even use it for development work. I've been getting around this by installing a 2nd M.2 SSD and installing Win11 Pro and using as needed. Occasionally, I'll need to access the VPN, or some other enterprise resource, so I was using Hyper-V to boot the physical Win10 bare metal drive using hypervisor. It worked fairly well, except I couldn't use Hyper-V Enhanced Session as my domain login didn't allow Remote Users, and every time I booted I had to enter the Bitlocker key.
Unfortunately, they have upgraded the Windows 10 image and now use TPM to secure the system. When I boot into Win10 in Hyper-V, Windows notifies me the security is broken and won't let me login to Enterprise functions until I shut-down and boot directly into Windows.
Turning on TPM in Hyper-V configuration results in not booting at all.
There doesn't seem to be a way to pass-thru TPM2.0 from the host to the virtualized boot, nor is there a way to 'export' a certificate from the host to use in the virtual machine (since it doesn't exist).
I've heard QMEU will use a 'real' TPM instead of a virtual certificate, but I haven't explored that option.
My work laptop was provided with Windows 10 Enterprise but has been extremely locked down to the point where I can't even use it for development work. I've been getting around this by installing a 2nd M.2 SSD and installing Win11 Pro and using as needed. Occasionally, I'll need to access the VPN, or some other enterprise resource, so I was using Hyper-V to boot the physical Win10 bare metal drive using hypervisor. It worked fairly well, except I couldn't use Hyper-V Enhanced Session as my domain login didn't allow Remote Users, and every time I booted I had to enter the Bitlocker key.
Unfortunately, they have upgraded the Windows 10 image and now use TPM to secure the system. When I boot into Win10 in Hyper-V, Windows notifies me the security is broken and won't let me login to Enterprise functions until I shut-down and boot directly into Windows.
Turning on TPM in Hyper-V configuration results in not booting at all.
There doesn't seem to be a way to pass-thru TPM2.0 from the host to the virtualized boot, nor is there a way to 'export' a certificate from the host to use in the virtual machine (since it doesn't exist).
I've heard QMEU will use a 'real' TPM instead of a virtual certificate, but I haven't explored that option.
My Computer
System One
-
- OS
- Windows 10 LTSC 1809
