KB5095093 covers Windows 11 versions 24H2 and 25H2. Check availability at Settings > Windows Update, and remember that gradual rollout can cause features to appear at different times on otherwise similar PCs. Do not treat Point-in-time Restore as a backup. Plan upgrades for Windows 11 24H2 Home and Pro before support ends on October 13, 2026, and use update pauses only for a defined testing need.
Notebookcheck describes KB5095093 as a substantial summer update. For WindowsForum readers, the practical priorities are narrower: confirm whether the update and its gradually released features have reached each PC, understand the limits of Point-in-time Restore, keep the Windows 11 24H2 support deadline visible, and use the expanded update-pause allowance as a testing tool rather than a long-term maintenance strategy.
Microsoft says Point-in-time Restore uses the Volume Shadow Copy Service, or VSS, to capture the PC’s state. Snapshots are created at an approximate default interval of every 24 hours and retained for up to 72 hours by default.
That short retention window defines the feature’s limits. A recent captured state may be available only briefly, and restoring the machine can affect applications, settings, and personal files. Point-in-time Restore therefore does not replace a separate backup that preserves data for longer periods or remains available when the PC or its local storage cannot be used.
Microsoft says the feature is enabled by default on Home and eligible Pro systems when the operating-system drive has a capacity of 200GB or more. The available information does not establish a default posture for every enterprise-managed configuration, so administrators should verify actual behavior on their own devices rather than assuming that all editions and management states are identical.
The supplied release information establishes the feature’s availability, scope, approximate default capture interval, default retention period, VSS foundation, and drive-capacity condition. It does not provide a verified entry path or complete invocation procedure. This article therefore explains Point-in-time Restore’s availability and limits rather than inventing steps for opening it, selecting a restore state, or restarting the PC. Users should follow Microsoft’s current on-screen guidance or official documentation when performing an actual restoration.
That is the main operational warning WindowsForum readers should carry forward. The feature’s broad scope means it should not be invoked casually. Support documentation should explain what the selected captured state represents and distinguish restoration from file recovery and long-term data protection.
The available facts support an approximate 24-hour capture interval and retention of up to 72 hours by default. They do not justify treating either number as a guaranteed recovery point for every incident. The useful restore state may predate recent work, and no suitable state should be assumed to exist without checking the device.
A concise support description is therefore:
KB5095093 changes the Windows Update pause experience from the previous fixed blocks of 7, 14, or 21 days. The verified limit is a maximum pause of 35 days, with the control available under Settings > Windows Update.
The expanded limit can be useful when a user or administrator needs additional time to test the cumulative update or confirm compatibility. It should not be interpreted as a reason to defer security updates for the full period by default. The appropriate pause is the shortest interval that addresses the identified testing need.
The timing also matters because Windows 11 version 24H2 Home and Pro will reach the end of updates on October 13, 2026. Pausing a cumulative update does not extend the support lifecycle of the installed Windows release. PCs approaching that date need an upgrade plan rather than a longer pause.
Point-in-time Restore has a separate verified drive-capacity condition: Microsoft says it is enabled by default on Home and eligible Pro systems with an operating-system drive of 200GB or larger. No broader enterprise default should be inferred from that statement.
The table also shows why an inventory entry that says only “Windows 11 24H2” is incomplete. Home and Pro have a different support milestone from Enterprise and Education, so edition affects upgrade urgency.
Microsoft also says affected devices can continue booting and receiving standard Windows updates. The expiration notice should therefore not be presented as a claim that every PC without a replacement certificate will immediately stop starting or updating.
The supported takeaway is more precise: Secure Boot certificate delivery is an ongoing part of Windows servicing, the transition is not completed everywhere at once, and continued delivery through Windows Update gives users another reason to keep supported devices current.
That information does not establish a universal firmware-deployment procedure or a single certificate-audit workflow for every organization. Hardware models, management tools, and deployment practices vary, and the release information does not support prescribing one process for all environments.
July 14, 2026 — Microsoft delivers the Patch Tuesday release identified as KB5095093 for Windows 11 versions 25H2 and 24H2.
October 13, 2026 — Windows 11 version 24H2 Home and Pro reach the end of updates.
October 12, 2027 — Windows 11 version 24H2 Enterprise and Education reach the end of support.
Widgets no longer open merely because the pointer passes over them. Notifications and taskbar badges are minimized by default. On first use, Widgets opens to its dashboard, where icons can display alert counts and badges clear after the user leaves a dashboard.
For users who want a full-screen color overlay, Screen Tint is available at:
Settings > Accessibility
Microsoft presents Screen Tint as an accessibility option intended to improve readability and reduce eye strain. Because its usefulness depends on the individual user, it is best treated as an optional display aid rather than a universal color-management setting.
Magnifier also gains controls that allow a zoom percentage to be entered directly and increments to be adjusted from the Magnifier interface. These changes reduce the need to move between Magnifier and the broader Settings application when selecting a preferred enlargement level.
Voice access and voice typing expand to French, German, and Spanish. Those additional language options are the significant verified change; broader claims about correction, grammar, punctuation, recognition in background noise, or other speech-processing behavior should not be inferred from the language expansion alone.
The address bar also accepts some less conventional path input containing double backslashes or quotation marks. Microsoft provides examples such as:
These changes may help users who paste paths from scripts, command output, documentation, or messages without first normalizing the formatting.
Microsoft also identifies improved explorer.exe reliability. That wording should not be expanded into claims about unspecified File Explorer fixes or particular launch, storage, cloud-sync, renaming, taskbar, or shortcut scenarios that are not documented in the available facts.
For organizations using the Entra ID quick actions, gradual rollout is especially relevant. Two devices can have the same cumulative update installed while only one currently exposes a newly released action. Help-desk guidance should therefore distinguish between “KB5095093 is installed” and “this feature has been enabled on this device.”
These are specific fixes rather than a general promise that every Bluetooth issue has been resolved. Testing should focus on the affected devices and workflows that matter in the local environment without extending the release notes into claims about unrelated Bluetooth behavior.
The networking work names several areas: Confidential Virtual Machines, SR-IOV, Windows Subsystem for Linux mirrored networking with VPNs, Wi-Fi, WWAN, IPv6 VPNs, and third-party VPN software. The release information identifies those areas, but it does not establish that every configuration-specific networking problem has been corrected.
Printing receives a concrete configuration change. New printer installations prefer Internet Printing Protocol when it is supported. Administrators can control the behavior at:
Settings > Bluetooth & devices > Printers & scanners > Default install printers using Windows Ready Print
The setting reflects a preference for IPP when compatible equipment is available. Administrators should verify the selected preference and the resulting installation behavior on the devices and printers they actually support.
Settings > Bluetooth & devices > Touchpad
The adjustment requires a touchpad with a pressable surface. That hardware qualification matters: the option should not be expected to provide the same behavior on every touchpad design.
For users who frequently trigger the wrong click near the lower portion of a compatible touchpad, the setting provides a direct place to tune the right-click area without relying on an undocumented registry change or a vendor-specific utility.
Those references identify affected components but do not support broader performance claims or detailed conclusions about every transfer, handwriting-recognition result, or location-related behavior. For WindowsForum readers troubleshooting one of those areas, the presence of a named change is a reason to install KB5095093 and retest the relevant workflow. It is not a guarantee that every superficially similar problem has the same cause.
As a result, two PCs can both report that they are current while showing different interfaces or features. Installing KB5095093 does not necessarily make every item in the release notes visible immediately.
This distinction affects testing, screenshots, training material, and help-desk scripts. A test PC may receive a new Widgets behavior, Entra File Explorer action, accessibility option, or other gradually released feature before another device running the same Windows version.
To verify the update, open:
Settings > Windows Update
Check for updates, install KB5095093 when offered, and complete any required restart. Then confirm the specific feature instead of relying only on the KB number. For Screen Tint, check Settings > Accessibility. For printer defaults, check Settings > Bluetooth & devices > Printers & scanners > Default install printers using Windows Ready Print. For the touchpad right-click zone, check Settings > Bluetooth & devices > Touchpad and remember that a pressable touchpad surface is required.
Notebookcheck presents KB5095093 as the July 14 Patch Tuesday package, while Microsoft’s servicing information distinguishes between normal and gradual feature availability. Those descriptions are compatible: the release begins availability, but not every included feature must appear on every eligible device on the same day.
Point-in-time Restore can return applications, settings, and personal files to a recent captured state, using an approximate default 24-hour capture interval and retention of up to 72 hours by default. Microsoft says it is enabled by default on Home and eligible Pro systems with an operating-system drive of at least 200GB. Its short window and broad scope make it a restoration capability, not a substitute for independently maintained backups.
The update-pause limit of 35 days offers more room than the former fixed 7-, 14-, and 21-day blocks, but it does not extend Windows lifecycle dates. Windows 11 24H2 Home and Pro still reach the end of updates on October 13, 2026.
Secure Boot certificate delivery also continues through Windows Update. Microsoft says affected PCs can continue booting and receiving standard updates, so the transition should not be described as an immediate universal failure event.
The practical verdict remains straightforward: install KB5095093 through Windows Update, test verified gradual-rollout features on each relevant device, preserve independent backups, and complete 24H2 Home and Pro upgrade planning before October 13, 2026.
The report also clarifies that the redesigned Start menu is now available to commercial and managed devices. Other newly documented changes include Phone Link call-routing improvements, GIPHY replacing Tenor as the emoji panel’s GIF provider, and a Graphics Kernel change allowing PCs with more than 32GB of RAM to run larger local AI models.
Point-in-time Restore can reportedly use up to 50GB of local storage, with capture frequency configurable as often as every four hours. Restoring a captured state reverses subsequent changes—including files, passwords, and certificates—so independent backups remain essential.
Windows Latest further confirms that the update-pause limit was already 35 days. The new feature is a calendar control for selecting an exact end date, replacing the less convenient fixed weekly choices.
The update also adds SHA-2 certificate-thumbprint support for Remote Desktop, while retaining SHA-1 compatibility for older deployments. Administrators should begin migrating toward SHA-256 certificates and review the expanded Group Policy controls for .rdp files.
Additional security changes enforce stricter registration requirements for third-party TDI network transports. Applications relying on unregistered transports may stop working until their networking components are updated, making compatibility testing important for organizations with older VPN, filtering, or network-management software.
KB5101650 also updates Windows’ bundled curl utility to version 8.21.0 and expands Microsoft’s targeted delivery of replacement Secure Boot certificates to more devices considered compatible.
The update also improves AirPods pairing visibility, Beats Studio Pro microphone reliability, and Bluetooth audio reconnection after waking from sleep. Users affected by these specific Bluetooth issues should install KB5101650 and retest their devices.
The update also changes how Windows unregisters and cleans up hotkeys. Microsoft warns that, in rare cases, built-in Windows experiences relying on the previous hotkey lifecycle may temporarily stop responding to certain keyboard shortcuts. Restarting the affected application should normally restore shortcut functionality; unresolved cases can be reported through Feedback Hub.
Administrators should add KB5099414 and build 22631.7376 to July compliance checks for remaining supported 23H2 devices. They should also include keyboard-shortcut testing for critical Windows workflows after deployment, particularly on shared workstations or systems that depend heavily on hotkeys.
According to the report, Microsoft had not listed any known issues specifically associated with these July updates at publication time. That status can change as deployment expands, so IT teams should continue monitoring Microsoft’s release-health information rather than treating the initial absence of known issues as a guarantee.
What changed / what to do now
- Install KB5095093 from Settings > Windows Update.
- Do not mistake Point-in-time Restore for a backup; its default capture and retention windows are short.
- Plan upgrades for Windows 11 24H2 Home and Pro before October 13, 2026.
- Test gradual-rollout features on each device rather than assuming that installation of the KB makes every feature immediately available.
Notebookcheck describes KB5095093 as a substantial summer update. For WindowsForum readers, the practical priorities are narrower: confirm whether the update and its gradually released features have reached each PC, understand the limits of Point-in-time Restore, keep the Windows 11 24H2 support deadline visible, and use the expanded update-pause allowance as a testing tool rather than a long-term maintenance strategy.
Point-in-time Restore Adds a Short-Term Recovery Option
Point-in-time Restore can return a PC—including its applications, settings, and personal files—to a recently captured state.Microsoft says Point-in-time Restore uses the Volume Shadow Copy Service, or VSS, to capture the PC’s state. Snapshots are created at an approximate default interval of every 24 hours and retained for up to 72 hours by default.
That short retention window defines the feature’s limits. A recent captured state may be available only briefly, and restoring the machine can affect applications, settings, and personal files. Point-in-time Restore therefore does not replace a separate backup that preserves data for longer periods or remains available when the PC or its local storage cannot be used.
Microsoft says the feature is enabled by default on Home and eligible Pro systems when the operating-system drive has a capacity of 200GB or more. The available information does not establish a default posture for every enterprise-managed configuration, so administrators should verify actual behavior on their own devices rather than assuming that all editions and management states are identical.
The supplied release information establishes the feature’s availability, scope, approximate default capture interval, default retention period, VSS foundation, and drive-capacity condition. It does not provide a verified entry path or complete invocation procedure. This article therefore explains Point-in-time Restore’s availability and limits rather than inventing steps for opening it, selecting a restore state, or restarting the PC. Users should follow Microsoft’s current on-screen guidance or official documentation when performing an actual restoration.
Restoration Can Reverse Recent Local Changes
The defining characteristic of Point-in-time Restore is that it returns the machine to an earlier captured state. Because applications, settings, and personal files are included, users need to understand that recent local work may be affected.That is the main operational warning WindowsForum readers should carry forward. The feature’s broad scope means it should not be invoked casually. Support documentation should explain what the selected captured state represents and distinguish restoration from file recovery and long-term data protection.
The available facts support an approximate 24-hour capture interval and retention of up to 72 hours by default. They do not justify treating either number as a guaranteed recovery point for every incident. The useful restore state may predate recent work, and no suitable state should be assumed to exist without checking the device.
A concise support description is therefore:
- Point-in-time Restore: A short-term method for returning the PC, applications, settings, and personal files to a recent captured state.
- Backup: A separately maintained copy intended for longer retention, historical recovery, or recovery when the original PC or drive is unavailable.
Update Pauses Still Have a 35-Day Limit
KB5095093 changes the Windows Update pause experience from the previous fixed blocks of 7, 14, or 21 days. The verified limit is a maximum pause of 35 days, with the control available under Settings > Windows Update.
The expanded limit can be useful when a user or administrator needs additional time to test the cumulative update or confirm compatibility. It should not be interpreted as a reason to defer security updates for the full period by default. The appropriate pause is the shortest interval that addresses the identified testing need.
The timing also matters because Windows 11 version 24H2 Home and Pro will reach the end of updates on October 13, 2026. Pausing a cumulative update does not extend the support lifecycle of the installed Windows release. PCs approaching that date need an upgrade plan rather than a longer pause.
| Windows 11 group | Covered by KB5095093 | Verified support milestone |
|---|---|---|
| Version 25H2 | Yes | No 25H2 end date is asserted here |
| Version 24H2 Home and Pro | Yes | Updates end October 13, 2026 |
| Version 24H2 Enterprise and Education | Yes | Support ends October 12, 2027 |
The table also shows why an inventory entry that says only “Windows 11 24H2” is incomplete. Home and Pro have a different support milestone from Enterprise and Education, so edition affects upgrade urgency.
Secure Boot Certificate Delivery Continues
Microsoft’s release information again addresses the expiration of Secure Boot certificates used by most Windows devices. That transition began in June 2026, and Microsoft says newer certificates are being delivered through Windows Update to consumer and non-managed business PCs. Delivery will continue over the coming months.Microsoft also says affected devices can continue booting and receiving standard Windows updates. The expiration notice should therefore not be presented as a claim that every PC without a replacement certificate will immediately stop starting or updating.
The supported takeaway is more precise: Secure Boot certificate delivery is an ongoing part of Windows servicing, the transition is not completed everywhere at once, and continued delivery through Windows Update gives users another reason to keep supported devices current.
That information does not establish a universal firmware-deployment procedure or a single certificate-audit workflow for every organization. Hardware models, management tools, and deployment practices vary, and the release information does not support prescribing one process for all environments.
Timeline
June 2026 — Secure Boot certificates used by most Windows devices begin expiring while Microsoft continues distributing updated certificates.July 14, 2026 — Microsoft delivers the Patch Tuesday release identified as KB5095093 for Windows 11 versions 25H2 and 24H2.
October 13, 2026 — Windows 11 version 24H2 Home and Pro reach the end of updates.
October 12, 2027 — Windows 11 version 24H2 Enterprise and Education reach the end of support.
Accessibility and Widgets Receive Visible Changes
KB5095093 includes several changes users may notice immediately, although gradual rollout means they may not appear on every updated PC at the same time.Widgets no longer open merely because the pointer passes over them. Notifications and taskbar badges are minimized by default. On first use, Widgets opens to its dashboard, where icons can display alert counts and badges clear after the user leaves a dashboard.
For users who want a full-screen color overlay, Screen Tint is available at:
Settings > Accessibility
Microsoft presents Screen Tint as an accessibility option intended to improve readability and reduce eye strain. Because its usefulness depends on the individual user, it is best treated as an optional display aid rather than a universal color-management setting.
Magnifier also gains controls that allow a zoom percentage to be entered directly and increments to be adjusted from the Magnifier interface. These changes reduce the need to move between Magnifier and the broader Settings application when selecting a preferred enlargement level.
Voice access and voice typing expand to French, German, and Spanish. Those additional language options are the significant verified change; broader claims about correction, grammar, punctuation, recognition in background noise, or other speech-processing behavior should not be inferred from the language expansion alone.
File Explorer Changes Focus on Entra Actions and Address Input
File Explorer receives new quick actions for work and school accounts using Microsoft Entra ID. When users hover over a file, available actions can include Open file location and Ask Copilot.The address bar also accepts some less conventional path input containing double backslashes or quotation marks. Microsoft provides examples such as:
Code:
C:\\Users\\user
"C:\Users\user"Microsoft also identifies improved explorer.exe reliability. That wording should not be expanded into claims about unspecified File Explorer fixes or particular launch, storage, cloud-sync, renaming, taskbar, or shortcut scenarios that are not documented in the available facts.
For organizations using the Entra ID quick actions, gradual rollout is especially relevant. Two devices can have the same cumulative update installed while only one currently exposes a newly released action. Help-desk guidance should therefore distinguish between “KB5095093 is installed” and “this feature has been enabled on this device.”
Bluetooth, Networking, and Printing Receive Targeted Work
The Bluetooth fixes include concrete issues involving AirPods and Beats Studio Pro headphones. Microsoft also addresses Bluetooth error 0x9F and a device-removal problem that could display the message “Remove failed.”These are specific fixes rather than a general promise that every Bluetooth issue has been resolved. Testing should focus on the affected devices and workflows that matter in the local environment without extending the release notes into claims about unrelated Bluetooth behavior.
The networking work names several areas: Confidential Virtual Machines, SR-IOV, Windows Subsystem for Linux mirrored networking with VPNs, Wi-Fi, WWAN, IPv6 VPNs, and third-party VPN software. The release information identifies those areas, but it does not establish that every configuration-specific networking problem has been corrected.
Printing receives a concrete configuration change. New printer installations prefer Internet Printing Protocol when it is supported. Administrators can control the behavior at:
Settings > Bluetooth & devices > Printers & scanners > Default install printers using Windows Ready Print
The setting reflects a preference for IPP when compatible equipment is available. Administrators should verify the selected preference and the resulting installation behavior on the devices and printers they actually support.
Touchpad Behavior Becomes More Adjustable
KB5095093 provides a setting for adjusting the touchpad’s right-click zone. Users can find it at:Settings > Bluetooth & devices > Touchpad
The adjustment requires a touchpad with a pressable surface. That hardware qualification matters: the option should not be expected to provide the same behavior on every touchpad design.
For users who frequently trigger the wrong click near the lower portion of a compatible touchpad, the setting provides a direct place to tune the right-click area without relying on an undocumented registry change or a vendor-specific utility.
Other Named Components Receive Fixes
Microsoft’s change list also names the Background Intelligent Transfer Service, Japanese handwriting recognition, and location settings.Those references identify affected components but do not support broader performance claims or detailed conclusions about every transfer, handwriting-recognition result, or location-related behavior. For WindowsForum readers troubleshooting one of those areas, the presence of a named change is a reason to install KB5095093 and retest the relevant workflow. It is not a guarantee that every superficially similar problem has the same cause.
Gradual Rollout Means Installation and Availability Can Differ
Microsoft divides the release between gradual rollout and normal rollout. A normal rollout broadly makes an update available to eligible devices at the same time. A gradual rollout releases features in phases, so availability can vary by device.As a result, two PCs can both report that they are current while showing different interfaces or features. Installing KB5095093 does not necessarily make every item in the release notes visible immediately.
This distinction affects testing, screenshots, training material, and help-desk scripts. A test PC may receive a new Widgets behavior, Entra File Explorer action, accessibility option, or other gradually released feature before another device running the same Windows version.
To verify the update, open:
Settings > Windows Update
Check for updates, install KB5095093 when offered, and complete any required restart. Then confirm the specific feature instead of relying only on the KB number. For Screen Tint, check Settings > Accessibility. For printer defaults, check Settings > Bluetooth & devices > Printers & scanners > Default install printers using Windows Ready Print. For the touchpad right-click zone, check Settings > Bluetooth & devices > Touchpad and remember that a pressable touchpad surface is required.
Notebookcheck presents KB5095093 as the July 14 Patch Tuesday package, while Microsoft’s servicing information distinguishes between normal and gradual feature availability. Those descriptions are compatible: the release begins availability, but not every included feature must appear on every eligible device on the same day.
WindowsForum-specific test matrix
This matrix is deliberately limited to verified affected areas. Record results by device because gradual rollout can produce differences even where the Windows version and installed KB match.| Verified area | Test on | What WindowsForum recommends checking |
|---|---|---|
| Screen Tint | Devices used for accessibility validation | Confirm whether Screen Tint appears under Settings > Accessibility and whether the overlay can be enabled and disabled |
| Widgets | Devices used for taskbar and dashboard testing | Confirm that pointer pass-over does not open Widgets; check dashboard opening behavior, alert counts, and badge clearing |
| Entra File Explorer actions | Work or school devices signed in with Microsoft Entra ID | Hover over an appropriate file and record whether Open file location and Ask Copilot are available |
| Printer IPP preference | Devices used to install supported printers | Check Default install printers using Windows Ready Print and verify the preference used for a new printer installation |
| Pressable-touchpad right-click zone | Laptops with a pressable touchpad surface | Confirm that the right-click-zone adjustment is present and that the selected zone behaves as configured |
| Business-critical VPN and WSL workflows | PCs that depend on VPN connectivity or WSL mirrored networking | Run the organization’s normal connection and WSL workflow and record any change after installation |
| Business-critical Bluetooth workflows | PCs using supported Bluetooth peripherals, especially affected AirPods or Beats Studio Pro devices | Test the required workflow and check whether error 0x9F or the “Remove failed” removal problem still occurs |
Action checklist for admins
- Install KB5095093 from Settings > Windows Update and record the Windows version and edition.
- Plan upgrades for 24H2 Home and Pro PCs before October 13, 2026.
- Describe Point-in-time Restore as short-term restoration, not as backup.
- Verify gradually released features per device before publishing support instructions.
- Run the WindowsForum-specific matrix for Screen Tint, Widgets, Entra File Explorer actions, printer IPP preference, the pressable-touchpad right-click zone, and business-critical VPN, WSL, and Bluetooth workflows.
- Use the update pause only when testing requires it and keep the pause within the verified 35-day maximum.
What Windows Teams Should Carry Forward
KB5095093 applies to Windows 11 versions 24H2 and 25H2, but installation alone does not prove that every gradually released feature is active. Users and administrators should check Windows Update, verify the specific capabilities they expect, and document differences between otherwise similar devices.Point-in-time Restore can return applications, settings, and personal files to a recent captured state, using an approximate default 24-hour capture interval and retention of up to 72 hours by default. Microsoft says it is enabled by default on Home and eligible Pro systems with an operating-system drive of at least 200GB. Its short window and broad scope make it a restoration capability, not a substitute for independently maintained backups.
The update-pause limit of 35 days offers more room than the former fixed 7-, 14-, and 21-day blocks, but it does not extend Windows lifecycle dates. Windows 11 24H2 Home and Pro still reach the end of updates on October 13, 2026.
Secure Boot certificate delivery also continues through Windows Update. Microsoft says affected PCs can continue booting and receiving standard updates, so the transition should not be described as an immediate universal failure event.
The practical verdict remains straightforward: install KB5095093 through Windows Update, test verified gradual-rollout features on each relevant device, preserve independent backups, and complete 24H2 Home and Pro upgrade planning before October 13, 2026.
Update: July Patch Tuesday identified as KB5101650 (July 14, 2026)
Windows Latest’s hands-on report identifies the mandatory July 2026 Windows 11 update as KB5101650, not KB5095093 as stated earlier. It advances Windows 11 25H2 to OS build 26200.8875 and Windows 11 24H2 to build 26100.8875. Users and administrators should use KB5101650 and these build numbers when checking deployment status, inventories, and support records.The report also clarifies that the redesigned Start menu is now available to commercial and managed devices. Other newly documented changes include Phone Link call-routing improvements, GIPHY replacing Tenor as the emoji panel’s GIF provider, and a Graphics Kernel change allowing PCs with more than 32GB of RAM to run larger local AI models.
Point-in-time Restore can reportedly use up to 50GB of local storage, with capture frequency configurable as often as every four hours. Restoring a captured state reverses subsequent changes—including files, passwords, and certificates—so independent backups remain essential.
Windows Latest further confirms that the update-pause limit was already 35 days. The new feature is a calendar control for selecting an exact end date, replacing the less convenient fixed weekly choices.
Update: KB5101650 fixes Office launch failures and strengthens Remote Desktop security (July 14, 2026)
TheWinCentral reports that KB5101650 resolves an Office compatibility problem introduced by June update KB5094126. Some third-party applications using OLE Automation could not launch Microsoft Office or open Office documents. Businesses affected by that regression should install the July update and retest their integrations.The update also adds SHA-2 certificate-thumbprint support for Remote Desktop, while retaining SHA-1 compatibility for older deployments. Administrators should begin migrating toward SHA-256 certificates and review the expanded Group Policy controls for .rdp files.
Additional security changes enforce stricter registration requirements for third-party TDI network transports. Applications relying on unregistered transports may stop working until their networking components are updated, making compatibility testing important for organizations with older VPN, filtering, or network-management software.
KB5101650 also updates Windows’ bundled curl utility to version 8.21.0 and expands Microsoft’s targeted delivery of replacement Secure Boot certificates to more devices considered compatible.
Update: KB5101650 adds Widgets memory and Bluetooth refinements (July 14, 2026)
Thurrott reports that KB5101650 reduces Widgets’ default memory footprint, particularly on lower-memory PCs, alongside the previously documented quieter notification and hover behavior.The update also improves AirPods pairing visibility, Beats Studio Pro microphone reliability, and Bluetooth audio reconnection after waking from sleep. Users affected by these specific Bluetooth issues should install KB5101650 and retest their devices.
Update: July patch also reaches Windows 11 23H2 (July 14, 2026)
Windows Report confirms that Microsoft’s July 2026 Patch Tuesday release also covers Windows 11 version 23H2 through KB5099414, advancing supported systems to OS build 22631.7376. The previously documented KB5101650 remains the update for versions 24H2 and 25H2.The update also changes how Windows unregisters and cleans up hotkeys. Microsoft warns that, in rare cases, built-in Windows experiences relying on the previous hotkey lifecycle may temporarily stop responding to certain keyboard shortcuts. Restarting the affected application should normally restore shortcut functionality; unresolved cases can be reported through Feedback Hub.
Administrators should add KB5099414 and build 22631.7376 to July compliance checks for remaining supported 23H2 devices. They should also include keyboard-shortcut testing for critical Windows workflows after deployment, particularly on shared workstations or systems that depend heavily on hotkeys.
According to the report, Microsoft had not listed any known issues specifically associated with these July updates at publication time. That status can change as deployment expands, so IT teams should continue monitoring Microsoft’s release-health information rather than treating the initial absence of known issues as a guarantee.
References
- Primary source: Notebookcheck
Published: 2026-07-14T10:03:00+00:00
Microsoft's July 2026 Patch Tuesday is here - Notebookcheck News
Microsoft's July 14 Patch Tuesday update brings Point-in-Time Restore, a redesigned pause updates feature, and the final Kerberos RC4 enforcement phase for Windows 11.
www.notebookcheck.net
- Related coverage: windowscentral.com
Windows 11’s huge July 14 update is loaded with new features — these are the 13 that matter most | Windows Central
Windows 11's July 2026 update is bigger than expected, bringing a new recovery feature, long-requested update controls, and many improvements.www.windowscentral.com - Related coverage: tomshardware.com
Microsoft rushes out emergency Windows 11 patch after botched update breaks Recovery — restores USB keyboard and mouse input inside WinRE for Windows 11 versions 24H2 and 25H2 | Tom's Hardware
KB5070773 fixes a WinRE bug introduced by October’s cumulative update.www.tomshardware.com
Last edited:
