Microsoft 365 Apps Not Working, Diagnosed and Fixed (2026 Guide)
Why Microsoft 365 Apps Stop Working
Picture this: you've got a deadline in 90 minutes, you double-click Word, and absolutely nothing happens. Or Excel opens to a completely blank screen. Or Access throws a cryptic error message that reads like it was written by someone who hates you. I've seen this exact scenario on dozens of machines across enterprise environments, home offices, and everything in between, and I can tell you with confidence that Microsoft 365 Apps not working is almost never caused by a single thing.
That's what makes it so maddening. The surface symptom looks simple, an app won't open, a feature is broken, a file won't save, but the root causes span a surprisingly wide range. You could be dealing with a corrupted installation, a sign-in conflict where "another account is already signed in," a damaged document that's choking the app on launch, or something as specific as a missing ODBC driver causing Access to silently freeze when you open a linked table.
Microsoft 365 Apps is a subscription-based suite that updates itself on a rolling basis. That's generally a good thing, you get security patches and feature improvements automatically. But it also means the version you installed six months ago is not the version running today, and occasionally an update introduces a regression. The Microsoft 365 Apps troubleshooting process has to account for this moving target.
Here's what the official documentation confirms as the main categories of failure:
- Word: Unsaved document recovery failures, corrupted or damaged document files, merge conflicts between documents
- Office Suite-wide: Converter download prompts that shouldn't appear, sign-in conflicts blocking app launch, work file creation errors during startup
- Excel: Formulas not counting correctly, workbook save failures, the blank white screen on launch
- PowerPoint: Slide export resolution problems, presentation corruption, fonts disappearing when sharing files
- OneNote: Notebook sync failures, offline location warnings, temporary file size download restrictions
- Access: Linked table freezes with SharePoint, SQL Server ODBC driver conflicts, ambiguous procedure name compile errors, database relationship errors
What makes these problems worse is that Microsoft's error messages are often almost useless for diagnosing root causes. "Could not create the work file" tells you nothing about whether the problem is a permissions issue, a temp folder path problem, or a corrupted installation. This guide cuts through that noise.
I know this is frustrating, especially when it blocks your work mid-session. But the good news is that fixing Microsoft 365 Apps is almost always achievable without reinstalling everything from scratch. Let's get you sorted. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go anywhere near registry edits or ODBC driver swaps, try the built-in repair tool. This resolves a surprising percentage of Microsoft 365 Apps not working cases, probably somewhere around 40-50% in my experience, and it takes less than five minutes.
Here's exactly what to do. Close every Office application first. Press Win + R, type appwiz.cpl, and hit Enter. That opens Programs and Features. Find Microsoft 365 Apps for Enterprise (or "Microsoft Office 365" depending on your install type) in the list. Click it once to select it, then click Change at the top of the window, not Uninstall.
You'll see two options: Quick Repair and Online Repair. Start with Quick Repair. It scans your installation files locally without needing an internet connection and replaces anything that looks corrupted. Click it, click Repair, and let it run. Takes roughly 2-4 minutes.
After it finishes, relaunch the specific app that was giving you trouble. If it works, great, you're done. If the problem persists, go back through the same steps and this time choose Online Repair. This one re-downloads the entire installation from Microsoft's servers and replaces every file. It takes longer (10-20 minutes depending on your connection speed) but it's far more thorough. Online Repair fixes problems that Quick Repair misses, particularly when installation files themselves are corrupted at a deep level.
One more thing to check before you start: if you're seeing the "Another account is already signed in" error when you try to open any Office app, that's a sign-in token conflict, and it won't be resolved by a repair. In that case, jump straight to Step 3 in the section below.
If Microsoft 365 Apps crashed mid-session and you're worried about lost data, do this before you touch anything else. Word, Excel, and PowerPoint all have AutoRecover built in, but you need to know where to look. Don't just relaunch the app and hope the recovery panel appears, because sometimes it doesn't.
For Word, navigate manually to this folder path in File Explorer:
C:\Users\[YourUsername]\AppData\Roaming\Microsoft\WordLook for files ending in .asd, those are AutoRecover saves. You can also open Word, go to File > Info > Manage Document > Recover Unsaved Documents. This opens a separate file browser pointed directly at the unsaved drafts folder.
For Excel, the path is:
C:\Users\[YourUsername]\AppData\Roaming\Microsoft\ExcelAnd within Excel, go to File > Info > Manage Workbook > Recover Unsaved Workbooks.
If Word or Excel themselves are failing to open (which is why you're here), you can still access these files directly through File Explorer without launching the app. Double-click the .asd file and Windows will try to open it in the associated application, or you can right-click and choose Open With to pick a specific app.
Once you've secured your recoverable files, then proceed with diagnosing and fixing the underlying Microsoft 365 Apps issue. Never skip this step, I've watched people reinstall Office only to realize afterward that their AutoRecover data was wiped in the process.
This error is one of the more common Office Suite-wide failures, and it almost always means something is wrong with your temporary file path or the permissions on the folder it points to. When Microsoft 365 Apps launch, they need to write temporary working files before they can open fully. If that write fails, you get this error and the app refuses to start.
First, check the Temp environment variable. Press Win + R, type sysdm.cpl, go to the Advanced tab, and click Environment Variables. Under "User variables," look for TEMP and TMP. Both should point to:
%USERPROFILE%\AppData\Local\TempIf either of them points to a network path, a deleted folder, or something that doesn't exist, that's your problem. Change them back to the local Temp path, click OK, then restart your machine.
Next, verify the Temp folder itself actually exists and that your account has write permissions to it. Open File Explorer, navigate to C:\Users\[YourUsername]\AppData\Local\Temp, and confirm the folder is there. If it's missing, create it manually. Then right-click the folder, choose Properties > Security, and confirm your user account has Full Control.
If this is happening on a domain-joined machine managed by IT, check whether Group Policy is redirecting your Temp folder to a network location, that's a common enterprise config that breaks Office startup. You'll need to either request an exception from your IT team or work around it by adjusting the per-user environment variables as described above.
After making changes, relaunch the Office app. If it opens cleanly, you've confirmed the temp folder was the culprit.
This one trips up a lot of people, particularly anyone who shares a machine, works with multiple Microsoft accounts, or recently changed their organization's tenant. The error appears during Office app launch and blocks you completely. The frustrating part is that the app is often already authenticating you silently in the background, but it's hitting a conflict with a cached token from a different account.
Here's the fix. Open the Windows Credential Manager. Press Win + S, type Credential Manager, and open it. Click Windows Credentials. Look for any entries that reference MicrosoftOffice, Office16, or your organization's domain. Remove them, click the entry, expand it, and click Remove.
Next, sign out of Office manually. Open any working Office app (or try to), go to File > Account, and click Sign Out under User Information. Then close the app completely.
Now open the Office app again. You'll be prompted to sign in fresh. Enter your correct Microsoft 365 credentials, and this time check the box that says "Allow my organization to manage my device" if it appears, this helps the token get stored correctly for future launches.
If you're on a corporate machine and your IT department uses Azure Active Directory conditional access policies, this error can also appear when your device's compliance status has lapsed, for example, after a period of inactivity. In that case, the fix isn't in Credential Manager. You'll need your device to re-check in with Intune or your MDM system. Running dsregcmd /status from an elevated command prompt will tell you whether your device is properly joined and compliant.
Once you're signed in cleanly, verify by going to File > Account in any Office app and confirming only your correct account appears under User Information.
Two very different apps, but they share a common failure pattern: the app launches but refuses to display any content. Excel shows a white screen. Word opens but the document looks corrupted or won't render. Both of these are documented Microsoft 365 Apps issues with specific causes.
For the Excel opening blank problem, the most common culprit is a DDE (Dynamic Data Exchange) setting conflict. Open Excel, go to File > Options > Advanced. Scroll down to the General section. Look for "Ignore other applications that use Dynamic Data Exchange (DDE)", if that box is checked, uncheck it. Click OK, close Excel, then try reopening a file normally by double-clicking it in File Explorer. This setting, when enabled, blocks Excel from receiving file-open commands from Windows Shell, which is why it opens but shows nothing.
If unchecking DDE doesn't help, the issue might be with your default file association. Open Settings, go to Apps > Default Apps, search for .xlsx, and make sure Excel is set as the default. Repeat for .xls and .csv if needed.
For damaged documents in Word, the official approach is to try opening the file in a different way to extract what it can. Go to File > Open > Browse, locate your document, but instead of just clicking Open, click the dropdown arrow next to the Open button. Choose Open and Repair. Word will attempt to reconstruct the document from whatever is salvageable in the file.
If Open and Repair fails, try copying the document's text through another method: paste the file path into WordPad (which opens .docx files in a degraded but sometimes workable way) or try inserting the file's contents into a new blank Word document via Insert > Object > Text from File.
If Microsoft Access is locking up the moment you click on a linked table, particularly one connected to a SharePoint list or SQL Server, you're dealing with one of two documented issues, and knowing which one matters for picking the right fix.
For SharePoint-linked table freezes: This happens when Access can't find locally cached credentials for the SharePoint site. There are three ways to resolve it. The fastest is to add a registry entry that re-enables legacy list authentication. Open Registry Editor (Win + R, type regedit), navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\ListCreate a new DWORD value named EnableLegacyListAuth and set its value to 1. Then verify that EnableADAL is set to 0 at:
HKCU\SOFTWARE\Microsoft\Office\16.0\Common\IdentityAlternatively, kill Access via Task Manager, reopen the database, right-click the linked table, select More Options > Refresh List, and log in with your credentials when prompted.
For the "String data, right truncation (#0)" error in Access with SQL Server: This error appears when you're trying to update a varchar(max) field containing more than 8,000 characters through a form or datasheet, and you're using the second or third-generation SQL Server ODBC driver. The cleanest fix is to change the data type in SQL Server from varchar(max) to nvarchar(max), this returns SQL_WVARCHAR values which have no character limit and bypass the truncation issue entirely. If changing the data type isn't an option, switching to the first-generation SQL Server ODBC driver (included in Windows Data Access Components) also resolves the error.
After applying either fix, restart Access and test the linked table or form again. The freeze and the error should both be gone.
Advanced Troubleshooting
If the steps above haven't resolved your Microsoft 365 Apps not working situation, it's time to go deeper. These techniques are for more persistent or environment-specific problems, domain-joined machines, Group Policy conflicts, enterprise deployments, and scenarios where the basic repair tools don't reach the real issue.
Check Event Viewer for Office Application Errors
Most people never look here, but Event Viewer is genuinely useful for Office crashes. Press Win + R, type eventvwr.msc, and navigate to Windows Logs > Application. Filter by Event Source, look for sources like Microsoft Office, Application Error, or the specific app name (WINWORD, EXCEL, MSACCESS). Event IDs in the 1000-1002 range are application crashes. The error detail often includes a faulting module name, something like mso20win32client.dll, which tells you exactly which component is failing and helps narrow down whether it's an Office file, a third-party add-in, or a Windows component.
Disable Add-ins in Safe Mode
Add-in conflicts cause a significant portion of Microsoft 365 Apps crashing cases that look like installation problems. Hold Ctrl while clicking the Office app icon to launch in Safe Mode, this disables all add-ins for that session. If the app works fine in Safe Mode but fails normally, an add-in is your culprit. Go to File > Options > Add-ins, change the Manage dropdown to "COM Add-ins," click Go, and start disabling add-ins one at a time until you identify the problematic one.
Fix "Ambiguous Name Detected" in Access VBA
If you're working in Access and hitting a compile error that reads "Ambiguous name detected: [ProcedureName]," this means you have two procedures with identical names in the same module, a duplicate. Open the form in Design view, go to View > Code (Access 2003) or Design tab > View Code (Access 2007 and later), then use Debug > Compile Database. When the compile stops and highlights the duplicate, find all instances of that procedure name in the module, determine which one is the correct version, and delete the other. Recompile to confirm the error is gone.
Group Policy and Enterprise Deployment Conflicts
In corporate environments, Group Policy Objects (GPOs) can override Office settings in ways that cause baffling behavior. Open an elevated command prompt and run:
gpresult /h C:\GPReport.htmlOpen the resulting HTML file and search for any Office-related policies. Pay particular attention to policies around "Trusted Locations," "Protected View," and "Block file formats", these frequently cause documents to fail to open or cause sign-in prompts that loop endlessly. If you find a policy that's clearly in conflict, work with your IT administrator to create an exception or adjust the policy scope.
PowerShell, Check Office Click-to-Run Service Status
Microsoft 365 Apps uses a Click-to-Run service to manage updates and licensing. If this service is stopped or broken, apps can fail to launch or lose activation. Run this in PowerShell as an administrator:
Get-Service -Name ClickToRunSvc | Select-Object Name, Status, StartTypeThe service should show as Running with a StartType of Automatic. If it's stopped, run:
Start-Service -Name ClickToRunSvcIf it fails to start, that's a deeper installation corruption and Online Repair is the right path.
gpresult before you call, it saves significant back-and-forth. You can reach support directly at Microsoft Support. For personal subscriptions, the support chat option is often faster than phone queues.
Prevention & Best Practices
Once you've fixed the immediate Microsoft 365 Apps issue, it's worth taking 20 minutes to set things up in a way that reduces the chance of this happening again. Most of these are one-time configuration changes that pay dividends for months.
Keep your Office version current. Microsoft 365 Apps updates on a monthly cadence by default, and many of the bugs described in this guide have already been patched in later builds. Staying current means you benefit from those patches automatically. You can check your current build by going to File > Account > About [App Name] in any Office application. The build number is shown there, compare it against Microsoft's release notes if you suspect a regression.
AutoSave and AutoRecover are your insurance policy. Make sure AutoRecover is enabled and set to a short interval, 5 minutes is reasonable for most people. Go to File > Options > Save in Word or Excel and confirm both "Save AutoRecover information every X minutes" and "Keep the last AutoRecovered version if I close without saving" are checked. This won't prevent crashes, but it drastically limits what you lose when one happens.
For Access users working with linked tables, especially SharePoint or SQL Server connections, document your ODBC driver version and test linked table connections after any major Windows update. ODBC driver updates bundled with Windows updates have been known to silently change the active driver version, which can reintroduce errors like the "String data, right truncation (#0)" problem.
If you manage Microsoft 365 for a team or organization, consider enabling the Monthly Enterprise Channel for updates rather than the Current Channel. Monthly Enterprise Channel releases updates that have already been in production for a month, giving you an extra layer of regression protection without falling too far behind on security patches.
- Set AutoRecover to save every 5 minutes in Word, Excel, and PowerPoint, go to File > Options > Save
- Store a copy of your ODBC driver version and Access linked table settings in a README file in your database folder, makes troubleshooting after Windows updates much faster
- Use Windows Credential Manager to remove stale Microsoft credentials immediately when you change your organization password, rather than waiting for an app to fail
- Run
Get-Service -Name ClickToRunSvcin PowerShell monthly to confirm the Click-to-Run service is healthy, schedule it as a 2-minute recurring task
Frequently Asked Questions
Why does Microsoft 365 keep asking me to sign in every time I open an app?
This usually means your authentication token is expiring or not being stored correctly. The two most common causes are a corrupted entry in Windows Credential Manager and a device compliance issue on a corporate machine. Start by opening Credential Manager (search for it in the Start menu), going to Windows Credentials, and removing any entries related to MicrosoftOffice or Office16. Then sign back in through File > Account in any Office app. If the problem returns within a day or two, check with your IT team, it's likely a conditional access policy or device enrollment issue that requires admin intervention.
Excel opens but shows a completely blank white screen, how do I fix this?
The blank white screen in Excel is almost always caused by a DDE (Dynamic Data Exchange) setting that's blocking Windows from passing the file-open command to Excel. Open Excel directly from the Start menu (not by double-clicking a file), then go to File > Options > Advanced, scroll to the General section, and uncheck "Ignore other applications that use Dynamic Data Exchange (DDE)." Click OK, close Excel, and try opening a file by double-clicking it again. If that doesn't fix it, also check your default app associations in Windows Settings, Excel should be set as the default for .xlsx, .xls, and .csv files.
My Access database freezes when I click on a table linked to SharePoint, what's going on?
This is a documented Microsoft issue that occurs when Access can't find locally cached credentials for the SharePoint site containing the linked list. Access tries to authenticate silently, fails, and hangs rather than showing a proper error. The fastest fix is to add a registry DWORD value called EnableLegacyListAuth set to 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\List. If you'd rather not edit the registry, kill Access in Task Manager, reopen the database, right-click the linked table, and select More Options > Refresh List to trigger a fresh authentication prompt. Note that for Access 2016, you need at least Click-to-Run version 1804 (build 9226.2114) for the registry method to work.
I'm getting "String data, right truncation (#0)" when updating a field in Access, what does that mean?
This error appears when you're trying to update a varchar(max) field in SQL Server through Access, the field contains more than 8,000 characters, and you're using the second or third-generation SQL Server ODBC driver. The driver hits a character limit that the field type technically shouldn't have, and Access throws this error instead of completing the update. The cleanest fix is to change the data type in SQL Server from varchar(max) to nvarchar(max), the nvarchar variant returns SQL_WVARCHAR data which doesn't have the 8,000-character limitation. If you can't change the data type, switching to the first-generation SQL Server ODBC driver (part of Windows Data Access Components) also resolves the issue.
PowerPoint slides look blurry or low-resolution when I export them as images, can I change this?
Yes, and it requires a registry edit because PowerPoint doesn't expose the export resolution in its own settings UI. By default, PowerPoint exports slides at 96 DPI, which looks terrible when you're creating images for printing or high-resolution displays. You can change this by adding a DWORD value called ExportBitmapResolution under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\PowerPoint\Options, set the value to 150 for standard quality or 300 for print-quality output. After adding the registry key, close and reopen PowerPoint, then use File > Export > Change File Type > PNG or JPEG and you'll get the higher-resolution output.
Microsoft 365 Apps won't activate, I keep getting a "Product Unlicensed" error even though I'm subscribed
Product Unlicensed errors despite an active subscription are almost always a token or licensing cache problem, not an actual subscription issue. Start by signing out of all Office apps (File > Account > Sign Out), then open a Command Prompt as administrator and run cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus to see what license state Office thinks it's in. If you see errors there, run the Online Repair process through appwiz.cpl, this resets the licensing cache. After repair, sign back in with your Microsoft 365 account and activation should complete automatically within a few minutes. If the problem persists, check that the Click-to-Run service is running and that your system clock is accurate, since token validation is time-sensitive.