Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image creation on Hyper-V with TPM set to on fails #566

Open
Trinity503 opened this issue May 1, 2023 · 4 comments
Open

Image creation on Hyper-V with TPM set to on fails #566

Trinity503 opened this issue May 1, 2023 · 4 comments

Comments

@Trinity503
Copy link

I tried to create a Windows 11 Image on a virtual machine on a Hyper-V server. After fog captured the Image the original machine ended in a BSOD. Also the machine to which the Image was deployed to. After hours of testing I found out, that it was the TPM-module, that was activated in the virtual machine. I suggest either to add a test for an activated TPM function before the Image is created and a notification for the user, that the deployment will likely fail, or add a note in the documentation, that when using virtual machines to turn TPM off (and use virtual discs with fixed sizes).

Thanks to the fog-team for all of your work!

@Trinity503 Trinity503 changed the title Image creation on Hyper-V with TPM on fails Image creation on Hyper-V with TPM set to on fails May 1, 2023
@darksidemilk
Copy link
Member

That's odd. Maybe this is Windows 11 specific because I enable TPM in my Vmware VM I use for imagine. I do configure our unattend file to clear the TPM at sysprep time so that each Windows install has that clean. That's all in Windows 10 though, I know Windows 11 claims to utilize it more.

@Trinity503
Copy link
Author

Thank you for your answer. Then the BSOD could have an other reason. I will investigate it further. Perhaps I was just lucky that it worked.

@Sebastian-Roth
Copy link
Member

@Trinity503 said:

After fog captured the Image the original machine ended in a BSOD.

Beside the other issue I might add this should never happen. Can you reproduce the problem over and over?

@Sebastian-Roth
Copy link
Member

@Trinity503 Any news on this topic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants