UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
USB capture card connected to a Windows PC on a dark desk with a frozen settings panel visible on the monitor
Fix It Yourself · Troubleshooting

capture card settings not changing

Updated 25 July 202611 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Your capture card shows up in Windows, your software recognises it, and yet every time you try to change a setting it either reverts, freezes, or does absolutely nothing. It's not the card that's broken. In most cases it's a permissions block, a dodgy USB connection, or Windows quietly cutting power to the device. This guide walks through every fix, from the fast two-minute check to a full driver reinstall, so you can get back to recording or streaming without pulling your hair out.

TL;DR

Capture card settings not changing is almost always caused by Windows privacy permissions, a USB 2.0 port or hub, USB selective suspend cutting power, or a stale driver. Start by unplugging, switching to a USB 3.0 port, and checking Camera and Microphone privacy in Windows Settings. If that doesn't sort it, disable USB selective suspend and reinstall the driver.

⏳️ 13 min read ✅ 87% success rate 📅 Updated July 2026

Key Takeaways

  • Capture card settings not changing is rarely a hardware fault. Software and Windows config cause it most of the time.
  • USB 3.0 port, directly on the motherboard, is non-negotiable for stable capture card operation.
  • USB selective suspend is a silent killer for capture devices. Disable it in Power Options.
  • Always delete and recreate the capture source in your software. Toggling it off and on doesn't clear stale settings.
  • A clean driver reinstall fixes the problem when nothing else does.

At a Glance

  • Difficulty: Easy to Medium
  • Time Required: 5 to 30 mins
  • Success Rate: 87% of users fixed without hardware replacement

What Causes Capture Card Settings Not Changing?

Here's the thing: capture cards are more dependent on Windows system settings than most people realise. They're not just a simple plug-and-play device like a mouse. They sit at the intersection of USB power management, Windows privacy controls, audio and video driver stacks, and whatever capture software you're running on top. When any one of those layers misbehaves, the result is often a settings panel that looks fine but does nothing when you interact with it.

The most common culprit I see in remote sessions is Windows Camera and Microphone privacy. Microsoft tightened these controls a few years back and they've caught a lot of people out. Your capture software might have had permission before a Windows update and quietly lost it afterwards. The card appears in Device Manager, it shows up in your software, but the moment you try to change anything, the request gets blocked at the OS level before it even reaches the device. The Microsoft support page on camera access covers this in detail if you want the official breakdown.

USB port choice matters more than people expect. Capture cards need USB 3.0 bandwidth and stable power. Plug one into a USB 2.0 port or through a hub and you'll get intermittent connections, power drops, and settings that refuse to stick. The card might even appear connected while actually running in a degraded state. Always go directly into a blue USB 3.0 port on the back of the motherboard if you can.

Then there's USB selective suspend. This is a Windows power-saving feature that cuts power to USB devices when they look idle to the system. Microsoft's own USB selective suspend documentation explains how it works at a driver level. For capture cards, 'idle' can mean any moment you're not actively streaming, and the device gets suspended mid-session without any obvious error message. Settings changes made during or after a suspend cycle often just don't apply.

Driver conflicts and stale software states round out the list. If another application has the capture card open (even minimised in the background), your main software can't write settings to the device. And if the driver itself is corrupt or mismatched after a Windows update, the settings interface might accept your input but fail silently when it tries to push the change to the hardware. These are the cases where a clean reinstall is the only proper fix.

Capture Card Settings Not Changing: Quick Fix

This takes five to ten minutes and clears the problem for the majority of users. It covers the USB connection and the Windows privacy settings that block capture card access most often.

1

USB Reconnect and Privacy Check Easy

  1. Unplug the capture card completely
    Pull it out of the USB port. Don't just disable it in software. Physically disconnect it.
  2. Close everything that might use it
    Close your streaming software, any video editing tools, Discord (yes, Discord can grab capture devices), and anything else that might have the card open. Check Task Manager if you're not sure.
  3. Reconnect to a USB 3.0 port
    Plug into a different USB 3.0 port, ideally on the back of the PC directly into the motherboard. USB 3.0 ports are usually blue inside. Avoid front panel ports and hubs for now.
  4. Check Camera privacy in Windows Settings
    Open Settings, go to Privacy and Security, then Camera. Make sure the toggle for your capture software is on. If it was already on, toggle it off, wait five seconds, toggle it back on.
  5. Check Microphone privacy the same way
    Still in Privacy and Security, go to Microphone and repeat the same check. Capture cards often register both a video and audio device, and the microphone permission blocks the audio side.
  6. Reopen your software and recreate the source
    Don't just relaunch and hope. Delete the capture card source from your scene or project and add it again from scratch. Reselect the device manually.
If settings now apply and persist after closing and reopening the software, you're sorted. Keep reading the prevention section to stop it happening again.
Dedicated video tools software can make capture card management a lot cleaner, with built-in device health checks and permission diagnostics that Windows doesn't expose natively. Worth considering if you run into this problem repeatedly.

If the quick fix didn't hold, don't worry. The next tier covers the system-level settings that cause capture card settings not changing in more stubborn cases. It's also worth checking if you have any microphone not working in Windows issues running alongside this, because the root cause is often the same privacy permission block affecting both devices at once.

More Capture Card Settings Not Changing Solutions

These fixes go a level deeper into Windows power management and the USB driver stack. If the quick fix didn't work, one of these almost certainly will. Budget around fifteen to thirty minutes.

2

Disable USB Selective Suspend Easy

  1. Open Control Panel
    Search for Control Panel in the Start menu. Don't use the Settings app for this one, it's not exposed there.
  2. Go to Power Options
    Click Hardware and Sound, then Power Options. Click Change plan settings next to your active plan.
  3. Open advanced power settings
    Click Change advanced power settings at the bottom of the page.
  4. Find USB settings
    Scroll down to USB settings, expand it, then expand USB selective suspend setting. Set it to Disabled for both On battery and Plugged in if you see both options.
  5. Apply and restart
    Click Apply, then OK. Restart the PC fully. A proper restart is needed for this to take effect on the USB controller.
After restarting, reconnect the capture card and try changing settings again. Most users find this alone fixes the problem when the quick fix didn't.
3

Reset USB Root Hub and Host Controller Medium

  1. Open Device Manager
    Right-click the Start button and select Device Manager.
  2. Expand Universal Serial Bus controllers
    You'll see a list of USB Root Hubs and USB Host Controllers. You want the ones associated with the port your capture card is using. If you're not sure which one, uninstall all of them. Windows reinstalls them automatically on restart.
  3. Uninstall each entry
    Right-click each USB Root Hub and USB Host Controller, select Uninstall device. Don't tick the box to delete the driver software. Just uninstall the device entry.
  4. Restart the PC
    Windows will detect the missing USB controllers on boot and reinstall them fresh. This clears any corrupted device state that was blocking settings changes.
  5. Reconnect the capture card and test
    After the restart, plug the card back in, open your software, and try changing a setting. Check that it persists after closing and reopening the application.
Don't panic when USB devices temporarily stop working after uninstalling the controllers. Everything comes back after the restart. Just don't shut down mid-process.

This is also a good point to check whether any recent Windows updates might be involved. A bad update can knock out USB controller drivers or reset privacy permissions. If you've had update trouble recently, our guide on Windows Update not working is worth a look before you go further, because a partially applied update can cause all sorts of downstream device issues including capture card settings not changing.

Advanced Capture Card Settings Not Changing Fixes

These steps are for persistent cases where the problem keeps coming back or where the intermediate fixes made no difference. You're looking at a full driver reinstall and a clean software state. It's not complicated, but it takes time and you need to be methodical about it. Skipping steps here is how people end up going around in circles.

4

Clean Driver Reinstall Advanced

  1. Download the latest driver from the manufacturer's website
    Go directly to the capture card manufacturer's support page. Don't use Windows Update or a third-party driver site. Download the full software and driver package for your exact model.
  2. Uninstall the current driver in Device Manager
    Open Device Manager, find the capture card under Imaging devices, Sound, video and game controllers, or USB devices (it might appear in more than one place). Right-click each related entry and select Uninstall device. This time, tick the box to delete the driver software if it appears.
  3. Unplug the capture card
    After uninstalling, physically disconnect the card. Don't reconnect it yet.
  4. Restart the PC
    A full restart clears the driver from memory. Don't skip this.
  5. Install the new driver package
    Run the installer you downloaded. Follow it through completely. If it asks you to restart again, do it.
  6. Reconnect the capture card
    Plug it back into the USB 3.0 port. Windows should recognise it and apply the new driver automatically.
  7. Reset the vendor control panel if applicable
    Some capture cards come with their own configuration app. Open it and reset the device configuration to defaults before making any changes. This clears any settings that were saved from the broken state.
  8. Create a fresh scene and source in your capture software
    Don't import your old settings or copy from an existing scene. Build a new scene from scratch and add the capture card as a new source. Stale source settings in OBS, Streamlabs, or similar apps can persist through driver reinstalls and keep the problem alive.
Took three reboots before this one stuck for one user I helped last month, so don't give up after the first attempt. If the driver installs cleanly and the source is recreated fresh, capture card settings not changing should be fully resolved at this point.
The HowToGeek guide on USB selective suspend has some useful extra context on how Windows handles USB power states if you want to understand what's happening under the hood during these steps.

One thing worth mentioning: if you've been running your capture software with an imported profile or a scene collection you've had for a long time, that's sometimes the actual root cause. Profiles carry old device references and broken source configs across reinstalls. Creating a completely fresh profile, not just a new scene inside an old one, is the proper fix in that situation.

Also, if you're seeing other odd Windows behaviour alongside this, like File Explorer acting up or system tools not responding, it can point to a broader OS issue rather than just the capture card. Our article on File Explorer not responding in Windows 11 covers some of the same underlying Windows state problems that can affect multiple devices and tools at once.

Preventing Capture Card Settings Not Changing

Once you've got it working, a few habits will keep it that way. Most of these take about two minutes to set up and save a lot of frustration later.

First priority: keep the capture card on a dedicated USB 3.0 port and don't move it. Every time you plug into a different port, Windows builds a new device instance. Over time this can create conflicts. Pick one port, label it if you have to, and always use that one.

Second: USB selective suspend should stay disabled permanently on any machine used for capture work. It's a power-saving feature designed for laptops and it causes more problems than it solves for desktop capture setups. Disable it once and forget about it.

Third: after every major Windows update, spend thirty seconds checking Camera and Microphone privacy permissions. Microsoft has a habit of resetting these during feature updates. It's a known issue and it's been the cause of capture card settings not changing for a lot of people who had everything working fine the day before an update. If you've had trouble with updates causing other problems, the patterns in our Windows Update troubleshooting guide are worth bookmarking.

Fourth: close other applications before launching your capture software. Discord, browsers with video tabs, video calling apps, even some media players can grab the capture device and hold it. Your streaming software then can't get exclusive access to write settings. Get into the habit of launching capture software first, before anything else.

Finally, if settings ever stop responding again inside your capture app, don't waste time toggling the source on and off. Delete it and recreate it from scratch. It takes ninety seconds and it works. Toggling almost never does.

Capture Card Settings Not Changing: Summary

Capture card settings not changing is a frustrating problem but it's almost never a sign of broken hardware. In the vast majority of cases it comes down to Windows privacy permissions blocking the capture application, a USB port that can't provide the right bandwidth or power, USB selective suspend cutting the device off mid-session, or a driver that needs a clean reinstall. Work through the fixes in order, start with the USB reconnect and privacy check, move to disabling selective suspend and resetting the USB controllers if needed, and fall back to a full driver reinstall for anything that persists. Recreate your capture source from scratch at each stage rather than carrying over old settings. That single habit prevents more repeat calls than almost anything else.

Frequently Asked Questions

Windows privacy permissions, USB power management, or a second application holding the card open are the most common reasons. Check Camera and Microphone privacy in Windows Settings first, then disable USB selective suspend in Power Options, and make sure nothing else has the card open.

Yes. USB 3.0 provides the bandwidth and stable power delivery that capture cards need. A USB 2.0 port or a hub can cause connection drops, power issues, and settings that refuse to apply. Plug directly into a USB 3.0 port on the motherboard if you can.

USB selective suspend is a Windows power-saving feature that cuts power to USB devices when they appear idle. For capture cards this can cause silent disconnections and prevent settings from being written. Disable it in Control Panel under Power Options, Change plan settings, Change advanced power settings, USB settings.

Always delete and recreate the source from scratch. Toggling it off and on leaves stale settings in place and the problem usually comes straight back. This applies to OBS, Streamlabs, and most other capture software.

It fixes it in a good number of cases, especially when the issue appeared after a Windows update or a software conflict. Download the latest driver from the manufacturer site, uninstall the current one in Device Manager, restart, then install fresh.