wonderful, the non-MS driver you mentioned above is working! Beeep! Someone suggested above trying beep.sys from WinXP x64, but you overlooked something (I did too):
support for Beep was dropped in Windows Vista and Windows XP 64-Bit Edition.
Hear that? "Windows XP 64-Bit". This has nothing to do with driver signing, although driver signing is mandatory on x64 systems, which is very annoying, on Win10 x32 I just copied the MS driver from WinXP to Win10 and it was starting all right, but on Win10 the driver MUST be signed, despite all the nonsense mentioned on the internet concerning the "testsigning" and "nointegritychecks" bcdedit params. Let me clarify this once and for all. If the "driver signature enforcement" is not disabled in the advanced menu of the Windows Boot Manager:
a) you can NOT install a driver unless a catalog (cat) file is present. The "this driver package does not contain a catalog file, proceed?" confirmation prompt is NOT presented AT ALL, instead installation fails silently (pnputil, infdefaultinstall). setupapi.dev.log contains weird entry:
Driver package does not contain a catalog file, and Code Integrity is in Test Signing mode.
Driver package failed signature validation. Error = 0xE000022F
The third-party INF does not contain digital signature information.
So? If test signing is on, why not prompt? Go ask Microsoft. Because if "driver signature enforcement" is disabled during boot, the confirmation dialog is presented, and it will say
Driver package does not contain a catalog file, and user does not want to install driver package.
or "wants to install" depending on what the user decides to do
b) You cannot start an UNSIGNED driver. What's ridiculous about this, you CAN start an IMPROPERLY signed driver. Like my certificate I use for driver signing is kind of invalid, despite being granted any and all "keyUsage"-s and "extendedKeyUsage"-s:
keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment, keyAgreement, keyCertSign, cRLSign
extendedKeyUsage = anyExtendedKeyUsage, 22.214.171.124.4.1.3126.96.36.199, serverAuth, clientAuth, codeSigning, emailProtection, timeStamping, OCSPSigning, msCTLSign, msEFS, 188.8.131.52.184.108.40.206.2, 220.127.116.11.4.1.318.104.22.168, msCodeInd, msCodeCom, msEFS, 22.214.171.124.4.1.3126.96.36.199.1, 188.8.131.52.4.1.3184.108.40.206, 220.127.116.11.4.1.318.104.22.168, 22.214.171.124.4.1.3126.96.36.199, 188.8.131.52.4.1.3184.108.40.206, 220.127.116.11.4.1.318.104.22.168, 22.214.171.124.4.1.3126.96.36.199, 188.8.131.52.4.1.3184.108.40.206, 220.127.116.11.4.1.318.104.22.168, 22.214.171.124.4.1.3126.96.36.199, 188.8.131.52.4.1.3184.108.40.206, 220.127.116.11.4.1.318.104.22.168, 22.214.171.124.4.1.311.20.1, 126.96.36.199.4.1.311.21.19, 188.8.131.52.4.1.3184.108.40.206, 220.127.116.11.4.1.311.21.5, 18.104.22.168.4.1.311.21.6, 22.214.171.124.4.1.3126.96.36.199, 188.8.131.52.4.1.3184.108.40.206, 220.127.116.11.18.104.22.168.5, 22.214.171.124.126.96.36.199.6, 188.8.131.52.184.108.40.206.7
something about "basicConstraints" Windows doesn't like, probably this:
basicConstraints = CA:true
so the "digital signature" dialog (explorer, right click driver file, "signatures" tab) whines about it:
Die Erweiterung für die Basiseinschränkung eines Zertifikats wurde nicht eingehalten.
Dieses Zertifikat ist ungültig, da eine der Zertifizierungsstellen im Zertifizierungspfad nicht berechtigt ist, Zertifikate auszustellen oder es kann nicht als Endeinheitszertifikat verwendet werden.
but the driver is still started. Microsoft and security. But as I said, the MS driver not beeping is not due to this, but simply because there is no MS beep.sys x64-bit that is actually beeping. Plus, what about this function?
Definitely not beeping either, in fact, I get no sound either through the sound card or through the speaker. neither with "Beep", nor with "MessageBeep". MS states:
Beep was rewritten to pass the beep to the default sound device for the session. This is normally the sound card
"Normally the sound card" all right, but what about their own Windows PE? WinPE does not come with an audio driver, so beeping through the sound card will not work, unless you rip out the drivers from Windows 10 Enterprise and integrate them into WinPE or something. Does not matter anyway, 'cause, as I said, the Beep function is NOT beeping through the sound card on my Windows 10 Enterprise either, although the sound card is working there.