Jump to content

Deep Behavioral Inspection causes cmd crash

Go to solution Solved by Marcos,

Recommended Posts

On computers with EEA installed, the window appears a few seconds after executing cmd, and then the window closes automatically.
If I disable Deep Behavioral Inspection or add c:\windows\system32\cmd.exe to the exclusion list, cmd will run normally.

Tried pre-releases update, still the same situation.

What can I do to solve this problem?

Windows 10 22H2 x64, EEA 11.0.2044 (Deep behavioral inspection support module 1150)

Link to comment
Share on other sites

  • Administrators
  • Solution

This is a known clash between CloudStrike and Deep Behavioral Monitor. While the issue is investigated, you can:


  1. Add cmd.exe, Powershell.exe, DllHost.exe, rundll32 to the Deep Behavioral Monitor exclusion list
  2. Temporary disable Deep Behavioral Monitor
  3. Try the latest version of modules from the pre-release update channel. If it makes no difference, resort to 1, 2 or 4.
  4. Disable Crowdstrike
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...