Solved Dev Build 26220.6982 trying to force install itself on PC's

FrancoDT · Oct 27, 2025

OK, does anyone else have an issue with WU trying to install the DEV build on their PC's? This has happened to me twice now in the last week, just now on the current beta build 26120.6982 and a few days ago on my girlfriend's laptop which isn't even on the insider problem and was on the latest public build. It suddenly shows up in WU out of the blue and I have to pause updates. To finally stop it on my girlfriends laptop I had to use a YouTube video and jump through a bunch of hoops switching back in forth from MS account to local account and changing all kind of account stuff to get that PC back to showing public builds again. Now the same issue on my old Beta PC and it's locked on the DEV build again and can't be changed. What the heck is going on with this update showing out of the blue. I can't select any insider settings or unenroll.

FrancoDT · Oct 27, 2025

Update, now it is occurring on one of my Release Preview build PC's! What the heck is going on here!

Reldel · Oct 27, 2025

DEV build installed itself on a release preview machine of mine back in July. I didn't catch it until three weeks ago and then I used a Macrium backup to correct the unwanted version and restore release preview.

FrancoDT · Oct 27, 2025

Reldel said:
DEV build installed itself on a release preview machine of mine back in July. I didn't catch it until three weeks ago and then I used a Macrium backup to correct the unwanted version and restore release preview.

I'm afraid that restoring my backups will just have it occur again though. This has happened on three different machines now.

FrancoDT · Oct 27, 2025

Now it just hit the forth machine that is also on RP. I have all three machines currently trying to install the DEV build pulsed.

FrancoDT · Oct 27, 2025

Just got this per Co-pilot:

Yes, Windows 11 Dev Build 26220.6982 has been reported to attempt installation on PCs not enrolled in the Dev Channel. This appears to be an unintended rollout affecting both Beta and public release systems.

What's Happening with Build 26220.6982
• Multiple users on forums like ElevenForum have reported that Windows Update is pushing Dev Build 26220.6982 (KB5067109) to systems that are:
• Enrolled in the Beta Channel
• Not enrolled in any Insider channel
• Running stable public builds
• The issue seems to have started around October 24–25, 2025, and affects PCs running Build 26120.6982 and other recent 24H2 builds.
• Some users have had to pause updates, switch between Microsoft and local accounts, and perform Insider settings resets to stop the forced install.

EASTER · Oct 27, 2025

So that's what is been going on with my recent Windows Updates lately that caused me to have to ABORT Pending Installs.

Thanks for opening this topic.

FrancoDT · Oct 27, 2025

EASTER said:
So that's what is been going on with my recent Windows Updates lately that caused me to have to ABORT Pending Installs.

Thanks for opening this topic.

So latest update, I'm posting this for anyone that gets stuck with the DEV build trying to install over and over again with the Windows Insider Program settings being completely greyed out. I've manually fixed the three PC's that were afflicted today using the instructions in this video:

Yes, it's a hassle and since the Windows Insider Program settings won't allow changes you will need to follow the two later steps of switching to a local account and doing the registry entry deletion. Once that is done and you've rebooted you will be unenrolled from the Insiders program but left on whatever your previous build was. So if you were on a public build you can stay there and if you want back in the insiders program you'll have to reenroll again for those updates to resume. My Windows Updates are functioning properly again but know I'm in a paranoid state wondering if they will stay that way or if I'll be switched back to the Dev builds again without asking. After seeing this on four different computers, one public, two RP, and one Beta I don't know what to expect anymore.

dacrone · Oct 27, 2025

will running this and using opt 4 not work to get out of it?

GitHub - abbodi1406/offlineinsiderenroll: OfflineInsiderEnroll - A script to enable access to the Windows Insider Program on machines not signed in with Microsoft Account

OfflineInsiderEnroll - A script to enable access to the Windows Insider Program on machines not signed in with Microsoft Account - abbodi1406/offlineinsiderenroll

github.com

FrancoDT · Oct 27, 2025

dacrone said:
will running this and using opt 4 not work to get out of it?

GitHub - abbodi1406/offlineinsiderenroll: OfflineInsiderEnroll - A script to enable access to the Windows Insider Program on machines not signed in with Microsoft Account

OfflineInsiderEnroll - A script to enable access to the Windows Insider Program on machines not signed in with Microsoft Account - abbodi1406/offlineinsiderenroll

github.com

I honestly couldn't tell you without actually trying it and I'm hoping not to have a recurrence of this issue. I'm saving that video I posted just in case though lol.

FrancoDT · Oct 27, 2025

Latest Co-Pilot news on this:

Dev build 26220.6982 (KB5067109) appears to have been mistakenly offered to devices outside the Dev Channel, including those on Beta and even public builds, due to a deployment misconfiguration.
Here's what happened:
• Multiple reports from users on forums like ElevenForum indicate that Windows Update unexpectedly attempted to install Dev build 26220.6982 on systems running Beta Channel builds (e.g., 26120.6982) and even on non-Insider/public release builds.
• This behavior is not typical and suggests a backend servicing error where the update targeting logic misidentified eligibility criteria.
• Some users noted that the update appeared “out of the blue” in Windows Update, prompting them to pause updates or take drastic steps (like switching between Microsoft and local accounts) to prevent the Dev build from installing.
• Microsoft has not yet issued an official explanation, but this kind of cross-channel update push is usually the result of incorrect flighting metadata or misassigned update rings during rollout testing.

Solved Dev Build 26220.6982 trying to force install itself on PC's

Well-known member

Attachments

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Similar threads