I'm am asking because a few users have reported in the Malwarebytes forum that that if Malwarebytes Premium is registered with the Windows Security Center as the primary real-time protection (i.e., Settings | Security | Windows Security Center | Always Register Malwarebytes in the Windows Security Center is turned ON in Malwarebytes Premium and the main Windows Defender AV real-time protection is disabled) then Limited Periodic Scanning can be turned ON but is automatically turned OFF after they re-boot their system as shown below. See my 31-Mar-2021 post in Dave-H's thread Malwarebytes 4.3.0 with Windows 10 Defender for further details.
I know that Norton users have previously reported that Windows Defender's Limited Period Scanning can be turned on and will run the occasional scan when Norton is installed (see Krusty13's 28-Jun-2018 comment in the Norton thread Canceling a Scheduled Scan for one example) but I'm not sure if Norton 360 and Limited Periodic Scanning still work together correctly these days. --------
64-bit Win 10 Pro v2004 build 19041.867 * Firefox v87.0 * Windows Defender v4.18.2102.4 * Malwarebytes Premium v4.3.0.98-1.0.1236
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, Toshiba 256 GB NVMe SSD, Intel UHD Graphics 620
I have Kaspersky Cloud Security installed on this machine and I did have LPS enabled but I just checked and it has been disabled again. I do also have MB Premium active but not registered in Windows Security Center so that may related here as well.
Thanks for your detailed feedback. That would seem to disprove the conjecture in Dave-H's thread Malwarebytes 4.3.0 with Windows 10 Defender that Limited Periodic Scanning "does not work on consumer versions of Windows Home and Pro and is for the business editions."
I normally have Security | Windows Security Center | Always Register Malwarebytes in the Windows Security Center turned OFF in Malwarebytes Premium and use Windows Defender as my primary real-time AV, but when I was running my tests for Dave-H with this setting turned ON I noticed that Malwarebytes was very slow to disable the Windows Defender AV and register itself as the primary real-time protection after each boot-up. Unless someone from Malwarebytes can come up with a better explanation (e.g., that Malwarebytes Premium is designed to turn off Limited Periodic Scanning when this third-party "antivirus replacement" is used as the primary real-time protection) I'm going to assume that this time lag to disable the Windows Defender AV and register Malwarebytes Premium with the Windows Security Center is the reason why Limited Periodic Scanning keeps turning itself off after each boot-up.
--------
64-bit Win 10 Pro v2004 build 19041.867 * Firefox v87.0 * Windows Defender v4.18.2102.4 * Malwarebytes Premium v4.3.0.98-1.0.1236
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, Toshiba 256 GB NVMe SSD, Intel UHD Graphics 620
Hello again!! I get the same results as bjm ALTHOUGH. I do NOT run MBAM in real time mode. Reboot results are the same for me. FWIW!! One of the links in Dave's older post states the following:
At this time, Windows 10 Limited Periodic Scanning is intended for consumers. We are evaluating this feature for commercial customers, but Limited Periodic Scanning only applies to unmanaged devices for the Windows 10 Anniversary Update
Unmanaged devices will NOT be in an enterprise environment. Below is a screenshot from my W10 Pro laptop in settings. The setting IS available in this version, I have 20H2 installed. Same as bjm.
Setting the periodic scanning to ON, you immediately get the following alert which I ignored and allowed the setting to remain. Same as bjm.
Norton prompts upon turning Periodic scanning On. and after machine Restart
Note: my Malwarebytes Premium is not registered with WSC, not start with Windows, not in system tray at this time.
Note: my Windows Security notification icon is in system tray at this time.
Note: ProgramFiles\Malwarebytes & ProgramData\Malwarebytes with Norton 360 exclusions.
Note: ProgramFiles\Malwarebytes & ProgramData\Malwarebytes with Microsoft Defender exclusions.