eM Client 11 will not restart after exit

I removed all eM Client apps, files, registries and reinstalled on windows 11.
When I install the app opens and looks OK.
If I exit the app, it will not reopen and I get this message
“Windows cannot access the specified device, path, of file, You may not have the appropriate permission to access the item”

Hi, sorry for the late reply.

Could you please tell us:

  1. Your Windows version and your eM Client version (Menu > Help > About, while it is open after the reinstall).
  2. How you try to start it again: from the Start menu, a desktop shortcut or a pinned taskbar icon? An old shortcut from version 10 points to a path that no longer exists, so please try starting it from the Start menu.
  3. Do you use antivirus or security software with folder protection (for example Windows Controlled folder access)? If so, check whether it blocks eM Client.
  4. Does it start again after a Windows restart?

Best,
eM Client Team

I found out why eMClient 11 would not start after an update to version 11. It had to do with account privileges for my windows account. When I installed or changed windows the privileges were not set correctly. Here is a detailed report created by Claude.ai of the issue, and fix
eM Client 11 won’t start after upgrade: “Windows cannot access the specified device, path, or file”

Nov 18, 2026 · @Dennis

Symptom

eM Client 11 opens once right after installing, then never again. Every later launch shows: “Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”

  • Happens from the Start menu, “Recently installed”, the taskbar and desktop shortcuts alike.
  • Reinstalling, or uninstalling v10 and installing v11 clean, does not fix it.
  • Get-AppxPackage *eMClient* reports the package as Status Ok.
  • Seen on Windows 11 with eM Client 11.0.1577.0, signed in to a normal administrator account with UAC on.

Root cause

Windows is denied access to the app’s own data folder when it starts eM Client. The folder is missing permissions for SYSTEM and Administrators.

  • eM Client 11 is a packaged Windows app (MSIX). Version 10 was a traditional MSI install, so v10 was never affected.
  • Every packaged app gets a per-user folder under %LOCALAPPDATA%\Packages, which copies its permissions from the Packages folder itself.
  • On the affected PC, the Packages folder listed only the user’s own account, with no SYSTEM and no Administrators. The eM Client folder copied that.
  • At launch, Windows needs SYSTEM access to that folder to set up the app’s environment. It is refused, so the launch fails with the generic permissions message.

The missing entries were probably removed earlier by a permissions-reset tool, a profile migration or a “take ownership” step. Any packaged app installed on the same PC could hit the same error.

Diagnose

Run these in a normal (not “Run as administrator”) PowerShell window. None of them change anything.

  1. Confirm the package is installed and healthy. Expect Status Ok.

    Get-AppxPackage *eMClient* | Select Name, Version, Status, InstallLocation
    
  2. Trigger the error, then read the app-launch log. The telltale entry is Event 208 with 0x80070005 (access denied), naming the eM Client package and ending in [LaunchProcess].

    Start-Process "shell:AppsFolder\eMClient.20054CA46072C_veq4nz3ze5v72!App"
    Get-WinEvent -LogName "Microsoft-Windows-AppModel-Runtime/Admin" -MaxEvents 10 | Format-List TimeCreated, Id, Message
    
  3. Check the permissions on eM Client’s folder and on the Packages folder above it.

    icacls "$env:LOCALAPPDATA\Packages\eMClient.20054CA46072C_veq4nz3ze5v72"
    icacls "$env:LOCALAPPDATA\Packages"
    

How to read icacls output: each line is who, then what they may do. (F) = full control, (OI)(CI) = also applies to files and subfolders inside, (I) = copied from the folder above. A healthy folder has NT AUTHORITY\SYSTEM, BUILTIN\Administrators and your own account, each with (OI)(CI)(F). If SYSTEM and Administrators are missing, this guide applies.

Affected output looked like this, with only the user listed:

...\Packages\eMClient.20054CA46072C_veq4nz3ze5v72 PCNAME\username:(I)(OI)(IO)(F)
                                                   PCNAME\username:(I)(CI)(F)

The two lines for one account are harmless. Together they equal a single (OI)(CI)(F) entry.

Fix

Add SYSTEM (S-1-5-18) and Administrators (S-1-5-32-544) back, first to eM Client’s folder and then to the Packages folder so future apps are covered. Each part saves the current permissions first so it can be undone.

  1. eM Client’s folder. eM Client should launch right after this.

    $p = "$env:LOCALAPPDATA\Packages\eMClient.20054CA46072C_veq4nz3ze5v72"
    icacls $p /save "$env:TEMP\emclient-acl.txt" /T /C
    icacls $p /grant "*S-1-5-18:(OI)(CI)(F)" "*S-1-5-32-544:(OI)(CI)(F)" /T /C
    
  2. The parent Packages folder. This stops the problem coming back for other packaged apps.

    $pk = "$env:LOCALAPPDATA\Packages"
    icacls $pk /save "$env:TEMP\packages-acl.txt" /T /C /Q
    icacls $pk /grant "*S-1-5-18:(OI)(CI)(F)" "*S-1-5-32-544:(OI)(CI)(F)"
    

Check that each grant ends with “Failed processing 0 files”. To undo either step, run icacls on the same parent folder with /restore and the saved file.

Do not use Reset on eM Client in Settings → Apps while troubleshooting. Packaged apps can keep their data inside the Packages folder, so Reset may erase the restored mailbox. Keep an eM Client backup .zip off the PC either way.

Verify and prevent

  1. Open eM Client from the Start menu, quit it completely (Menu → Exit, tray icon gone), then open it again. The second launch is the real test.

  2. List any other app folders still missing SYSTEM. No output means none are affected.

    Get-ChildItem "$env:LOCALAPPDATA\Packages" -Directory | Where-Object { -not ((Get-Acl $_.FullName).Access | Where-Object IdentityReference -eq 'NT AUTHORITY\SYSTEM') } | Select-Object Name
    

    For any folder it lists, run the step 1 grant from Fix with $p set to that folder.

  3. If the error returns later, run icacls on the eM Client folder again. Missing entries mean a security or cleanup tool is stripping permissions.

For a clean v10 → v11 upgrade next time:

  • Back up in v10 (Menu → Backup) and copy the .zip off the PC.
  • Quit eM Client completely, including the tray icon, before installing.
  • After installing, delete old v10 shortcuts, taskbar pins and shell:startup entries. They point at C:\Program Files (x86)\eM Client\MailClient.exe, which no longer runs.
  • Launch from the Start menu and pin it from there. Turn on start-with-Windows in eM Client’s own settings.
  • To restore, skip the setup wizard and use Menu → File → Restore, with the .zip in Documents\eM Client.

Sources