Slack Error “0x80070005” Access Denied during Launch

Slack launch error 0x80070005 is the standard Windows system code for “Access Denied.” It strikes when the Slack desktop client tries to launch or write to its local runtime directory, but your Windows user account lacks NTFS file permissions to read or modify those files. This usually happens after Slack was launched as an Administrator, leaving locked files behind, or when endpoint security software blocks access to %LocalAppData%\slack.

Fast-Fix: The 45-Second Solution

Error 0x80070005 means Windows blocked Slack from accessing its execution files. Close Slack completely via Task Manager. Press Win + R, enter %LocalAppData%, right-click the slack folder, and select Properties > Security. Ensure your Windows account has Full Control. If the issue persists, launch Command Prompt as Administrator and run icacls "%LocalAppData%\slack" /reset /t /c /l /q to repair broken folder permissions.

Quick Logic Snapshot

• Severity: Operational / Moderate to High (Completely blocks the Slack desktop application from launching)
• Impact: Single User / Device Level (Restricted to the local Windows user profile)
• Primary Cause: Corrupted NTFS file permissions or Administrator ownership on %LocalAppData%\slack
• Rare/Security Cause: Controlled Folder Access or Enterprise EDR / Antivirus blocking executable write operations

Low Risk vs. High Risk Scenarios

                             [ 0x80070005 Launch Error ]
                                          |
               -------------------------------------------------------
               |                                                     |
  [ Local Permission Lockout ]                         [ Domain / EDR Policy Block ]
               |                                                     |
• Lower Risk: User ran Slack as Admin once,          • Higher Risk: Group Policy (GPO) or EDR engine
  locking local cache permissions.                     blocking process execution in AppData.
               |                                                     |
-> Action: Reset NTFS ACLs on AppData                -> Action: Escalate to Enterprise IT to whitelist
   or reinstall in user context.                        Slack execution path in security console.

• If limited to a single user workstation after a Windows or Slack update: Lower Risk. The issue is isolated to permission flags or file ownership in the user’s local profile folder.
• If occurring right after running Slack as Administrator: Lower Risk. Launching with elevated rights assigned file ownership to the Administrator account, locking the standard user profile out of its own cache.
• If popping up across multiple managed devices across a corporate network: High / Systemic Risk. Group Policy (GPO), AppLocker, or corporate Endpoint Detection and Response (EDR) agents are actively blocking execution inside %LocalAppData%.

What This Means

Think of Windows file permissions like a padlocked toolbox. When you launch Slack normally, the program acts on behalf of your standard Windows user account to grab its tools, DLLs, database files, and cache buffers, from the %LocalAppData%\slack folder.

Error 0x80070005 happens when another process or user changes the padlock. If Slack was previously opened with Administrator rights, Windows writes new files using the Administrator’s padlock. When you open Slack normally later, your standard key won’t unlock the box. The operating system halts the launch process immediately to protect the file system, returning E_ACCESSDENIED (0x80070005).

Probability Breakdown

Root Cause	Likelihood	Key Diagnostic Indicator
Admin Privilege Mismatch / Ownership Lockout	50%	Error began after manually choosing “Run as Administrator” or during a background update elevated by UAC.
Corrupted NTFS Access Control Lists (ACLs)	25%	Windows Security tab shows “Unknown Account (S-1-5-…)” or grayed-out permissions on %LocalAppData%\slack.
Antivirus / Controlled Folder Access Interference	15%	Windows Defender Notification Center reports an “Unauthorized changes blocked” message targeting slack.exe.
Damaged AppData Temporary Installation Files	10%	Slack launches successfully in web browser, but installer and desktop client fail consistently.

Logic Escalators

Several background factors can escalate simple permission errors into stubborn launch blocks:

• User Account Control (UAC) Elevation: Forcing slack.exe to always run as Administrator breaks Slack’s update mechanism, causing subsequent background updates to fail with permission errors.
• Windows Defender Controlled Folder Access: Enabling ransomware protection features without whitelisting Slack prevents the client from updating its local cache files in %AppData% and %LocalAppData%.
• Roaming Profiles / Folder Redirection: Corporate setups that redirect user profile folders to network shares frequently drop NTFS permission inheritance during domain syncs.
• Corrupted Windows Update / Security Patching: Interrupted OS updates can leave system-level security descriptors in an inconsistent state across user directories.

If Ignored: 1 Hour → 1 Day → 1 Week

• 1 Hour: The desktop app remains completely unusable. Desktop notifications stop, forcing you to rely on web browser workarounds.
• 1 Day: Background sync processes drop offline. Unsaved local message drafts and cached file attachments stored in the local profile become inaccessible.
• 1 Week: Persistent launch failures cause background update loops to fail repeatedly, leading to corrupted installation files and requiring a total clean removal of Slack registry keys and profile directories.

Confused With / False Positives

Make sure you do not confuse 0x80070005 with other common Slack Windows installation or execution errors:

• 0x80040103 (Something Went Wrong): Represents authentication or local token database corruption rather than file system permission blocks. See Slack “Something went wrong” (Error Code: 0x80040103).
• 0x80040154 (Class Not Registered): Caused by missing or unregistered COM interfaces or damaged system components. See Slack “0x80040154” Class Not Registered Error.
• 0x80070002 (File Not Found): Triggers when required Slack installation binaries or shortcut paths are missing entirely from the system.
• WebView2 Runtime Failures: Causes blank or black window frames rather than an explicit “Access Denied” error dialog during launch. See Slack “WebView2 Runtime” Missing or Damaged.

What To Do Right Now

Follow these steps in order to restore file access permissions and launch Slack:

Step 1: Force Close All Slack Processes

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Locate any active instances of Slack or Slack Helper.
3. Select each process and click End Task.

Step 2: Reset Folder Permissions via Command Prompt

1. Press the Windows Key, type cmd, right-click Command Prompt, and select Run as Administrator.
2. Copy and paste the following command to reset permissions on the local Slack folder:DOS icacls "%LocalAppData%\slack" /reset /t /c /l /q
3. Press Enter. This replaces broken access lists with clean inherited permissions.

Step 3: Check Controlled Folder Access Settings

1. Open Windows Security from the Start menu.
2. Click Virus & threat protection, then scroll down to Ransomware protection.
3. Click Manage ransomware protection.
4. If Controlled folder access is turned ON, click Allow an app through Controlled folder access and add slack.exe.

Step 4: Perform a Deep AppData Reset

If permissions are reset but Slack still crashes on launch, clear the local cache:

1. Press Win + R, type %AppData%, and press Enter.
2. Locate the Slack folder, right-click it, and rename it to Slack.old.
3. Launch Slack. It will generate a clean cache directory with default permissions. For a complete guide, see How to Clear Slack Desktop Cache (The Deep Clean Method) and Troubleshooting: Slack “Local Data Corruption” repair guide.

Immediate Intervention Flags

Stop troubleshooting and contact your system administrator if:

• The icacls command returns “Access is denied” even when running Command Prompt as Domain Administrator.
• Group Policy or corporate endpoint protection automatically deletes or re-locks the %LocalAppData%\slack directory within seconds of modification.
• Your Windows account has been converted to a restricted guest or temporary profile that prevents permanent changes to %LocalAppData%.

What a SysAdmin Will Check

When escalating to a systems administrator or IT helpdesk, technicians will perform the following diagnostics:

1. NTFS ACL Auditing: Inspect security inheritance flags on %LocalAppData% using icacls or PowerShell’s Get-Acl.
2. Software Restriction Policies / AppLocker Rules: Verify whether AppLocker policies prohibit executable files from running inside user AppData paths. See Troubleshooting: Slack “Organization Policy” blocking Desktop Login.
3. EDR Threat Event Logs: Review CrowdStrike, Defender for Endpoint, or SentinelOne management consoles for blocked file-write attempts targeting slack.exe.
4. Machine-Wide MSI Installer Deployment: Reinstall Slack using the Machine-Wide MSI installer (/allusers) to place binaries in C:\Program Files\Slack rather than user AppData folders.

Administrative Scope

• User Scope: Fixing local folder ownership, clearing corrupt %AppData%\Slack caches, and adjusting Windows Defender Controlled Folder Access settings.
• Team Scope: Ensuring non-admin users have standard write rights within their own user profile directories without requiring administrative elevation.
• Tenant / Domain Scope: Managing AppLocker rules, configuring Group Policy file paths, and pushing Machine-Wide Slack deployments across the enterprise fleet.

Related Logical Handshakes

• If Slack fails to launch due to startup crashes, see Slack Desktop App Crashing on Windows 11 Startup.
• If clearing local profile directories is required, see How to Clear Slack Desktop Cache (The Deep Clean Method).
• If organization policy blocks desktop authentication, see Troubleshooting: Slack “Organization Policy” blocking Desktop Login.
• If Slack displays a blank screen due to underlying rendering issues, see Slack Desktop App Blank Screen after Update.

Operations Summary

Slack error 0x80070005 is almost always an authorization roadblock on your local hard drive, not a network failure or account ban. Once you reset NTFS permissions on %LocalAppData%\slack, remove conflicting Administrator flags from executable shortcuts, or whitelist the client in Windows Defender, Slack will be able to read its core runtime files and launch normally.