Wes Sato
Backend developer for a long time, currently mostly APIs and databases. Interested in wordpress, static sites, testing.
- Reputation
- 73
- Topics
- 0
- Posts
- 8
- Solutions
- 0
- Joined
- 29 January 2026
Hello and welcome! Don't be afraid of basic questions. Most of us started by breaking something and asking someone how to fix it.
💯
@wsato works on paper, not in real life, try turning off the settings first, fixed it for me idk maybe im wrong lol
hmmmm
lol this thread is gold... try turning off the router first, fixed it for me any ideas??
Uninstall teh ghost entries: Device Manager View Show hidden devices , then remove greyed out entries for the headset under Sound , Audio inputs and outputs and Human Interface Devices . Replug and let Windows enumerate it fresh.
been there man if the headset uses a companion app with its own driver, reinstall that apps latest version from the makers support page 😂 A mismatch between the apps driver and a newer Windows audio stack can block detection.
hmmm do a proper clean install of the previous driver: download it from the NVIDIA support page, boot into Safe Mode, run DDU , reboot, then install. A plain rollback in Device Manager sometimes leaves the problematic profiles in place.…