Hello Hafiz Othman,
By design, Windows Update for Business (WUfB) policies are applied on a scheduled refresh cycle, so newly configured deadlines may take a few hours before they appear on client devices. While there is no dedicated “force rescan” button, there are several effective methods to trigger a faster policy refresh and update detection.
On the client device, you can first run gpupdate /force to refresh policy assignments, then execute commands such as usoclient startscan or usoclient startdownload to manually initiate a Windows Update scan. Depending on the Windows version, PowerShell commands like Get-WindowsUpdate or legacy commands such as wuauclt /detectnow may also help, although some older commands are now deprecated in recent builds.
You can also restart the Windows Update service or reboot the machine, as both actions force the client to re-evaluate update policies. If the device is managed through Intune, triggering a manual “Sync” from the Intune admin center is another reliable way to force the device to check in and retrieve updated policy settings immediately.
Additionally, it is worth verifying that the device can successfully reach Microsoft Windows Update endpoints and that the Intune policy assignment is properly targeted. In some cases, delays are caused by proxy, firewall, or network restrictions rather than the WUfB client itself.
In summary, although WUfB does not provide an instant “force rescan” feature, combining a policy refresh (such as gpupdate or an Intune sync) with a manual Windows Update scan typically achieves the expected result.
I hope this information helps. If you found the response useful, please consider selecting “Accept Answer.”
Jason