|
|
Post by ihatemetro on Oct 31, 2020 16:13:04 GMT -8
Gentlemen, ye learned how to close the "themesection" handle of winlogon.exe in memory (NT Object Manager namespace), and created this and similiar previous utilities. But when disassembling ye surely have understood, which system call is behind this. My question in about patching the "winlogon.exe" (or another responsible binary) direcly, (for example I use Windows 10 build 1607). I understand that it would invalidate the checksum of the binary, but I am ready to boot the Windows with disabled "driver signature verification". Who can indicate, how to patch, at which offset, which bytes? Not happening. Our method (disabling the theme section, not closing it) is easier by a far stretch and actually allows for UWP fo work alongside classic theme. Further it allows for going back to the standard theme if/when anything breaks. Also doing what you said would require a new patch every update. That’s stupid Agreed. Patching it is way harder and you have to access startup options EVERY TIME to disable driver signature enforcement. |
|
