screen capture is supported but access is blocked by permission or policy
A permission failure can block perfectly healthy hardware. DeviceOK separates browser permission from whether the device exists and produces a usable signal.
Do not jump to the most invasive fix
Do not reinstall hardware drivers before checking the site/browser and operating-system privacy controls.
Retest the same condition
After permission is granted, rerun the relevant live test and confirm the device produces the expected signal/output.
Rule out the simple causes
- 1
Run the DeviceOK screen-share test from a normal top-level tab.
- 2
Check OS screen-recording/privacy permission for the browser.
- 3
If this is a work/school device, check whether an administrator policy blocks capture.
Work through the problem in order
- 1
After granting permission, fully quit/reopen the affected browser if the OS requires it.
- 2
Run DeviceOK again before testing the meeting app.
- 3
If DeviceOK passes, inspect meeting-host or organization policies next.
If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.
If the same capability also fails in DeviceOK and another trusted diagnostic path, broaden the investigation to connection, operating-system/device state, official driver or firmware support, and finally hardware.