CLR Asset Failure !AreCETShadowStacksEnabled() || UseSpecialUserModeApc() error

[TusharBeniwalGH]

Seeing below exception when empty lambda function is run in visual studio 2022 with profile Mock Lambda Test Tool

Profile

{
"profiles": {
"Mock Lambda Test Tool": {
"commandName": "Executable",
"commandLineArgs": "--port 5050",
"workingDirectory": ".\bin\$(Configuration)\net8.0",
"executablePath": "%USERPROFILE%\.dotnet\tools\dotnet-lambda-test-tool-8.0.exe"
}
}
}

Please assist.

[shruti0085]

Hi @TusharBeniwalGH can you share details about the type of project you are attempting to launch the mock lambda test tool with? Is it a .NET 8 project?
Also could you please share your toolkit logs to help us investigate this further?

[TusharBeniwalGH]

Hi it is AWS Lambda Project (.NET Core C#) ,yes it is .NET 8 project

below error snippet from event viewer

[normj]

Can you run the dotnet --list-sdks and dotnet --list-runtimes commands and let us know the output. Wondering if you have any preview SDK versions that is possibly causing a corruption of the lambda tool host that the .NET SDK generates when the tool is installed.

Can you also try uninstalling and reinstalling the test tool from the command line?

dotnet tool uninstall -g amazon.lambda.testtool-8.0
dotnet tool install -g amazon.lambda.testtool-8.0

[TusharBeniwalGH]

Also did below as asked but still same exception

dotnet tool uninstall -g amazon.lambda.testtool-8.0
dotnet tool install -g amazon.lambda.testtool-8.0

[TusharBeniwalGH]

any update please @normj @shruti0085 @redhotpenguin @hyandell , I am waiting since last week.

[TusharBeniwalGH]

any update please

[normj]

From my understanding the AreCETShadowStacksEnabled error can happen due to antivirus or security software. Or admin policies set on the local machine. Can describe your development environment. Is this Windows X64 or ARM? Are there any special Antivirus or security software running in the environment? Do you know if other .NET tools work in this environment. For example we have a new preview version of the tooling, can see if you has the same startup issue. To do that that test run the following commands.

dotnet tool install -g amazon.lambda.testtool --prerelease
dotnet lambda-test-tool start --lambda-emulator-port 5050

If that does fail with the same error can you run

dotnet lambda-test-tool info