yeah I was going to, but it says they aren't plugged in :O but im using them now and sound works fine, something has to be fucking with something else the mic works, settings just aren't being saved they keep reverting.try setting default communications to headphones maybe. I'm just guessing at this point
is that what you ended up doing, or did you roll back? im not sure if the two are the same or not like I said when I rolled it back, it was labled "Microsoft" instead of "realtek"couldn't hurt
I don't have another PC around to test it, but the mic itself does work, like I stated a few times it works for about 5 minutes when the pc is starting up, its the options that aren't staying saved, in windows or in realtek audio manager.This is going to sound silly, potentially, but do you have the driver disk for your motherboard? What you should do, is completely remove the realtek sound drivers and related software, then put the disk in and look for the system audio drivers. It -should- autodefault back to it without you having to reinstall everything.
edit: Also, you really need to test your mic on something else to make sure it is working. And if the headset is usb and installed drivers when you first plugged it in, you probably want to delete those and let windows reinstall the driver for the microphone.
No I was unable to get CCleaner to actually install... that was the other weird thing I got to the part where you uncheck google toolbar, and when I did that the install closed itself out, everytimeThe realtek driver is your onboard sound driver. Have you done the full uninstall + CCleaner + reinstall latest realtek driver?
To me it sounds like either a driver conflict or a program you are running is conflicting it. I would start turning off programs and seeing after each one if you can save your volume settings.
Motherboards - Z87-PLUS - ASUSGrab the audio drivers from the website for your motherboard and use those.
alright, is there a reason CCleaner scans my pc find a bunch of junk, but then when I right click on the problems, and click "clean" nothing happens it says it removed stuff but they just keep reappearing.If that's your motherboard they should work. They're verified anyways, then you can upgrade later if you n eed to
Right click the CCCleaner program and select "Run as Administrator" and that might solve your problem with it not letting you clean files. Alternatively, boot into safe mode and then do it from there.Motherboards - Z87-PLUS - ASUS
pretty sure that's them, idk for sure though.
so ccleaner finished scanning... but I cant actually delete any of the shit it scanned and wants me to remove, I keep right clicking and selecting "clean" nothing happens.
tried opening as admin, still didn't work it scans but when I go and right click select "clean" it dosent actually get rid of any files, I updated to the trial just to see if that was the problem.Right click the CCCleaner program and select "Run as Administrator" and that might solve your problem with it not letting you clean files. Alternatively, boot into safe mode and then do it from there.
To check if it is a problematic program, use the msconfig.exe program (just type msconfig in the search bar of the start menu) and then choose selective startup. Go into the "Startup" tab and uncheck everything (unless this is a laptop, then you want to double check each startup program so that the basic device software such as keyboard and monitor etc are loading) and then save setting and restart. Load up sound recorder (again, just type into startup) and test your mic from there. If it works in that configuration, your issue is an installed program, which I would then go through the list and load stuff one at a time to see where the problem lies, starting with audio programs such as teamspeak, mumble, iTunes, etc.
Since you don't think you did anything crazy after it worked during the raid and then the next day it didn't, do you have auto-updates for Windows and other programs turned on? If so, and it might be painful, but go into the update manager (Windows Update, for example) and look at the update history and see if anything was updated during the time frame. Then just roll back those specific changes and see if that fixes the issue. It isn't super uncommon for a hotfix that solves one problem to break something else by accident.