How to Fix Zoom "Error Code 1132" Sign-In Error

By FixMyError · Updated October 16, 2026 · 6 min read

What "Error Code 1132" means

Most sign-in errors are about credentials: a wrong password, an expired session, a locked account. Error code 1132 is different. It means Zoom's servers looked at your sign-in attempt and refused it because of a device or user-profile level restriction. In plain terms, Zoom recognizes your device or your Windows or Mac user profile as flagged, and it blocks the sign-in before your account is even checked. That is why retyping your email and password, resetting your password, or even creating a new Zoom account on the same machine changes nothing — the block is aimed at the device, not the login.

The most frustrating part of 1132 is how stubborn it is. Uninstalling and reinstalling Zoom usually makes no difference, because the restriction is stored both on Zoom's servers and in local identifiers on your machine that a normal uninstall leaves behind. When the fresh install phones home, Zoom recognizes the same device fingerprint and applies the same block. That persistence is exactly what makes this error so annoying — but it also tells us where the fix has to happen: either Zoom's team has to clear the flag (through the official report flow in step 1), or you have to present a genuinely fresh identity, by scrubbing every leftover Zoom identifier or signing in from a brand-new OS user profile (steps 2 and 3). The fixes below go in that order, from official to self-service.

Common causes

• Device or profile-level restriction: Zoom flagged your device or OS user profile, and the flag is stored server-side — it follows the device, not your account.
• Local identifiers surviving a normal uninstall: leftover data in %appdata%/Zoom on Windows (or the hidden Zoom.tbd file on Mac) lets a fresh install get flagged again.
• Outdated Zoom client: old app builds run into sign-in checks that Zoom's current servers no longer accept, triggering 1132 instead of a helpful message.
• Network or security interference: a VPN, firewall rule, or antivirus hook can corrupt the sign-in handshake badly enough to trip the error.
• Stuck sessions from other devices: conflicting active sessions on phones, tablets, or other computers can confuse the sign-in flow on your main machine.

How to fix "Error Code 1132" — step by step

Work through these fixes in order. Step 1 is Zoom's official fix — start there, because only their team can clear a server-side flag.

1. Update Zoom and use the official Report to Zoom flow. This is Zoom's own documented path for error 1132, so do it first. Open the Zoom app, click your profile picture in the top-right corner, and choose Check for Updates — install anything it finds, since an outdated client can trigger 1132 on its own. Then sign in to reproduce the error. Next to the 1132 error message, click Report to Zoom and fill in the information it asks for. Zoom sends a confirmation email to the address you used to sign in — open it and confirm the report so your case is actually logged. Their team will follow up by email with further details; while you wait, keep reading, because the steps below may unblock you on your own.
2. Do a true clean reinstall and delete Zoom's leftover data. A standard uninstall is not enough for 1132, because it leaves behind the local identifiers Zoom uses to recognize your device. Uninstall Zoom first: open Settings, then Apps, then Installed apps, select Zoom, and choose Uninstall. Now hunt down the leftovers. Press Win + R, type %appdata%, press Enter, and delete the Zoom folder. Press Win + R again, type %localappdata%, and delete the Zoom folder there too if one exists. On a Mac, open Finder, press Command + Shift + . to reveal hidden files, navigate to ~/Library/Application Support/zoom.us, and delete its contents — look specifically for a hidden file named Zoom.tbd and delete it as well. Empty the trash, restart your computer, then download a fresh installer from Zoom's official download page (not a saved old copy) and install again.
3. Sign in from a brand-new OS user profile. If the clean reinstall still hits 1132, the restriction is tied to your original OS user profile rather than the Zoom install itself — and a new profile presents a fresh identity that Zoom has never flagged. On Windows, go to Settings, then Accounts, then Other users, and click Add account to create a new local user (no Microsoft account needed). Sign in to Windows as that new user, launch Zoom, and sign in to your Zoom account there. On a Mac, open System Settings, then Users & Groups, and add a new user, then log in as that user. Many people stuck on 1132 report that this works when nothing else did — it is the most reliable self-service fix for a profile-level block.
4. Join from the browser or test on another device. This step does two jobs: it gets you into your meetings immediately, and it tells you where the problem lives. Click your meeting link in Chrome or Edge and choose "Join from your browser" — the web client signs in through a completely different path and usually works even when the desktop app is blocked. Also try signing in on a different phone or computer. If Zoom works everywhere except your main device or profile, you have confirmed the block is local to that machine or profile, not your account — and the new-profile fix in step 3 is your best bet.
5. Rule out VPN, firewall, and antivirus interference. Network interference can garble the sign-in handshake badly enough to trigger 1132, especially through aggressive VPN routing. Disconnect your VPN temporarily and try signing in again. If it still fails, open Windows Defender Firewall settings and make sure Zoom is on the allowed list, then check your antivirus (tools like Avast or AVG are common culprits) — pause its protection briefly, or better, add Zoom as an exception and try again. Finally, power-cycle your network: unplug your modem and router, wait at least a full minute, plug the modem back in and wait for it to fully reconnect, then plug in the router and retry.
6. Reset your sessions and escalate to Zoom support. Sign in to zoom.us in a browser, open your account's security settings, and sign out of all devices to kill any stuck or conflicting sessions. Then try signing in on the desktop app again — and if you have access to a second Zoom account, try that too, to confirm the block is about the device rather than one specific account. If 1132 still appears on the same device or profile, you have done everything self-service can do: contact Zoom support directly (their support center or the email thread from step 1), tell them your client version, your OS, the error code, and every step you already tried. Since they hold the server-side flag, their intervention is the final path when the restriction won't clear locally.

Did this fix it? Quick checklist

• You can sign in to the Zoom app without the 1132 error
• Zoom's leftover data folders (%appdata%/Zoom, and Zoom.tbd on Mac) are deleted
• Zoom is updated to the latest version on every device you use
• You confirmed the "Report to Zoom" email so your case is logged with their team

If you've done all six steps and the 1132 error still greets you on the same device or profile, the restriction is almost certainly server-side — and that means the ball is firmly in Zoom's court. Keep the browser workaround for your meetings (it keeps working while the block is active), and keep your step-1 report email thread alive: reply to it with your client version and a note that reinstalls, clean installs, and even a new OS user profile didn't clear it. When a user-side fix is possible, the new-profile step is the one that usually lands — so give it a real try before concluding you need to wait on support.