A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component failure. For macOS app privacy permissions, first inspect Privacy & Security and test the app immediately after granting one permission.
What this covers
- macOS app privacy permissions with this exact failure state
- Diagnosis across system permission versus app selection, managed policy and relaunch requirement
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleCheck Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. Expected behavior: grant the selected app only the camera, microphone, files, accessibility or screen access it needs.
Isolate the component boundary
ReversibleInspect Privacy & Security and test the app immediately after granting one permission. Test the peripheral on a different port or user account, and test a different peripheral on the same port. Boundary to separate: system permission versus app selection, managed policy and relaunch requirement.
Correct only the proven cause
ReversibleGrant the narrow permission and relaunch/update the app. Reinstall or roll back the driver, or grant the missing app permission.
Verify and stop safely
ReversibleConfirm the feature works after a full restart in at least two different applications. Do not grant Full Disk Access or Accessibility to an untrusted app.
Evidence ledger
Sources behind this answer
Exact questions