Excel can't open file from hyperlink after upgrade windows11

The core issue, since web URLs work but local and network files don't, is a broken integration between Office and the Windows shell. Your goal is to find and fix the break in the chain:

Hyperlink Click → Windows Shell (Interprets file:// or UNC path) → Launches Excel/Word with the file.

Phase 1: The "Most Likely" Quick Fixes (Start Here)

These address the most common post-upgrade culprits and take under a minute each.

 1. The "Ignore DDE" Setting (Most Common)

• What it is: Dynamic Data Exchange (DDE) is a protocol Windows uses for applications to communicate with the shell. A Windows upgrade can break this registration, and Office has a setting to ignore it entirely, causing silent failures.
• The Fix: In Excel, go to File > Options > Advanced > General and UNCHECK "Ignore other applications that use Dynamic Data Exchange (DDE)". Do the same in Word. Restart Office and test.
• This is the top suspect from your linked proposal and should be the first thing you try.

2. Repair Office File Registrations

• What it is: This directly fixes the broken DDE/shell handlers that the "Ignore DDE" setting is a workaround for.
• The Fix: Run a Quick Repair on Microsoft 365 (Windows Settings > Apps > Installed Apps > Microsoft 365 > Modify). If the problem persists, run the Online Repair. This is more comprehensive and is the most direct way to fix broken shell integration without resorting to registry edits.

Phase 2: Diagnostic Verification (If Phase 1 Fails)

Before diving deeper, we need to prove the problem is entirely outside of Office.

• The Run Dialog Test: Press Win + R and paste the exact full path from a failing hyperlink (e.g., \\server\share\file.xlsx or C:\Temp\file.xlsx). If this also fails silently, the problem is a system-wide Windows shell association issue, not an Office setting. If it works, the problem is isolated to how Office is calling the shell.
• The VBA Test: Since you're a developer, run this macro in a fresh Excel workbook (adjust the path to a known file):

vba

Sub TestHyperlink()

    ' This bypasses the cell hyperlink UI and tests the shell command directly

    On Error Resume Next

    ActiveWorkbook.FollowHyperlink "C:\Temp\test.xlsx" ' Or a UNC path

    If Err.Number <> 0 Then

        MsgBox "Error: " & Err.Description

    End If

    On Error GoTo 0

End Sub

A silent failure here is a strong indicator of a broken DDE registration or shell handler.

Phase 3: Targeted System-Level Fixes

If the Run Dialog test or VBA test also fails, the issue is not with Office's settings but with Windows itself.

 1. Check Default App Associations: Go to Windows Settings > Apps > Default Apps. Search for .xlsx. Ensure it's set to Excel. Do more than that: scroll down and click "Choose default apps by file type" and verify .xlsx, .xls, .docx, etc. Then, click "Choose default apps by protocol" and ensure protocols like ms-excel are associated with Excel.

 2. Advanced Diagnostic - Command Line: Open a Command Prompt and run:

cmd

assoc .xlsx

ftype Excel.Sheet.12

The output from ftype should point to the correct EXCEL.EXE path and include the /dde switch. If it doesn't, the "Online Repair" in Phase 1 is the correct solution.

 3. The Nuclear Option - Process Monitor: This is the ultimate diagnostic from your proposal.

• Download Sysinternals Process Monitor.
• Run it and set a filter for Process Name is EXCEL.EXE.
• Click the hyperlink in Excel and immediately stop the capture in ProcMon.
• Look for Process Create operations (to see if it even tries to launch Excel again) or RegQueryValue operations with "ACCESS DENIED" results under HKEY_CLASSES_ROOT. This will pinpoint a permission or registration failure.

Action Plan...

1. Uncheck "Ignore DDE" in both Excel and Word. If fixed, you're done.
2. Run an Office Online Repair. This solves 95% of the remaining cases by fixing the registration identified in step 1.
3. Run the Win + R diagnostic. If it fails, the Online Repair is still the right fix, but it may also point to a corrupted user profile.
4. Use Process Monitor only if you need to log the exact failing registry key for a support ticket or advanced manual fix.

My answers are voluntary and without guarantee!

Hope this will help you.

Was the answer useful? Mark as best response and like it!

This will help all forum participants.