Microsoft warns of Windows update delays due to wrong timestamp

Microsoft has acknowledged a new issue that is causing delays in the delivery of the June 2025 Windows security updates. This complication arises from an incorrect metadata timestamp, which has implications for both Windows 10 and Windows 11 systems operating under quality update deferral policies. These policies allow IT administrators to postpone the installation of updates on managed devices.

As detailed in a recent advisory, while delays in update deployment are anticipated when utilizing such policies, the erroneous timestamp for the June security updates could extend these delays beyond the timeframe set by administrators. This situation may inadvertently leave unpatched systems vulnerable to potential attacks.

Details of the Issue

Microsoft elaborates, “Some devices in environments where IT admins use quality update (QU) deferral policies might experience delays in receiving the June 2025 Windows security update. Although the update was released on June 10, 2025, its update metadata timestamp reflects a date of June 20, 2025. This discrepancy might cause devices with configured deferral periods to receive the update later than expected.”

While the investigation into this known issue continues, Microsoft has proactively provided several temporary workarounds for Windows administrators to expedite the deployment of the June 2025 updates until a permanent fix is implemented.

Workarounds for Administrators

To facilitate a quicker rollout, Microsoft recommends creating an expedited deployment policy that bypasses deferral settings. This approach ensures immediate delivery of updates in organizations utilizing Windows Autopatch. Alternatively, administrators can adjust deferral configurations or deployment rings to reduce delays for affected devices.

The steps to create an expedited deployment policy are outlined as follows:

  1. Navigate to Intune > Devices > Windows Updates.
  2. Select the Quality Updates Tab.
  3. Click on “Create Expedite Policy.”
  4. Choose the 6B release, complete the relevant details, and assign the desired Entra groups.
  5. Validate your update as usual and assign additional groups to the policy to finalize the rollout of the latest updates to your devices.

Microsoft reassures users that “this delay issue affects only the timing of update availability for organizations using QU deferral policies and doesn’t impact the quality or applicability of the update.” The company has confirmed that it will not alter the metadata value from the current June 20, 2025, timestamp, stating that the provided workaround is the definitive resolution for this matter.

Earlier this month, Microsoft also released a configuration update (KB5062324) aimed at resolving a known issue that led to update failures after the scan for Windows updates ceased functioning on certain Windows 11 systems. In May, the company addressed another bug that had hindered the delivery of Windows 11 24H2 feature updates via Windows Server Update Services (WSUS) following the installation of the April 2025 security updates. Additionally, a month prior, Microsoft rectified a “latent code issue” that caused some PCs to upgrade to Windows 11 overnight, despite Intune policies designed to prevent such upgrades.

In a bid to enhance the update experience, Microsoft has also unveiled plans to unify the updating system for all applications, drivers, and system components across Windows systems through a new update orchestration platform built on the existing Windows Update infrastructure.

Winsage
Microsoft warns of Windows update delays due to wrong timestamp