Interactive Troubleshooter

Published: Sep 22, 2026

Excel File Crashes on Open: Safe Mode and Add-ins Recovery Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Excel startup crashes are typically caused by faulty COM add-in DLL hooks, corrupted startup template files, hardware acceleration conflicts with display drivers, or bad registry keys. This interactive diagnostic decision tree systematically isolates process execution paths, isolates faulting modules via Windows Event Viewer, and recovers affected workbooks using Excel Safe Mode and registry repairs.

Full Diagnostic Tree & Step-by-Step Overview

What occurs when launching Microsoft Excel or opening a specific workbook file?

Excel opens normally in Safe Mode (`excel /safe`), but crashes or freezes instantly during standard launch
Excel crashes immediately on startup regardless of whether Safe Mode is used or if launching without a file
Excel launches fine, but crashes instantly when opening one specific `.xlsx`, `.xlsm`, or `.xlsb` file
Excel launches, displays a white/grey blank canvas, and freezes with 'Not Responding' when switching displays or rendering sheets

Since Excel opens cleanly in Safe Mode, which environment component triggers the crash in normal mode?

Crash occurs due to an active third-party COM Add-in or Excel Add-in (.xlam)
Crash is caused by corrupt files or templates inside the XLSTART auto-load directory
Crash is caused by corrupt user options or toolbar registry keys in HKEY_CURRENT_USER
Crash is caused by a default network printer or printer driver communication timeout during layout initialization

Disable Faulty COM Add-ins via Binary Search and Registry In-Process Server Flags

Solution:

Root Cause: Unhandled In-Process DLL Exception in COM Add-in

When Excel starts normally, it initializes registered Component Object Model (COM) add-ins registered in HKLM or HKCU. A corrupted or incompatible DLL (e.g., outdated PDF creators, financial terminal plugins, or legacy antivirus hooks) injects unhandled exceptions into the excel.exe process space, causing an immediate crash.

Diagnostic Verification:

1Open Event Viewer (eventvwr.msc).

2Navigate to Windows Logs > Application.

3Filter for Event ID 1000 (Application Error) with Source Application Error.

4Check the Faulting module name (e.g., ABBYY_FINEREADER.DLL, PowerPivot.dll, VBE7.DLL).

Step-by-Step Fix:

1Launch Excel in Safe Mode: Press Win + R, type excel /safe, and press Enter.

2Navigate to File > Options > Add-ins.

3At the bottom of the window, select COM Add-ins from the Manage dropdown and click Go....

4Uncheck all active COM Add-ins and click OK.

5Restart Excel normally. If it boots successfully, re-enable add-ins one by one to identify the faulting DLL.

6To force-disable stubborn add-ins via Windows Registry:

Open regedit.exe and navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\

Select the target add-in subkey and change the LoadBehavior DWORD value from 3 (Load at startup) to 0 (Disabled).

Prevention & Long-Term Monitoring:

Audit third-party COM add-ins prior to major Office architecture updates (e.g., 32-bit to 64-bit migrations). Refer to the Microsoft Official Support Guide for detailed add-in management rules.

Clear Corrupted Workbooks and Templates from XLSTART and Startup Folders

Solution:

Root Cause: Corrupted Auto-Load Workspace or Template File

Excel automatically evaluates and opens every workbook, macro sheet, or template located within designated startup folders (XLSTART) during process invocation. If Personal.xlsb or a custom Book.xltx file becomes corrupted, Excel crashes during the pre-render boot sequence.

Diagnostic Verification:

Verify if Excel opens cleanly when suppressing startup files:

1Press Win + R, type excel /unregserver, and press Enter to reset registration.

2Execute excel /safe. If Safe Mode works, inspect the XLSTART directory paths for unauthorized or corrupt binary files.

Step-by-Step Fix:

1Close all Excel processes using Task Manager or PowerShell:

powershell
   Stop-Process -Name "EXCEL" -Force -ErrorAction SilentlyContinue

2Navigate to the primary user XLSTART directory:

C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Excel\XLSTART\

3Cut all files (including PERSONAL.XLSB) and paste them into a temporary backup folder on your Desktop.

4Navigate to the system-wide Office startup directory:

64-bit Office: C:\Program Files\Microsoft Office\root\Office16\XLSTART\

32-bit Office: C:\Program Files (x86)\Microsoft Office\root\Office16\XLSTART\

5Clear any custom files found inside this folder.

6Check alternative startup paths defined in Excel settings by navigating in Safe Mode to File > Options > Advanced > General and clearing the At startup, open all files in: path.

7Launch Excel normally.

Prevention & Long-Term Monitoring:

Avoid manually placing untrusted macro files directly into XLSTART. Maintain periodic backups of PERSONAL.XLSB.

Rebuild Corrupted Excel HKCU Registry Subkeys and Ribbon Customizations

Solution:

Root Cause: Registry Key Corruption in User Profile Options Hive

User-specific settings, UI panel layouts, gridline preferences, and custom Ribbon toolbar files (Excel.officeUI) are written to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel. Invalid pointer references or corrupted binary blobs in these keys prevent Excel from constructing the main window frame.

Diagnostic Verification:

Create a test local user profile on the machine and launch Excel. If Excel launches without error under the new user profile, the issue is isolated to the original user's HKCU registry hive.

Step-by-Step Fix:

1Exit Excel completely.

2Open the Windows Registry Editor (regedit.exe).

3Navigate to the main Excel configuration hive:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel

4Right-click the Excel key, select Export, and save a backup named Excel_Registry_Backup.reg to your Desktop.

5Delete the Options subkey under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Options.

6Delete the Resiliency subkey located at:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Resiliency

7Rename the custom toolbar file to reset the UI frame layout:

Navigate to %LOCALAPPDATA%\Microsoft\Office\

Rename Excel.officeUI to Excel.officeUI.old

8Restart Excel normally. Office will automatically regenerate default registry keys.

Prevention & Long-Term Monitoring:

Export a clean backup of HKCU\Software\Microsoft\Office\16.0\Excel after configuring deployment profiles.

Resolve Printer Driver Initialization Timeouts During Page Layout Pre-Rendering

Solution:

Root Cause: Default Printer RPC Timeout During GUI Initialization

Upon startup, Excel queries the default system printer driver to calculate page breaks, default font metrics, and rendering view boundaries. If the default printer is an offline network printer or has an uncorrected driver deadlock, the Win32 spooler call causes excel.exe to freeze or terminate unexpectedly.

Diagnostic Verification:

Inspect process status in Task Manager during launch. If CPU consumption freezes while spoolsv.exe shows elevated CPU usage, Excel is hanging on printer initialization.

Step-by-Step Fix:

1Open Windows Settings (Win + I) and navigate to Bluetooth & devices > Printers & scanners.

2Toggle Off the setting: *Let Windows manage my default printer*.

3Select a virtual software printer (e.g., Microsoft Print to PDF or Microsoft XPS Document Writer).

4Click Set as default.

5Attempt to launch Excel normally.

6If Excel opens successfully, update or re-install the driver for the physical network printer that caused the timeout.

Prevention & Long-Term Monitoring:

Always set a stable, local software print queue as the default printer on mobile laptops that frequently disconnect from corporate networks.

Since Excel crashes even in Safe Mode, which system-level component is failing?

Core Office installation binaries, Click-to-Run DLLs, or C++ Runtimes are damaged
Third-party security software, Endpoint Detection (EDR), or Antivirus injected hooks are blocking `excel.exe`
Corrupted Windows system files, MSVCR/VCRUNTIME binaries, or system fonts
Office Automation or Personalization Registry keys in `HKEY_LOCAL_MACHINE` are corrupt

Perform Office Click-to-Run Full Repair and Re-register Binaries

Solution:

Root Cause: Corrupted Executable Binaries or Office Installation Manifests

If Excel crashes even in Safe Mode (excel /safe), core executable binaries (mso.dll, excel.exe, or c2r32.dll) have suffered file corruption, incomplete updating, or corrupted dynamic-link libraries within the Click-to-Run virtualization layer.

Diagnostic Verification:

Open Command Prompt as Administrator and run the Office licensing and status verification script:

cmd
cscript "C:\Program Files\Microsoft Office\Office16\OSPP.VBS" /dstatus

If status queries throw library load errors, the C2R framework installation is damaged.

Step-by-Step Fix:

1Open Windows Settings (Win + I) and go to Apps > Installed apps.

2Scroll to Microsoft 365 Apps (or Office Desktop Edition), click the three dots, and select Modify.

3Select Online Repair (do not use Quick Repair, as it does not replace corrupted payload DLLs).

4Click Repair and allow the process to complete.

5If Online Repair fails, forcibly remove and reinstall Office using the official deployment scrubber:

Open administrative PowerShell and execute:

powershell
     Setup.exe /configure configuration.xml

6Reboot the system and verify Excel launch.

Prevention & Long-Term Monitoring:

Ensure corporate patch management tools do not interrupt Office Click-to-Run background download jobs.

Isolate Endpoint Detection (EDR) DLL Injection and Antivirus Hooks

Solution:

Root Cause: Security Software API In-Process Interception Failure

Antivirus, EDR, and Data Loss Prevention (DLP) agents monitor Office applications by injecting API hook DLLs (e.g., AppInit_DLLs or AMSI providers) into the process space of excel.exe. Memory corruption inside these interceptor DLLs causes instant crashes before Safe Mode parameters can be parsed.

Diagnostic Verification:

Open Event Viewer (eventvwr.msc), navigate to Application Logs, and review Event ID 1000. Look for faulting module paths residing in C:\Program Files\Security Vendor\ or C:\Windows\System32\drivers\.

Step-by-Step Fix:

1Boot Windows into Safe Mode with Networking:

Run msconfig, go to the Boot tab, check Safe boot > Network, and restart.

2Launch Excel. If Excel opens without error in Windows Safe Mode, third-party security filter drivers are confirmed as the cause.

3Reboot back into normal Windows.

4Temporarily disable the Antivirus/EDR AMSI (Antimalware Scan Interface) integration for Office apps.

5Add an administrative exclusion path for:

C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE

6Update the Endpoint protection agent software to the latest build version released by your security vendor.

Prevention & Long-Term Monitoring:

Maintain vendor-recommended process exclusions for Office 365 executables in EDR policies.

Repair Visual C++ Redistributable Runtime Packages and System Integrity

Solution:

Root Cause: Corrupted VC++ Runtime Libraries or System Font Files

Excel relies heavily on shared Microsoft Visual C++ Redistributable runtimes (vcruntime140.dll, msvcp140.dll) and system font metrics. Corrupted system files or third-party font overrides trigger memory access violations (0xC0000005) during initialization.

Diagnostic Verification:

Run Windows System File Checker to identify corrupted core DLLs:

cmd
sfc /scannow

Check C:\Windows\Logs\CBS\CBS.log for unrepairable errors related to vcruntime or fontsub.dll.

Step-by-Step Fix:

1Open Command Prompt as Administrator.

2Execute the DISM image repair tool followed by SFC:

cmd
   DISM.exe /Online /Cleanup-image /Restorehealth
   sfc /scannow

3Download and re-install the latest combined Visual C++ Redistributables (2015-2022 x86 and x64).

4Clear the system font cache:

Open Service Control Manager (services.msc).

Stop the Windows Font Cache Service (FontCache).

Delete files inside %LOCALAPPDATA%\ServiceProfiles\LocalService\AppData\Local\FontCache\

Restart the service.

5Relaunch Excel.

Prevention & Long-Term Monitoring:

Avoid installing unvalidated third-party custom fonts across enterprise workstations.

Reset Machine-Wide HKLM Office Policies and Installation Registry Keys

Solution:

Root Cause: Corrupted Group Policy Registry Overrides in HKLM

Corporate Group Policy Objects (GPO) or software deployment tools write machine-wide policies to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Excel. Malformed security settings, disabled file formats, or corrupt licensing keys block excel.exe execution.

Diagnostic Verification:

Inspect registry policy keys for unexpected entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Excel
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Excel

Step-by-Step Fix:

1Open regedit.exe with Administrative privileges.

2Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Excel

3Export a backup copy of the key to your Desktop.

4Delete the Excel subkey under Policies.

5Navigate to disabled items registry key and purge stale entries:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Excel\Resiliency\DisabledItems

Delete all binary values inside DisabledItems.

6Force a Group Policy refresh from administrative Command Prompt:

cmd
   gpupdate /force

7Launch Excel normally.

Prevention & Long-Term Monitoring:

Validate GPO updates targeting Office 365 Administrative Templates (.admx) in a staging OU before enterprise rollouts.

What structural component or object inside this specific workbook triggers the crash?

Corrupted VBA project code, automatic `Auto_Open`/`Workbook_Open` macros, or userforms
Corrupted cell drawing layer objects, shapes, images, or chart rendering caches
Broken external data connections, Power Query queries, or OLAP pivot caches
XML calculation engine corruption, circular reference stack overflow, or damaged styles

Bypass Automatic Execution Macros and Clean Corrupted VBA Projects

Solution:

Root Cause: Corrupted Compiled VBA Code (P-Code) or Auto-Exec Hooks

When a workbook opens, Excel executes auto-start macros (Workbook_Open or Auto_Open). If the compiled binary representation of the VBA project (P-code) becomes desynchronized from the raw code text, or if an infinite loop/stack overflow occurs, Excel crashes instantly upon file load.

Diagnostic Verification:

Suppress macro execution during workbook load:

1Open Excel as a blank application (do not open the broken file directly).

2Press and hold the SHIFT key.

3Drag and drop the problematic file into Excel, keeping SHIFT depressed until the file opens.

4If the file opens without crashing, macro code execution is confirmed as the root cause.

Step-by-Step Fix:

1Open a blank Excel application.

2Navigate to File > Options > Trust Center > Trust Center Settings > Macro Settings.

3Select Disable all macros without notification and click OK.

4Open the crashing workbook (it will now open safely without executing code).

5Press Alt + F11 to open the Visual Basic for Applications (VBA) editor.

6Click Debug > Compile VBAProject.

7Inspect ThisWorkbook and all standard modules for syntax errors or corrupted UserForm references.

8Export all modules (Right-click module > Export File...), delete the modules from the project, and re-import them to strip corrupt P-code.

9Re-enable macros in Trust Center settings.

Prevention & Long-Term Monitoring:

Use Office VBA Code Cleaner utilities regularly on heavily edited .xlsm projects to strip compiled P-code headers.

Purge Corrupted Drawing Objects and Shapes via Open and Repair Workflow

Solution:

Root Cause: Damaged Drawing Layer Binary Stream in Workbook XML

In .xlsx and .xlsm OpenXML zip containers, embedded images, charts, conditional formatting icons, and shapes reside in xl/drawings/drawing1.xml. Corrupted XML tags in the drawing stream cause Excel's rendering engine to throw access violations during page setup.

Diagnostic Verification:

Open the file using the built-in repair sandbox:

1Open a blank Excel application window.

2Click File > Open > Browse.

3Select the problematic file (single click).

4Click the small dropdown arrow on the Open button and select Open and Repair....

Step-by-Step Fix:

1In the prompt window, select Repair.

2If Repair fails or crashes, repeat step 1 and select Extract Data to salvage formulas and values.

3To manually repair drawing object XML:

Create a copy of the workbook and change its file extension from .xlsx to .zip.

Extract the ZIP contents to a folder.

Navigate to xl/ inside the extracted folder.

Rename or delete drawings/ and calcChain.xml.

Select all files, zip them back up, and change the extension back to .xlsx.

Open the rebuilt file in Excel.

Prevention & Long-Term Monitoring:

Limit excessive stacked transparent drawing shapes and legacy ActiveX controls in shared workbooks.

Disable Automatic Data Connection Refresh and External Links on Open

Solution:

Root Cause: External Database Timeout or Memory Allocation Lock

Workbooks configured to automatically refresh external Power Query feeds, OLEDB/ODBC database connections, or Web queries upon opening will crash if the network endpoint returns unexpected data payloads, invalid schema changes, or authentication drops.

Diagnostic Verification:

Disconnect your workstation from all network interfaces (Ethernet and Wi-Fi), then attempt to open the file. If the workbook opens without crashing, an external data connection refresh is the cause.

Step-by-Step Fix:

1Keep your computer offline (Airplane Mode ON).

2Open the problematic Excel file.

3Navigate to Data > Queries & Connections.

4Right-click each connection under the Connections pane, select Properties, and go to the Usage tab.

5Uncheck Refresh data when opening the file.

6Save the workbook under a new filename.

7Re-connect your network interfaces.

8Open the newly saved file, navigate to Data > Refresh All, and step through individual queries to identify the failing data source.

Prevention & Long-Term Monitoring:

Always set external background queries to manual refresh during dashboard development phases.

Rebuild Corrupted Calculation Chains and Excessive Custom Styles

Solution:

Root Cause: Calculation Engine Tree Stack Overflow or Custom Style Accumulation

When a file contains tens of thousands of custom cell styles (often caused by copy-pasting between disparate workbooks) or a corrupted calcChain.xml state, Excel exhausts its stack memory space when evaluating formulas on open.

Diagnostic Verification:

Check the file size of the workbook. If a simple text spreadsheet is unexpectedly large (e.g., >20 MB without images), style or calculation tree bloat is present.

Step-by-Step Fix:

1Open Excel in Manual Calculation Mode:

Open a fresh, blank Excel window.

Go to Formulas > Calculation Options and set it to Manual.

2Open the problematic workbook (Excel will bypass formula recalculation on boot).

3Rebuild the calculation tree manually by pressing Ctrl + Alt + Shift + F9.

4Clear custom style bloat:

Navigate to Home > Cell Styles.

Right-click and delete unused custom styles, or run the following PowerShell/VBA style cleaner macro:

vba
     Sub ClearStyles()
         Dim st As Style
         For Each st In ActiveWorkbook.Styles
             If Not st.BuiltIn Then st.Delete
         Next st
     End Sub

5Save the file and switch Calculation Options back to Automatic.

Prevention & Long-Term Monitoring:

Avoid merging sheets from legacy .xls workbooks into modern .xlsx templates without clearing formatting.

How does the rendering or display subsystem behave when Excel crashes or freezes?

Canvas turns grey/black or glitches when moving the Excel window across multi-monitor setups
Crash occurs specifically when hovering over or rendering complex Excel charts and 3D maps
Excel freezes with High CPU / Memory usage when zooming sheets or modifying page layout views
Excel crashes when interacting with Touch Screen inputs or high-DPI scaling configurations

Disable Hardware Graphics Acceleration and Direct3D Registry Pipeline

Solution:

Root Cause: Direct3D GPU Driver Pipeline Rendering Failure

Modern Excel uses hardware graphics acceleration via Direct3D to render cell grids, animations, and smooth scrolling. Incompatibilities between discrete GPU drivers (NVIDIA/AMD) and integrated display adapters (Intel UHD) cause window context creation failures, producing blank grey windows or application crashes.

Diagnostic Verification:

Launch Excel. If screen redraw glitches, flickering ribbons, or black canvas boxes occur prior to process termination, graphics acceleration is failing.

Step-by-Step Fix:

1If Excel can stay open briefly, navigate to File > Options > Advanced > Display.

2Check the box Disable hardware graphics acceleration and click OK.

3If Excel crashes before you can access Options, disable hardware acceleration via Registry Editor:

Press Win + R, type regedit, and press Enter.

Navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Graphics

If the Graphics key does not exist, right-click Common, select New > Key, and name it Graphics.

Right-click Graphics, select New > DWORD (32-bit) Value, and name it DisableHardwareAcceleration.

Double-click DisableHardwareAcceleration and set its Value data to 1.

4Restart Excel.

Prevention & Long-Term Monitoring:

Update graphics card drivers to WHQL-certified enterprise releases on multi-monitor workstation builds.

Fix Chart Subsystem Hardware Acceleration and GDI Handle Leaks

Solution:

Root Cause: GDI Object Exhaustion and Chart Rendering Engine Lock

Rendering sheets containing hundreds of embedded charts or sparklines relies heavily on Windows Graphics Device Interface (GDI) handles. Reaching the default 10,000 GDI handle limit per process causes immediate execution halts during chart canvas draws.

Diagnostic Verification:

Open Windows Task Manager, switch to the Details tab, right-click column headers, enable GDI objects, and watch EXCEL.EXE. If GDI objects approach 10,000 before the crash, handle exhaustion is confirmed.

Step-by-Step Fix:

1Open Registry Editor (regedit.exe).

2Increase the per-process GDI handle quota in Windows:

Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows

Locate GDIProcessHandleQuota.

Change value base to Decimal and increase value from 10000 to 15000 (Max allowed is 16384).

3Disable chart animation features in Office registry:

Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Graphics

Create a DWORD DisableAnimations and set value to 1.

4Restart Windows and launch Excel.

Prevention & Long-Term Monitoring:

Convert legacy chart arrays into dynamic image snapshots or isolated dashboard worksheets.

Reset Page Layout View Settings and Clear Default Metric Caches

Solution:

Root Cause: Page Layout View Printer Metric Recalculation Loop

When a sheet is saved in Page Layout View instead of Normal View, Excel continuously queries print driver page boundaries while zooming or modifying columns. Discrepancies in DPI scaling lead to infinite recalculation loops and memory allocation crashes.

Diagnostic Verification:

Open the file. If the bottom status bar indicates Page Layout View (showing rulers and page margins) before freezing, layout pre-rendering is failing.

Step-by-Step Fix:

1Open a fresh blank workbook in Excel.

2Set calculation to manual (Formulas > Calculation Options > Manual).

3Open the target file while suppressing automatic layout rendering.

4Switch sheet views immediately:

Click View > Normal on the top ribbon.

5Select all worksheets (Right-click sheet tab > Select All Sheets).

6Switch all sheets simultaneously to Normal View.

7Save the file under a new name and close Excel.

8Re-open the saved workbook.

Prevention & Long-Term Monitoring:

Always switch large production workbooks back to Normal View before saving and distributing across networks.

Configure Per-Monitor DPI Awareness and Touch Keyboard Hooks

Solution:

Root Cause: Win32 High-DPI Display Context Misalignment

Running Excel across displays with different DPI scaling settings (e.g., a 4K laptop display at 200% scale connected to 1080p monitors at 100% scale) causes Win32 child window handle positioning errors in Office visual components, triggering crashes on drag operations.

Diagnostic Verification:

Drag Excel between monitors with differing DPI scaling percentages. If the crash occurs precisely when the window crosses display boundaries, DPI context switching is the root cause.

Step-by-Step Fix:

1Open Excel.

2Navigate to File > Options > General.

3Under User Interface options, locate When using multiple displays.

4Change the setting from *Optimize for best appearance* to Optimize for compatibility.

5Click OK and restart Excel.

6Alternatively, set DPI compatibility on the executable:

Right-click C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE > Properties.

Select Compatibility tab > Change high DPI settings.

Check Override high DPI scaling behavior and set Scaling performed by to System (Enhanced).

Prevention & Long-Term Monitoring:

Align display scale percentages across all external monitors in enterprise workstation configurations.

Related Diagnostic Guides

Printer Driver Is Unavailable Windows 11: Driver Store Cleanup Fix

SD Card Reader Not Working After Update: Realtek Driver Tree

USB C Hub Not Detecting HDMI: DP Alt Mode Diagnostic

Laptop Touchpad Not Working After Windows Update: Precision Driver Tree

MEMORY_MANAGEMENT BSOD While Gaming: XMP Profile Diagnostic

Subscribe to StepDiag

Embed Guide on Your Website