I deleted my Plug n Play Software Device Enumerator, do I need it?

[mmv]

This is a question about a resolved problem's side effect,

I lost sound yesterday when booting win 7 after a Steam update. There was a yellow "!" next to my Plug and Play Software Device Enumerator as well as my Facetime HD Camera and my Cirrus Logic CS4206B and AMD High Definition Audio Device in Device Manager (I'm running Win7 Home Premium 64 bit on a mid 2011 iMac on a partition via bootcamp 5).

After lots of searching, I resolved the issue by deleting the nonworking Plug n Play Software Device Enumerator driver and running System File Checker from C:\ prompt. Reset and everything is working, I am a very happy human, but the Plug n Play Software Device Enumerator is still gone from Device Manager.

I had assumed, like other drivers, Windows would detect and re-install it. I don't even know what it is (or if I possibly could have just run the System File Checker and resolved the issue without deleting it) but I want to know if this is likely to cause problems down the line, or if it is something I shouldn't worry about. Everything is working fine, I just no longer see it in Device Manager, whereas deleting the other drivers would lead to their re-install...

Anyone got anything for me on this? Basically just looking to know if I'm ok, or should try and re-install this Software Device Enumerator. Thanks!

 

[maxie]

Hi mmv Welcome to Seven Forums .I would try a Restore point

 

[andrew129260]

See here: Plug and Play Software Device Enumerator

The Plug and Play Software Device Enumerator component provides support for device enumeration. This component supplies the Plug and Play Software Device Enumerator in the swenum.sys file. This component also supplies the machine.inf file, which is a system-supplied INF (information) file for a standard device.

You will need this. I highly suggest a restore point as suggested above. It basically in simple terms allows windows to install standard USB drivers to standard devices such as flash drives etc.

I would also suggest running system file checker.
Instructions to do so can be found here:

Open Command Prompt as an administrator, often referred to as an "elevated" Command Prompt.

Important: For the sfc /scannow command to work properly, it must be executed from an elevated Command Prompt window in Windows 8, Windows 7 and Windows Vista. This is not required in previous versions of Windows.

Once Command Prompt is open, type the following command and then press Enter.

sfc /scannow
Note: There's a space between sfc and /scannow.

Important: If you're trying to use System File Checker from the Command Prompt available from Advanced Startup Options or System Recovery Options, see Tip #1 at the bottom of the page for some changes in how you execute sfc /scannow.

System File Checker will now verify the integrity of every protected operating system file on your computer.

Note: In some situations, especially in Windows XP and Windows 2000, you may also need access to your original Windows installation CD or DVD.

Restart your computer if sfc /scannow did actually repair any files.

Note: System File Checker may or may not prompt you to restart but even if it doesn't, you should restart anyway.

 

[torchwood]

The Easy way

ControlPanel>devicedriver>Scroll to device error`!` highlight >click on action> click on scan for hardware changes,
enter it will then reinstall the device driver