Forum Discussion
Signature update finished. No updates needed. Co-managed device
2289820, The4thLegacyHi we are facing exactly the same issue. Did you or anyone else ever find the issue and where able to fix it?
Set gpo to 0 for define the number of days before virus security intelligence is considered out of date.
This workaround will come with other issues such as end user toast notifications and DFE device health reporting out of date.
If anyone has a better solution please post as I'd be open to changes 😄
Goodluck!! 🙂
2289820
We have found some more information on this. We can confirm that the issue is caused by the registry settings inHKLM:\Software\policies\Microsoft\Windows\WindowsUpdateThere you have 4 keys:
SetPolicyDrivenUpdateSourceForDriverUpdates
SetPolicyDrivenUpdateSourceForFeatureUpdates
SetPolicyDrivenUpdateSourceForOtherUpdates
SetPolicyDrivenUpdateSourceForQualityUpdatesAll of which are set to 1 by Configuration Manager if you have Co-Management enabled and the Workloads for Windows Update policies and Office Click-To-Run set to Configuration Manager (or Intune Pilot and the devices having the issues are not in that Pilot collection).
Setting SetPolicyDrivenUpdateSourceForOtherUpdates to 0, restarting the Windows Update service and triggering the signature Update by any means, instantly updates your signatures. However according to this documentation: https://learn.microsoft.com/en-us/windows/deployment/update/update-other-microsoft-products, this also sets the updates for other products, which for us is a no go.Currently we are checking if setting the Defender Preference OobeEnableRtpAndSigUpdate to true with PowerShell and rebooting the device fixes the issue.
Set-MpPreference -OobeEnableRtpAndSigUpdate $trueThis was suggested by MS support. I will get back to you once we have reliable results.
Hi abs168
I just found this thread today because I'm doing some research about this issue. We're also affected by this one. Did you manage to solve it?
Hi ClientAdmin,
yes, in the end setting
Set-MpPreference -OobeEnableRtpAndSigUpdate $truedid fix the issue. The initial tests did fail because on that device we had a wrong signature fallback order.
