Plug and Play Software Device Enumerator


Recommended Posts

After powering off my computer for a minute to plug in a new keyboard, I turned the system on and suddenly the sound driver and a system device called "Plug and Play Software Device Enumerator" were failing.

(image removed)

How do I repair that system driver? I tried reinstalling drivers and 2 other sound cards, all had the same issue. The corrupted Device Enumerator apparently inhibits the sound device from working. The error I kept getting when reinstalling sound drivers was "The I/O operation has been aborted because of either a thread exit or an application request" (image removed)

For the moment, I'm at a loss. I don't know what to do. I'm scared and afraid :cry:

Edited by Isuldor
  Quote
I tried reinstalling drivers [...]  The error I kept getting when reinstalling sound drivers was "The I/O operation has been aborted because of either a thread exit or an application request"

I also tried removing rebooting and reinstalling that system driver. Turns out when you remove it, it's gone. I had to google a way to reinstall it by tweaking an INF file. Anyway it solved nothing because it still comes up corrupted. Is there some binary file that driver depends on that might have been corrupted, that I can replace?

Otherwise I'm still at a loss as of what to do ;\

  Quote
tried [...] 2 other sound cards

Thanks warwagon, but that does not appear to be the issue.

After Googling awhile, I've found people with similar problems. I also found a somewhat helpful thread on another site that explains how to reinstall the Plug and Play Software Device Enumerator, as well as various people complaining about the driver failing.

But in the end, none of the related files on my system were corrupted (I compared checksums with files on other systems) and reinstalling the driver always resulted in a failure message "The driver may be corrupted or missing. (Code 39)".

I guess I'll be reformatting. :no:

Edited by Isuldor
  • 1 year later...
  Isuldor said:
Thanks warwagon, but that does not appear to be the issue.

After Googling awhile, I've found people with similar problems. I also found a somewhat helpful thread on another site that explains how to reinstall the Plug and Play Software Device Enumerator, as well as various people complaining about the driver failing.

But in the end, none of the related files on my system were corrupted (I compared checksums with files on other systems) and reinstalling the driver always resulted in a failure message "The driver may be corrupted or missing. (Code 39)".

I guess I'll be reformatting. :no:

Hello to everyone

I realize that I am about 9 months late with this post (just joined) but I am having the exact same problem as Isuldor.

The Plug and Play Software Device Enumerator reports the error "The driver may be corrupted or missing. (Code 39)" in the Device Manager.

So far I have uninstalled the drivers for the sound card, uninstalled the PnP Enumerator and reinstalled it after editing "allmachine" Setup File in Notepad by deleting line 22 under "Control Flags" After a reboot, the same error occurs. I have also replaced the swenum.sys and streamci.dll files from a known working box and repeated the above process all over again.

I also searched the registry for SWENUM and found a folder by that name. It contained a corrupt key. I was unable to manually delete the key but I ran Registry Mechanic after uninstalling the PnP Enumerator and then reinstalled it. Now the folder called SWENUM is gone and my situation is exactly the same.

I cannot figure out if the problem is hardware or sofware related!

I REALLY don't want to reformat. If anyone can help I would be greatly appreciative.

My Specs:

Intel D865PERL Motherboard

Windows XP SP 2

P4 2.6 Ghz Processor

1 GB of RAM

NVidia 5200 AGP Video Card

On Board Sound running the SoundMax drivers for my audio

Thanks!

  • 1 month later...

Hello jacomus, welcome to the forums.

Looking back now, I wasn't ever able to solve the problem. It did appear to be a software problem, since I tried multiple hardware configurations. And the error message was certainly no help, since I also verified (using a hash sum calculator) that all of the files in question were in fact not corrupt. It's unfortunate that the problem has not been experienced and dissected by smarter Neowin users. I bid you luck on a fresh operating system installation in your near future. :cry:

  • 8 months later...

I've just had a similar problem, but managed to fix it. I installed some drivers (Conexant 878 tv tuner drivers) that caused my system to reboot halfway through the install and corrupt all sorts of drivers at the same time. Scandisk gave me at least three pages of errors. The Plug and Play Software Device Enumerator was showing a code 39, all my cd drives were inaccessible, and pretty much everything related to multimedia was broken.

What worked for me was to boot into safe mode, insert the WinXP SP2 CD, and copy the I386 folder to the hard drive. Then I used regedit to set the following registry key : HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/CurrentVersion/Setup/SourcePath to point at the folder containing the I386 folder (eg. "C:\").

Once I restarted, the Device Manager was back to normal, and everything seems to be working again.

The only other thing I did was to reinstall my Audigy 2 ZS drivers before loading safe mode. Installation finished on the same reboot as everything began working again.

If all that doesn't work, maybe http://www.updatexp.com/scannow-sfc.html will help.

  • 5 weeks later...
  kappaoflegend said:
I've just had a similar problem, but managed to fix it. I installed some drivers (Conexant 878 tv tuner drivers) that caused my system to reboot halfway through the install and corrupt all sorts of drivers at the same time. Scandisk gave me at least three pages of errors. The Plug and Play Software Device Enumerator was showing a code 39, all my cd drives were inaccessible, and pretty much everything related to multimedia was broken.

What worked for me was to boot into safe mode, insert the WinXP SP2 CD, and copy the I386 folder to the hard drive. Then I used regedit to set the following registry key : HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/CurrentVersion/Setup/SourcePath to point at the folder containing the I386 folder (eg. "C:\").

Once I restarted, the Device Manager was back to normal, and everything seems to be working again.

The only other thing I did was to reinstall my Audigy 2 ZS drivers before loading safe mode. Installation finished on the same reboot as everything began working again.

If all that doesn't work, maybe http://www.updatexp.com/scannow-sfc.html will help.

Thanks 'kappaoflegend', Google pointed me to your posting and you truely saved my Winstallation. Lest I've been to reinstall all teh windowshell.

PS Tis this http://www.realtek.com.tw/downloads/downlo...p;GetDown=false drivers that caused my x64 Windows to loose all CD-DVD-Roms, Audio Devices and go havoc

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Wine 10.10 released, brings updated Mono engine, bug fixes for several games, and more by David Uzondu Nearly two weeks after Wine 10.9 dropped, Wine 10.10 is here with an updated Mono engine and the complete removal of a major graphics dependency. The Wine Mono engine, which provides .NET Framework support, has been bumped to version 10.1.0. Another major change is the removal of the OSMesa library as a dependency. OpenGL rendering on memory device contexts will now be handled by a pbuffer, cleaning up the graphics stack. Here are other notable changes with this release: More support for generating Windows Runtime metadata in WIDL. Locale data updated to Unicode CLDR 47. P010 format support in Media Foundation. Of course, no development release would be complete without a boatload of bug fixes. This version crushes a total of 38 bugs, addressing problems in a wide range of applications and games. Gamers will be pleased to see fixes for titles like F.E.A.R., S.T.A.L.K.E.R.: Anomaly, and StarCraft Remastered. Issues that caused a black screen in Steam's Big Picture mode and crashes when starting a new game in F.E.A.R. have been resolved. The fixes go way back, even tackling issues in ancient software like Lotus Freelance Graphics 2.1 and input problems in the classic indie game Braid. Here's the full list of game-related issues addressed: Rise of Nations: Both mouse buttons were required for a single left-click Braid: Both Shift keys needed to move puzzle pieces F.E.A.R: Crashed with an "Out of memory" error when starting a new game F.E.A.R Combat: Black screen at startup due to memory error S.T.A.L.K.E.R. Anomaly: Crashed when loading into a save file StarCraft Remastered: Game wouldn't start with Wine 10.5 Unreal II: Hangs with a black screen when switching to 1440x900 resolution Eador. Masters of the Broken World: Bad map textures after starting the game Horizon Chase: Freezes on startup The Fidelio Incident and Vampyr: Beeping noise on exit Burger Shop: Shifted to the top left corner in fullscreen mode And here's the rest of the issues that were fixed: Lotus Freelance Graphics 2.1: Hangs at the splash screen HTML-Kit 292: Tab bar isn't fully visible without scrolling at 96 DPI Tab completion for cmd: Improvements made regedit: Binary values editor layout is broken and .reg files couldn’t be imported Baofeng5-5.31.1128: Welcome window crashes on start Canon printer driver installation now works Steam Big Picture mode: Fixed black screen when using d3d10 Noteworthy Composer: Crashes in winealsa resolved Ricoh Digital Camera Utility 5: Crashes when switching between Browser and Laboratory modes Wondershare Uniconverter 13: Characters now display properly AVCLabs Video Enhancer AI: No longer crashes on start New thread stack memory usage optimized PlayOnline Viewer: Window now properly activates after being minimized Virtual desktop behavior fixed secur32:ntlm tests now pass on Windows 11 24H2 d3d9:device WM_WINDOWPOSCHANGED test no longer fails on Linux GitLab CI no longer crashes in various multimedia tests HP Prime Virtual Calculator: Fixed startup crash Qt Installer for Windows: Now functions correctly SHIFT-based range selection logic corrected Creating 64-bit wineprefix with old wow64 now possible Regression from realloc switch fixed (memory now zeroed as expected) RTTI now works on arm32 after recent changes Smartsuite 3.1 installer no longer crashes Fixed possible use-after-free in dbghelp's symt_add_func_line Build issues with clang for x86_64 resolved due to RTTI changes You can read the full release notes here. The source code for this release is also available. To get started, follow the installation instructions for your platform: Ubuntu/Debian, Fedora, or macOS.
    • Nice! I hate the chop shop approach as well.
    • Ouch, man.. Hope you can get a replacement for that..
    • They just need to add a transparency slider. I’d prefer a middle ground where everything is transparent, but background items are blurred.
  • Recent Achievements

    • Week One Done
      Simmo3D earned a badge
      Week One Done
    • One Month Later
      Simmo3D earned a badge
      One Month Later
    • One Month Later
      greege earned a badge
      One Month Later
    • Week One Done
      greege earned a badge
      Week One Done
    • Week One Done
      LagFighterZ earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      547
    2. 2
      ATLien_0
      232
    3. 3
      +FloatingFatMan
      165
    4. 4
      Michael Scrip
      119
    5. 5
      +Edouard
      91
  • Tell a friend

    Love Neowin? Tell a friend!