Win Update KB5129195 Windows 11 Out-of-band Cumulative Update build 26100.9457 (24H2), 26200.9457 (25H2), and 26300.9457 (26H2) - Sept. 14

gunrunnerjohn · 2026-09-16T15:42:32-0400

File History is just a poor excuse for real backup.

garlin · 2026-09-16T15:44:26-0400

fg2001gf11F said:
@garlin,
I tried to use your script on a USB drive bigger than 32GB because it has faster r/w speeds, but I end up with a message saying "Drive E: is READ-ONLY" even if it is not. Any explanation?

The original idea was to check if your drive letter was actually a Removable device (as reported by Windows). You obviously can't write the updated boot.wim back to a read-only device (actual DVD or an ISO file mounted as a drive letter).

I removed that check in this version.

garlin · 2026-09-16T15:47:16-0400

gunrunnerjohn said:
File History is just a poor excuse for real backup.

I think the point is if File History isn't officially dead, why break it with this summer's updates?

According to the one person on Tech Community, File History was probably broken in the July Preview/August Monthly. But nobody started checking until now. I wouldn't blame the September update, it's more likely the August build.

FrancoDT · 2026-09-16T15:49:24-0400

HTA said:
Hasn't File History in the process of being phased out?

I've read that Microsoft now considers it a legacy feature and is removing it from the Settings app and relegating it back to the legacy Control Panel. Also, while it remains available on traditional x86/x64 PCs via the Control Panel, it was excluded from ARM64 builds which explains why it is completely absent on my Surface Laptop 7.

gunrunnerjohn · 2026-09-16T15:50:00-0400

garlin said:
I think the point is if File History isn't officially dead, why break it with this summer's updates?

According to the one person on Tech Community, File History was probably broken in the July Preview/August Monthly. But nobody started checking until now. I wouldn't blame the September update, it's more likely the August build.

Well, I can't really argue with that. However, it's quite possible they didn't actually intend to break it, but since it stopped working, it's a low priority to get it running again. I know that I, for one, would rather they fix the stuff that isn't being depreciated first!

PurSpyk!! · 2026-09-16T16:20:53-0400

gunrunnerjohn said:
File History is just a poor excuse for real backup.

Nope, it's a system that works really well.

fg2001gf11F · 2026-09-16T17:02:53-0400

garlin said:
The original idea was to check if your drive letter was actually a Removable device (as reported by Windows). You obviously can't write the updated boot.wim back to a read-only device (actual DVD or an ISO file mounted as a drive letter).

I removed that check in this version.

@garlin,
I think this updated the boot.wim in the USB drive but still left the message to copy Updated_Boot.wim to the USB drive.

garlin · 2026-09-16T17:07:50-0400

Thanks. I commented out that section for you.

When I wrote this script as a half-joke I didn't think it would be broken for this long. Maybe like 1-2 builds and then nobody would need it any more...

Let's see if tomorrow's AMA means someone will forward the news back to Windows team. The fix is right there in the posted comments; so they don't really have any excuses, and throwing in the extra DLL's won't cause any bad side effects.

fg2001gf11F · 2026-09-16T17:14:16-0400

garlin said:
Thanks. I commented out that section for you.

When I wrote this script as a half-joke I didn't think it would be broken for this long. Maybe like 1-2 builds and then nobody would need it any more...

Let's see if tomorrow's AMA means someone will forward the news back to Windows team. The fix is right there in the posted comments; so they don't really have any excuses, and throwing in the extra DLL's won't cause any bad side effects.

This is what I see about removable. Is there another place to check?

garlin · 2026-09-16T17:26:41-0400

The script reads what PowerShell returns for "Get-Volume -DriveLetter X", and if it includes "Removable".

Based on feedback from the Secure Boot scripts, some drives don't report this correctly (or at least when formatted a certain way). The script just takes the reported result on face value, and doesn't try other methods to confirm if the drive's Removable or not.

JamesSmith · 2026-09-16T17:29:36-0400

TheVisitor said:
As usual I'm lost or behind somewhere - what is this for and does everyone need to run this ?

It automatically installed on my computer and I have Get the latest updates as soon as they're available possible turned off.

fg2001gf11F · 2026-09-16T17:35:45-0400

garlin said:
The script reads what PowerShell returns for "Get-Volume -DriveLetter X", and if it includes "Removable".

Based on feedback from the Secure Boot scripts, some drives don't report this correctly (or at least when formatted a certain way). The script just takes the reported result on face value, and doesn't try other methods to confirm if the drive's Removable or not.

@garlin,
Thanks for the clarification, that command returns Fixed DriveType, which in this case I think it should say Removable.

I don't know why it shows fixed? It is a USB connected drive in a SABRENT enclosure.

This explanation below is from A.I.
Your SABRENT enclosure shows a drive as a Fixed Disk rather than a Removable Disk because of how the enclosure’s internal SATA/NVMe-to-USB bridge controller (such as ASMedia or Realtek chips) passes along hardware identifiers to your operating system. [1, 2]

Anyway, here what I got with your latest script update. And "Repair my PC" works fine.

garlin · 2026-09-16T17:51:13-0400

You missed the endless pages of fun on "what's a 'Removable' drive?" :crys:

To a non-technical user, this answer should be obvious. A removable drive is either a CD/DVD, or a portable USB thumb drive. But any ISO image mounted under a drive letter is "Removable". What we discovered in the Secure Boot scripts thread was several users had USB drives that reported themselves as "Fixed" devices.

Blame Windows or PS... After 4 different attempts at a workaround, we settled on a mostly OK method for determining that you have what a normal user thinks is a removable device. But that would make the Repair My BootWIM script more complicated than it needs to be.

JandS · 2026-09-16T18:53:21-0400

nayro said:
Hi everyone,

I installed the update and experienced a few issues right after, although everything seems fine now. I’m still a bit concerned and curious if others had similar problems.

Here’s what happened:

During boot, before the MSI motherboard logo appears, I got a black screen with a small white line in the top-left corner (like a terminal cursor). It lasted longer than usual.

On the login screen, I had a long freeze when entering my PIN. Also, instead of the usual rotating Windows background, my personal desktop wallpaper was displayed.

My wireless Logitech headset was no longer recognized (USB dongle). Even after several reboots, it didn’t work. I fixed it by plugging the USB receiver into a different port.

Everything is working normally now, but the behavior right after the update was a bit worrying.

Has anyone experienced something similar with this update?

I did. I had problems with both a Logitech MX Keys S keyboard and Logitech Trackball MS Ergo S, both using a single LogiBold USB receiver. Needed much consternatory exclamations while attempting to resolve, multiple removals of the USB receiver as well as plugging into different ports and system reboots. I have no idea what actually fixed it, but fortunately didn't deplete consternatory reserves.

fg2001gf11F · 2026-09-16T19:27:44-0400

More of this, on Public Build.

Banjoman301 · 2026-09-16T19:33:02-0400

garlin said:
As an emergency fix, MS is only concerned about Remote Desktop, Hyper-V, and broken audio support.

We don't use RD or Hyper-V, and audio works fine for us on 26200.9445

No zero days, so no compelling reason for us to install it at this time.

fg2001gf11F · 2026-09-16T21:25:30-0400

garlin said:
You missed the endless pages of fun on "what's a 'Removable' drive?"

To a non-technical user, this answer should be obvious. A removable drive is either a CD/DVD, or a portable USB thumb drive. But any ISO image mounted under a drive letter is "Removable". What we discovered in the Secure Boot scripts thread was several users had USB drives that reported themselves as "Fixed" devices.

Blame Windows or PS... After 4 different attempts at a workaround, we settled on a mostly OK method for determining that you have what a normal user thinks is a removable device. But that would make the Repair My BootWIM script more complicated than it needs to be.

@garlin,

I added this to my post #112.

This explanation below is from A.I.
Your SABRENT enclosure shows a drive as a Fixed Disk rather than a Removable Disk because of how the enclosure’s internal SATA/NVMe-to-USB bridge controller (such as ASMedia or Realtek chips) passes along hardware identifiers to your operating system. [1, 2]
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
And more on Sabrent:

Understanding Drive Status in Windows

Fixed vs. Removable: Windows treats USB-connected storage controllers based on how the bridge chip (such as JMicron, ASMedia, or Realtek inside the Sabrent enclosure/dock) reports its device flags to the operating system.
Custom Firmware: Manufacturers like Sabrent rarely release custom firmware to change the fixed/removable flag because it can affect TRIM support, write-caching behavior, and Windows' handling of the filesystem.
Alternative Workarounds: If you need Windows to treat a fixed external drive as removable (for instance, to bypass caching or allow easier ejection of specific partitions), it is usually managed via Windows Device Manager under the drive's Policies tab ("Quick removal" vs. "Better performance") rather than a device firmware flash.

Steve C · 2026-09-17T02:12:38-0400

gunrunnerjohn said:
File History is just a poor excuse for real backup.

I use both!

Win Update KB5129195 Windows 11 Out-of-band Cumulative Update build 26100.9457 (24H2), 26200.9457 (25H2), and 26300.9457 (26H2) - Sept. 14

Improvements​

Component updates​

Windows 11 servicing stack update (KB5124007) - 22621.9441​

Known issues in this update​

How to get this update​

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Active member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

Improvements

Component updates

Windows 11 servicing stack update (KB5124007) - 22621.9441

Known issues in this update

How to get this update

My Computers

My Computer

My Computer

My Computers

My Computers

My Computers

My Computer

My Computer

My Computer

My Computer

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer