Browser privacy settings blocking hardware tests?

A browser test says a feature is unavailable, a device is missing, or some computer details cannot be read. That can look like hardware failure, but privacy settings may be limiting what the browser is allowed to share.

Use Browser Info to check your browser's permissions, privacy details, and supported features. Then compare the failing test with a few targeted changes before you assume the device is broken.

Check what your browser allows

Open Browser Info in the same browser where the test failed. Review the information about the browser version and engine, permissions, privacy, and supported features.
Return to the test that failed and note what is missing. A camera or microphone test should request permission first. Other tests may depend on a browser feature that is not supported or is restricted.
If the browser asks for camera or microphone access, allow it only if you want to run that test. Then reload the page and try again. For example, compare the Camera Test or Microphone Test with the permission information in Browser Info.
Open the same test in a regular browser window if you were using a private window, or compare it in another browser. A difference points toward browser settings, extensions, or compatibility, not necessarily a faulty device.
If you use a privacy extension or a built-in site protection feature, temporarily relax it for TooLab and test again. Restore your usual setting after the check, especially if you changed a global protection setting.

What the result means

A browser feature is listed as unsupported

The current browser or device does not expose a feature the test needs. This is a compatibility or browser limitation, not proof that the hardware is broken. Check the same test in an up-to-date browser that supports the feature, or use the operating system's own settings or diagnostic options.

A permission is blocked or denied

The browser cannot use that device on the page until you grant access. This commonly affects the camera and microphone. A site permission can be blocked in the browser even when the operating system allows the browser to use the device.

The test works in another window or browser

The device is probably working, and the difference is in the first browser's privacy settings, extensions, or site permissions. Private browsing can use separate permissions or stricter protections, so compare like with like before changing system settings.

Only some details are missing

Browsers intentionally limit or simplify certain information to reduce device fingerprinting, which is the practice of identifying a device from a collection of details. A browser may provide only a rounded hint about RAM rather than the exact amount. Missing detail does not mean the hardware is absent.

The permission is allowed, but the device still does not respond

Check the device selection, system permission, connection, and other apps that might be using it. If the same device also fails in another supported browser or in the operating system, a driver, connection, or hardware problem becomes more likely.

How to fix a blocked diagnostic

Allow access for this site. Open the site controls next to the address bar and check the permission for the device the test needs. Set it to allow, then reload the page. Browser menus differ, so look for the site permission rather than changing every privacy setting.
Check operating system permissions. On Windows 11, open Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone. Turn on access for the device and allow desktop apps to access it. On macOS, open System Settings › Privacy & Security › Camera or System Settings › Privacy & Security › Microphone, then enable your browser if it appears.
Check phone permissions if you are testing on a phone. On Android, open Settings › Apps › your browser › Permissions and allow camera or microphone access as needed. On iPhone, open Settings › Privacy & Security › Camera or Settings › Privacy & Security › Microphone and check browser access. Names can vary slightly by operating system version.
Make a site-specific privacy exception. If a tracking protection feature or extension blocks a test, allow the site temporarily or turn off that feature just for the test. Avoid disabling protections for every site. Retest, then restore the original setting if it made no difference.
Close other apps using the device. A meeting or recording app may hold a camera or microphone, or change which input is selected. Close it fully, then reload the test. Choose the intended device in the test if more than one is available.
Update or switch browsers. Install browser updates and try a current browser that supports the feature. If the result changes, keep the device and system settings the same while you compare, so you can identify the cause.
Reconnect the hardware. For a USB device, try another port and reconnect it. For a wireless device, check its connection and battery. If it fails in multiple supported browsers and the operating system cannot use it either, investigate the device or its driver.

When the hardware may be at fault

Privacy restrictions are a more likely explanation when a test reports a blocked permission or unsupported feature. Hardware becomes a stronger possibility when the device is missing from the operating system too, fails in more than one supported browser, or works intermittently when its cable moves. For a USB accessory, test another port or computer if available. If the failure follows the device, check its warranty or arrange a repair or replacement.

Privacy can limit a test without breaking it

A browser test can only report what the browser exposes. Some privacy protections deliberately reduce device information, while other settings block access to a particular device. Neither result is a complete hardware inspection. Use Browser Info to separate browser support and permission issues from the behavior you observe in the test, and avoid weakening protections that do not affect the feature you need.