Bug Report - Windows Defender detect suspicious behavior #3607

Closed
opened 2026-01-30 23:25:25 +00:00 by claunia · 2 comments
Owner

Originally created by @rodoac89 on GitHub (Aug 28, 2019).

Originally assigned to: @bitcrazed on GitHub.

Environment

Windows build number: 18965
Windows Terminal version: Dev Build

Steps to reproduce

  1. Open Windows Terminal

Expected behavior

  1. Open default tab

Actual behavior

After open Windows Terminal (Dev Build), Windows Defender detect a suspicious behavior, and block the execution
Windows Defender Message:
Behavior:Win32/Generic.WR!ml
Alert level: Severe
Status: Quarantined
Date: 08/27/2019
Category: Suspicious behavior
Details: This program is dangerous and Executes commands from attacker
Affected items: file:
appmodel: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe

file: C:\Users\rodoa\source\repos\WindowsTerminal\terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\conhost.exe

Note: I compiled and deployed 8 hours ago and it ran fine, but I opened it (from start menu) again a few minutes ago and W.D. alerted of the thread

Originally created by @rodoac89 on GitHub (Aug 28, 2019). Originally assigned to: @bitcrazed on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 18965 Windows Terminal version: Dev Build ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open Windows Terminal # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> 1. Open default tab # Actual behavior <!-- What's actually happening? --> After open Windows Terminal (Dev Build), Windows Defender detect a suspicious behavior, and block the execution Windows Defender Message: Behavior:Win32/Generic.WR!ml Alert level: Severe Status: Quarantined Date: 08/27/2019 Category: Suspicious behavior Details: This program is dangerous and Executes commands from attacker Affected items: file: appmodel: WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe file: C:\Users\rodoa\source\repos\WindowsTerminal\terminal\src\cascadia\CascadiaPackage\bin\x64\Debug\AppX\conhost.exe Note: I compiled and deployed 8 hours ago and it ran fine, but I opened it (from start menu) again a few minutes ago and W.D. alerted of the thread
claunia added the Needs-Tag-Fix label 2026-01-30 23:25:25 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Aug 29, 2019):

This is external to us, but internal to Microsoft. We'll pursue it from our side.
Thanks!

@DHowett-MSFT commented on GitHub (Aug 29, 2019): This is external to us, but internal to Microsoft. We'll pursue it from our side. Thanks!
Author
Owner

@AshrafMichail commented on GitHub (Sep 3, 2019):

What's the workaround people use? Adding the full path of the built conhost.exe location to the exclusion list? Of course, I wouldn't want to do anything to exclude scanning for the actual conhost.exe virus that defender is trying to protect against.

@AshrafMichail commented on GitHub (Sep 3, 2019): What's the workaround people use? Adding the full path of the built conhost.exe location to the exclusion list? Of course, I wouldn't want to do anything to exclude scanning for the actual conhost.exe virus that defender is trying to protect against.
Sign in to join this conversation.
No Label Needs-Tag-Fix
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3607