Insider KB5039304 Windows 11 Insider Release Preview build 26100.994 (24H2) - June 20

Josey Wales · Sunday at 1:38 PM

mecanicogolf said:
Thanks. But can I also downgrade to the regular standard Win 11 non-insider build? 22631?

It has be my experience that this works only by using a build from the dump. I would make a backup image first.

fg2001gf11F · Sunday at 1:41 PM

mecanicogolf said:
Thanks. But can I also downgrade to the regular standard Win 11 non-insider build? 22631?

If you uninstall the Beta Enablement packs it should go back from 22635.xxx to 22631.xxx.
Before doing that, you may want to get out from insider by deleting the WindowsSelfHost key and rebooting.

Josey Wales · Sunday at 1:45 PM

fg2001gf11F said:
If you uninstall the Beta Enablement packs it should go back from 22635.xxx to 22631.xxx.
Before doing that, you may want to get out from insider by deleting the WindowsSelfHost key and rebooting.
View attachment 99852

You are probably correct but I have gone back from DEV builds by just using the Dump. Thanks for the info though I was not aware that was even possible. :thumbsup:

fg2001gf11F · Sunday at 2:10 PM

Josey Wales said:
You are probably correct but I have gone back from DEV builds by just using the Dump. Thanks for the info though I was not aware that was even possible.

That only works from Beta 22635 to 22631, not from Dev.
Dev is 26120.xxx, that can go back to 26100.xxx. To go back to 22631 from Dev 26120 it requires a clean install.

Bree · Sunday at 2:11 PM

Josey Wales said:
The FBH is something that MS came up with to make users feel that they actually listen.

fg2001gf11F said:
They read and take action on some of them.
More upvotes and more FBH reports get more action.

Sometimes MS will ask for your feedback, if they don't listen to that I don't know what they'd act on. They've just asked me in Beta for my opinion of the new user account menu in Start. I told them exactly what I thought of it :wink:

Josey Wales · Sunday at 2:33 PM

Bree said:
Sometimes MS will ask for your feedback, if they don't listen to that I don't know what they'd act on. They've just asked me in Beta for my opinion of the new user account menu in Start. I told them exactly what I thought of it

I used to use it a great deal when I was in The IP. I sent feedback and they wanted my Email Address and cell so they could respond. This I did maybe 30 times without so much as a Thank you, although they gave me trophies for being an insider for 9 years. I even sent Brandon LeBlanc a Tweet and he blocked me for bothering him. It is manned by AI. I just have no use for it. If I need anything , I am better off coming here. :thumbsup:

Zardoc · Sunday at 6:58 PM

Josey Wales said:
I used to use it a great deal when I was in The IP. I sent feedback and they wanted my Email Address and cell so they could respond. This I did maybe 30 times without so much as a Thank you, although they gave me trophies for being an insider for 9 years. I even sent Brandon LeBlanc a Tweet and he blocked me for bothering him. It is manned by AI. I just have no use for it. If I need anything , I am better off coming here.

I have the same opinion as you. After a while I felt like cheap labour. That's why I stopped. I also rather be here with other users who put their heart and soul in finding help and helping others.

PurSpyk!! · Monday at 1:25 AM

fg2001gf11F said:
If you uninstall the Beta Enablement packs it should go back from 22635.xxx to 22631.xxx.
Before doing that, you may want to get out from insider by deleting the WindowsSelfHost key and rebooting.
View attachment 99852

If you installed the beta enablement patch to go to build 26120.xxx and you can no longer uninstall this patch, can you manually revert back to build 26100.xxx?

markw51 · Monday at 4:15 AM

PurSpyk!! said:
If you installed the beta enablement patch to go to build 26120.xxx and you can no longer uninstall this patch, can you manually revert back to build 26100.xxx?

No as it's a different insider branch.

fg2001gf11F · Monday at 4:18 AM

PurSpyk!! said:
If you installed the beta enablement patch to go to build 26120.xxx and you can no longer uninstall this patch, can you manually revert back to build 26100.xxx?

The enablement pack can be uninstalled from 26120.xxx and that will bring you back to 26100.xxx.
I don't know why you cannot uninstall it.

If that was really the case, you could still get out from Dev by deleting the registry WindowsSelfHost key and rebooting.
After that use the 26100.863 ISO and try an update repair in place.
Once that is done, rejoin insider Release Preview channel and use W.U. to get to the latest 26100.994

PurSpyk!! · Monday at 5:02 AM

fg2001gf11F said:
The enablement pack can be uninstalled from 26120.xxx and that will bring you back to 26100.xxx.
I don't know why you cannot uninstall it.
If that was really the case, you could still get out from Dev by deleting the registry WindowsSelfHost key and rebooting.
After that use the 26100.863 ISO and try an update repair in place.
Once that is done, rejoin insider Release Preview channel and use W.U. to get to the latest 26100.994

View attachment 99894

Odd on my system its no longer listed as installed, although I am on 26120.xxx.

I have lots of odd things in this 261xx.xx build. Task Manger odd graph colours, quick access crashes, and now updates no longer listed. Another recent issue is Microsoft 365 in unable to load, and my Microsoft Subscriptions are no longer shown under the Accounts section in the Settings App.

fg2001gf11F · Monday at 5:16 AM

PurSpyk!! said:
Odd on my system its no longer listed as installed, although I am on 26120.xxx.

I have lots of odd things in this 261xx.xx build. Task Manger odd graph colours, quick access crashes, and now updates no longer listed. Another recent issue is Microsoft 365 in unable to load, and my Microsoft Subscriptions are no longer shown under the Accounts section in the Settings App.

Weird conditions.

I'd suggest getting out from Dev insider by deleting the WindowsSelfHost key and rebooting, then try an update repair in place with ISO 26100.863 and go from there.

PurSpyk!! · Monday at 5:27 AM

fg2001gf11F said:
Weird conditions.
I'd suggest getting out from Dev insider by deleting the WindowsSelfHost key and rebooting, then try an update repair in place with ISO 26100.863 and go from there.

I actually did an in place upgrade before I decided to use the beta enablement patch. It never fixed the issues. I am actually still in the Release Preview. So I have an odd hybrid install at moment.

On top of that my new i9 system is not 100% stable due to all the recent issues with bios and overvolting etc.

This is the odd Microsoft 365 issue, I did report this earlier in this thread by it seemed to go unnoticed. I haven't seen anyone else report this.

fg2001gf11F · Monday at 5:32 AM

PurSpyk!! said:
I actually did an in place upgrade before I decided to use the beta enablement patch. It never fixed the issues. I am actually still in the Release Preview. So I have an odd hybrid install at moment.

On top of that my new i9 system is not 100% stable due to all the recent issues with bios and overvolting etc.

This is the odd Microsoft 365 issue, I did report this earlier in this thread by it seemed to go unnoticed. I haven't seen anyone else report this.

Weird that you are still on 26120.
Which ISO did you use?

I just tried here, and I am at 26100.863.

Edition Windows 11 Pro
Version 24H2
Installed on ‎6/‎24/‎2024
OS build 26100.863
Experience Windows Feature Experience Pack 1000.26100.6.0

And W.U. in R.P. got it up to 26100.994.

PurSpyk!! · Monday at 5:59 AM

fg2001gf11F said:
Weird that you are still on 26120.
Which ISO did you use?

I just tried here, and I am at 26100.863.

Edition Windows 11 Pro
Version 24H2
Installed on ‎6/‎24/‎2024
OS build 26100.863
Experience Windows Feature Experience Pack 1000.26100.6.0

And W.U. in R.P. got it up to 26100.994.
View attachment 99904

I had 26100.712 then installed the beta enablement patch manually, and now I have a hybrid system. Initially I had the option to remove the beta patch, but as per my earlier screenshots, its no longer listed. I even tried to remove it with PowerShell and it could not be uninstalled for some reason.

PerpetualCycle · Monday at 1:45 PM

PurSpyk!! said:
I had 26100.712 then installed the beta enablement patch manually, and now I have a hybrid system. Initially I had the option to remove the beta patch, but as per my earlier screenshots, its no longer listed. I even tried to remove it with PowerShell and it could not be uninstalled for some reason.

Did you run dism ..... /resetbase or any script with that in it to cleanup after installation?

Dirtyflash · Monday at 1:46 PM

fg2001gf11F said:
Perhaps the enablement is not showing if you installed it manually.

I've found WU history's record of installs can get deleted when using DISM commands to cleanup, ie, after Patch Tuesdays.

PerpetualCycle · Monday at 1:52 PM

Dirtyflash said:
sing DISM commands to cleanup, ie, after Patch Tuesdays.

It is the dism command:

dism /online /cleanup-image /startcomponentcleanup /resetbase

That does it ( /resetbase) . It basically pares back any unnecessary system packages, including such updates that got you there (making it the base image). You can't go back because the updates have been removed.

PurSpyk!! · Monday at 3:27 PM

PerpetualCycle said:
Did you run dism ..... /resetbase or any script with that in it to cleanup after installation?

Ja, that's what's happened. Damn

PerpetualCycle · Monday at 3:31 PM

PurSpyk!! said:
Ja, that's what's happened. Damn

If you don't want that behavior, don't use the "/resetbase" switch. It won't reclaim as much space, but will retain the updates intact so you can uninstall them if desired.