Solved Looks like an old problem of the Windows Insider Program is back

In the early Windows 10 testing days, Microsoft would push out a new build, and it would take a while before that build would propagate to all Insider PCs...
Sometimes up to 24 hours.

Well, seems like this behavior is back with 26220.6760.

Out of curiosity I tried to upgrade my 26200.6725 install to the Dev Channel, instead of pulling 6760, it pulled the older build 6690.
And no matter how many times I click on "Check for Updates", build 26220.6760 is not offered.
Although it says there is a newer build in the insider settings.

Try deletng downloads folder (c:\windows\softwaredistribution\downloads) and rebooting and then check for updates.

TechnoFlash7560 said:

In the early Windows 10 testing days, Microsoft would push out a new build, and it would take a while before that build would propagate to all Insider PCs...
Sometimes up to 24 hours.

Well, seems like this behavior is back with 26220.6760.

Out of curiosity I tried to upgrade my 26200.6725 install to the Dev Channel, instead of pulling 6760, it pulled the older build 6690.
And no matter how many times I click on "Check for Updates", build 26220.6760 is not offered.
Although it says there is a newer build in the insider settings.

Click to expand...

Hello,

You can see if resetting Windows Update using the method in the tutorial below may fix this for you.

Brink said:

Hello,

You can see if resetting Windows Update using the method in the tutorial below may fix this for you.

Reset Windows Update in Windows 11

This tutorial will show you how to completely reset Windows Update components and policies to default in Windows 10 and Windows 11. Windows Update keeps Windows 11 updated by automatically downloading and installing the latest updates, drivers, and hotfixes released by Microsoft. Sometimes you...

www.elevenforum.com

Click to expand...

Hello, Brink, thank you. Just a small slightly offtopic question, I see you run W11 Pro for Workstations instead of the more full-featured Enterprise edition.

Why would that be? Is there some advantage to ProWS that Enterprise does not have? Thank you again.

TechnoFlash7560 said:

Hello, Brink, thank you. Just a small slightly offtopic question, I see you run W11 Pro for Workstations instead of the more full-featured Enterprise edition.

Why would that be? Is there some advantage to ProWS that Enterprise does not have? Thank you again.

Click to expand...

Hello,

W11 Pro for Workstations is still considered part of the "Home/Pro" family that uses retail keys, where as "Enterprise" is more commercial/business.

I use it on my desktop, so no need for an Enterprise edition that requires a volume license.

Update: The insider team confirmed to me on X that they've pulled 26xx0.6760.

TechnoFlash7560 said:

In the early Windows 10 testing days, Microsoft would push out a new build, and it would take a while before that build would propagate to all Insider PCs...
Sometimes up to 24 hours.

Well, seems like this behavior is back with 26220.6760.

Out of curiosity I tried to upgrade my 26200.6725 install to the Dev Channel, instead of pulling 6760, it pulled the older build 6690.
And no matter how many times I click on "Check for Updates", build 26220.6760 is not offered.
Although it says there is a newer build in the insider settings.

Click to expand...

It's called Regression testing (or lack of). --In plain English this is when a later defect is fixed which "undoes" a fix to a previous defect (not necessarily related to the current problem in question).

This is a very unglamourous part of I.T maintenance and it has a very low profile and usually this type of maintenance is given very few resources - but given the sheer complexity of modern I.T systems this should mean that management get on board quickly with this stuff.

It's quite complex to devise good regression testing scripts / environments but it really IS IMPORTANT. Aso what can happen is that just applying the original old fix will cause the new fix for the new problem to break -- so it really is a complex area. In extreme cases a totally NEW OS must be rolled out which can only be installed via a clean install and not via update. Even then this is not without problems.

Too often - especially with off shored I.T functionality - a list of defects is handed out to the maintenance team who probly just fix those one by one - and if you are lucky they will do a system test to ensure those are fixed - but it's 100% certain they won't bother with regression testing of previous defects.

Cheers
jimbo