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

Files patched but unsigned driver not work #121

Closed
Gelip opened this issue May 15, 2024 · 3 comments
Closed

Files patched but unsigned driver not work #121

Gelip opened this issue May 15, 2024 · 3 comments
Labels
bug Something isn't working invalid This doesn't seem right

Comments

@Gelip
Copy link

Gelip commented May 15, 2024

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

SystemBootEnvironmentInformation:
        - BootIdentifier: {453c784e-e38f-11ee-a703-cdd306f600bc}
        - FirmwareType: UEFI
        - BootFlags: 0x0

SystemModuleInformation:
        - Kernel: ntoskrnl.exe (\SystemRoot\system32\ntoskrnl.exe)

SystemCodeIntegrityInformation:
        - IntegrityOptions: 0x0001
           0x0001: CODEINTEGRITY_OPTION_ENABLED

SystemKernelDebuggerInformation:
        - KernelDebuggerEnabled: 0
        - KernelDebuggerNotPresent: 1

SharedUserData->KdDebuggerEnabled: 0x00

efidsefix -c
Checking for working EFI SetVariable hook...
Success.

efidsefix -r
Querying g_CiEnabled value...
nt!g_CiEnabled at 0xFFFFF80001C7CEB8.
Success. g_CiEnabled value: 0x0

Attachments

No response

@Gelip Gelip added the bug Something isn't working label May 15, 2024
@Mattiwatti
Copy link
Owner

You do understand that in order for me to reproduce your issue, I will (at the very least) need both:

  1. Your "beepxp driver", as well as precise steps on how to install it (meaning exactly the steps you used to install this driver on your system), and
  2. The actual file(s) for your "no_pg_ds_v3" fix, as I do not have an account on exetools.com, nor would I even know what file(s) to download if I did, or what to do with them in order to recreate your exact setup.

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.

@Mattiwatti Mattiwatti added the invalid This doesn't seem right label May 17, 2024
@Gelip
Copy link
Author

Gelip commented May 18, 2024

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

@Mattiwatti
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants