Office Apps Not Opening

Fix Office Apps Not Opening for Additional Windows Users

Chanuka GeekiyanageChanuka Geekiyanage Nov 3, 2026 869 views

Question details

Users need to resolve an issue where Office applications fail to open when launched from a Windows Explorer session running under a different domain account.

How to Fix Office Apps Failing for an Additional Windows User
Product
Microsoft 365 Apps
Device & OS
Windows
Scenario
Opening Office files from a Windows Explorer window that is running under a secondary domain account or via a RUNAS command.
Observed behavior
The application fails to launch, often returning the error message "A specified logon session does not exist."
Before you start

Ensure you have the necessary administrative privileges on your Windows computer and check if any recent Microsoft 365 or Windows updates have altered your user profile permissions.

Solution 1Recommended

Use Alternative Launch Methods

Bypass the logon session error by running the application directly as an administrator or switching your active Windows Explorer session.

This issue typically arises due to a conflict between the domain account running the Windows Explorer process and the primary user session. Bypassing the Explorer file-open method directly solves the symptom.

1
Launch via the Start Menu

Click the Windows Start menu, locate the specific Office application (such as Excel or Word), right-click the icon, select 'More', and choose 'Run as administrator'.

2
Open the File from within the App

Once the application is open under the correct administrator privileges, use the 'File' > 'Open' menu to locate and open your document instead of double-clicking it in Windows Explorer.

3
Switch Explorer Sessions

If you must use Windows Explorer, fully switch your Windows user session to the target domain account rather than using the RUNAS command within your current session.

Verified Workaround: Launching the Office application directly from the Start menu avoids the session overlap that triggers the 'logon session does not exist' error.
Free Microsoft Office alternative

Switch to WPS Office for a Hassle-Free Experience

If Microsoft Office continues to fail due to complex Windows user profiles or domain account permission errors, consider switching to WPS Office. It is a highly compatible, lightweight alternative that simplifies document management across multiple user profiles without throwing complex logon session issues.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installer for Windows.
  2. 2. Install the Software: Run the setup file and follow the on-screen prompts to complete the installation.
  3. 3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Office files without worrying about logon session errors.
Fully compatible with Microsoft Office formats including Word, Excel, and PowerPointLightweight architecture minimizes system and permission-based launch errorsSeamlessly manage multiple tabs in a single window regardless of the active Windows userFree to download and use with a familiar, easy-to-navigate user interface
microsoft office alternative - wps office

Frequently Asked Questions

Why do I get 'A specified logon session does not exist' when opening Excel?

This error frequently occurs when you try to open an Office file from a Windows Explorer instance running under a different domain account than the currently logged-in user. It is often triggered after certain Windows or Microsoft 365 updates alter security permissions.

Does the 'Run as administrator' option fix this Windows user issue?

Yes, right-clicking the Office application shortcut directly from the Start menu and selecting 'Run as administrator' typically bypasses the Explorer-related logon session error and allows the app to launch normally.

Is this launch issue specific to domain accounts?

Usually, yes. Testing indicates that while local administrator accounts might experience different launch behaviors or minor glitches, the specific 'logon session does not exist' error is predominantly linked to secondary domain accounts running cross-session.