Report abuse. Details required :. Cancel Submit. Well, there was a service, recreating them on reboot, but a friend of mine a computing engineer made some changes in the registry, and cut a folder from system32, to paste it in a Temp folder i assume some useless drivers and services , and since no devices are getting recreated in the Dev Manager on reboot and I only have 3 instances left of unknown devices, which are disabled : So thank you very much, I guess the problem is solved now :.
How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. This site in other languages x. Right-click on the downloaded file and select [Extract All] to unzip the compressed folder. Select [I accept the terms in the license agreement] and start the download session. After the download session has complete open the downloaded file and double-click [Autorun] to install. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page.
View all page feedback. In this article. However, if you want to permanently remove the associated file or files, using TweakUI will give you the name of the main file involved, and you can then delete it by hand. Generally, installing a newer version of a driver for existing hardware is easier than getting rid of those related to hardware you are about to or have already removed.
Nevertheless, many musicians run into problems while updating audio-interface drivers and, once again, thoroughly removing the old ones first nearly always results in fewer 'issues' later on. As I've already reminded you, scrupulously following the manufacturer's instructions always helps, particularly relating to the order in which you should install drivers and plug in the hardware, and whether or not you need to remove the hardware before updating the drivers which tends to be the case with dongles, for example.
Some obscure audio and MIDI interface installation faults can be traced to duplicated and redundant entries in the Registry, which has device driver limits that may prevent you properly installing a new interface. Using the Device Manager clean-up described in the main text removes these unwanted extras, as you can see from this screenshot. In the upper, 'before', Registry window you can see a total of eight wav devices, while 'after' the cleanup lower window the total has dropped to five.
Some musicians still automatically launch Device Manager, right-click on the device whose drivers they want to update and choose the 'Update Driver' option to launch Window's Hardware Update Wizard.
While doing this will provide you with an extra option to connect to the Internet so that Windows Update can search for new drivers for you, the chances of finding any for the majority of professional audio and MIDI interfaces is almost nil. However, the main problem with leaving Windows in charge of audio or MIDI interface driver updates is that it's been known for it to discover some existing old driver files part-way through the update, even after you've pointed at the location of the new ones, resulting in a mix of old and new driver file versions being installed.
Such mix-ups didn't happen so often when manufacturers insisted that new drivers should always be copied onto a floppy disk before installing them, because the source drive was then A: and the destination drive C:, but nowadays nearly all of us download new drivers via the Internet, so both old and new files end up on our hard drives and the possibility for Windows confusion increases. For years, the next line of defence against such problems was to follow detailed step-by-step instructions, downloaded from the interface manufacturer's web site, on how to remove all references to their hardware by hand, before attempting to install newer driver versions, to stop such version conflicts.
However, since many owners ignored these instructions and ran into problems, such manual uninstall information is disappearing and the tiny Kb zipped collections of driver files that we used to download are being replaced by intelligent belt-and-braces installers of several megabytes in size. These perform all the searches for us, delete all the driver files, and then place the same Kb of new driver file versions into the appropriate folders, before telling us to reboot our PCs.
Thus, when Windows detects a soundcard and finds no drivers installed for it, the complete set of new files is sitting there ready and waiting for it, with no possibility of confusion.
Yet another reason to follow the manufacturer's instructions when upgrading audio or MIDI interface drivers is that most modern interfaces have dedicated Control Panel utilities or complex mixer console software as well as the driver files.
Windows doesn't know about these, and if you let it take charge you could end up with new drivers being controlled by an older version of the Control Panel, which is another recipe for crashes or other weird and wonderful problems for the future. If you're installing your interface for the first time, letting Windows take the strain will also result in no Control Panel utility appearing at all — only the drivers will be installed.
I'll say it one last time: it really does pay you to follow the manufacturer's advice! If the hardware utility you want to remove doesn't appear in Control Panel and you suspect that it's being run as a startup routine, the easiest way to find out is using Microsoft's System Configuration utility, which you can launch by selecting the Run option in the Start menu, entering 'msconfig' into the text dialogue and pressing return.
On the Startup page you'll find a list of routines that are either in the common Startup folder or in the Registry's Run or RunOnce sections. Just as with extraneous Control Panel entries, unticking one will stop it being loaded on the next boot ideal for double-checking that it isn't still required , and you can then delete the file manually.
If your old audio interface leaves behind a startup utility, you should be able to find it using the freeware Autoruns. A rather more elegant utility is the freeware Autoruns from SysInternals www. It can also display other parameters, such as Explorer add-ons shell extensions, custom toolbars, and the like , and helpfully lets you hide the multitude of Microsoft entries if you're searching for third-party add-ons.
Using Autoruns you can selectively disable any extension and also permanently delete it, from within the same application. So what can you do if the worst happens and you've already yanked out and disposed of loads of hardware without first uninstalling its drivers?
Well, first take a look in your 'Add or Remove Programs' list. If there's still an entry for the hardware in question, it's still worth trying to run it. You can also downoad and run any dedicated uninstall utilities after the event. In the absence of such device-specific options, there are various manual techniques you can use to track down driver files, and references to them in the Registry. However, anyone who wants to try these techniques should be aware that they can entail grave risks, and if you accidentally delete any system files or Registry entries that may still be required, you may subsequently be unable to boot up Windows at all.
If you want to try the techniques, I would strongly recommend first creating a backup image of your Windows partition, using a suitable utility, such as Norton's Ghost, so that if you run into problems you can use the saved image file to exactly restore Windows to its former state.
Judging by the number of times readers have since asked me for the link to the on-line version, it has since become a well-used routine amongst PC musicians. The Windows NT, and XP Device Manager only normally displays Registry entries for devices that are currently connected, even if you use its'show hidden devices' function, but if you follow these steps you can force it to display redundant devices that are no longer connected, so that you can delete them once and for all.
Here are some additional points that may help.
0コメント