Fix Your Microsoft Account Requires Attention in Windows 11

"Your Microsoft account requires attention" shows up when you try to join the Windows Insider Program and the sign-in token Windows is holding for your Microsoft account has gone stale — usually because of a security check, a password change, or a Family/child account restriction it never tells you about. The fix in most cases is to re-link the account from Settings, not to click the on-screen "Fix" button, which frequently does nothing at all.

If you clicked Join the Insider Program and got stopped cold by a red banner reading "Your Microsoft account requires attention," you're not alone, and you're not doing anything wrong. It's one of the oldest, most persistent bugs in this specific corner of Settings — it was around when Windows 10 first opened Insider enrollment, and a version of it is still around now, just wearing a slightly different UI.

What's changed is what actually causes it, and what actually fixes it. The registry trick that used to be the go-to answer still exists, but on its own it fixes almost nothing in 2026. The real fix lives somewhere most people don't think to look: the sign-in relationship between your device and your Microsoft account, not the Insider Program screen itself.

Which Version of This Error Do You Actually Have?

Before you touch anything, figure out which of these you're looking at — they look almost identical but need different fixes:

Fix It on Windows 11 (This Is the One Most People Need)

These steps assume Windows 11 25H2 or 24H2, which is the vast majority of active installs right now. Work through them in order — don't skip to the registry method, it's not the fix most people think it is.

Method 1: Re-link the account from Settings > Accounts

This is the fix that actually works most of the time, and it isn't the button the error message points you to.

1. Open Settings (Win + I).
2. Go to Accounts > Your info.
3. Click Sign in with a local account instead and complete the switch — you'll set a temporary local username and password.
4. Restart, or just sign out and back in.
5. Go back to the same screen and click Sign in with a Microsoft account instead, and sign back in with the same account.
6. Open Windows Update > Windows Insider Program again.

What you're actually doing here is forcing Windows to throw away the stale token and negotiate a fresh one from scratch, which is exactly what the on-screen Fix button is supposed to do but frequently doesn't. The round trip through a local account is the reliable version of the same action. One more thing before you write this method off: if the switch completes cleanly but the Insider Program page still shows the error, restart the PC a second time — one restart isn't always enough for the fresh token to take everywhere.

Method 2: Sign in fresh through a full browser first

If Method 1 doesn't clear it, the token isn't just stale — it's being actively blocked, usually by a security challenge Microsoft's servers want to run that the embedded sign-in window inside Settings can't display properly. If your account has a pending "unusual sign-in" security flag waiting on it, this is the method you need — Method 1 alone won't clear that.

1. Open a normal browser and go to account.microsoft.com.
2. Sign in fully, completing any "we noticed unusual activity," password re-confirmation, or two-factor prompt it throws at you.
3. Once you're all the way in and see your account dashboard, go back to Windows Insider Program in Settings and try enrolling again.

Ethan's explanation for why this works, after Jake asked why opening a browser fixes a Settings problem: the sign-in window built into Settings is a stripped-down browser, and it can't always render the extra security screen Microsoft wants to show. Complete that screen once in a real browser, and the account is "clean" everywhere else on the device for a while.

Method 3: Confirm the account is actually allowed to join

This is the one people skip, and it's the one that wastes the most time, because no amount of re-linking fixes it. Windows Insider Program refuses two categories of Microsoft account, and it shows the exact same "requires attention" wording either way instead of telling you the real reason.

Family Safety / child accounts. Child accounts under the age of majority can't join. If this is the account on the device, you'll need an adult Microsoft account that's an administrator on the PC.

Work or school (Azure AD) accounts that aren't IT-managed for Insider access. If your PC is signed in with a company or school account and your organization hasn't specifically enabled Insider enrollment through Intune, the account will never fully authenticate for this feature. You'll need a personal Microsoft account instead, and it needs to be an administrator on the device.

Method 4: The registry fallback — EnableInsiderPreviewBuilds

This was the headline fix in the old version of this guide, back when Insider enrollment was newer and buggier. It still exists, and it can still help in one specific situation: when the Windows Insider Program page itself refuses to even show you the join option, rather than showing it and then rejecting your account.

1. Open Registry Editor (Win + R, type regedit, Enter).
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability.
3. Find EnableInsiderPreviewBuilds and set its value to 1. If the key doesn't exist, right-click the Applicability folder, choose New > DWORD (32-bit) Value, and name it exactly that.
4. Restart, then go to Windows Update > Windows Insider Program again.

Method 5: Check the system clock before you blame the account

An account sign-in token is checked against a certificate, and certificate checks depend on the device's clock being roughly correct. A PC with a dead CMOS battery, or one that's been offline for months and just booted up, can throw the exact same error purely because Windows thinks the certificate isn't valid yet or has already expired.

Go to Settings > Time & language > Date & time and confirm Set time automatically is on, then click Sync now if the option is there. It takes ten seconds to rule out and it's a genuinely common cause on machines that don't get restarted often.

Method 6: Clear the Windows Update cache

Rare, but worth knowing: a corrupted Windows Update download cache can make the Insider Program page behave as though your account is the problem when it's actually a broken local update state. The tell is usually that regular Windows Update also shows unrelated errors — a stuck download percentage, a generic 0x8024xxxx code — around the same time the Insider error started, rather than the Insider page being the only thing misbehaving on the device.

1. Open Command Prompt as administrator.
2. Run net stop wuauserv.
3. Delete the contents of C:\Windows\SoftwareDistribution\Download.
4. Run net start wuauserv, then restart the PC and try enrolling again.

Method 7: Automate the check (for the power user who scrolled this far)

If you're helping several machines in a shop or a small office, clicking through Settings on each one gets old. PowerShell can query the same registry state Method 4 edits and confirm whether the visibility flag is actually the problem before you touch a single UI:

Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\WindowsSelfHost\Applicability" -Name EnableInsiderPreviewBuilds -ErrorAction SilentlyContinue

No output, or a value of 0, tells you the visibility flag is off and Method 4 is worth trying. A value of 1 with the error still showing confirms it's an account problem, not a registry problem — skip straight to Method 1 or 2 and don't waste time in regedit.

What's Actually Changed Since This Error First Appeared

This exact error message has been showing up in Settings since Windows 10's earliest Insider builds, but the reason behind it isn't the same reason anymore. It's worth laying out plainly, because the old advice floating around the web — including our own original version of this post — was accurate for a version of Windows Insider Program that doesn't really exist in this form today.

Back in 2016, joining was a single decision between the Fast ring and the Slow ring, Microsoft account sign-in was the expected path but local-account workarounds during setup were common and mostly tolerated, and the "requires attention" error was almost always just a plain expired token — sign out, sign back in, done. There was no Family Safety enforcement blocking child accounts specifically for Insider, no separate re-consent flow, and no channel restructuring to worry about.

None of that setup exists in quite the same shape now. Microsoft account enrollment is enforced far more strictly at every stage of Windows 11 — the local-account bypass during initial setup was removed outright in 2025 — and two-factor authentication is the default rather than the exception, which is exactly the kind of interruption that produces Method 2's "requires attention" symptom. Child accounts under the age of majority are now blocked from Insider enrollment specifically, which wasn't a documented restriction a decade ago. And the channel names themselves have already been rebuilt once this year. The error message hasn't changed in ten years. Almost everything sitting behind it has.

The registry key in Method 4 is the clearest example of a fix that used to matter more than it does now.

The 2026 Channel Restructure Can Trigger the Same Error

If you were already enrolled and this error appeared out of nowhere after an update, this is very likely why. In spring 2026 Microsoft retired the familiar Dev and Canary channel names and replaced them with a new structure:

Existing enrollments were migrated automatically for most people, but on some accounts — particularly ones that had been dormant on an old channel for a long time — Windows asks you to re-consent to the new terms before continuing. That re-consent step goes through the same authentication flow as a fresh sign-in, and if your token happens to be stale at that exact moment, you get the "requires attention" banner instead of a clean channel migration. Method 1 or 2 above clears this the same way it clears a first-time enrollment error.

One honest limitation here: we can't promise the exact channel names or migration behavior won't shift again before you read this. Microsoft has changed this structure once already in 2026, and it's the kind of thing that can move without much notice. If a channel name in Settings doesn't match what's described above, that's the most likely reason, not a sign something's broken on your end.

Windows 10: Why You Won't See This Screen at All

When this guide first went up, the "requires attention" error was purely a Windows 10 problem — that's what the Insider Program looked like at the time, and the steps above worked exactly as described for it. Two things have since changed the picture completely. First, Microsoft wound down Windows 10 Insider builds ahead of end of support — the reopened Beta Channel closed in late 2024 — and today the option is gone entirely, not hidden behind a setting or a registry key somewhere. Second, Windows 10 reached end of support on October 14, 2025. It still boots and runs, but without enrolling in Extended Security Updates it no longer receives free security patches.

If you're on Windows 10 and came here looking for Insider builds specifically, there's nothing to fix — the feature isn't there to fix. What's actually worth your time instead is making sure the machine is covered: Consumer ESU is still open for enrollment as of this rewrite, runs through October 2027 for enrolled devices, and costs either nothing (if you sync settings through Windows Backup), 1,000 Microsoft Rewards points, or a one-time roughly $30. It's genuinely one of the better deals in the Windows ecosystem right now, and it buys real time to plan a Windows 11 upgrade instead of being rushed into one.

Skip the Account Fight Entirely: Third-Party Routes

Jake's actual question after the third failed attempt was blunt: "Is there just... a way to get the ISO without dealing with any of this?" There is, and it's honest to say so, with the trade-offs named.

UUP dump repackages the same update files Microsoft's own Insider servers deliver into a downloadable ISO you install like any other Windows image, with no Microsoft account gate at all. It's a legitimate, widely used tool among enthusiasts and IT people who want a specific build's bits without an ongoing enrollment. What you give up: no automatic future Insider updates, no feedback hub reporting, and you're responsible for tracking when a build goes end-of-life yourself.

One thing worth doing regardless of which route you take: verify the SHA256 checksum of any downloaded ISO against the value UUP dump displays before you install from it, using Get-FileHash in PowerShell. It's a one-line check, and it's the difference between confirming you got Microsoft's actual build files and installing whatever a mirror happened to serve you that day.

Testing in a VM, on a Laptop, or Over Remote Desktop

A few edge setups worth knowing about before you spend an afternoon on this:

Virtual machines. You still need a working Microsoft account inside the VM — the account check happens regardless of whether Windows is running on real hardware or virtualized. What a VM buys you is isolation: if the build breaks something, it's a snapshot rollback, not a wrecked daily driver. If you're going to fight through Methods 1–3 anyway, do it inside a VM first.

Laptops that sleep instead of shutting down. The clock-drift issue in Method 5 shows up disproportionately on laptops that are closed and reopened for weeks without a full restart. If Insider enrollment fails on a laptop specifically, check the clock before anything else.

Remote Desktop / VDI sessions. Insider enrollment inside an RDP session to a remote machine behaves the same as local, but the "sign in through a full browser" step in Method 2 sometimes needs to happen on the actual remote session, not your local machine's browser, because the token being checked belongs to the remote device.

Azure Virtual Desktop and Windows 365 Cloud PC. If you're testing Insider builds on a Cloud PC rather than physical hardware, enrollment is usually managed centrally by an administrator through Intune rather than the per-device toggle in Settings, and the "requires attention" error on a Cloud PC more often points to a policy conflict than a token issue — an admin has enabled the Windows Insider Program policy but the specific account hasn't been granted the right license or role assignment yet. If you hit this on a work-issued Cloud PC, that's a request for IT, not something Methods 1 through 6 above will resolve, since the account restriction is being enforced by policy rather than by Microsoft's consumer authentication flow.

If Nothing Above Works

We won't pretend there's always a fix. Occasionally the account itself is genuinely in a bad state on Microsoft's side — flagged for suspicious activity, mid-recovery after a compromise, or stuck in a support ticket queue — and no amount of local troubleshooting reaches that. If you've tried Methods 1 through 3 and the account still won't authenticate for Insider specifically while working fine everywhere else, that's the likely explanation.

• Try a second, unused Microsoft account you don't mind creating just for this test. If it enrolls cleanly, the problem is scoped to the original account, not the PC.
• Create a fresh local administrator account on the same device and attempt enrollment from there with the same Microsoft account. This isolates whether the device profile itself is corrupted.
• Contact Microsoft support directly about the account, specifically mentioning Windows Insider Program enrollment — general troubleshooting steps can't fix an account-side restriction, only Microsoft can lift one.

Before You Fight to Get In: Should You?

Jake asked this after his second call: "I'm about to spend my Saturday fighting an account error just to get a version of Windows that isn't even finished yet. Why would I do that on purpose?"

Ethan's honest answer: most people shouldn't. Beta and Experimental builds break things — drivers stop working, apps crash, the odd update fails to install cleanly. If this is your only PC, or a machine a business depends on, Release Preview is the only channel worth the risk, because it's the closest to what's about to ship publicly. Beta and the Experimental tiers are for a spare laptop, not a daily driver.

Worth naming plainly: joining also means Microsoft collects more diagnostic data from the device than a standard install. Insider builds ship with diagnostic data set to the fuller "Optional" level by default rather than "Required," and the Feedback Hub app ties whatever you report — screenshots, crash details, comments — directly to the Microsoft account you enrolled with. And this one isn't optional in practice: sending optional diagnostic data is a requirement of staying enrolled. Turn it off under Settings > Privacy & security > Diagnostics & feedback and Windows stops delivering Insider builds to the device entirely — there is no way to run Insider builds while keeping diagnostic data at the lower level. If that trade-off matters to you — a work laptop, a machine handling client data — it's a reason to test in an isolated VM per the section above rather than on the machine itself, not a reason to avoid Insider builds entirely.

The one hardware check worth doing before you fight the account error at all: if the Insider toggle is grayed out rather than showing the "requires attention" banner, that's not an account problem — it's a hardware eligibility block. Windows 11 Insider builds still require TPM 2.0, Secure Boot capability, and a CPU on Microsoft's approved list. No account fix gets around that; it needs an unsupported install method instead, which carries its own risks around future update reliability.

Once You're In: What to Do Next

Pick Release Preview unless you have a specific reason to want earlier features — it's the sane default for anyone not doing dedicated testing. After your first Insider update installs, you have a limited window (typically around ten days) where you can roll back to your previous build cleanly through Settings > System > Recovery if something breaks. Past that window, rolling back means a clean reinstall, so don't let a bad build sit untouched for two weeks assuming you can always undo it later.

Back up anything you can't afford to lose before your first Insider update lands, the same way you would before any major update. Jake's shop rule after a customer's laptop hit a bad Insider build mid-project: nothing that matters lives only on a machine running pre-release Windows.

If you do hit a genuine bug, report it through the Feedback Hub app rather than a forum post — it's the only channel that reaches the actual build team, and a report with reproduction steps and the exact build number attached is far more likely to get looked at than a one-line complaint. Search for the issue first; duplicate reports without new information tend to get triaged lower than the original.

Frequently Asked Questions

What does "Your Microsoft account requires attention" actually mean?

It means the sign-in token Windows stored for your account has gone stale or been invalidated, usually by a password change or a security challenge, and Windows can't silently re-verify you until you sign in again.

Do I need a Microsoft account to install Windows Insider Preview builds?

Yes, to join and manage the enrollment itself. You can switch to a local account afterward for day-to-day use, but joining and choosing a channel both require a signed-in Microsoft account.

Why does the Fix button in Windows Insider Program not do anything?

It re-runs the same silent check that already failed, so on a genuinely expired token it just returns the same error. It only helps with brief network hiccups, not real authentication problems.

Can I use a child or Family Safety account for Windows Insider builds?

Child accounts under the age of majority can't join. You'll need an adult Microsoft account that's an administrator on the device.

Can I join Windows Insider Program with a work or school (Azure AD) account?

Only if your organization's IT admin has specifically enabled it through Intune or Group Policy. On an unmanaged work account, expect this error indefinitely.

Is the EnableInsiderPreviewBuilds registry key safe to use?

Safe to set, but it only makes the option visible. It doesn't fix an expired token or a blocked account, so treat it as a narrow fallback, not a first move.

Why did my Insider channel disappear or get renamed?

Microsoft restructured the channels in spring 2026, replacing Dev and Canary with Beta, Experimental, Experimental (26H1), and Experimental (Future Platforms). Re-consenting to the change can surface this same error.

Does Windows 10 still get Insider Preview builds?

No. Microsoft wound down Windows 10 Insider builds ahead of end of support — the reopened Beta Channel closed in late 2024 — and today the option is gone entirely, so it isn't there to trigger this error.

Will joining Windows Insider Program void my warranty or break my PC?

It won't touch your warranty, but pre-release builds do break things — driver issues and app crashes aren't rare. Avoid running them on your only PC.

How do I leave the Windows Insider Program and go back to a stable build?

Unenroll under Settings > Windows Update > Windows Insider Program, then either wait for the next public release or do a clean install of the current stable version if you need out immediately.

Why does two-factor authentication fail during the Insider sign-in step?

The embedded sign-in window inside Settings sometimes can't render the extra security prompt properly. Completing it once in a full browser at account.microsoft.com usually clears it.

My PC doesn't meet Windows 11 requirements — can I still get Insider builds?

Only through an unsupported install method, and Microsoft can block enrollment outright on hardware that fails TPM 2.0, Secure Boot, or the approved-CPU list. An account fix won't help here.

Does changing my time zone or region fix the "requires attention" error?

Not directly, but a wrong system clock can break the certificate check behind the sign-in token and produce the same symptom, so it's worth ruling out first.

Should I use a local admin account or my everyday account for testing Insider builds?

Use a separate local administrator account where possible, and keep your everyday Microsoft account off the test machine so a broken build only risks a throwaway profile.

Can I use a UUP dump ISO instead of fighting this error?

Yes, if you just want a specific build's files rather than ongoing enrollment. It skips the account gate entirely but you lose automatic future updates and feedback reporting.

Can I run Windows Insider builds in a virtual machine to avoid this account hassle?

You still need a working Microsoft account inside the VM, so it doesn't skip the authentication step, but it isolates any breakage to a disposable VM instead of your real machine.

Has joining Windows Insider Program gotten harder since 2016?

In practice, yes. Microsoft account enrollment is enforced more strictly, two-factor authentication is now the default rather than optional, and child accounts under the age of majority are blocked in a way they weren't originally. The underlying error message hasn't changed, but more things can now trigger it.

Revision note. Originally published December 21, 2016, describing this error on Windows 10 at the start of the Insider Program. Rewritten August 2026 for Windows 11 25H2 and 24H2. Microsoft has since retired Windows 10 Insider enrollment entirely, restructured the channel names in spring 2026, and Windows 10 itself reached end of support in October 2025 — the steps above reflect the current sign-in flow and account restrictions. If you've been staring at this same stubborn screen since the Windows 10 days, we hope this is the visit that finally gets you past it.