Defender update frequency normal?

Mcd73165 said:

Also the date showing when you disabled the task is in June and the issue started about August 1.

There is misunderstanding. On my Windows 10, the date "6/11/2018" denotes November 6 rather than June 11.

Hi, that's odd, it is supposed to (if you have system restore enabled) only create a windows installer module restore point when you update a QU (commonly know as a cumulative update) and indeed it is what happens on my machines.

I received two defender updates yesterday, and one this morning, and yesterday I updated KB4343909 , since the original was corrupted.Restore only made the one RP, this was for the QU KB4343909. So all normal here. I might add that reg mod mentioned is standard (added by us) on all of our machines, has been for years.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\installer" /v LimitSystemrestoreCheckpointing /t REG_DWORD /d 1 /f

We also add this to control WU, so no forced updates can occur.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoUpdate /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v AUOptions /t REG_DWORD /d 2 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoRebootWithLoggedOnUsers /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v ScheduledInstallDay /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v ScheduledInstallTime /t REG_DWORD /d 3 /f

arso96 said:

Hi, that's odd, it is supposed to (if you have system restore enabled) only create a windows installer module restore point when you update a QU (commonly know as a cumulative update) and indeed it is what happens on my machines.

I received two defender updates yesterday, and one this morning, and yesterday I updated KB4343909 , since the original was corrupted.Restore only made the one RP, this was for the QU KB4343909. So all normal here. I might add that reg mod mentioned is standard (added by us) on all of our machines, has been for years.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\installer" /v LimitSystemrestoreCheckpointing /t REG_DWORD /d 1 /f

We also add this to control WU, so no forced updates can occur.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoUpdate /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v AUOptions /t REG_DWORD /d 2 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoRebootWithLoggedOnUsers /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v ScheduledInstallDay /t REG_DWORD /d 0 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v ScheduledInstallTime /t REG_DWORD /d 3 /f

I don't think I understand what you're saying. Do you mean that if I were to add these registry entries that there will be no Windows Modules Installer System Restore points created when Windows Defender Verification task runs?

Matthew Wai said:

There is misunderstanding. On my Windows 10, the date "6/11/2018" denotes November 6 rather than June 11.

Thanks for letting me know that.

Windows Defender was updated yesterday and today the WD Verification task ran and did not create a Windows Module Installer restore point. Can this issue finally be fixed? I'll wait for the task to run one more time to make sure. The WD Scan still returns a result of (0x2)

Mcd73165 said:

Windows Defender was updated yesterday and today the WD Verification task ran and did not create a Windows Module Installer restore point. Can this issue finally be fixed? I'll wait for the task to run one more time to make sure. The WD Scan still returns a result of (0x2)

Same thing for me with the Verification Task. We should know more in a day or so. As for the 0x2 -- it's still not fixed by MS and the auto scan's been broken since the Anniversary Update. Also still not fixed in 1809 is the Defender definition timestamp in the program. It's off by 5 hours. However, the timestamp in Windows Update is accurate. BTW -- the Defender definition timestamp was accurate in 1803.

Crizal said:

Same thing for me with the Verification Task. We should know more in a day or so. As for the 0x2 -- it's still not fixed by MS and the auto scan's been broken since the Anniversary Update. Also still not fixed in 1809 is the Defender definition timestamp in the program. It's off by 5 hours. However, the timestamp in Windows Update is accurate. BTW -- the Defender definition timestamp was accurate in 1803.

Hi, Crizal. I'm keeping my fingers crossed for the WD Verification Task. Doesn't seem like MS will ever fix the WD Scan Task. I still haven't received the 1809 update on either of my computers. (Still have 1803). I haven't run a self Windows Update check. I'll let the update happen when it's ready to install automatically.
Mark

Mcd73165 said:

Hi, Crizal. I'm keeping my fingers crossed for the WD Verification Task. Doesn't seem like MS will ever fix the WD Scan Task. I still haven't received the 1809 update on either of my computers. (Still have 1803). I haven't run a self Windows Update check. I'll let the update happen when it's ready to install automatically.
Mark

Mark -- for what it's worth -- I got 1809 when it first came out (before it was paused). It's been fine on my system even though I have one of the Intel graphics drivers that gave some people issues and I also have an HP printer and didn't have any of the issues associated with some of those. Guess I was lucky. Your decision to wait for WU is most prudent.

@Mcd73165 -- Hello Mark. Some good news and I hope it holds. Windows Defender ran the verification task last night at 8:58PM and for the second consecutive time, there was no Windows Module Installer restore point set. Is it finally fixed? Time will tell.