Fix Windows 10 LTSC panic/crash due to kernel missing CET features #673
Conversation
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
Member
|
Is this "Windows 10 IoT Enterprise LTSC 2021"? |
Member
Author
Yes, this is the latest build of Windows 10 IoT Enterprise LTSC |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Windows 10 IoT LTSC and older Windows 10 builds don’t support Control-flow Enforcement Technology (CET).
CET’s Shadow Stack feature helps defend against return-oriented programming (ROP) attacks, but since these systems lack CET support, disabling CET compatibility causes no loss of security or functionality in this program btw