-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
ShellHost.exe -System Error #103
Comments
Thank you for opening your first issue! Please make sure to include the following information:
Warning: Systems using other hardening scripts or unsupported OS are not supported by us. Please consult the readme and test the script in a virtual machine prior to running it on your system. Note: Users need to show they have read the readme. If you haven't read the most basic documentation in the readme, you are not in need of support yet. For general questions, please use the discussions page. We will move an issue to the discussions if we see fit to do so. To learn how to customize, troubleshoot, or revert the changes in the script, please see the wiki. |
I am using Windows 11 24H2 and I read the readme file saying to create a local user. However I am confused on if I need to create another local user after the initial setup. |
You should only have to create local accounts in lue of any accounts originally set up with a Microsoft login with email. |
As far as your issue goes, we've not been able to replicate the issue on W11 24H2 base with all updates installed. We need you to answer all of the questions the bot has asked to continue.
|
Discussed in #102
Originally posted by Kawika498 November 27, 2024
I did a fresh install of Windows on this Desktop I am hardening After running the script and reseating the device when I log into my Admin user the desktop keeps crashing and a prompt saying that the system detected an overrun of stack-based buffer in this application. Are there any idea on what might be causing this I have done 3 fresh installs just to make sure it wasn't an application that was causing the issue
The text was updated successfully, but these errors were encountered: