sascha/wsltty
1
0
Fork 0
mirror of https://github.com/mintty/wsltty.git synced 2025-01-31 02:01:01 +00:00
Code Issues Releases Wiki Activity

Add note about Windows Defender issue.

Browse Source 
I've noticed that any process run via WSL will fire up "Antimalware Service Executable" and peg the CPU. Adding this directory as an excluded path helped considerably. I don't really know the security implications of this. 🙈
This commit is contained in:
Brian Dailey 2018-05-09 15:02:11 -05:00 committed by GitHub
parent 26a1abb148
commit 0d1fb55028
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -150,6 +150,14 @@ you may append a shell pathname and an optional `-l` parameter
to the mintty invocation (in shortcuts, scripts, or context menu entries): to the mintty invocation (in shortcuts, scripts, or context menu entries):
* `%LOCALAPPDATA%\wsltty\bin\mintty.exe --WSL= --configdir="%APPDATA%\wsltty" /bin/bash -l` * `%LOCALAPPDATA%\wsltty\bin\mintty.exe --WSL= --configdir="%APPDATA%\wsltty" /bin/bash -l`
#### Windows Defender and wsltty
If you note that "Antimalware Service Exectutable" pegs your CPU
during usage of mintty, particularly with WSL, you may want to add
`%LOCALAPPDATA%\wsltty\bin\` to your list of folders excluded from real-time
antivirus scanning.
--- ---
### Components and Credits ### ### Components and Credits ###