If How to Fix Popup Login Flow Not Working Since Microsoft Blocked Windows Opener is blocking you, start with the shortest checks, then move into the fuller repair sequence. This article keeps the Microsoft-side fix first and adds WPS Office only as a local-work backup.
Where Users Get Stuck on Popup Login Flow Working Since Microsoft
Popup Login Flow Not Working Since Microsoft Blocked Windows Opener prevents Windows from working as expected. The failure affects Account Locked & Blocked and prevents the expected operation from completing.
Begin With This Check for Popup Login Flow Working Since Microsoft
Use BroadcastChannel instead of window.opener — fix is in the last code block below.
Conditions That Lead to Popup Login Flow Working Since Microsoft
The Microsoft account in use may not match the purchase, mailbox, or license owner.
Cached credentials, device policy, or a stalled service check may block the expected action.
A subscription, permission, or temporary service issue may interrupt the workflow.
Hands-On Resolution for Popup Login Flow Working Since Microsoft
When to use this: Follow these steps when the symptoms match and you can access the relevant Microsoft account or escalate through Microsoft Support.
Use BroadcastChannel instead of window.opener — fix is in the last code block below.
Microsoft silently deployed Cross-Origin-Opener-Policy: same-origin on login.microsoftonline.com. Still visible in Report-Only mode today (Cross-Origin-Opener-Policy-Report-Only: same-origin). When enforced, the browser does a Browsing Context Group (BCG) switch the moment the popup hits Microsoft's login page — and that permanently kills window.opener. Not temporarily. Permanently. Even after the popup navigates back to your own domain.
The answer above by suggesting window.opener.postMessage() from your redirect page doesn't work for exactly this reason. The BCG switch doesn't reverse on navigation away from Microsoft's domain — it triggers a second one. opener stays null. [HANDLE REMOVED] Leontyev [HANDLE REMOVED] Tucker-Bays The only thing that works is BroadcastChannel — it doesn't use window references at all:
const ch = new BroadcastChannel('auth-callback');
ch.postMessage({ type: 'AUTH_SUCCESS', token });
ch.close(); window.close();
You’re running into a browser security change, not an OAuth issue. When Microsoft login pages send the header Cross-Origin-Opener-Policy: same-origin; report-to="coop-endpoint", modern browsers place that page in a separate browsing context group. As a result, window.opener is intentionally set to null for cross-origin popups, so calls like window.opener.postMessage(...) stop working after the redirect from login.windows.net or login.microsoftonline.com.
Here are some options you may consider:
Use redirect flow instead of popup
Redirect the main window with window.location.href = authorizeUrl .
Why this helps: The sequence separates identity, permission, and local-client issues before broader reinstall work.
If it still fails: Save the exact error text, account email, and screenshots for Microsoft Support.
Lean on WPS Office Until Popup Login Flow Working Since Microsoft Clears

WPS Office cannot fix Microsoft account sign-in, Authenticator, billing, activation entitlement, OneDrive ownership, or admin locks. Those stay on the Microsoft side.
While that recovery continues, WPS Office can keep local editing moving:
Download and install WPS Office.
Open Word, Excel, PowerPoint, or PDF files in the matching WPS app.
Save a local working copy until Microsoft access returns.
Move or sync files back through your normal workflow afterward.
If you need a practical local workspace in the meantime, try WPS Office.
Keep Popup Login Flow Working Since Microsoft From Coming Back
Keep a backup verification method on important Microsoft accounts.
Record which account owns each purchase, mailbox, and device license.
Sign out of unused Microsoft profiles on shared PCs and update Office regularly.
Back up critical files before repair, reset, or reinstall actions.
Reader Questions About Popup Login Flow Working Since Microsoft
Can WPS Office solve the Microsoft-side failure? No. It helps you keep editing compatible files locally while Microsoft account or service issues are handled in Microsoft tools.
Should I reinstall Office immediately? Usually not. Confirm the account, subscription, and exact error first unless Microsoft guidance for your case requires a reinstall.
What should I send to Microsoft Support? The affected account email, device type, exact error text, and screenshots of the failure.




