Microphone Not Working in Proctorio? Fix It Before Your Exam Locks You Out
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic TestProctorio's mic detection fails almost every time because Chrome's site-level microphone permission was silently blocked, not because your microphone is broken. The extension performs its audio check inside a sandboxed iframe, which means it reads Chrome's permission state independently of your OS audio settings. If Chrome denied mic access to any site recently, that denial can propagate and block Proctorio's initializer even when your system mic is physically active and showing input levels in Windows Sound settings or macOS Audio MIDI Setup.
Confirm the Microphone Is Actually Working First
Before touching Chrome or Proctorio, verify the hardware is functional. Use the Mic Test tool in a separate tab. It drives the browser's getUserMedia API directly and shows a live waveform with dB input level. If the waveform moves when you speak, your microphone, cable, and OS driver are all functional. If it stays flat, the problem is upstream of Chrome entirely.
Common hardware causes of a flat waveform:
- USB microphone connected to a bus-powered hub with insufficient current. Plug directly into a rear motherboard USB-A port instead.
- 3.5mm combo jack mic not seated fully. The TRRS plug requires a firm click past the TRS detent on most laptop jacks.
- Headset mic muted at the inline controller. The mute button on cables like those using the CVC noise-cancellation module cuts signal before it reaches the ADC.
- Windows selecting the wrong default recording device. Open
mmsys.cplvia Run, go to Recording tab, right-click your actual mic, and set it as Default Device and Default Communication Device separately.
On macOS, open System Settings, go to Privacy and Security, then Microphone, and confirm Chrome is listed and toggled on. Then go to Sound, Input, select your device, and speak. The input level meters must move before Chrome can ever see audio.
Fix Chrome Permissions for Proctorio Mic Not Working
This is the fix that resolves the microphone not detected Proctorio error in the majority of cases. Chrome stores per-origin permission grants in its site settings database, and a single previous denial sticks until you manually clear it.
- In Chrome, go to
chrome://settings/content/microphonedirectly in the address bar. - Under the Allowed section, confirm your exam site's origin (e.g.,
https://yourschool.instructure.com) is listed. If it is in the Blocked section, click the trash icon to remove the block. - Also check
chrome://settings/content/microphonefor any wildcard blocks like[*.]instructure.comthat an IT policy may have pushed. - Navigate to your LMS exam page, click the lock icon in the address bar, find Microphone, and set it explicitly to Allow.
- Reload the page. Proctorio's setup wizard will re-run its media check.
If your institution manages Chrome via policy (common in university Chromebooks), go to chrome://policy and look for AudioCaptureAllowed set to false or AudioCaptureAllowedUrls missing your exam domain. You cannot override policy-level blocks yourself. Contact your IT helpdesk and show them the policy page screenshot.
Proctorio Extension Conflicts and Version Mismatches
Proctorio updates its Chrome extension frequently, and running an outdated version causes the mic initialization handshake to fail silently. The extension ID is bandnfifhokldkdgkgmobijgkemhggjf. Go to chrome://extensions/, find Proctorio, and verify the version matches what your institution's support page specifies. Toggle Developer Mode on in the top right to see the full version string.
Other extensions that capture audio can block Proctorio's exclusive access request:
- Voice recorder extensions
- Google Meet or Zoom browser extensions that pre-claim audio devices
- Krisp or NVIDIA RTX Voice browser plugins
- Any extension with the
audioCapturepermission listed in its manifest
Disable all other extensions except Proctorio, then reload the exam tab. You can do this quickly by creating a Chrome profile used only for exams, with no other extensions installed.
| Symptom | Most Likely Cause | Fix Location |
|---|---|---|
| Proctorio setup spinner never advances past mic check | Chrome site permission blocked | chrome://settings/content/microphone |
| Mic test passes but Proctorio still fails | Conflicting extension holding audio device | chrome://extensions/ โ disable others |
| No input level anywhere in OS or browser | Wrong default recording device or muted hardware | mmsys.cpl (Windows) or System Settings Sound (Mac) |
| Works on one account, fails on another on same machine | Chrome profile-level permission denial | Per-profile site settings, not system-wide |
| Policy block visible at chrome://policy | IT-managed AudioCaptureAllowed = false | IT helpdesk only, cannot self-resolve |
Last-Resort Steps If Microphone Not Working in Proctorio Persists
If you have confirmed hardware function via the Mic Test, cleared Chrome permissions, and disabled conflicting extensions, work through these in order:
- Open Chrome with a fresh temporary profile: launch with the flag
--user-data-dir=/tmp/testprofileon Windows via a shortcut, install only the Proctorio extension, and retry. This eliminates all profile corruption. - On Windows, go to Settings, Privacy and Security, Microphone, and confirm both "Allow apps to access your microphone" and "Allow desktop apps to access your microphone" are on. Chrome falls under the desktop apps toggle, not the modern apps toggle.
- Check Windows audio exclusive mode. Open
mmsys.cpl, Recording tab, double-click your mic, go to Advanced, and uncheck "Allow applications to take exclusive control of this device." Some DAW software or communication apps lock the device. - Update your audio driver directly from the chipset manufacturer. For Realtek, download from realtek.com, not Windows Update. For USB mics using a CM108 or CM6206 chip, the driver is built into Windows but a firmware reset via the manufacturer's utility can clear a stuck mute state.
- Run the Webcam Test as well. Proctorio requires both mic and camera to pass simultaneously. A camera failure can mask itself as a mic failure in the setup wizard's error messaging.
If your exam is within 30 minutes and nothing has worked, contact your institution's exam support line immediately. Most proctoring setups allow a proctor override or a reschedule for documented technical failures. Screenshot chrome://settings/content/microphone and the Proctorio error message as evidence.
Frequently Asked Questions
Why does the mic test pass on other sites but fail in Proctorio specifically?
Proctorio's extension requests microphone access from inside a sandboxed iframe context tied to your LMS origin, not the Proctorio domain itself. Chrome evaluates the permission against the LMS origin. If that specific origin was ever blocked, even months ago, the block persists. Other sites that work are using different origins with their own separate permission grants.
Does Proctorio work with Bluetooth headset microphones?
Technically yes, but Bluetooth audio on Windows uses two profiles: A2DP for high-quality stereo output and HSP/HFP for microphone input. When Windows switches to HFP mode to enable the mic, audio output quality drops to 8kHz or 16kHz and the device appears as a second audio endpoint. Chrome must have this HFP endpoint selected as the input device. Go to mmsys.cpl, Recording tab, and confirm the Bluetooth Hands-Free device is set as default, not the Bluetooth stereo device.
Can I use a virtual microphone or audio routing software with Proctorio?
No. Proctorio actively checks for virtual audio devices by inspecting the device label string returned by enumerateDevices(). Device labels containing strings associated with VB-Cable, Voicemeeter, BlackHole, or NVIDIA RTX Voice virtual mic endpoints will cause the check to fail or flag the session. Use a physical microphone.
Will reinstalling the Proctorio extension fix the microphone not detected error?
Sometimes. Reinstalling forces Chrome to re-register the extension's permissions manifest and clears any corrupted local storage the extension uses to cache device state. Go to chrome://extensions/, remove Proctorio, then reinstall it from the Chrome Web Store using the extension ID bandnfifhokldkdgkgmobijgkemhggjf. Do not reinstall from a third-party link.
My microphone works in the Proctorio setup but cuts out during the exam. Is that a different problem?
Yes. Dropout during an active session is almost always a USB power management issue or a Windows audio session timeout. Go to Device Manager, expand Sound, Video and Game Controllers, right-click your audio device, Properties, Power Management tab, and uncheck "Allow the computer to turn off this device to save power." Also go to Power Options in Control Panel, change the plan to High Performance, and under advanced settings set USB selective suspend to Disabled.
Does the browser matter, or does Proctorio require Chrome specifically?
Proctorio's extension is Chrome-only. It does not support Firefox, Safari, or Edge. Some institutions have begun piloting a Firefox-compatible version, but unless your institution's exam instructions explicitly list Firefox as supported, use Chrome version 110 or later. Check your current version at chrome://settings/help.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic Test