Fix: Loom “Desktop App” stuck on “Initializing”

When the Loom desktop app gets stuck on “Initializing,” the software has launched its core framework but cannot finish loading the recording interface. This stall happens when Loom fails to query local audio/video hardware, encounters a corrupt local configuration cache, or gets blocked while attempting an outbound connection to its session servers. You are left with a persistent spinner or an unresponsive control panel.

Fast Fix

Force-quit all background Loom processes, disconnect external webcams or USB audio interfaces, and restart the app. If the status remains stuck on “Initializing,” delete the local cache folder in %APPDATA%\Loom on Windows or ~/Library/Application Support/Loom on macOS. This forces Loom to regenerate clean device configurations on startup without deleting your cloud-stored recordings.

---

Diagnostic Snapshot

Parameter	Operational Detail
Failure Layer	Local hardware handshake or client-side cache corruption
Operating Systems Affected	Windows 10/11, macOS (Intel & Apple Silicon)
User Scope	Individual workstation
Admin Rights Required	No (standard user directory modification)
Data Loss Risk	Low (videos stored in cloud; unsaved local drafts may reset)

---

Diagnostic Path: Pinpointing the Hang

Follow these targeted checks to locate which subsystem is failing:

App launches -> Displays "Initializing..."
       │
       ├──> Do you have external AV devices (Elgato, Focusrite, virtual cams)?
       │      └── YES: Unplug hardware / close virtual camera drivers.
       │
       ├──> Does the app load when disconnected from VPN / Proxy?
       │      └── YES: Corporate firewall/DLP is blocking Loom signaling.
       │
       └──> Does the issue persist with native hardware on direct internet?
              └── YES: Local application cache or device lockfile is corrupt.

1. Check for Zombie Processes: Even if the window closes, Loom worker processes (such as audio-daemon or screen-capture hooks) can remain active in memory. If a background process locks the local SQLite configuration database, a newly launched instance cannot initialize.
2. Isolate Virtual and USB Audio/Video Drivers: Loom polls every active audio and video input during initialization. Software like OBS Virtual Camera, Camo, Voicemeeter, or disconnected docking station audio jacks frequently fail to respond to direct API polling, locking the initialization thread.
3. Verify Corporate Network Filtering: If your device is behind a strict zero-trust proxy or corporate firewall, Loom can hang indefinitely while waiting for an authentication response from its API endpoints. If enterprise policies block screen recording tools, refer to Fix: Loom “Screen Recording” blocked by Corporate Security (DLP).

---

Resolution Steps

Step 1: Terminate All Loom Background Processes

Before modifying files, make sure the operating system has released all file locks.

• On Windows:
  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Locate Loom under Apps and Background processes.
  3. Select each instance and click End task.
• On macOS:
  1. Press Cmd + Space, type Activity Monitor, and press Enter.
  2. In the search bar at the top right, type Loom.
  3. Highlight all active processes, click the Stop (X) button in the toolbar, and choose Force Quit.

Step 2: Disconnect Peripheral Hardware and Virtual Drivers

1. Unplug all external USB webcams, audio interfaces, and multi-port docks.
2. Disable software virtual inputs:
   • Close applications like OBS Studio, Logi Tune, Elgato Camera Hub, or Krisp.
   • If you suspect your camera feed is tied up by another meeting client, see How to Resolve: Loom “Camera Bubble” Frozen or Disappeared.
3. Relaunch Loom using only your laptop’s built-in webcam and microphone. If it loads immediately, reconnect devices one by one to isolate the malfunctioning driver.

Step 3: Clear the Corrupted App Data Cache (Deep Reset)

Purging the local data folder removes stale device indexes and broken authentication tokens without deleting any recordings saved to your Loom workspace.

• Windows:
  1. Press Windows Key + R to open the Run dialog.
  2. Type %appdata% and click OK.
  3. Find the folder named Loom.
  4. Right-click and delete the Loom folder (or rename it to Loom_Old if you want a backup).
  5. Open the Run dialog again, type %localappdata%, click OK, and delete the loom-updater folder if present.
  6. Restart Loom and sign back in.
• macOS:
  1. Open Finder.
  2. Press Cmd + Shift + G to open the “Go to Folder” prompt.
  3. Paste ~/Library/Application Support/ and press Enter.
  4. Move the Loom folder to the Trash.
  5. Go to ~/Library/Caches/ and delete any folders labeled com.loom.desktop.
  6. Empty the Trash and restart the app.

Step 4: Check Hardware Encoding and GPU Acceleration

If Loom initializes to a blank, black, or grey box, your graphics driver may be failing during video hardware acceleration initialization. You can force software encoding if your GPU driver is hanging during handshake routines. Review our diagnostic breakdown in Troubleshooting: Loom “Hardware Encoding” vs “Software Fallback” to configure your rendering pipeline properly.

---

Advanced System Checks

If clearing the cache does not resolve the freeze, the app is failing to establish an initial session handshake with Loom’s cloud infrastructure.

• Validate WebSockets and SSL Inspection: Loom requires open outbound communication on port 443 via WebSockets (wss://). If your network uses deep-packet inspection or SSL decryption, the desktop app may drop the connection silently while initializing. Temporarily bypass any active VPN or corporate proxy to test connectivity.
• Inspect Local App Logs:
  • Windows: Navigate to %APPDATA%\Loom\logs and open main.log.
  • macOS: Navigate to ~/Library/Logs/Loom/ and check main.log.
  • Look for repeated entries marked E_DEVICE_BUSY, ERR_CONNECTION_TIMED_OUT, or TIMEOUT_WAITING_FOR_DEVICES. A device timeout confirms a dead hardware driver, while a connection timeout indicates network filtering.

---

Hard Stops and Escalation

Stop troubleshooting local files and contact your IT administrator if:

• The issue only occurs when connected to your company’s network or VPN, indicating an enterprise SSL certificate inspection block.
• Loom fails across multiple corporate-managed machines simultaneously, which points to a firewall or endpoint security rule update.
• Your organization enforces enterprise single sign-on that drops during initialization; in that scenario, consult Fix: Loom “SSO” sign-in loop for Enterprise accounts.