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

Apps with CET support enabled do not launch #110920

Open
PiMoNFeeD opened this issue Dec 23, 2024 · 1 comment
Open

Apps with CET support enabled do not launch #110920

PiMoNFeeD opened this issue Dec 23, 2024 · 1 comment
Labels
area-VM-coreclr untriaged New issue has not been triaged by the area owner

Comments

@PiMoNFeeD
Copy link

Description

I've recently updated a .NET app I had to a newer version and found out that it doesn't launch. Fast forward 2 days, I tracked down the issue to the fact that the app was upgraded from .NET 8.0 to 9.0, and testing in multiple configurations on my local machine revealed that any .NET 9.0 app simply doesn't work on my machine, unless I explicitly add <CETCompat>false</CETCompat> to the .csproj file.

Debugger is entirely useless as it only shows this:

The program '[XXX] XXX.exe' has exited with code 3221227010 (0xc0000602) 'The process aborted due to a fail fast exception.'.

If I create a console application instead, I also get this right above the aforementioned crash:

CLR: Assert failure(PID 4452 [0x00001164], Thread: 20648 [0x50a8]): !AreShadowStacksEnabled() || UseSpecialUserModeApc()
    File: D:\a\_work\1\s\src\coreclr\vm\threads.cpp:7938

That led me to #108589, where someone else had the same assert and updating their Windows helped, but they updated to the exact same build I am running from 2023, so I hardly believe this to be an issue.

Reproduction Steps

...

Expected behavior

...

Actual behavior

...

Regression?

There was no crash until CET support was forced on by default

Known Workarounds

Disabling CET support on a per-app basis

Configuration

.NET 9.0.0
Windows 10 Pro 22H2 x64 build 19045.2965, Windows Feature Experience Pack 1000.19041.1000.0

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 23, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 23, 2024
@vcsjones vcsjones added area-VM-coreclr and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 23, 2024
Copy link
Contributor

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-VM-coreclr untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

2 participants