Open karl-police opened 3 days ago
@microsoft/windowsaudio can you please take a look
Audio processing objects load in audiodg.exe which runs as a child process of the audiosrv service in session 0, and therefore need to be signed. If you're installing on a test system, test-signing is okay. If you're installing a production system they need to be production-signed; Microsoft will production-sign your driver for you if you submit it to Hardware Dev Center.
Test instructions here: https://github.com/microsoft/Windows-driver-samples/tree/main/audio/sysvad
Submission to Hardware Dev Center instructions here: https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-submission-create
More on signing drivers: https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/signing-a-driver
I heard that if you want to create a driver e.g.
test.sys
and use it without restriction, it needs to be signed. I know that one can build driver and run in test mode, but that doesn't speak for me as a non-profit thing at all.But what about APO? These COM things or whatever it is. Do custom APO also have to be signed or not?
Can someone please tell me?