Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
  • Interests
    Computer Engineering, Coding, Violin, Swimming, Gaming

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Although parental control for Android is working great, one specific game called Dragon Land is bypassing both app restrictions and time restrictions even if I disallow the app through parental control settings. This is the only app so far that is able to bypass parental control. Can you fix it?
  2. Excluding only the Canonical folder for Ubuntu in "%userprofile%\AppData\Local\Packages" or the corresponding WhitewaterFoundry for WLinux seems to work for me also. As you say this solution is far from ideal. We are now at least 2 people experiencing this issue so it can't be a coincidence. Eset should take a look at this.
  3. ekrn had also a very high number of file event in the same procmon I posted above. I run sysbench fileio sequential read/write test on wsl and noticed that when eset protection is not off/or the folder C:\Users\ntona\AppData\Local\Packages is not excluded from scanning there is a latency in read/write operations. Also i do not trust the CPU utilization because I am running the October update of Windows 10 1809 and I read that there is a bug where CPU % is reported falsely. The important thing is that in real world usage there is a slowdown caused by ESET in various WSL operations. If you install a free version of WSL like Ubuntu you can test it. With ESET protection off or the folder excluded it performs noticeably faster.
  4. The procmon log I posted in my first reply was not about gcc but was captured during apt-get install commands. I captured a new Procmon log when compiling a test project (see attachment in this post). I tried excluding the folder C:\Users\ntona\AppData\Local\Packages and It actually makes a difference, speeding things up. Is it safe to have all the contents of this folder excluded? It would be better if there wasn't the need to exclude the whole folder though. Logfile GCC slowdown.zip
  5. Yes i notice slowdown using wsl with eset in general. I notice a slowdown when starting/executing applications, compiling etc. Though slowdown is most prevalent during apt-get operations and dpkg but it is not limited to it. With protection disabled wsl feels overall snappier. For example when compiling a simple small project written in C with gcc I can prove that with real time protection OFF the compilation process is about 30% faster! This is a small project. Imagine when compiling a larger project, a slowdown penalty of 30% would matter a lot! I measured the compilation of the project 3 times for consistency with protection OFF and Protection ON. (We observe that each time I compile the project the compilation time is shorter due to OS/hardware optimizations like caches, TLB etc but with Protection ON is always about 30% slower)
  6. No problem, I also try to learn something new every day. There is always something new to learn Also, thanks for your interest in helping me😃. I just hope ESET will take a look at this.
  7. I used VM in the past, but WSL suits me better and I prefer it. There are several reasons to use WSL. For example: Bash interactions with windows programs. Run native Linux binaries without the overhead of a VM (WSL is not an emulator as you say, but it runs Linux binaries directly). WSL requires fewer resources (CPU, memory, and storage) than a full virtual machine (It uses only 2 gb of storage in my machine). WSL also allows you to run Linux command-line tools and apps alongside your Windows command-line, desktop and store apps, and to access your Windows files from within Linux. WSL enables you to use Windows apps and Linux command-line tools on the same set of files if you wish. It is very useful for developers, because you can use developing tools from both worlds (Windows and GNU/Linux) on the same files without dual-booting or transferring files to the VM. You can even shift+right-click in Explorer and open bash quickly in the current directory with "Open Linux Shell here" option. For me, these conveniences are enough to switch from VM/dual booting to WSL. I don't prefer to exclude WSL from being scanned and I believe it won't reduce system impact either, because each program that runs through WSL is executing directly on Windows (as shown above in the screenshot of task manager) so I will have to exclude every single user/Linux program-package I use in WSL separately in order to reduce system impact, which is not ideal. I think this is an issue that could affect many people, especially in the future where WSL may be adopted by other people. So I think it is wise to bring this issue to ESET and find a solution for this problem before it affects other people.
  8. First of all, I should note that Windows Subsystem for Linux (and consequently WLinux or any other Linux flavors that use it) is of great importance to me. I am studying computer engineering in a university and WSL is a great development tool allowing running Linux command-line tools directly on Windows. It is a shame discovering that ESET Internet Security, which is a product I admire and love, causing a slowdown when using it. WLinux includes a built-in script that automates and simplifies the installation of various developer tools (such as python3, node.js, vscode etc). With my preferences, after running the script, WLinux occupies approximately 2gb of space in disk. In order to compare the performance impact of ESET Internet Security, I run the same script with the same preferences two times, while previously resetting WLinux app through windows settings. Running the complete script with real-time protection disabled took about 14 minutes. Running the complete script with real-time protection enabled took about 33 minutes! Almost 20 minutes slowdown! I noticed that the there was a significant slowdown caused by high ESET service activity, when the script was unpacking packages and installing applications through the apt-get system. Though, the slowdowns caused by ESET are also noticable in various WSL functions like opening an application like code through X410. Here is a link to the generated Procmon log. I recorded all the events, while running the script with ESET real-time protection enabled. Because it took 33 minuted to finish, it was too big (1gb compressed) to post here so I uploaded to Mega. Also, I attach in this reply, the ESET settings I used, exported using ESET's import/export settings tool. eset settings.zip
  9. I have noticed that ESET Service has a relative high CPU usage when using Windows Subsystem for Linux compared to other processes. Please see the attached screenshot where I use WLinux, a WSL distro from Microsoft Store. My System Specs are also attached. I am running latest version of ESET System Specs.txt