Win Update KB5095093 Windows 11 Cumulative Update Preview build 26100.8737 (24H2) and 26200.8737 (25H2) - June 23

cute two · Thursday at 12:03 PM

KevTech said:
Seems to just be using the system-generated name assigned to the file when sent to the recycle bin.

View attachment 175028

View attachment 175029

It's not the exact name : You have "I" and Windows change it to "R".

cute two · Thursday at 12:31 PM

After update to this build, I see the GPU celsius without need to press on it (See it aside) : (This feature fixed probably after many time)

Mike1776 · Thursday at 3:28 PM

Screen Tint, new in this build under Settings Accessablility.... It is embeded in multiple Reg addresses so, deactivating there could possibly wreck other color, tint settings or worse beyond desired outcome. Report back to MS, not happy with this thingy.

rawintellect · Thursday at 10:25 PM

26200.8524 checks out fine. Rolling back to 26200.8737.

rawintellect · 2026-06-26T12:32:57-0400

26200.8655 checks out. Moving on to the next one.

rawintellect · 2026-06-26T22:23:22-0400

Ah ha! It started with 26200.8728 and continued into 26200.8737!

hader · 2026-06-27T06:39:15-0400

rawintellect said:
Ah ha! It started with 26200.8728 and continued into 26200.8737!

View attachment 175321

Well looking at the error; it seems there is a driver inside C:\Windows\System32\drivers that the Memory integrity does not like and refuses to load. Is Memory Integrity turned on or off? Turn it on. If it refuses than look what it's refusing. It will show you a list of drivers that it has issues with. You have then deinstall these drivers because MS don't trust them. It can be: I had a case once; The signature of the driver was expired. No new software available that had a valid signature. Had a similar issue with SAFE_OS but during the MIGRATE_DATA proces. (Error: 0x8007042B -0x2000D) Could not fix that one. The advice was; disconnect all USB-drives, to stop all non-MS services. Did not resolve my issue so I proceeded with a clean install. The problem was gone. Could be a driver issue also. Got rid of it with that clean install. It is wise before each update (seen this issue) to check if there are unknown device inside the device manager. Had this recently. Some unknown devices; it appears that it was missing some Intel drivers. Had a hard time to find the right ones.
- An Intel(R) Rapid Storage Technology Driver (RAID driver. My board is capable using RAID, but I don't use it.
- An Intel Management Engine Interface driver from the motherboard manufacture.

It seems that some driver is hampering this update proces. Can not solve it and roles back again to the previous build.
I am also not sure why you use UUP builds that is not on the official update roadmap like; 8313 and 8728.
The official ones are 8328->8457->8524->8655->8737. Any other on-official builds may introduce issues. And when you have 8328 you don't have to go through all those steps like 8457->8524->8655->8737. You can from here (8328) update directly towards 8737.

pietcorus2 · 2026-06-27T07:11:22-0400

hader said:
Well looking at the error; it seems there is a driver inside C:\Windows\System32\drivers that the Memory integrity does not like and refuses to load. Is Memory Integrity turned on or off? Turn it on. If it refuses than look what it's refusing. It will show you a list of drivers that it has issues with. You have then deinstall these drivers because MS don't trust them. It can be: I had a case once; The signature of the driver was expired. No new software available that had a valid signature. Had a similar issue with SAFE_OS but during the MIGRATE_DATA proces. (Error: 0x8007042B -0x2000D) Could not fix that one. The advice was; disconnect all USB-drives, to stop all non-MS services. Did not resolve my issue so I proceeded with a clean install. The problem was gone. Could be a driver issue also. Got rid of it with that clean install. It is wise before each update (seen this issue) to check if there are unknown device inside the device manager. Had this recently. Some unknown devices; it appears that it was missing some Intel drivers. Had a hard time to find the right ones.
- An Intel(R) Rapid Storage Technology Driver (RAID driver. My board is capable using RAID, but I don't use it.
- An Intel Management Engine Interface driver from the motherboard manufacture.

It seems that some driver is hampering this update proces. Can not solve it and roles back again to the previous build.
I am also not sure why you use UUP builds that is not on the official update roadmap like; 8313 and 8728.
The official ones are 8328->8457->8524->8655->8737. Any other on-official builds may introduce issues. And when you have 8328 you don't have to go through all those steps like 8457->8524->8655->8737. You can from here (8328) update directly towards 8737.

hader , do you think its worth trying to update to this latest preview........??
Asking you , coz you know much more about these update-questions then I do !
btw had to roll back from previous preview avoiding lots of errors , now all fine version 8655..........

FrankW · 2026-06-27T07:30:35-0400

Installed fine on both my systems, DISM and SFC no isues

rawintellect · 2026-06-27T07:39:13-0400

hader said:
Well looking at the error; it seems there is a driver inside C:\Windows\System32\drivers that the Memory integrity does not like and refuses to load. Is Memory Integrity turned on or off? Turn it on. If it refuses than look what it's refusing. It will show you a list of drivers that it has issues with. You have then deinstall these drivers because MS don't trust them. It can be: I had a case once; The signature of the driver was expired. No new software available that had a valid signature. Had a similar issue with SAFE_OS but during the MIGRATE_DATA proces. (Error: 0x8007042B -0x2000D) Could not fix that one. The advice was; disconnect all USB-drives, to stop all non-MS services. Did not resolve my issue so I proceeded with a clean install. The problem was gone. Could be a driver issue also. Got rid of it with that clean install. It is wise before each update (seen this issue) to check if there are unknown device inside the device manager. Had this recently. Some unknown devices; it appears that it was missing some Intel drivers. Had a hard time to find the right ones.
- An Intel(R) Rapid Storage Technology Driver (RAID driver. My board is capable using RAID, but I don't use it.
- An Intel Management Engine Interface driver from the motherboard manufacture.

It seems that some driver is hampering this update proces. Can not solve it and roles back again to the previous build.
I am also not sure why you use UUP builds that is not on the official update roadmap like; 8313 and 8728.
The official ones are 8328->8457->8524->8655->8737. Any other on-official builds may introduce issues. And when you have 8328 you don't have to go through all those steps like 8457->8524->8655->8737. You can from here (8328) update directly towards 8737.

I've done all of this. This isn't my first time with this error. It is the first time in a long while however. It's not a driver issue (at least any of my drivers I have installed). It's a WinRe (driver) issue. Which is why I tried all the versions leading up to 26200.8728 and they worked fine. In fact, I've researched this and it appears this issue was once in the dev/beta builds recently. I'm going to just assume someone let it slip though the cracks. I am currently on 26200.8737 but I had to use the MSU file to do it.

As for using UUP builds? Because without sounding like a jerk: I want to. I'm not a rookie. I've been in IT professionally for over 35 years. I can handle most errors the installer throws at me. I even solved the 0xc1900101 before with stetupdiag.exe. It reads the logs and tells you what drivers are being rejected. 0xc1900101 is a generic rollback code that could be a lot of things, hence the use of setupdiag.exe to find and correct them. Setupdiag.exe simply showed no errors whatsoever other than the generic rollback code. The last action it completed was the removal of system restore points and PITR points (which happens right before the reboot into WinRe). They were successful (read "true"). Nothing else.

This failure happens as soon as the PC boots into WinRe. The only error I did see twice was "boot drive not detected." I suspect the drivers for storage are just not there and I'm again going to go ahead and assume someone forgot to drop those into WinRe which uses a completely different (basic) set of drivers to start the WinRe environment.

Microsoft has dropped the ball many times in the past (hence the need for this forum to discuss them) and they will again in the future. I'm simply discussing the issue. Also as I'm not the author of the other thread I linked I know I'm not the only one that discovered this issue.

I have a sneaky suspicion this will correct itself soon as the builds filter down to the RP channel.

But I do thank you for your reply.

You're welcome to try this yourself. I'd be very shocked if it worked. It can't hurt anything as the failure will simply cause windows to roll back to your current version.

P.S. A quick google search within the last month (using the tools tab to filter on the last month) shows the 0xc1900101 has been happening very recently. I'm not alone. I'm also not stuck as I've indicated the workaround is to just use the MSU until Microsoft gets it sorted.

I included one search result below. There are many more.

https://www.reddit.com/r/Windows11/comments/1ua7oyf/announcing_windows_11_insider_beta_preview_build

EB2XR6 · 2026-06-27T07:52:50-0400

FrankW said:
Installed fine on both my systems, DISM and SFC no isues

Do you check for Reclaimable Packages when you run DISM and if so reclaim them ?
If I reclaim the packages that is when I see the issues.

hader · 2026-06-27T10:08:35-0400

EB2XR6 said:
Do you check for Reclaimable Packages when you run DISM and if so reclaim them ?
If I reclaim the packages that is when I see the issues.

As everyone already knows; It wil find 2 reclaimable packages. But after a CleanupComponentStore action there will be still 2 packages to be reclaimed. They are some packages left belonging by the initial 1742 release and remains to be there until a real next release. Inside the ComponentStore are all belong to 26100. Windows is saying 25200 but that is not the case. Maybe they will disappear with 26300 beloning to 26H2 but I have hard hopes for it. 26100 belongs still to 24H2 and they just fixed Winver that it always reports 26200 and called it 25H2. What you see inside the ComponentStore says otherwise. All those update are called for builds 26100.8737 and 26200.8737 for a good reason; they are the same. That 1742 base build has been there from the beginning with 24H2 and 25H2. It it some base build that needs to be there. In all builds since 26100.1742, 1742 packages are superseded remains. Even with 26200.8737 these two versions are still present till today. Deleting those 2 1742 packages will hamper future updates and causing issues; so they must be left alone;

Code:

------------------------------------------------------------
This 26200.8737 Update contains 10 different build versions.
------------------------------------------------------------
   72X  1742           <-----
   11X  26100.1       
    1X  6717           
    1X  7900           
    1X  8037           
    1X  8117           
    1X  8733           
   72X  8737           <-----
    1X  9335           
    1X  9337           
===========================================================
Total number of packages found: 162

TraderGary · 2026-06-27T11:08:21-0400

It's interesting. Some people have update problems. Some don't. I've not had a single update problem in the five years I've had Windows 11. Why?

rawintellect · 2026-06-27T11:12:54-0400

I ran the install again just now to obtain the latest setupdiag.exe data. As you can see the only error message is the finalized last operation which was the removal of the PITR points. But then later in the log it says that operation completed successfully (true). All of this occurs before the reboot into WinRe. It's failing at literally the beginning. When it loads the mouse and keyboard. Both of which I removed when troubleshooting this before. It made no difference.

neldog · 2026-06-27T12:09:18-0400

TraderGary said:
It's interesting. Some people have update problems. Some don't. I've not had a single update problem in the five years I've had Windows 11. Why?

Mostly, it is because in the five years since you installed Windows 11, you have not installed any software that alters the OS. Also, you have not hacked around in the registry very much... if any at all.

Slavic · 2026-06-27T13:26:36-0400

Slavic said:
If someone will keep a note about the restore experience since this update, it would be very interesting.

On my PC, for the past 3 days the Point-in-time restore automatically created 5 restore points, much more than expected from the default frequency settings (24 hours, it cannot be changed in UI). In practice, the time between the points is much less and different in each case, from 8 to 20 hours. At the same time, classic System restore hasn't created even a single point since 24 June, so it has completely separate schedule.
Apparently, the new restore service works not as intended or at least as announced.

BrianInEngland · 2026-06-27T13:47:43-0400

Slavic said:
On my PC, for the past 3 days the Point-in-time restore automatically created 5 restore points, much more than expected from the default frequency settings (24 hours, it cannot be changed in UI). In practice, the time between the points is much less and different in each case, from 8 to 20 hours. At the same time, classic System restore hasn't created even a single point since 24 June, so it has completely separate schedule.
Apparently, the new restore service works not as intended or at least as announced.

Perhaps it creates new points if you make changes such as install drivers/software or update something. System restore would often do that.
24 hours is probably the default if no changes are made

TraderGary · 2026-06-27T14:19:06-0400

neldog said:
Mostly, it is because in the five years since you installed Windows 11, you have not installed any software that alters the OS. Also, you have not hacked around in the registry very much... if any at all.

I've also never had a computer that wasn't fully Windows 11 compliant. Could that also be a factor?

neldog · 2026-06-27T14:31:13-0400

TraderGary said:
I've also never had a computer that wasn't fully Windows 11 compliant. Could that also be a factor?

Yes...

Josey Wales · 2026-06-27T15:07:37-0400

TraderGary said:
It's interesting. Some people have update problems. Some don't. I've not had a single update problem in the five years I've had Windows 11. Why?

Because you don't F around with it.

Available	Next Step
	Open Start > Settings > 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
	To install this release from the Microsoft Update Catalog, select the option that matches your device architecture (arm64 or x64), and then follow the instructions.

Win Update KB5095093 Windows 11 Cumulative Update Preview build 26100.8737 (24H2) and 26200.8737 (25H2) - June 23

Announcements and messages​

Redesigned Start menu availability for commercial and managed devices​

End of updates​

Change log​

Highlights​

Windows 11 PC experiences​

Components updates​

AI components​

Servicing stack update (SSU)​

Known issues in this update​

How to get this update​

Deployment​

Install this update​

File information​

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

Mr. Biscuit

My Computer My Computer

At a glance

Mr. Biscuit

My Computer My Computer

At a glance

Mr. Biscuit

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

Mr. Biscuit

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

Stock Market Wizard

My Computers My Computers

At a glance

At a glance

Mr. Biscuit

My Computer My Computer

At a glance

Rancho Seldom Siesta

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

Stock Market Wizard

My Computers My Computers

At a glance

At a glance

Rancho Seldom Siesta

My Computers My Computers

At a glance

At a glance

Announcements and messages

Redesigned Start menu availability for commercial and managed devices

End of updates

Change log

Highlights

Windows 11 PC experiences

Components updates

AI components

Servicing stack update (SSU)

Known issues in this update

How to get this update

Deployment

Install this update

File information

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computers

My Computers

My Computers

My Computer

My Computer

My Computers

My Computers

My Computer

My Computers

My Computer

My Computer

My Computers

My Computers

My Computers