Office Apps Stuck on “Getting Office Ready” Splash Screen

Microsoft 365 apps become stuck on the “Getting Office Ready” splash screen when the Office Click-to-Run service hangs while trying to provision initial user registry settings or validate license tokens. This loading loop prevents Word, Excel, and Outlook from opening the main user interface. It is caused by stalled background processes, corrupt FirstRun registry keys, or interrupted auto-updates. Ending background Click-to-Run tasks, running Office in Safe Mode, or disabling the FirstRun wizard via the Windows Registry restores normal app startup immediately.

Fast-Fix: The 45-Second Solution

The “Getting Office Ready” freeze occurs when the Click-to-Run service stalls during initial user provisioning or background licensing validation. Risk Tier: Low to Moderate. Fix it by killing all Office background processes in Task Manager, launching Word in Safe Mode (winword /safe) to bypass the splash screen, or repairing the Click-to-Run service through Windows Installed Apps.

Diagnostic Snapshot

• Severity Tier: Low to Moderate (App launch blocked on desktop; web apps remain fully accessible).
• Data Safety Risk: Minimal (Existing documents and cloud files are completely unaffected).
• Common Cause: Stalled Office Click-to-Run service process, incomplete FirstRun setup registry keys, or conflicting background updates.
• Admin Requirement: Standard user account for process termination and Safe Mode launch; Local Administrator rights required for registry edits or full repairs.

Condition: Low Risk vs. High Risk

• Low Risk: The splash screen freeze occurs after a fresh installation or Windows update on a single application, and closing the app via Task Manager clears the hang on second launch.
• High Risk: The loading screen hangs infinitely across every desktop app (Word, Excel, Outlook, PowerPoint), persists after a full system reboot, or affects multiple workstations across a enterprise-managed tenant following a Group Policy deployment.

The System Break (What This Means)

When you launch a Microsoft 365 application, the app executes a pre-flight startup sequence before displaying the main workspace. The main program executable calls the Office Click-to-Run engine (OfficeClickToRun.exe) to check user licensing tokens, query the local identity cache, and write initial configuration flags into the user registry profile.

Think of it like an engine starter motor spinning endlessly because the flywheel teeth won’t engage, the core application code is intact, but the ignition sequence is jammed waiting for a handshake signal that never returns. If the Click-to-Run service fails to finish reading the FirstRun registry key or encounters a file lock while updating background components, the loading animation loops indefinitely while the application thread waits for a completion signal that never arrives.

Root Cause Probability

• Likely (60%): A stalled or orphaned OfficeClickToRun.exe background thread blocking new application calls.
• Possible (30%): Unfinished or corrupted FirstRun setup configuration keys in HKCU\Software\Microsoft\Office\16.0\Common\General.
• Rare (10%): Corrupted Click-to-Run installation binaries resulting from a disrupted background update.

Conflict Escalators

• Pending Windows or Office Updates: Interrupted background updates lock shared Office binaries, causing new startup calls to wait for file locks to release.
• Third-Party Antivirus & Endpoint Security: Real-time file scanners inspecting %LocalAppData%\Microsoft\Office\16.0 can delay or block registry writes during startup.
• Roaming Profiles & VDI Deployments: Virtualized environments that purge local registry hives upon logoff often trigger the first-run initialization sequence on every single login.

Progression: 1 Hour -> 24 Hours -> 1 Week

• 1 Hour: Applications remain non-responsive on launch, showing the splash screen until force-closed through Task Manager.
• 24 Hours: Users are completely locked out of desktop applications, though documents can still be opened and edited through Office on the Web.
• 1 Week: Unresolved installation locks can stall broader Windows update routines and prevent Office auto-updates from applying critical security patches.

Common Misdiagnoses

• Misdiagnosed as Activation Token Failure: Do not attempt account relinking or license resets yet. If the app is freezing before the UI opens, the license service hasn’t failed, it simply hasn’t been reached. If apps open but close immediately after loading, consult Microsoft 365 Apps Closing Immediately After Sign-in.
• Misdiagnosed as Identity Vault Corruption: Clearing Windows Credential Manager will not resolve a stuck startup thread. Credential resets are only necessary if sign-in prompts loop continuously after the UI loads; see How to Clear Office Credential Cache on Windows 11 (The Modern Way).
• Misdiagnosed as Server Timeout: Network connection issues throw explicit dialogs rather than endless splash screens. If you suspect network transport drops, review Office Activation Fails with “Server Not Responding”.

Immediate Action Steps

Step 1: Force End Stuck Click-to-Run Processes

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Select the Details tab.
3. Locate and select the following processes if present:
   • WINWORD.EXE
   • EXCEL.EXE
   • OUTLOOK.EXE
   • OfficeClickToRun.exe
4. Click End task for each process.
5. Alternatively, open Command Prompt as Administrator and run: DOS taskkill /f /im OfficeClickToRun.exe taskkill /f /im WINWORD.EXE
6. Relaunch Word or Excel to check if the app opens normally.

Step 2: Launch Office Apps in Safe Mode

Running Office in Safe Mode bypasses add-ins, customized templates, and initial splash screen opt-in checks.

1. Press Windows Key + R to open the Run dialog.
2. Type winword /safe and press Enter. (For Excel, use excel /safe; for Outlook, use outlook /safe).
3. If the app opens in Safe Mode, navigate to File > Options > Add-ins.
4. Select COM Add-ins from the Manage dropdown and click Go.
5. Uncheck all active add-ins and click OK.
6. Close the application and launch it normally.

Step 3: Bypass FirstRun Registry Handshakes

If the FirstRun setup wizard is looping in the background, set its registry values to a completed state manually.

1. Press Windows Key + R, type regedit, and press Enter.
2. Navigate to the following path:
   HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\General
3. Right-click in the right panel, select New > DWORD (32-bit) Value, and name it ShownFirstRunOptin.
4. Double-click ShownFirstRunOptin and set its Value data to 1.
5. Locate the key FirstRun under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\General if it exists, right-click it, and select Delete.
6. Close Registry Editor and restart your PC.

Step 4: Run a Quick Repair on the Office Click-to-Run Engine

If background binaries are corrupted, run a repair to re-register the Click-to-Run services.

1. Press Windows Key + R, type appwiz.cpl, and press Enter.
2. Scroll down and select Microsoft 365 Apps (or your installed Office version).
3. Click Change at the top of the window.
4. Select Quick Repair and click Repair.
5. Once complete, relaunch your Office application.

Hard-Stop Red Flags

• “Background Installation Error”: If Quick Repair throws an error stating Office setup cannot continue, the Click-to-Run service files are severely damaged, requiring an uninstall and reinstall using the Microsoft Support and Recovery Assistant. For activation reset steps, see How to Reset the Microsoft 365 Activation State (Using SaRA Tool).
• Access Denied Errors During Registry Modifies: If editing 16.0\Common\General returns permission blocks despite using an Administrator account, review permissions using How to Fix “0x80070005” Access Denied Activation Error.

What the IT Admin Will Check

1. Click-to-Run Service Status: Ensure the ClickToRunSvc service is running under services.msc and set to Automatic startup type.
2. Group Policy Overrides: Check if Group Policy or Intune policies are enforcing conflicting FirstRun preferences under User Configuration > Administrative Templates > Microsoft Office 2016 > First Run Install.
3. Software Restriction Policies: Verify that AppLocker or Windows Defender Application Control (WDAC) is not blocking execution paths in %ProgramFiles%\Common Files\microsoft shared\ClickToRun.

Resolution Complexity

• Minor to Moderate: Ending background tasks or launching Safe Mode resolves most user instances within minutes. Modifying registry keys requires standard local administrative rights.

Related Error Escalators

• If clearing the splash screen leads directly to modern authentication prompt loops, review How to Resolve Modern Authentication (ADAL/MSAL) Failures in 2025.

Ticket Closed

An endless “Getting Office Ready” screen is a startup sequence hang rather than a broken installation or expired subscription. Terminating stuck OfficeClickToRun.exe tasks and marking the ShownFirstRunOptin registry flag as complete bypasses the blocked setup wizard and returns Microsoft 365 apps to normal operation.