What is Reddit's opinion of Driver Store Explorer?

From 3.5 billion Reddit comments

Realtek Universal Audio Driver.

https://github.com/AlanFinotty/AAFDCHDriverMod
https://github.com/pal1000/Realtek-UAD-generic

Gw pake yg versi Alan Finotty tanpa addon lainnya kayak Dolby dll karena driver ori Dell ada addon Waves MaxxAudio (yang ngeselin banget dan gak enak suaranya), entah kenapa pake versi pal1000 gak muncul notification untuk jack-nya. Udah gitu pake versi AAF gak ada suara pop-up setiap play audio tiba-tiba. Kayaknya kalo versi pal1000 harus ganti regedit di Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e96c-e325-11ce-bfc1-08002be10318}\00##\PowerSettingsPowerSettings > ConservationIdleTime & PerformanceIdleTime (## = ganti sama angka)

Jangan lupa matiin automatic driver update dan uninstall audio driver related pake Driver Store Explorer https://github.com/lostindark/DriverStoreExplorer

https://github.com/lostindark/DriverStoreExplorer/releases This is a good tool to remove old drivers from Windows's driver storage.

And then use this for the rest of the hidden places Nvidia likes to put them: http://www.gameplayinside.com/optimize/cleaning-up-old-nvidia-driver-files-to-save-disk-space/

This.

A copy of the drivers is also in the windows driver store and using DDU will also get rid of that giant waste of space. Or a tool like this can be used.

Did you nuke all the drivers that get cached into C:\Windows\System32\spool\drivers ?

IIRC to make sure it cleans them out properly you might need to stop the local print spooler service, delete all the drivers from that folder and then restart the PC.

You could also try Driver Store Explorer as this can sometimes show drivers that are getting loaded even if they don't appear in device manager, I'm not sure if print drivers will show here but might be worth a try:

https://github.com/lostindark/DriverStoreExplorer

I had the same problem and found a fix in another thread. There's an old version of the Windows Hello Face Software Device (HelloFace.inf) still installed.

It must be a leftover from Windows 10. Using Driver Store Explorer, I deleted all versions of the driver and restarted the computer. Upon restart, windows had installed the proper driver and facial recognition was working once again.

For stability, remove outdated drivers with the Internet turned off using Driver Store Explorer and reinstall the driver.

Drivers to remove: iaLPSS2_GPIO2_CNL.inf , iaLPSS2_I2C_CNL.inf , iaLPSS2_SPI_CNL.inf , iaLPSS2_UART2_CNL.inf .

What if I told you there was ANOTHER copy of the same folders in the Windows SxS folder? You can use a program called Driver Store Explorer to find and delete them- https://github.com/lostindark/DriverStoreExplorer

Have you tried using DDU in safe mode and disabled windows update to keep it from installing GPU drivers in the background? You can also use a tool like driver store explorer to check if there are any old AMD GPU drivers present Windows might use.

With the GPU drivers completely gone I would also uninstall Afterburner and any other tool capable of altering GPU clocks before trying to install any drivers again. 18.11.2 or 18.12.1 seem to be a good start since they are based on an older Adrenalin feature build.

Once the drivers are back to working order I recommend not opening Wattman at all and try the latest Asus GPU Tweak or Afterburner instead.

If everything fails you can always try the second bios on your card.

Visual Studio stuff should be in your Program Files - not really sure how they are factored into the 43 GB.

You could also use DriverStore Explorer to check if you have an unexpected issue with old driver packages sitting around. This would manifest as a LOT of packages which are multiple hundreds of MB each - I've only seen this once, but it is possible.

Otherwise, you'd just have to dig into the WinDirStat results a bit more to see what's what. A fresh install of Windows is typically 15-20GB, so depending on what you've installed and where, it is hard to say what that 43 GB is composed of.

YES! I've had this problem and couldn't find out if it was a Windows Driver Update or Lenovo Driver Update.

In the end, I did a factory restore and am still re-installing my programs which is just a waste of time/energy. I couldn't find which driver update caused the issue but since you seem to have found it, you can try removing the driver and see if it works again?

Use https://github.com/lostindark/DriverStoreExplorer Driver Store Explorer to forcibly remove the Lenovo Dynamic Power Uitility

I've fighting with this crapware/crapdriver for two days, I don't use the internal soundboard, so could've just disabled it in BIOS and go ahead with my life, but had to try, so in the end what worked for me was:

-Uninstall Sonic Studio Virtual Mixer and Realtek from device manager

-Stop Nahimic and Realtek services

-Uninstall Realtek driver from apps and features if it is present.

-And last, and most important, remove all Realtek, A-Volute, Nahimic or Sonic Studio related drivers from driverstore, using DriverStoreExplorer

After rebooting, Windows loaded a standard Microsoft HD driver for the soundcard, it works fine, and detects headphones connection. I also uninstalled Realtek console, so it doesn't asks me what is plugged in the connector anymore, but I think the console is safe to keep, I just went berserk while uninstalling ...

If you had Windows 10, it will probably automatically install base drivers it needs and boot up just fine. When it boots up, you should manually uninstall old drivers(from control panel or using RAPR) and use DDU to uninstall old gpu drivers. Then reinstall new one from mobo and gpu sites.

This should work fine, but reinstalling system is recommended.

I found this in asus forum. I ran these steps to get rid of Sonic Studio from my computer.

CLEANUP

/!\ If you already had Realtek (HD) Audio Driver, Realtek Audio Control/Console, Sonic Studio III & Sonic Radar III installed /!\ Uninstall them (Start > Settings > Apps) then restart your PC - Launch Driver Store Explorer (https://github.com/lostindark/DriverStoreExplorer/releases/latest) > Check the boxes of all versions of drivers which .inf starts with (if you find them) : a-volute | avolute | dts | hdx | realtek - Check the box "Force Deletion" then click on the "Delete Driver(s)" button then restart your PC

https://github.com/lostindark/DriverStoreExplorer/releases

Damit kannst du die Treiber endgültig löschen. Das Tool nutzt Windows eigene Befehle hinter der Oberfläche. Aber sei vorsichtig, damit kann man auch viel kaputt machen.

if it was ever paired before, uninstall them from device manager.. then unpair from bluetooth settings under settings, if that doesnt work and bluetooth is usb, change usb port and try again.. if its a pcie card, uninstall it.. check https://github.com/lostindark/DriverStoreExplorer out, use it to clean the old uninstalled drivers.. otherwise it might just be broken..

Able to solve the problem.

Uninstall software.

Using your utility tool CleanupRazerDrivers.exe, clean up drivers.

Clear Temp folder.

Clear registry. HKEY_LOCAL_MACHINE/Software/RAZER

Clear inf files related to razer here - C:\Windows\System32\DriverStore\FileRepository

Using driver store explorer confirm there are no drivers related to razer are installed. https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.8.3

Restart.

Install the software again.

Got your system info file, thank you! The only suspect is vigembus driver, and its creator has described how it can be removed (also, he recommended this tool for removal, I'd start there: remove the vigembus driver, reboot, check that it's not there and check on reWASD)

Once the driver is removed completely, reWASD (and the system) should see your controller as DS4 right away.

Hi! Thanks for your response.

Have disabled auto update via Control Panel > System & Security > System > Advanced System Settings > Hardware > Device Installation Settings.

Before I saw your comment, I realized that when going into Device Manager > Display Adapters > Intel UHD Graphics 620 > Driver > Update Driver > Browse My Computer for Drivers, there were two Intel Drivers that always seemed to be listed. I found that they "lived" in C:/Windows/System32/DriverStore. I tried to remove the folders a few different ways, but was always rejected access because I needed access from "System". I downloaded DriverStoreExplorer and was able to successfully locate and remove the two drivers.

Following this, I changed the video driver to the Basic Display Adapter driver and went to Intel's website and downloaded the most recent DCH driver for my device. I am on driver version 30.0.100.9805 and haven't experienced any overt issues since installing.

Keeping my fingers crossed that this solves my black screen issue. Removing the drivers seemed to really be the trick, as somehow broken ones would continue to install even after installing the most recent ones from Intel/Lenovo/Whoever.

From my experience, you can first try device manager. I open it by typing it's name at the search bar near the start menu.

Once open, select the menu option "view" and "show hidden devices". Then click to uninstall device on all Realtek devices with the checkbox to delete driver software checked. Don't reboot. Now install your drivers.

Also have the option to use a program such as https://github.com/lostindark/DriverStoreExplorer To force deletion of old drivers.

I had to install my Realtek audio drivers in this manner. The installer stuck itself in a loop upon reboot. It was set to uninstall drivers then reboot and reinstall. However, I assume by the time it rebooted, windows had already reinstalled the old drivers before the installer could.

i use now other and better alternative now. here

you can choose any mod you want in this list:

Realtek Default Effects

Realtek Default Effects with DDL & DTS

Dolby Digital

DTS Interactive

A-Volute Nahimic 3

A-Volute Sonic Studio 3 (ASUS ROG)

Dolby Atmos Speaker System

Dolby Atmos for Gaming

DTS HeadphoneX v1

DTS:X Ultra

DTS Sound Unbound

​

iam testing this with music, home theater, and gaming and it work greater than before.

you just need to properly uninstall old audio driver with DriverStoreExplorer

Try Driver Store Explorer, it's way more user friendly than calling pnputil manually. Also, keep in mind Core Isolation often can't be used on older PCs due to vital drivers being incompatible (e.g. integrated GPU or SATA controller). You can't remove that without rendering the entire OS broken...

Have you disabled all sound devices other than the DAC in Device Manager?

Install DriverStoreExplorer and make sure that you do not have any old drivers in your storage. Select Old Drivers -> Delete Drivers. Then go through and look manually.

https://github.com/lostindark/DriverStoreExplorer

Yeah it definitely ain't a voltage supply problem, but I just wanted to make sure 100% since what you are having is the same symptoms for an unstable voltage supply/failing processor. It seems like some very important driver is crashing and causing these freezes. Go to myASUS and download Serial IO and Intel Dynamic Platform and Thermal Framework Driver. Then download "DriveStore Explorer" from here https://github.com/lostindark/DriverStoreExplorer/releases/download/v0.11.64/DriverStoreExplorer.v0.11.64.zip

Now turn off your laptop's internet then launch drivestore explorer and sort by Device Name to make things easier to find. Select Intel Dynamic Platform and Thermal Framework Manager and Intel Dynamic Platform and Thermal Framework Processor Participant, Intel Serial IO GPIO Host Controller and Intel Serial IO I2C then tick force deletion then click Delete Driver(s). Now simply install the two drivers you have downloaded from myASUS and see if that fixes the problem.

I might've (hopefully) finally (probably) managed to prevent its damn reinstall:

1. Open Device Manager and uninstall these following components + their driver software:

   • Sound, video and game controllers > Nahimic mirroring device
   • Software components >AVoluteNH3Ext

2. Verify that Nahimic Service in services.msc is disabled/stopped/gone. If it's not, stop the service, open %WINDIR%\System32 and locate Nahimic/NhNotifSys related files (sort by date modify next to find files dated exactly the same time), and remove those files. Next run in an elevated CMD window sc delete NahimicService to remove the service.

3. Browse to %LOCALAPPDATA% and remove the NhNotifSys folder entirely. If you can't you have to exit the Nahimic Companion app in the notification area (or kill NhNotifSys process through Task Manager).

4. Use DriverStoreExplorer to force delete the A-Volute Extension driver package.

5. Use the Show or Hide Updates troubleshooter (direct link) to hide the A-Volute - Extension driver update.

6. Restart the system for good effort.

After this, hopefully, the damn thing should remain off the system. In my testing, triggering a "Scan for hardware changes" in Device Manager didn't allow the Nahimic companion app to come back, which it used to do before I hid the update using the Show/Hide Updates troubleshooter.

Try uninstall with DDU: https://www.wagnardsoft.com/DDU/download/DDU%20v18.0.3.4.exe It’s also for audio. Maybe also check driverleftovers with DriverExplorer https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.11.64 (but be careful with selecting. If you don’t know what to do, skip this) You may also want install the Realtek driver from pal1000 https://github.com/pal1000/Realtek-UAD-generic/releases but this is up to you.

Manually installed drivers usually pop up there. Alternatively you can use DriverStoreExplorer to let it show all installed drivers on your computer - in case it is a driver.

Yo sorry for the late reply as something came up that didn't let me use reddit until now.

Download this tool: https://github.com/lostindark/DriverStoreExplorer/releases/download/v0.11.37/DriverStoreExplorer.v0.11.37.zipand prepare your asus system control driver then turn off your laptop's internet.

Now Open the tool you've downloaded, then you want to look for every asussci2.inf and then tick all of them. Now tick "force deletion" then click "Delete Driver", let it complete and refresh. Now install your driver and see if its working as it should. (There could be some old ASUS System Control V2 drivers conflicting with the new ones, happened to me too a while back)

Download O&O ShutUp10 and turn off the Windows driver update options, restart your machine. Then download Driver Store Explorer (RAPR) located here: https://github.com/lostindark/DriverStoreExplorer/releases/latest and let it search and delete all old driver version Windows is keeping on hand for fast re-installation. Delete and restart. Then do your driver mods accordingly.

I would use Driver Store Explorer and run it in admin mode: it'll give you a list of device drivers installed in the catalog, you choose the one at fault and remove it completely, then install the right ones. At least give it a try, just be careful.

We are seeing this on a bunch of machines as well. For a M720s (this worked https://support.lenovo.com/us/en/solutions/ht510392-audio-device-missing-or-cannot-find-audio-device-thinkcentre-m720s-m720t/)

On T490s, would go into device manager for both audio devices right click uninstall (check box to delete driver), REBOOT, run updates and it should pull the new driver. Might need to run a few times if there are a bunch of older drivers still loaded on the system. I like using DriveStoreExplorer (https://github.com/lostindark/DriverStoreExplorer) to see all of the installed drivers and use "Force Remove" to pull the audio ones out.

Use Driver Store Explorer for uninstalling drivers ( set force delete option )

intel I219-V driver ( Only driver ) - ( Full package )

I found this thread. You may need to do a clean install. There's this comment towards the end it seems to have worked for a few people.

' folks, if you guys are still having problems with the Realtek UAD drivers and getting RPC service errors:
uninstall the Realtek UAD driver by using either DDU (display driver uninstall utility) or Driver Store Explorer (RAPR) [remove all extensions and components related to Realtek if using RAPR], also uninstall Realtek Audio Console UWP app, reboot and clean install whatever UAD driver you were using '

sure, this is how I did it (in Windows7); I had problems figuring it out too... so I downloaded DriverStoreExplorer which shows all installed drivers, and has a Add Driver button.

then I installed the Clock Work Mod-universal drivers through the Installer. (which didn't fix it, yet)

then I went to DriverStoreExplorer and clicked Add Driver and selected android_winusb.inf from C:\Program Files (x86)\ClockworkMod\Universal Adb Driver\usb_driver\ (this might be unnecessary, but It's what I did)

then I connected my Phone and selected File Transfer (MTP) on it..

then I went to Device Manager ^(My Computer>Right Click>Properties, sidebar has Device Manager)

there I found the Unknown USB device (don't remember exact name, as all Devices are recognized and it was the only one not back then)

right click>Properties>Driver>Update Driver>Browse my computer for driver software > Let me pick from a list of device drivers on my computer got me to the Driver Selection Screen.

on the left side I selected ClockworkMod as the Manufacturer.

and on the right side I selected Spreadtrum Android Interface

and that got windows to recognize the phone... and adb devices command to show it.

On Windows 7, I actually had to uninstall the Korg USB Midi Driver AND remove it from the Driver Store as well ( https://github.com/lostindark/DriverStoreExplorer ).

Now it just works using a generic USB audio driver.

From what I can tell from a very quick google search, they are realtek drivers. I had a few drivers that had the issue with the System permission, I removed them with an app called 'driver store explorer' - link. I can't vouch for the apps integrity though, so do your due diligence before you decide to use it. Maybe first just uninstall any realtek devices in device manager, or try updating the drivers to see if that clears it up first (Windows should reinstall the correct drivers after a reboot). A virus/malware scan is never a bad idea either.

It was best practices back in the days of XP/ME/98. Switch out a mobo and not reinstall those OS's = BSOD as chipset drivers would conflict. Now, it's not a huge deal (although I still personally recommend installing and keeping your chipset drivers up-to-date).

Finally, I would highly recommend using something like Driver Store Explorer to remove any old drivers from the Windows Driver store and keep it "clean". Conflicts can still happen...

Download the “DriverStore Explorer”: https://github.com/lostindark/DriverStoreExplorer/releases

and unzip the Package. Then start the Rapr with Administrative Privileges. After that search and delete the driver.

https://i.imgur.com/AJzZMu2.png

This is what the program looks like. Everything underneath Display adapters, aside from the most recent one, should be deleted. If they're in use, you won't be able to delete them, so leave it.

https://github.com/lostindark/DriverStoreExplorer/releases/download/v0.10.54/DriverStoreExplorer.v0.10.54.zip

Extract and run the program in that archive. Click on "Select Old Drivers" on the left and then "Delete Package" once it selects them.

Now https://github.com/lostindark/DriverStoreExplorer Obviously you want to install something without checking its fine & works so do that... Then when you are sure i'm not a douche & its legit, start the programme, click Select old drivers then it'll select old drivers for USB e.t.c. & then hit Delete Driver. Should remove any conflicting USB drivers If thats the issue hopefully its fixed it, if not then im out of ideas probably something faulty on touching inside the device on the USB line?

You could try this as well... But its really Techy... & I cant really help you with. So this is a Microsoft programme, lets you see whats running, Be very careful as once you delete something its GONE from the o/s system!. You seem to have enough knowledge so look around at audio drivers running & start up e.t.c. I'd only use it to view then go through google & control panel > programmes > uninstall/ alt+ctrl+Del>task manager>start up tab or Services tab to track them down & disable.

I've found that installing over the current ones and then using something like DriverStoreExplorer to delete the older drivers to be a bit more effective.

Sorry about that, it always worked for me. The only thing I can now is to fully uninstall every last trace of every Wacom driver version yo have installed while trying (use the uninstallers for the software/control panel applet and also remove the actual driver from the driver store whit something like this: https://github.com/lostindark/DriverStoreExplorer). Then reboot (twice, because sometimes the uninstallers need cleanup after a reboot) and try again with the linked version.

About the actual calibration, the bad mapping only occurred on the borders for me. So I was able to get a fairly wide area with good mapping.

And for the fingerprint, again, sorry I can't help more, but I do not remember what else I might have done to get it working.

My Windows folder is 14,3 GB. I keep it clean with DriverStoreExplorer and by using DISM cleanup in an elevated command prompt : DISM /Online /Cleanup-Image /StartComponentCleanup

Try using RAPR to clean up old drivers (saved me a few GBs) or PatchCleaner to clean up left over patches

Probably because the driver is saved locally in the driver store so Windows is pulling it from there. Your PC cannot function without a SATA driver so Windows will reinstall one and the most up to date version available to it is the 1.3.1.276 one so it installs that. You'd need to download a software like RAPR to delete the AMD SATA driver off the driver store so Windows cannot install it back and instead installs the basic Microsoft one. Not sure if you will have problems pulling this off though so be aware of that and save any important data you got before doing it.

Most likely because you frequently update your graphics drivers and NVIDIA is terrible about cleaning out the old packages properly (not sure about AMD/Intel, but probably the same).

Either use DDU to completely remove everything, then reinstall, or use DriverStoreExplorer to delete them manually.

Pro-tip #1: if your motherboard drivers have been removed, your system will not crash. In fact you can boot without having any of these installed - it's how stuff works on first boot. If these files are corrupted you should boot into safe mode (this is basically Windows booting without extraneous drivers) with networking and reinstall the drivers; this is not hard.

Pro-tip #2: If your system files are missing or corrupted, you can fix this using your windows install media to repair your installation. If you don't have windows install media available, you can create a recovery drive using Microsoft's recovery drive feature, available through their site.

Pro-tip #3: In the future a much cooler and more useful tool than any single-driver uninstall utility is DriverStoreExplorer(Rapr.exe): https://github.com/lostindark/DriverStoreExplorer. This tool can be used not only to remove the currently-functioning GPU driver, but also relic GPU drivers Windows has held onto in the past prior. I used this software along with a registry cleaner and file cleaner to pretty much turn my years-old Windows install (Win 7 - Windows 10 upgrade) into a brand-new install because that's how much I hate reinstalling windows.

Pro-tip #4: This is really probably not the AMD tool's fault. I've used it before; lots of people use it successfully. Absent your event logs we will never know what truly happened, but software (and computers in general) is great because it behaves repeatably. I say this as a support technician/engineer-y guy - your issue probably had to do with some kind of unexpected prior setting on your system, something unexpected that occurred during the software's operation, or user error. In any case, you have plenty of options for recourse; all is not lost. You can move forward on this.

Try:

1. Go into the Device Manager disable the Killer device
2. Uninstall the Killer Drivers there (you will also want to uninstall the Killer Networking software suite from the Programs and Features if you have it installed)
3. Use DriverStore Explorer to remove the driver package from your system
4. Restart and enable the Killer device in the Device Manager (you may need to restart the device again)

It may end up working fine with the generic Windows wi-fi drivers, and these steps should ensure you you can give them a try.

Boot into Safe Mode > uninstall the drivers > use DriverStore Explorer to also remove them from the store > boot into your normal account

Try using this program to find the problem drivers.

Then right click > change status > Stop

If that doesn't work, you may need to change the startup type to Disabled via right click, then reboot the system.

You can then delete the files and use DriverStore Explorer to make sure they are gone.

If you can't get the drivers to stop or change their start-up type, try using Autoruns > Drivers tab > uncheck + right click Delete them > restart

Edit: Also, if you want you can wait on this. I'm walking another guy through the same procedure to get rid of this driver. Not sure if Windows has a substitute for this particular mouse so you may have to leave it running without a replacement. The bottom line is that you both have unexplained crashes, and are both running this odd 4 year old driver which caused problems with previous versions of Windows 10.

If you have another mouse around that you can use for a bit then you might try doing that for a couple of days to see if the crashes subside. That would of course involve getting rid of the t_mouse.sys driver beforehand.

As asked, what is the Make and Model of your motherboard?

You could use DriverStore Explorer to try and manually remove any old USB related device drivers which you aren't using.