Hi, Bernard Kripkee
Thanks for the detailed testing, that actually helps narrow this down a lot. At this point I do not think your Office install has somehow become “web-only.” The desktop versions of Word and Excel support hyperlinks to files on your computer, while Microsoft 365 Online has the simplified hyperlink feature set.
What your tests suggest instead is that Office on this specific PC is failing to hand off local file links to Windows. There have also been previous Office build regressions where local hyperlink behavior broke in certain versions and users had to revert to an earlier Click-to-Run build while waiting for a fix.
Since the same Office build works correctly on your wife’s laptop, I would stop blaming the spreadsheet and focus on machine-specific Office behavior. The next things you should try are:
Create a new Windows user account on the same PC and test one simple local hyperlink there. If it works, that points to something corrupted in your current user profile or HKCU-level Office settings rather than Excel itself.
Test an explicit file URI instead of a plain path, for example:
=HYPERLINK("file:///C:/Users/[username]/Test%20file.txt","Open test file")
Older Office discussions show that Office sometimes handles file:// links differently from plain C:\ or C:/ paths.
If you only did a normal uninstall, run Microsoft’s full Office uninstall troubleshooter, then reinstall. A standard uninstall can leave Click-to-Run components or per-user settings behind. Previous Office issues have also shown that reinstall alone does not always clear a bad build/state.
Try a temporary rollback to an earlier Office build. If rollback fixes it, that is strong evidence this is an Office regression on your machine rather than bad file data.
If you are comfortable with Registry Editor, there is an older workaround called ForceShellExecute that tells Office to use the Windows shell to open links instead of Office’s own handling. In older Word/Excel discussions this was suggested for file:// hyperlink problems under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Common\Internet
add DWORD ForceShellExecute = 1
If Office is 32-bit on 64-bit Windows, the Wow6432Node path may also be relevant. I should add that reports are mixed on newer Office versions, so I would treat this as a test, not a guaranteed fix.
So my best guess now is: either a machine-specific Office/profile corruption, or a current build regression that only shows up on this PC. If a new Windows profile fixes it, the problem is probably in your user-level Office/registry settings. If rollback fixes it, the culprit is probably the installed Office build.