Solved "Device failed to connect" sound plays randomly

[ThisIsMadness91]

"Device failed to connect sound" plays randomly

Hi. This my first time posting here, but I've visited these forums on several occasions in the past to solve various problems, so hopefully someone will be able to help with mine.

My parents and I moved into a new house on the 25th of April, and I got my desktop computer hooked up a few days later. When I started it up, it (re)installed a few drivers (the connected devices were my mouse, keyboard and HDTV that I also use as a monitor), and I was prompted to restart the computer to finish installing them. Because our internet connection wasn't set up until the 10th of May, I only used my desktop a few minutes a week to transfer pictures I'd saved on my laptop while visiting relatives. Ever since I hooked my desktop up in the new house, I've noticed that the "device failed to connect" sound randomly plays after automatically logging into Windows. I usually only need to start my computer up once a day, sometimes restarting to finish installing a program or update. The problem usually occurs once every four or five start-ups, and the sound only plays once each time.

When I started using my computer, I had some trouble double-clicking with my left mouse button for a few days or so, but it works fine now. I've tested the connection of all my devices, and they appear to be as tight as they can be. The Device Manager doesn't show any problems, except when I set it to show hidden devices, but I think that's because the mouse and keyboard I'm currently using aren't the same ones that came with the computer when I bought it. The last Windows update I installed before moving out of the old house was a security update on the 24th of April. I tried to use System Restore to go back to before that update was installed, but the process failed. I recently learned of the Event Viewer while trying to determine the cause and solution to the problem, and I saw that the restore point was either damaged or deleted during the restoration process. I've also noticed two logs that have appeared shortly after logging into Windows every day since I started using the computer in the new house.

Information: The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.

Warning: The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&1&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.00#8&35CCDA1&0&20060413092100000&0#.

I'm not sure if this has anything to do with the problem I'm experiencing, but I think it's too big a coincidence that these logs started showing up around the same time the "device failed to connect" sound started randomly playing. While my computer generally appears to be performing as well as it did before I moved out, this little problem is becoming quite frustrating. I'm sorry if a lot of this information is unneeded, but I thought it would help to be thorough. I'm also sorry if this is the wrong section. Thanks for reading, and I hope you can help.

 

[TVeblen]

Hello ThisIsMadness91. Welcome to the forum.

There is not enough to go on there. There are some good clues though.
That "USBSTOR#DISK...." smells like a USB connected disk drive. Is there one connected? Was there one ever connected (at the old house)?

What would help is a complete description of the old and new setup - right down to the length of the cables used to connect devices to the PC. We are looking for any differences here.

You say you are using a new keyboard and mouse. It would be good to know what the old and new devices are (brand & model #). Were any of these installed with drivers? (keyboard driver or mouse driver).

 

[ThisIsMadness91]

Hi, TVeblen. Thanks for the warm welcome. I'll give you what information I can now, but some will have to come later today when I have a chance to speak with my dad.

I must mention that I don't know much about the technical aspects of computers, so I apologise if I get anything mixed up. I had to look up what a USB disk drive was, and I'm pretty sure I've never had one connected since I bought the computer. I do have a couple of USB flash drives that I occasionally use, though.

Unfortunately, I can't remember exactly what mouse originally came with the computer as it's been roughly two years since I replaced it, but I believe it was a generic Microsoft mouse, possibly the Basic Optical mouse. I've been using a Roccat Kova[+] since then (and I hope to replace it later this summer). Both mice had drivers automatically installed upon connecting them to the computer, and the Roccat mouse came with a CD to install a driver specifically for it. I'm not sure what the model number is, though, or how to find out.

The keyboard that came with the computer was a Packard Bell KB-0420, and I kept it until a few months ago when I accidentally dropped it and broke one of its legs. Since I couldn't find any replacement legs for sale, I bought a cheap replacement, an Acer KU-0420. The only noticeable difference I can see between the two keyboards is the connector - the old one had a PS/2 connector while the new one has a USB connector. Unlike my Roccat mouse, the only drivers for both of these keyboards were the ones automatically installed upon connecting them to the computer.

Sorry if this information isn't particularly helpful. I've been using these current devices for so long that I didn't think I'd ever need to think back to the old devices. I'll speak with my dad later so that he can help me gather any more information, including the lengths of the cables.

One last thing. I don't know if the position of my computer means anything, but when I was living in the old house, I had my computer on the floor because my bedroom had laminate flooring. Right now, it's on my desk next to my TV because my bedroom currently has carpet flooring.

 

[TVeblen]

It's all good. These weird problems take some digging, but it usually ends up being something obvious or overlooked.

Anything you changed while still living in the old house is irrelevant based upon your statement that the problem did not occur while at the old house but only started occurring when you assembled everything in the new house. So if you had that new keyboard and mouse connected and working fine before your move then we can rule that out. We are only interested in what is different from the old setup the day you left.

That error message about UMDF I believe refers to the "Windows User Mode Driver Framework". This would indicate there is a problem with one of the drivers for one of the devices attached or in the computer. If this never happened in the old house then you need to ask: "what changed"?

One thing that can happen is that if you disconnect or remove a device or component without properly removing it from Windows first it can cause problems like this, even if you reinstall it later in the same place. This does not usually apply to USB connected devices though. That is why you need to think about anything you changed or did differently after the move.

 

[ThisIsMadness91]

I can't think of any setup changes, at least not any I was aware of at the time. All of the devices currently connected are the same as what was connected before the problem started occurring. I haven't added any new ones or removed any old ones. The last time I used my computer in the old house, I switched it off before disconnecting anything. Before switching it on for the first time in the new house, I had everything connected again so the drivers started to reinstall themselves as soon as I was logged into Windows.

I had another look at the Event Viewer log mentioning the UMDF reflector, and the source is "DriverFrameworks-UserMode", the Event ID is "10114", and the Task Category is "Startup of the UMDF reflector".

 

[TVeblen]

I have disconnected and/or moved computers many times and have never seen any device drivers reinstalled (as long as it was the exact same setup). So the fact that you did is what has me fixated on something changing.

But it could be possible that something inside the PC was shaken loose in the move, and now is not completely seated.

I will check with others to see about that UMDF notice.

 

[tom982]

Hello ThisIsMadness91, welcome to SevenForums!

I would like to ascertain a few more details before we continue. Can you download Service Scanner (by farbar) and double click on it to run it:

Farbar Service Scanner Download

When it appears, tick every box on the list and click Scan. After a few seconds, a notepad window should open with FSS.txt (this is saved in the same location as FSS.exe). Copy and paste the contents into your next post please!

SFC Scan

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

 

[ThisIsMadness91]

I have disconnected and/or moved computers many times and have never seen any device drivers reinstalled (as long as it was the exact same setup). So the fact that you did is what has me fixated on something changing.

But it could be possible that something inside the PC was shaken loose in the move, and now is not completely seated.

I will check with others to see about that UMDF notice.

Thanks. I also thought it was strange that the drivers were reinstalled. I disconnected my computer two or three months ago to clean it, and I don't recall having to reinstall the drivers when I reconnected it. I don't think my dad had to do it with his computer, either. When I first noticed the problem, I also wondered if something had come loose inside.

Hello ThisIsMadness91, welcome to SevenForums!

I would like to ascertain a few more details before we continue. Can you download Service Scanner (by farbar) and double click on it to run it:

Farbar Service Scanner Download

When it appears, tick every box on the list and click Scan. After a few seconds, a notepad window should open with FSS.txt (this is saved in the same location as FSS.exe). Copy and paste the contents into your next post please!

SFC Scan

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

Hi, Tom. Thanks for welcoming me. I've run the Farbar Service Scanner and will post the results now. Because my user name is the same as my real name, I've replaced it with "User Name" for privacy reasons.

Farbar Service Scanner Version: 31-05-2013 01
Ran by User Name (administrator) on 06-06-2013 at 12:40:09
Running from "C:\Users\User Name\Desktop"
Windows 7 Home Premium Service Pack 1 (X64)
Boot Mode: Normal
****************************************************************

Internet Services:
============

Connection Status:
==============
Localhost is accessible.
LAN connected.
Google IP is accessible.
Google.com is accessible.
Yahoo IP is accessible.
Yahoo.com is accessible.


Windows Firewall:
=============

Firewall Disabled Policy:
==================


System Restore:
============

System Restore Disabled Policy:
========================


Action Center:
============


Windows Update:
============

Windows Autoupdate Disabled Policy:
============================


Windows Defender:
==============

Other Services:
==============


File Check:
========
C:\Windows\System32\nsisvc.dll => MD5 is legit
C:\Windows\System32\drivers\nsiproxy.sys => MD5 is legit
C:\Windows\System32\dhcpcore.dll => MD5 is legit
C:\Windows\System32\drivers\afd.sys => MD5 is legit
C:\Windows\System32\drivers\tdx.sys => MD5 is legit
C:\Windows\System32\Drivers\tcpip.sys => MD5 is legit
C:\Windows\System32\dnsrslvr.dll => MD5 is legit
C:\Windows\System32\mpssvc.dll => MD5 is legit
C:\Windows\System32\bfe.dll => MD5 is legit
C:\Windows\System32\drivers\mpsdrv.sys => MD5 is legit
C:\Windows\System32\SDRSVC.dll => MD5 is legit
C:\Windows\System32\vssvc.exe => MD5 is legit
C:\Windows\System32\wscsvc.dll => MD5 is legit
C:\Windows\System32\wbem\WMIsvc.dll => MD5 is legit
C:\Windows\System32\wuaueng.dll => MD5 is legit
C:\Windows\System32\qmgr.dll => MD5 is legit
C:\Windows\System32\es.dll => MD5 is legit
C:\Windows\System32\cryptsvc.dll => MD5 is legit
C:\Program Files\Windows Defender\MpSvc.dll => MD5 is legit
C:\Windows\System32\ipnathlp.dll => MD5 is legit
C:\Windows\System32\iphlpsvc.dll => MD5 is legit
C:\Windows\System32\svchost.exe => MD5 is legit
C:\Windows\System32\rpcss.dll => MD5 is legit


**** End of log ****

 

[ThisIsMadness91]

Sorry for double posting, but I'm trying to complete the second task and can't seem to save the CBS log to my desktop. It keeps telling me that either the syntax of the command is incorrect or the system can't find the path specified. Are there any examples of a completed command so that I know what I'm supposed to type? I'm guessing what I'm trying to type in place of %windir% and %userprofile% is wrong.

Also, is it possible to remove individual events from a log in the Event Viewer, or am I only able to clear the entire log? I'm asking because there are over 50,000 events in the log and it makes navigating to logs from a particular date a bit tricky.

 

[tom982]

Sorry for double posting, but I'm trying to complete the second task and can't seem to save the CBS log to my desktop. It keeps telling me that either the syntax of the command is incorrect or the system can't find the path specified. Are there any examples of a completed command so that I know what I'm supposed to type? I'm guessing what I'm trying to type in place of %windir% and %userprofile% is wrong.

Also, is it possible to remove individual events from a log in the Event Viewer, or am I only able to clear the entire log? I'm asking because there are over 50,000 events in the log and it makes navigating to logs from a particular date a bit tricky.

Just copy and paste the command that I posted into command prompt. Windows will automatically expand %windir% and %userprofile% to their relevant locations so you don't need to change a thing


There isn't an easy way to remove individual events from the Event Viewer logs I'm afraid but you can filter the results to remove the main occurrences.

 

[ThisIsMadness91]

Thanks. I'll run the SFC scan again later and post the results. Too bad about Event Viewer, but I guess I can manage.

 

[ThisIsMadness91]

I copied and pasted the second command, but it still didn't save anything onto my desktop. However, I've been doing a bit more looking around in the Event Viewer and found some things that may of interest.

I've noticed that the logs I mentioned in my first post (the information log about the UMDF reflector and the warning log about the driver load failure) also appeared a few times on the 20th and 21st of February. Before those logs are a few logs referring to installation of a device's drivers. The Device Instance IDs in these logs all being with USB\VID_05AC&PID. Although searching the full IDs don't result in any exact matches, searching for "USB\VID_05AC&PID" brings results relating to Apple drivers. I remember connecting my iPhone to my computer a few months ago while trying to solve a problem with it. I restarted my computer with the phone still connected but disconnected it before the computer finished restarting. When it logged into Windows, I heard the "device failed to connect" sound. I reconnected my phone and restarted the computer again, but this time I waited for it to finish restarting before disconnecting the phone. I didn't hear the sound again after that.

Looking at the logs from the 28th of April, I've noticed that the UMDF reflector and driver load failure logs didn't appear immediately after setting up the computer in the new house. I set it up at around 5PM to make sure it worked, and I remember my dad mentioning that he could use his mobile phone as a hotspot so that he could access the internet on his computer. I tried to do the same with my iPhone at about 9PM, but because the hotspot feature wasn't part of my contract, I simply disconnected it and waited for BT to set our internet connection back up. The information and warning logs start to appear around 9PM, not 5PM. Before those logs, again, are logs referring to drivers being installed for a device with USB\VID_05AC&PID at the beginning of the Instance IDs.

There's one more thing I noticed. Both before the 20th of February logs and before the 28th of April logs, there are logs referring to changes made to the start types of two services.

Information - The start type of the Windows Driver Foundation - User-mode Driver Framework service was changed from auto start to demand start.

Information - The start type of the Windows Image Acquisition (WIA) service was changed from demand start to auto start.

Currently, the Driver Foundation service's start type is set to manual, while the WIA service's start type is set to automatic.

I'm sorry if I've presented this information in a way that makes it difficult to comprehend. I've tried to present it chronologically and in such a way that I'm not jumping back and forth between points of interest. I currently have two ideas. The first is to change the start types of these services (change Driver Foundation to automatic and and WIA to manual). The second is to uninstall and reinstall all Apple-related software and devices. I'm going to change the start types before I go to bed and see how things go over the next week. If I don't encounter the problem again, I will let you know. If I do, I'll either try the second idea or see what other suggestions you have.

 

[tom982]

Hi ThisIsMadness91,

If you don't mind, I'll deal with the SFC problem first then come back to this driver issue - or someone else can help out as well. SFC is what I'm best at so I'll stick to that, for now.

Navigate to the following folder:

C:\Windows\Logs\CBS

And copy the file CBS.log to your Desktop. Zip it up and attach it to your next post please

Tom

 

[ThisIsMadness91]

Not sure if there's a problem with SFC other than not being able to copy the log to my desktop. I've done as you asked, but unless it has a possible solution to my original problem or if it detects other major problems, I think I'll leave it as it is.

I've started up my computer three times so far with the service start types changed. The two logs haven't show up since then, but it's usually not until the fourth or fifth start-up that I hear the beep.

 

[tom982]

You've certainly got something wrong in the background. Your CBS log is full of these errors:

2013-06-11 19:17:15, Info                  CBS    Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-06-11 19:17:15, Info                  CBS    Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2013-06-11 19:17:15, Info                  CBS    Warning: Unrecognized packageExtended attribute.

Manifests are responsible for a vast range of things - from sample videos to drivers. There's a chance, although it's small, that this is the cause of your other problem.

Can you download and install the System Update Readiness Tool please?

Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [May 2013] from Official Microsoft Download Centre

Post the log when finished:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Hopefully this will reveal the faulty manifest!

Tom

 

[ThisIsMadness91]

I'm downloading it now and will run it later, but there are several new updates available right now. Should I install them first or should I run this tool first?

Also, how far back do these errors go? If it's up to last Tuesday, it may be because I used System Restore to undo a bad NVIDIA driver update (probably not the best way to go about it, but I haven't encountered any issues since then) and it may have undone some Windows updates as well.

 

[ThisIsMadness91]

I decided to hold off on running the tool until after the updates were installed. Since they installed successfully, is it still worth running the tool? I'll do so if it is.

 

[tom982]

Hi ThisIsMadness91,

Sorry for the delay, I had an exam this morning.


This error can't be fixed by an update as the corrupt component is part of an update, so the problem will still exist even though it hasn't surfaced yet. If we don't fix it now, it will certainly crop up at a later date so it's best to get it done now whilst it's still an easy job So yes, run the tool and post the log then we'll attempt a fix.


Tom

 

[ThisIsMadness91]

No worries. I appreciate you taking the time to help me. It took a while, and I thought the installer had frozen or something, but the tool ran successfully. Here are the contents of the log.


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 19.0
2013-06-14 07:30

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 842
Found 2 errors
CBS MUM Corrupt Total count: 2

Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat



I've started and restarted the computer several times this week with the service start types changed, and I haven't seen the logs or heard the "device failed to connect" sound. As relieving as this is, it makes me wonder if the problem was always there and was simply hidden until the service start types changed, or if the problem only recently started and is only being hidden now. It would be cool if your advice manages to get rid of the problem altogether, but I'm somewhat content with these results. I'll stick around, though, until we either find a solution to this other problem that's been brought to light, or decide that it's minor enough to ignore.

 

[tom982]

No worries. I appreciate you taking the time to help me. It took a while, and I thought the installer had frozen or something, but the tool ran successfully. Here are the contents of the log.


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 19.0
2013-06-14 07:30

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 842
Found 2 errors
CBS MUM Corrupt Total count: 2

Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat



I've started and restarted the computer several times this week with the service start types changed, and I haven't seen the logs or heard the "device failed to connect" sound. As relieving as this is, it makes me wonder if the problem was always there and was simply hidden until the service start types changed, or if the problem only recently started and is only being hidden now. It would be cool if your advice manages to get rid of the problem altogether, but I'm somewhat content with these results. I'll stick around, though, until we either find a solution to this other problem that's been brought to light, or decide that it's minor enough to ignore.

It's great that the device issue has gone by modifying the service settings!


You'll be glad to hear that the errors in this log are nothing of concern and are simply caused by a bug in the way the System Update Readiness Tool detects package names

So, subject to no further problems, you're good to go! If you ever get any Windows Update problems the post back in this thread and I'll sort those out for you - I'm not convinced the manifest problem has gone, but as the SURT can't find it I don't think we should worry about it.