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

vscode and ungoogled chromium cannot open/launch crash on start #315

Open
onguarde opened this issue Nov 13, 2024 · 2 comments
Open

vscode and ungoogled chromium cannot open/launch crash on start #315

onguarde opened this issue Nov 13, 2024 · 2 comments
Labels
bug Something isn't working info-needed Further information is requested

Comments

@onguarde
Copy link

Took me some time to trace it to windhawk, i thought it was my antivirus that is preventing the programs from starting up...

image

When I added the process in the exclusion list above, it launches perfectly. My question is why is this exclusion required? Why is windhawk interfering with programs launching. Even launching the program as administrator from file explorer doesn't work.

I want to understand what is happening and whether windhawk will interfere with other programs in such a drastic way.

@onguarde onguarde added the bug Something isn't working label Nov 13, 2024
@onguarde
Copy link
Author

onguarde commented Nov 13, 2024

image

Btw, I'm using these mods, but disabling all of them still issue persists.
I'm on the latest v1.5.1.

Windows 11

Troubleshooting lists the following programs as incompatible. I'm surprised vscode is not on the list. It maybe something specific to my setup.
VirtualBox - see Issue #25.
Battlefield 2042 - see Issue #169.

@m417z
Copy link
Member

m417z commented Nov 13, 2024

It still might be related to an antivirus not liking Windhawk's injection. Which antivirus are you using? If possible, could you try disabling it or excluding the Windhawk folder?

Both VSCode and Chromium are definitely supported.

Also, is there a crash on launch? Can you capture a crash dump? You should be able to get it with the following steps:

  • Open regedit
  • Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
  • Create a key named LocalDumps
  • Create a DWORD value named DumpType with value 2
  • Trigger the crash
  • Go to the %LocalAppData%\CrashDumps folder, you should see a dump file in there

@m417z m417z added the info-needed Further information is requested label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working info-needed Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants