Closed Gelip closed 6 months ago
You do understand that in order for me to reproduce your issue, I will (at the very least) need both:
Basically: I cannot read your mind, and I also do not have remote access to the contents of your hard drive.
So, assuming you want me to reproduce this so that I can fix it (and also assuming there is something to fix in EfiGuard here), I'm going to need a lot more information than this.
BeepXP driver > http://www.waldbauer.com/tmp/dl.php?download=beepxp64 Install instruction:
1) Disable Windows' own BEEP.SYS driver
sc config Beep start= demand
2) Right click onto the beepxp.inf file and choose "Install." The driver will now be installed into the system. If there are no errors on installation, it will silently proceed.
3) Reboot your machine so that the driver gets loaded on startup.
To test, go to CMD and run command: echo Ctrl+G Enter or use test.exe
Not only does the driver you linked work fine on my Windows 7 installation, you don't even need EfiGuard or test signing enabled to load this driver at all since it has a valid SHA256 signature (as stated in the README...).
My only guess is that you are missing the SHA256 signing updates KB4474419 and KB4490628 for Windows 7. You should have these installed anyway as they have been required for Windows 7 updates since 2019.
If for some reason you must use an unpatched Windows 7, you need to configure EfiGuard's loader to disable DSE at boot time instead of disabling it at runtime. This is required for this driver as it is configured as system start, meaning the driver has already failed to load by the time you are disabling DSE.
Closing this as this is not a bug in EfiGuard.
Operating system
Windows 7 SP1 build 17514
Issue description
Patched files successfully but the unsigned driver BeepXP does not work: Cannot open Beep driver: 2
P.S. I use another PatchGuard (no_pg_ds_v3) fixed by me for UEFI and working: https://forum.exetools.com/showpost.php?p=130940&postcount=54
Steps to reproduce
I try both method - loader and driver. The application EfiDSEFix sees hook.
Logs
Attachments
No response