{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreicvnp3xwucpo5kmejyndxr6637toeshy3fg4qhpeiaueeiahr7xsq",
"uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3mnvfqy62kmy2"
},
"description": "🚨Major Update: This post contains a significant change that may impact your organisation.\n\nWhat and why:\nThe June 2026 Windows security update will be released as a [standard update] instead of a [hotpatch update]. As a result, hotpatch-enabled devices will require a restart to complete installation.\n\nThis change prioritizes security following public disclosure of a vulnerability outside coordinated disclosure best practices (CVE-2026-45585).\n\nRollout schedule:\n\n * June 2026: Standard update wi",
"path": "/m365-message-center/message/mc1385496/",
"publishedAt": "2026-06-10T00:00:04.000Z",
"site": "https://blog.tophhie.cloud",
"tags": [
"CVE-2026-45585",
"Windows 11",
"Windows Servers"
],
"textContent": "🚨\n\n**Major Update:** This post contains a significant change that may impact your organisation.\n\n**What and why:**\nThe June 2026 Windows security update will be released as a [standard update] instead of a [hotpatch update]. As a result, hotpatch-enabled devices will require a restart to complete installation.\n\nThis change prioritizes security following public disclosure of a vulnerability outside coordinated disclosure best practices (CVE-2026-45585).\n\n**Rollout schedule:**\n\n * **June 2026** : Standard update with restart required for hotpatch-enabled devices.\n * **July 2026** : Planned baseline update month with restart required.\n * **August 2026** : Next hotpatch update expected.\n\n\n\n**Impact on your organization:**\n\n * Hotpatch-enabled devices will require a restart to complete installation of the June 2026 security update.\n * Hotpatch-enabled devices will remain enrolled in hotpatch updates.\n * No change for devices not using hotpatch updates (standard updates already require restart).\n\n\n\n**Action required / recommendations:**\nNo additional configuration is required to stay enrolled in hotpatch updates.\n\n**Compliance considerations:**\n\n * No compliance action is required.\n * Update installation and restart behavior will be reflected in update history and compliance reports as usual.\n\n\n\n**Additional information:**\nYou can track the hotpatch update calendars on the Windows release health site for both Windows 11 and Windows Servers.",
"title": "MC1385496: June 2026 Windows security update requires restart for hotpatch-enabled devices",
"updatedAt": "2026-06-10T00:00:04.455Z"
}