Bug 1441918 Comment 91 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has correctly been addressed. Attached is a comparison of a previous recording (top) with a new recording (bottom).

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing (e.g. youtube.com) with Firefox, bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, so the numbers for Chrome would be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can then check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has correctly been addressed. Attached is a comparison of a previous recording (top) with a new recording (bottom).

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, so the numbers for Chrome would be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can then check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has correctly been addressed. Attached is a comparison of a previous recording (top) with a new recording (bottom).

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, the new numbers for Chrome should be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can then check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has correctly been addressed. Attached is a comparison of a previous recording (top) with a new recording (bottom).

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com on my machine), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, the new numbers for Chrome should be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can then check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has correctly been addressed. Attached is a comparison of a previous recording (top) with a new recording (bottom).

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com on my machine), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, the new numbers for Chrome should be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has been addressed correctly. Attached is a comparison of a previous recording (top) with a new recording (bottom).

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com on my machine), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, the new numbers for Chrome should be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has been addressed correctly. Attached is a comparison of a previous recording (top) with a new recording (bottom) when loading youtube.com.

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com on my machine), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, the new numbers for Chrome should be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.
I was able to install `mpengine.dll` version 1.1.20200.3, which should incorporate the fix for the performance issue mentioned in comment 82 and described in comment 87. I confirm that this performance issue has been addressed correctly. Attached is a comparison of a previous recording (top) with a new recording (bottom) when loading YouTube.

The numbers suggest a ~75% improvement in CPU usage from MsMpEng.exe when browsing with Firefox (the specific number applies to browsing youtube.com on my machine), bringing it close to where CPU usage was when browsing with Chrome back in comment 78 (of course, since the performance improvement benefits all programs installed on the system, the new numbers for Chrome should be lower if measured with version 1.1.20200.3 of `mpengine.dll`).

You can get `mpengine.dll` version 1.1.20200.3 (currently Beta) as follows:
- run a Powershell terminal as administrator;
- type `Set-MpPreference -EngineUpdatesChannel Beta`, press Enter;
- open Windows Update, browse updates, a new update should appear, install it;
- back in the terminal, you can type `Set-MpPreference -EngineUpdatesChannel Broad` and press Enter if you don't want to stay in Beta for the future.

You can check your version of `mpengine.dll` as follows:
- navigate to `C:\ProgramData\Microsoft\Windows Defender\Definition Updates\`;
- look for a folder named something like `{7C9E9F14-9A1B-4833-AC74-DA15E21884D4}`, open it;
- right click on `mpengine.dll`, `Properties`, `Details`, look for `Product version`.

Disclaimer: I have also received updates for my whole system and Firefox between the two recordings, which may also partially affect the numbers observed here.

Back to Bug 1441918 Comment 91