Fix windows 11 compatibility#180
Open
maxDcb wants to merge 13 commits into
Open
Conversation
Loader now user VirtualAlloc instead of NtCreateSection, because windows 11 enforce memory stricter protections on mapped image memory.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Loader now uses VirtualAlloc instead of NtCreateSection, as Windows 11 appears to enforce stricter protections on mapped image memory.
Memory permissions are now managed page by page rather than section by section.
Bypasses are disabled for shipped builds, as Windows appears to check DLL integrity and crash the process if direct patches are applied to AMSI or ETW.