How to Fix OneNote Startup Crashes on Domain-Joined Windows Computers
Question details
Users on domain-joined Windows computers are experiencing persistent startup crashes when attempting to launch Microsoft OneNote.

- Product
- Microsoft OneNote (Microsoft 365 Apps)
- Device & OS
- Windows
- Scenario
- Launching OneNote in an enterprise environment managed by domain Group Policies.
- Observed behavior
- ONENOTE.EXE crashes upon startup before the user interface loads, which persists even after standard repairs, reinstalls, or clearing application data.
Ensure you have local administrator privileges or can coordinate with your IT department, as resolving this issue requires modifying the Windows Registry and verifying domain Group Policies.
Modify the Server Reachability Registry Policy
Adjusting the DisableServerReachability registry key resolves crashes caused by strict Office policies preventing necessary network access.
This issue is frequently caused by a Group Policy Object (GPO) or logon script that incorrectly restricts Microsoft Office's ability to reach necessary server resources or document caches.
Press the Windows key + R to open the Run dialog, type 'regedit', and press Enter to launch the Registry Editor.
Using the left-hand navigation pane, go to HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Common\Internet.
Locate the 'DisableServerReachability' DWORD value on the right panel. Double-click it, change the Value data to '0', and click OK.
Restart your computer to ensure the changes take effect and attempt to launch OneNote from the Start menu.

Review Group Policy and Logon Scripts (For IT Admins)
Identify and update the specific domain policy that is distributing the problematic registry key to affected workstations.
Test OneNote with a Controlled Local User Account
Isolate the issue by verifying whether the crash is tied to the domain user profile or is a machine-wide installation defect.
Experience a Stable and Lightweight Office Alternative
If your organization is facing persistent deployment and startup crashes with Microsoft Office applications, consider switching to WPS Office. It provides a robust, lightweight suite with excellent compatibility for your document needs, free from complex domain policy conflicts.
- 1. Visit the Official Website: Navigate to wps.com in your web browser to access the free installer.
- 2. Install the Software: Run the downloaded executable file to install the lightweight suite on your Windows machine.
- 3. Start Working Immediately: Open your existing Office files directly in WPS Office without needing to convert them.

Frequently Asked Questions
Why does OneNote crash immediately on startup without an error message?
Immediate crashes are often caused by restrictive Group Policies, specifically the DisableServerReachability registry key, which aggressively prevents OneNote from accessing required cloud services and document caches during its initial startup phase.
Will reinstalling Microsoft 365 fix the domain-joined OneNote crash?
Typically, reinstalling, repairing, or clearing application data will not resolve this issue if a domain Group Policy is actively pushing a conflicting registry setting. The underlying GPO must be corrected by an administrator.
How can I check my Office version if OneNote crashes before opening?
You can check your exact Office version build by opening another functioning Microsoft 365 application, such as Word or Excel, and navigating to File > Account. The version information displayed there applies to the entire Office suite.




