Insider KB5065426 Windows 11 Insider Release Preview build 26200.6584 (25H2) - Sep. 9

cereberus said:

This is incorrect.

In fact the menu has shipped in 24H2 but is not active yet, but will become active when the 25H2 enablement package is used.

It can be enabled on 24H2 using vivetool.

I do not see MS making the feature available in 24H2 without using vivetool.

Click to expand...

Two PCs here with 25H2, neither have the new start menu
Neither PC has the Phone link Start sidebar either, which was in 24H2 for a while then disappeared

cereberus said:

This is incorrect.

In fact the menu has shipped in 24H2 but is not active yet, but will become active when the 25H2 enablement package is used.

It can be enabled on 24H2 using vivetool.

I do not see MS making the feature available in 24H2 without using vivetool.

Click to expand...

In some updates you get the most features immediately. In another updates you do not get the features even after install the next update.

[UPDATE 9/10] The ISOs for Windows 11, version 25H2 are now available for download.

Brink said:

[UPDATE 9/10] The ISOs for Windows 11, version 25H2 are now available for download.

Click to expand...

downloading now it is build 26200.5074

Dave44 said:

downloading now it is build 26200.5074

Click to expand...

I'll wait for MCT when they release it to the general public.

fg2001gf11F said:

I'll wait for MCT when they release it to the general public.

Click to expand...

maybe end of September but most likely be October i would guess for general public

Does anyone know if the "Enterprise" ISO includes the same editions as what they usually call "Business" (as opposed to Home) in other places?

26200.6584 iso already downloaded, and I am now updating through Windows Update to 6584 from 5074... No trouble at all with 25H2 5074 so far.

Dave44 said:

maybe end of September but most likely be October i would guess for general public

Click to expand...

Current 25H2 Insider R.P. ISO is 26200.5074 and over 7GB.

KB5065426 is a good update, and I feel that Alt + Tab switching from the game to other windows is much more responsive.

I was having Windows Update error while installing the update. Install Error: 0x800f081f



I reset Windows Update directory and catroot2 folder but still no go. I downloaded .msu file from Windows Update Catalog. Still nothing.

I downloaded the whole update build 26200.6584 from UUPDUMP and now trying it.

Further to my post above, my upgrade unfortunately did not go well and the whole re-installation over the current build was not successful, either.

After the first restart I got "Config Initialization failed" error message on the black screen of death. After returning to the previous build, I was greeted with this screen.

We couldn't install Windows 11. 0xC1900101 - 0x20017 Installation failed at SAFE_OS phase during boot process (Sorry for any error in my translation).



When I saw the error code, I told myself "History repeats itself, so does Microsoft". Long long time ago my Realtek audio chipset driver was causing such an error while installing Windows 10. So I disabled Realtek audio. I did something else, too. I disabled Windows Update checking at the setup screen.

Later, I did so many dirty upgrades after Windows 10 and Windows 11 but did never meet this error code. It seems it haunted again.

Then I re-attempted to install Windows 11 Build 26200.6584. This time installation went smoothly. No problems so far. SFC came up clean.

After the upgrade I saw that this new build created its own Recovery partition.



The previous Recovery partition was of size 659 MB. Now this build created a new one of size 749 MB.

suatcini54 said:

After the upgrade I saw that this new build created its own Recovery partition.

View attachment 145004

The previous Recovery partition was of size 659 MB. Now this build created a new one of size 749 MB.

Click to expand...

Windows will create a new Recovery if the existing one isn't big enough.
What I do before a repair install is from an Admin command prompt:

reagentc /disable (disables the recovery partition)
diskpart
list disk
select disk (select your OS disk number)
list partition
select partition (select recovery partition number)
delete partition override (this part is important as the recovery can't be deleted normally)
exit
Then in Disk management extend the Windows partition into the space

During the install a new Recovery will be created at the size it needs

fg2001gf11F said:

Current 25H2 Insider R.P. ISO is 26200.5074 and over 7GB.
View attachment 144988

View attachment 144987

Click to expand...

22gb heavy, LTSC will be half 11gb

@BrianInEngland Thank you for your reply. The only thing is, I don't know when Windows deems necessary to increase Recovery partition size. Therefore, you have to do your procedure before every attempt to upgrade over the current installation, which I prefer to leave it to the discretion of Windows 11 installer. It is too much annoyance.

Some time in the long past, I happened to have more than 5 independent Recovery partitions, which I wished to sell back to Microsoft.

suatcini54 said:

@BrianInEngland Thank you for your reply. The only thing is, I don't know when Windows deems necessary to increase Recovery partition size. Therefore, you have to do your procedure before every attempt to upgrade over the current installation, which I prefer to leave it to the discretion of Windows 11 installer. It is too much annoyance.

Some time in the long past, I happened to have more than 5 independent Recovery partitions, which I wished to sell back to Microsoft.

Click to expand...

Always worth doing before a Repair install, I do it to avoid the problem you have

To Suatcini54: I've been upgrading through the Windows Update Insiders for years (I have ~11 TBs of programs and data I don't want to have to reinstall with a clean install, so I run a tight c:\ partition) and never had a problem with upgrading the newer build on top of the older build. All settings transfer, even Group Policy. Frankly, if the Windows installer expanding a recovery partition by a mere 100 mbs or so is disturbing, then I'd say the problem lies in the fact that your c:\ partition is too small and needs to be sized larger, or your C:\ drive needs to be replaced with a newer, larger drive altogether. Also, check the size and setup of your page files on c:\, as a common error is huge page files that aren't needed and consume space and slow you down. Run with 32GBs of system ram, minimum, if possible.

I like to have my C:\ partition 800-100 GBs larger than it needs to be, so that C:\ can grow when it needs to without problems and errors, and the only thing that I put on c:\ is the OS, device driver files and whatever utility programs I use. Application programs, data, games and so forth all go on other partitions. When you save a game these days, for instance, the save file goes right on c:\, and that is also true of many other programs, so the space need grows and you don't know it until you start getting errors caused by a lack of space on c:\. It's also much easier & faster to back up c:\ after a new build install, as well, as you are not backing up everything installed on your computer! NVMe capacity is cheap these days, and my total c:\ partition size is ~300 GBs with 80-100GBs of that space free, as I mentioned. HDD space is much cheaper, still.

Basically, the errors you report are not common and should not be happening to you, as Win11 is nowhere near that buggy. Admittedly, I am running the Release Preview channel build, not the beta, Dev, or Canary channel builds any longer, which most certainly are apt to be buggier than the RP channel builds, which are the closest thing to the retail commercial versions available from Microsoft Insider's, with the added advantage that I note that bugs plaguing the commercial release builds get fixed in the RP builds before they hit the official commercial patches.

Good luck, and I wanted to relate this to assure you that your experience is not common at all in the RP channel Insiders channel builds! Hopefully, this will help you discover the actual problem you are having.

BrianInEngland said:

Always worth doing before a Repair install, I do it to avoid the problem you have

Click to expand...

When I got that type of problem the 1st time, I set my recovery partition much bigger, from 1.5 to 2.5 GB and I never got a problem with the space of the recovery partition again. This shows 1.43 GB used out of 2.53 GB.

I always delete recovery partition and merge with drive C. I do it in Win PE. That is useless drive.