Win Update KB5124010 Windows 11 Cumulative Update Preview build 26100.9550 (24H2), 26200.9550 (25H2), and 26300.9550 (26H2) - Sept. 22


UPDATE 9/29:


 Microsoft Support:

This cumulative update for Windows 11, versions 26H2, 25H2, and 24H2 (KB5124010), includes production-quality improvements.

Announcements and messages​

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Windows Secure Boot certificate expiration

Important:
Secure Boot certificates used by most Windows devices started to expire in June 2026. Microsoft has been updating these certificates on consumer and non-managed business devices over the past several months. Devices that haven’t received the newer certificates will continue to start and operate normally, and standard Windows updates will continue to install. Updated certificates will continue to be delivered through Windows Update in the coming months. For more information, see Windows Secure Boot certificate expiration and CA updates.

End of updates
Windows 11, version 24H2 Home and Pro editions will reach end of updates on October 13, 2026. Devices running these editions will no longer receive fixes for known issues, time zone updates, technical support, or monthly security and preview updates containing protections from the latest security threats. Enterprise and Education editions remain supported until October 12, 2027.

To stay protected and up to date, we recommend you upgrade to the latest version of Windows 11.

Change log:

Change date​
Change description​
September 29, 2026Added "Devices might experience a black screen or desktop loading issues after sign-in" to Known Issues

Highlights​

This update is available through two release phases: gradual rollout and normal rollout. A gradual rollout delivers an update in phases, so features reach devices over time instead of all at once, meaning availability varies by device. A normal rollout is the broad release to all eligible devices at the same time, usually when it reaches general availability (GA).

Note If you installed earlier updates, your device downloads and installs only the new updates contained in this package.


 Gradual rollout

The following summary outlines new Windows 11 PC experiences, along with improvements and fixes. The bold text within the brackets indicates the item or area of the change.
  • [File Explorer]
    • New! This update adjusts how the preview pane handles files downloaded from the web. For HTML files, a new Preview anyway button lets you acknowledge the warning and preview the file. Non-HTML files, such as PDFs, are now previewed automatically.
    • New! File Explorer Home now preserves the state of sections (expanded or collapsed), so you can pick up where you left off.
    • New! This update improves the reliability of thumbnail previews for cloud files in the Details pane. The pane has also been reorganized so file properties are easier to find and review at a glance.
    • New! The update addresses an issue that could clear the address bar contents when entering edit mode by clicking near the right side of the address bar.
  • [Emoji]
    • New! This update adds support for Emoji 17.0, including new emoji such as distorted face, fight cloud, and hairy creature. To insert them, press Windows + . to open the emoji panel.
    • New! This update also refines the design of several existing emoji for better consistency across platforms, including saluting face, face with peeking eye, goose, lotus, and kissing cat.

  • [Widgets] New! This update introduces the Tips widget, which provides short, helpful guidance about Windows features. To add it to your Widgets board, open the board, select Add widgets, and then choose Tips. To add it to your lock screen, go to Settings > Personalization > Lock screen and add Tips to your lock screen widgets.

  • [Personalization] This update includes a variety of improvements to desktop background experiences.
    • This update improves the reliability of the Personalization > Background page in Settings.
    • This update adds support for using DIB image files as desktop backgrounds.
    • This update improves reliability of desktop slideshow transitions on newly created accounts.
    • This update improves resolution of previews when selecting a desktop background in Personalization > Background.
    • This update improves desktop background preview display in Settings for users with portrait mode monitors.
    • This update improves reliability of processing desktop wallpaper changes when they happen in quick succession.
    • This update adds support for using slideshow wallpapers with multiple desktops, so that it won’t automatically switch you back to Picture.

  • [Bluetooth]
    • This update contains several enhancements to improve reliability and experience when connecting to and using Bluetooth devices:
      • During voice calls, the Windows shell volume flyout now appears when adjusting the volume of a Bluetooth Classic Audio accessory via the volume controls on the accessory, providing visual feedback of the new volume level.
      • This update improves the accuracy of the connection state displayed by Windows for accessories that have disconnected from the PC.
      • This update improves stability of the Bluetooth and devices page in Settings when managing Bluetooth and audio devices.
      • This update resolves an issue where the Bluetooth radio could be turned off, but the state of the radio control toggle in the Bluetooth and devices page in Settings shows as on.
    • This update improves Bluetooth audio stability and compatibility:
      • This update improves microphone compatibility with certain Bluetooth Classic audio accessories.
      • This update resolves an issue that could result in a crash (error code 0x139) while streaming Bluetooth audio.
      • This update improves reliability and performance with LE Audio accessories.
      • This update improves the reliability of shared audio.

  • [Accessibility]
    • New! This update introduces Open apps maximized, an accessibility setting that automatically maximizes app windows as they open. It removes a bit of everyday friction whether you use a screen reader or magnification, work in tablet mode, or simply prefer a consistent, full-screen workspace. To turn it on, go to Settings > Accessibility > Visual effects and turn on Open apps maximized.

    • This update improves navigation of the Bluetooth quick settings page when using keyboard input, gamepad input, or Narrator.
  • [Magnifier]
    • New! This update brings a modernized visual refresh to the Magnifier taskbar.
      • Updated icons Magnifier's toolbar icons align with Windows 11 visual design, giving the tool a cleaner, more modernized feel.
      • Refined spacing and padding The padding is adjusted with spacing across the toolbar for a more polished, consistent layout.
    • Views, zoom controls, keyboard shortcuts, and Read Aloud all behave exactly as they did in earlier versions.
  • [Settings]
    • This update improves the reliability of Settings when interacting with the contents of the Settings > Bluetooth & Devices > Printers & Scanners page.
    • This update updates Settings > Apps > Installed apps to show the version number at the top level for packaged apps, as it already does for other apps.

    • This update improves the time picker control in Settings so that it reflects your preferred time format when you switch between 12-hour and 24-hour time. This applies in places such as setting active hours and scheduling Night light.
    • This update improves persistence of the Allow multiple apps to use camera at the same time option in Settings > Bluetooth & Devices > Camera settings.

  • [Touchpad]
    • New! Additional gesture controls for precision touchpads are available in Settings > Bluetooth & devices > Touchpad:
      • Single-finger scrolling — Scroll vertically with one finger starting from the left or right side of the touchpad.

      • Automatic scrolling — Keep scrolling without lifting your fingers by moving them near the edge of your touchpad while scrolling.

    • Previously, gesture controls for scroll and zoom speed and accelerate scrolling were released in the July 2026 update (KB5101684).

  • [Copilot key] New! This update introduces a new Windows 11 setting that lets you remap the Copilot key to function as the Right Ctrl or Context Menu key, helping preserve familiar keyboard shortcuts and accessibility workflows. For more information, see Understand updates to the Copilot key on Windows devices.

  • [Camera roll]1 New! This update introduces Camera roll backup in Settings, helping eligible users protect their photos with OneDrive. You can turn on the feature from the Settings Home or Accounts page and complete setup on a mobile phone using a QR code.
  • [Fonts]
    • New! This update adds support for the Garay and Beria Erfe scripts to the Ebrima font, the first Microsoft font to support both. Garay was encoded in Unicode 16.0 and Beria Erfe in Unicode 17.0.
    • New! This update also refines the Adlam glyph designs in Ebrima to align with the current Unicode standard and improve consistency.
  • [Windows Recovery (WinRE)]
    • New! This update enables WinRE to automatically reuse eligible Wi-Fi profiles already saved in Windows, including supported certificate-based networks. Devices can now get online automatically during recovery scenarios such as quick machine recovery or cloud rebuild, without preconfiguring Wi-Fi credentials in WinRE. This capability is on by default, and IT admins can disable it. For more information, see Windows Recovery Environment (Windows RE).
    • New! This update adds a recovery remote management plug-in for extending WinRE management capabilities for MDM providers. For more information, see Recovery Remote Management Overview.
  • [Kiosk mode]
    • The Windows + Tab keyboard shortcut is now disabled when using a restricted UX kiosk.
    • The Windows + A and Windows + C keyboard shortcuts are now disabled when using single-app kiosk mode.
  • [Windows Backup]
    • PC-to-PC Migration is no longer available. This feature, introduced through a phased rollout, previously allowed you to transfer files and settings directly from your previous PC when setting up a new Windows PC. To back up and restore your files, settings, and other supported items when moving to a new PC, use Windows Backup. For more information, see Backup and restore with Windows Backup.

  • [Power and battery] This update improves display and performance in certain scenarios where a plugged-in laptop incorrectly detects a transition from AC power to battery power.
Notes
  1. Feature availability depends on your device and market.

 Normal rollout

This non-security update includes quality improvements. The following summary outlines key issues addressed by the KB update after you install it. Also, included are available new features. The bold text within the brackets indicates the item or area of the change.
  • [Camera] This update addresses an issue where the built-in camera might stop working in the Camera app and other apps that use the camera.
  • [File History] This update addresses an issue where File History might fail to back up or restore files to an external drive or network location. Affected devices might incorrectly display a “Reconnect your drive” message even when a compatible backup drive is connected and working properly.
  • [System Monitor (Sysmon)]
    • This update fixes an issue with header validation for executable files. Truncated or malformed files could cause unpredictable memory use and result in unreliable tampering detection.
    • This update fixes an issue with the Sysmon file system filter driver. If the archive directory failed to open during file monitoring, closing an uninitialized handle could cause a stop error.
    • This update fixes an issue with process tampering detection. Sysmon incorrectly generated Event ID 25 alerts for the Windows Session Manager (smss.exe) process.

Components updates​

AI components
This release updates the following AI components to version 1.2608.951.0: Image Search, Content Extraction, Semantic Analysis, and Settings Model.

To learn more, see Release information for AI components.

Servicing stack update (SSU)
Includes KB5124009 (Build 26100.9539), which improves the reliability of the Windows update installation process. To learn more about SSUs, see Simplifying on-premises deployment of servicing stack updates.

Known issues in this update​

Symptoms

After installing the August 2026 Windows non-security preview update KB5120998 and subsequent updates, some devices might experience desktop loading issues. This issue has been primarily observed on Azure Virtual Desktop (AVD) hosts using FSLogix. This issue appears to occur more frequently with some existing user profiles.

Affected users might see a black screen after sign-in, with the desktop session failing to load automatically. In some cases, users might be unable to access their desktop until the desktop session is started manually. Application event logs might also show Windows Explorer crashes.

Workaround

Affected customers can apply one of the following workarounds to mitigate the issue:
  1. Manually launch explorer.exe: Users can temporarily mitigate this issue by opening Task Manager (Ctrl+Shift+Esc), selecting Run new task, entering explorer.exe, and selecting OK.
  2. Mitigate through Known Issue Rollback (KIR): This issue is mitigated using Known Issue Rollback (KIR).
For enterprise-managed devices where Windows updates are managed by IT departments, IT administrators can apply the KIR by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > Group Policy name listed below

Group Policy downloads with Group Policy name:

Important

You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting. Note that this Group Policy will disable the change causing this issue until a resolution is released in a future Windows update.
For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback

Resolution

We are working on a resolution for this issue, and it will be released in a future Windows update.

Symptoms

After installing the September 8, 2026, Windows security update (KB5124008), or later updates, some Credential Guard protected machine accounts might lose their secure channel with an on-premises Active Directory (AD) domain. Users might then be unable to sign in interactively with valid domain credentials and might receive a message stating that the trust relationship between the device and the domain failed. Offline sign-in using previously cached credentials might continue to work. AD replication and AD services on the domain controllers are not affected.

This issue occurs because KB5124008 and later updates enable the Machine Identity Isolation feature. While the update does not directly enable Machine Identity Isolation enforcement, it does cause Windows to begin honoring any existing or policy-provisioned settings that enabled Machine Identity Isolation enforcement. However, this feature is only supported for environments connected to domain controllers running at a Windows Server 2025 Domain Functional Level (DFL) and above. The feature should be disabled elsewhere. Any devices previously configured to use Machine Identity Isolation that are not connected to Windows Server 2025 domain controllers will experience this issue and will need to disable the feature.

Workaround

Important: This section contains information about modifying the registry. Before you modify the registry, back it up and make sure that you know how to restore it if a problem occurs. For more information, see How to back up and restore the registry in Windows.

To work around this issue, disable Machine Identity Isolation using the same management method that was used to enable it. Choose the applicable option below:
  1. If Machine Identity Isolation was enabled by Intune policy, disable Machine Identity Isolation with Intune.
  2. If Machine Identity Isolation was enabled by Group Policy, disable Machine Identity Isolation with Group Policy.
  3. If Machine Identity Isolation was enabled directly in the registry, use these steps to disable it:
    • On the Windows 11, version 24H2 or 25H2 device, locate the following registry paths:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MachineIdentityIsolation

      HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard\MachineIdentityIsolation
    • For either of these registry keys, if the value of MachineIdentityIsolation is set to 2, change it to:

      MachineIdentityIsolation = 0
After you disable Machine Identity Isolation, restart the device.

Then reset the secure channel using the following command:

Test-ComputerSecureChannel -Repair -Credential (Get-Credential)

Resolution

Microsoft plans to resolve this issue in a future Windows update by temporarily preventing Machine Identity Isolation enforcement while improvements are made to the feature.

Symptoms

After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms:
  • The device displays an error in Device Manager: "This device cannot start (Code 10)."
  • No audio output.
  • Volume controls are unresponsive or remain at zero.
  • Sound settings are unresponsive or unavailable.
This issue is limited to USB Audio Class 1.0 devices.

Resolution

Microsoft is working on a resolution and will update this documentation when more information is available.

How to get this update​

Before you install this update​

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Deployment​

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note: The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:
  • Use the Update WinPE script to update an existing Windows image. (Recommended)
  • Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.
For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update​

To install this update, use one of the following Windows and Microsoft release channels.

AvailableNext Step
Available
Open Start
windowslogo.png
> Settings
settings.png
> Windows Update > Advanced options > Optional updates. In the Optional updates available area, you will find the link to download and install available updates.
Check for optional updates
Available
To install this update, download the standalone package(s) for this update from the Microsoft Update Catalog. This update contains MSU files that require installation in a specific order. Follow the Arm64 installation instructions or x64 installation instructions, as appropriate.
If you install additional Dynamic Update packages, use versions from the same release month as this update. If a Safe OS Dynamic Update or Setup Dynamic Update is not available for the same release month, use the most recently released version.
Note This latest cumulative update includes updates for AI components. AI components are applicable only to Copilot+ PCs and will not install on other Windows client PCs or Windows Server.

File information​

For a list of the files provided in this update, download the file information for cumulative update KB5124010.

For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5124009) - version 26100.9539.


 Source:



Check Windows Updates


UUP Dump:

64-bit ISO download:

ARM64 ISO download:

 
Last edited:
Just to be real; There is nothing changed under the hood since 24H2. Feature may be added but all packages inside the Component Store are still called 26100.xxxx. That was the case with 25H2 and now with 26H2. The only thing they changed is the Build version from 26100 -> 26200 -> 26300.
My current 26H2 26300.9550 build is just the same as yesterday before the "Update" as 25H2 26200.9550. Old wine into new bags....
With each update they are all ment for 26100.xxxx, 26200.xxxx and now 26300.xxxx.

Update history 24H2: Windows 11, version 24H2 update history | Microsoft Support
Update history 25H2: Windows 11, version 25H2 update history | Microsoft Support
Update history 26H2: Windows 11, version 26H2 update history | Microsoft Support


That CBS-bug that was introduced with 26200.8655 is still present with 26200.9550 and now with 26300.9550. And it will say there until MS is solving this issue. Until now they are apparently stone deaf and just don't care. This will not change.... It is an illusion that any OS would be bug free...
Oh, I know...I'm aware that as they share a common servicing branch and the underlying codebase is already there. As such, I'm one Windows Update and an eKB Enablement Package away from turning on 26H2 if I so choose, which 'should' happen w/o much fanfare. It's just that the track record for Windows Updates has been well, a bit spotty and Microsoft can't seem to get it right lately, or as you indicate, they just don't care. Regardless, I'd rather avoid the drama and not inject known issues into my machines if I can avoid it. I currently have a three machines that dual-boot Linux Mint & Windows 11 on unsupported hardware. Right now they all work just fine, and I've got options if I feel I should hold off on an update. Plus, I'd like to see whether the jump to 26H2 makes sense on my unsupported hardware vs moving to 25H2 first, not to mention that the 'Feature Update Lottery' means there's no guarantee you get all the cool new stuff they promised if you update anyway. Lacking some sort of ZeroDay vulnerability that forces me to update, I'm in no rush. YMMV
 

My Computers My Computers

  • At a glance

    Windows 11 Pro 24H2 Linux Mint 22.2Intel® Core i7-10850H64 GB DDR4-3200MHzNVIDIA Quadro® T2000
    OS
    Windows 11 Pro 24H2 Linux Mint 22.2
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkPad P1
    CPU
    Intel® Core i7-10850H
    Memory
    64 GB DDR4-3200MHz
    Graphics Card(s)
    NVIDIA Quadro® T2000
    Screen Resolution
    4K (3840x2160)
  • At a glance

    Windows 11 Pro 24H2Intel® Core I9-10850KG.Skill Trident Z 32GB CL16 DDR4-3600MHz | Sa...EVGA | NVIDIA GeForce RTX 3080 Ti FTW3 Ultra ...
    Operating System
    Windows 11 Pro 24H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    NHRacecraft Custom Build
    CPU
    Intel® Core I9-10850K
    Motherboard
    ASUS ROG Maximus XII Hero | Z490
    Memory
    G.Skill Trident Z 32GB CL16 DDR4-3600MHz | Samsung B-Die
    Graphics card(s)
    EVGA | NVIDIA GeForce RTX 3080 Ti FTW3 Ultra Gaming
    Sound Card
    ROG SupremeFX S1220
    Monitor(s) Displays
    Samsung G6 G60SF 27" 500Hz OLED Gigabyte AORUS CV27Q-SA 27" LED HP Development Z24q G3 24" LED
    Screen Resolution
    2K QHD (2560x1440)
    Hard Drives
    Samsung 500GB 980 Pro M.2 PCIe 4.0 x4 NVMe
    Samsung 2TB 980 Pro M.2 PCIe 4.0 x4 NVMe
    Samsung 2TB 860 Pro 2.5" SATA III SSD
    Western Digital 4TB WD Black 3.5" SATA III HDD
    PSU
    Seasonic Prime PX-850 Platinum 850W
    Case
    Razer Tomahawk ATX Mid-Tower w/ Fractal Design Flex B-20 Vertical GPU
    Cooling
    NZXT Kraken Z53 Liquid AIO
    Keyboard
    IQUNIX Zonex 75 Custom
    Mouse
    Logitech G PRO X Superlight 2
    Internet Speed
    Fidium Fiber 2.2Gbps Symmetrical
    Browser
    Firefox ESR | Brave
    Antivirus
    Windows Defender
  • Lenovo ThinkPad P51 [Windows 11 Pro 24H2, Intel® Core i7-7820HQ, 64GB DDR4-2400MHz, NVIDIA Quadro® M2200]
    Lenovo ThinkStation P320 SFF [Windows 11 Pro 24H2, Intel® Xeon E3-1240v5, 40GB DDR4-2400MHz, NVIDIA® Quadro® P1000]
    Lenovo ThinkPad X1 Carbon G3 [Windows 11 Pro 24H2, Intel® Core i7-5600U, 8GB DDR3L-1600MHz, Intel® HD 5500]
    Lenovo ThinkPad T450s [Windows 11 Pro 24H2, Intel® Core i7-5600U, 20GB DDR3L-1600MHz, Intel® HD 5500]
Oh, I know...I'm aware that as they share a common servicing branch and the underlying codebase is already there. As such, I'm one Windows Update and an eKB Enablement Package away from turning on 26H2 if I so choose, which 'should' happen w/o much fanfare. It's just that the track record for Windows Updates has been well, a bit spotty and Microsoft can't seem to get it right lately...
If it helps, I've just updated all of my 25H2 machines to 26H2, including a couple that are unsupported devices.
Nothing has blown up ;)
 

My Computers My Computers

  • At a glance

    Windows 11 HomeAMD Athlon Silver 3050U8GBRadeon Graphics
    OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23-R9VY
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD (from April 2026: 250GB EVO 850)
    Internet Speed
    150 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    UPDATE - 11 April 2026: due to lid hinges starting to break up this laptop has been retired from active duty. The OS with all software and files has been migrated to my System Seven in 'Other systems' to carry on as my general purpose 'main machine'.

    I've now clean installed 25H2 and used Garlin's scripts to update Secure Boot to CA 2023 and revoke the PCA 2011 certificates. It's new role is to test secure boot issues.

    Info for 2021-2026:
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2, and 25H2 on 30th September 2025 through Windows Update by setting the Target Release Version for 25H2.
  • At a glance

    Windows 11 ProIntel® Core™ i5-520M8GB(integrated graphics) Intel HD Graphics
    Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround.

    In-place upgrade to 22H2 using ISO and a workaround.
    Feature Update to 23H2 by manually installing the Enablement Package.
    In-place upgrade to 24H2 using hybrid 23H2/24H2 install media.
    Upgraded to 25H2 by Enablement Package.
    Upgraded to 26H2 by Enablement Package.

    Also running Insider Experimental 263xx and 29xxx builds and Windows 10 as native boot .vhdx.
  • My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro.

    My SYSTEM FOUR was a 2-in-1 convertible Lenovo Yoga 11e (1st gen) type 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device. This has now been sold. It has been replaced by my System Eight.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 1TB NVMe ssd, supported device running Windows 11 Pro, plus Insider Beta, Experimental 263xx and 29xxx builds (and a few others) as a native boot .vhdx.

    My SYSTEM SIX is a Dell Latitude 5550, Core Ultra 7 165H, 64GB RAM, 1TB NVMe SSD, supported device, Windows 11 Pro, Hyper-V host machine. Updated to 25H2 on 30th September 2025.

    My SYSTEM SEVEN is a Lenovo Thinkpad T580, 1920x1080 touchscreen, Intel Core i7-8650U, 16GB RAM, 512GB NVMe SSD + 2nd 512GB NVMe SSD, a supported device for Windows 11. This is my current general purpose 'main machine'. The installed Windows 11 Home from my System One has been migrated to this machine. As its new home has an existing digital licence for Pro I've been able to upgrade the migrated OS from Home to Pro.
    29 Sept. 2026 Feature Update to 26H2 through Windows Update.

    My SYSTEM EIGHT is a 2-in-1 convertible Lenovo Yoga 11e (5th gen) type 20LN, Celeron N4120, 8GB RAM, 512GB NVMe ssd, a supported device for Windows 11. Currently running Windows 11 Pro, plus Insider Beta, Experimental 263xx and 29xxx builds as native boot vhdx.
If it helps, I've just updated all of my 25H2 machines to 26H2, including a couple that are unsupported devices.
Nothing has blown up ;)
Same
 

My Computers My Computers

  • At a glance

    Win 11 Pro (26H2 Experimental Preview)Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz 2.40...32GBNvidia GeForce GTX 1650, Intel UHD 630
    OS
    Win 11 Pro (26H2 Experimental Preview)
    Computer type
    Laptop
    Manufacturer/Model
    Acer AN515-54
    CPU
    Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz 2.40 GHz
    Memory
    32GB
    Graphics Card(s)
    Nvidia GeForce GTX 1650, Intel UHD 630
    Monitor(s) Displays
    Acer CB272D
    Screen Resolution
    1920x1080
    Hard Drives
    256GB and 1T SSD
    Internet Speed
    500MB
    Browser
    Edge (Stable)
    Antivirus
    Microsoft Defender
  • At a glance

    Win 11 Pro (26H2 RP)Intel(R) Core(TM) Ultra 9 275HX (2.70 GHz)32GB DDR5-5600NVIDIA® GeForce RTX™ 5060 8GB
    Operating System
    Win 11 Pro (26H2 RP)
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Legion 5 16IAX10 - Type 83NX
    CPU
    Intel(R) Core(TM) Ultra 9 275HX (2.70 GHz)
    Memory
    32GB DDR5-5600
    Graphics card(s)
    NVIDIA® GeForce RTX™ 5060 8GB
    Monitor(s) Displays
    Acer CB272D
    Screen Resolution
    1920x1080 75Hz
    Hard Drives
    WD Green SN3000 (2TB)
    Samsung Portable T5 (2TB)
    Keyboard
    Logi MX Keys
    Mouse
    Logi MX Anywhere 3
    Internet Speed
    500MB
    Browser
    Edge
    Antivirus
    MS Defender

Latest Support Threads

Back
Top Bottom