How to Fix Microsoft 365 Sign-In Error “Something Went Wrong [1001]”

“Something went wrong [1001]” can appear when signing in to Microsoft 365 desktop apps on Windows. Start by checking whether the account works in a browser. If web sign-in succeeds while desktop apps fail, investigate the local sign-in components rather than repeatedly changing the password.

Microsoft documents more than one cause, including interference with the Web Account Manager (WAM) plug-in and problems with user-profile management. The error alone does not prove that your computer has malware or that one repair will fix every case.

1. Check the connection and scope of the failure

• Save your work, close the affected apps, and restart Windows.
• Check whether other websites load and whether the same Microsoft account can sign in on the web.
• Note which desktop apps fail and whether this is a personal or work/school account.
• Install available Windows and Microsoft 365 updates, then try again.

If the connection itself fails, use Windows’ network help. In Windows 11, look under Settings → System → Troubleshoot → Other troubleshooters; the options may open Get Help. Older screenshots may show different names.

If browser sign-in also fails, follow the displayed account or organization error. Re-registering a Windows component will not resolve every account restriction or service outage.

2. Repair WAM for the affected Windows user

Microsoft’s error 1001 guidance lists these commands as a possible temporary repair. Close Microsoft 365 apps first, as the commands can stop affected processes.

Open PowerShell in the affected user’s normal session. Use user mode rather than “Run as administrator.” On a managed device, ask IT to perform or approve the repair if your organization restricts it.

Run the following commands one at a time:

Add-AppxPackage -Register "$env:windirSystemAppsMicrosoft.AAD.BrokerPlugin_cw5n1h2txyewyAppxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

Add-AppxPackage -Register "$env:windirSystemAppsMicrosoft.Windows.CloudExperienceHost_cw5n1h2txyewyAppxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

The backslashes and double quotation marks matter. Double quotes let PowerShell expand $env:windir to the Windows directory. Do not paste a version in which the path separators are missing.

The screenshot is illustrative; follow the user-mode instructions and exact command text above. If a command reports a missing manifest, access denial, or another error, record it and stop rather than changing system permissions. Reopen the affected app and test sign-in.

3. Address a recurring failure

If the repair works only briefly, IT should investigate security-software interference and roaming or migrated profile data. Do not disable WAM, remove security protection, or disconnect a managed work account as a routine workaround.

Avoid deleting arbitrary Teams, Outlook, or OneDrive folders. Clearing %temp% is not a targeted WAM repair, and application data should not be treated as disposable cache.

For broader Windows corruption symptoms, the SFC and DISM guide explains a separate diagnostic path. It is not a guaranteed fix for authentication problems.

What to send to support

Record the exact error, affected apps, account type, whether web sign-in works, and the result of each repair. Include the Office version and build; the Office version guide shows where to find them. If available, use the web apps temporarily while your administrator or Microsoft Support investigates.