-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Description
I am currently experimenting with the MS Sample code for Virtualization-Based Security (VBS) and utilizing Azure's Trusted Signing service for signing purposes. Previously, the signing process was successful, and the sample code executed without any issues. However, I have recently encountered a problem where the signing process is generating the signature correctly, but upon attempting to run the code, the following error message is displayed:
======================================================================================
Diagnostic message: D:\TPMs_codes\VBSTest\Enclave_Sample-master\Enclave Host\enclapp.cpp(107)\VbsEnclaveApp.exe!00007FF7372D78B2: (caller: 00007FF7372DA384) ReturnHr(1) tid(ba94) 80070241 Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
[Run(LoadEnclaveImageW(Enclave, L"vbsenclave.dll"))]
If you developer-signed the DLL, make sure that you have enabled test signing.
======================================================================================
Could anyone provide guidance or suggest potential solutions to resolve this issue?
Note:
- I am doing this on a x64 machine in Win10 and Win11 both, and have met all the requirements listed here:
https://learn.microsoft.com/en-us/windows/win32/trusted-execution/vbs-enclaves#development-prerequisites
This issue occurred on both Win10 and Win11. - I followed the guide below:
https://learn.microsoft.com/en-us/windows/win32/trusted-execution/vbs-enclaves-dev-guide