"Device failed to connect" sound plays randomly

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.

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

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

Code:

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

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 said:

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.