BCM20702A0 driver  

maxie said:

Have a read at the Link below ... But do not do any thing as it could make things worse ...


Cannot repair tcpmon.ini - Microsoft OS Forum - Software & Operating Systems - Dell Community

Good morning guys. Ok, so the computer burned the midnight oil installing 189 updates. Now we are sharing a cup of coffee over another 7 updates. Currently, the audio tone heard when I plug in the USB bluetooth adapter consists of the 3 quick tones which I believe tells me driver issues still exist. Starting from scratch, I attempted the Broadcom set up as the device manual suggests. Again, it quickly tells me it failed to update software. How should I proceed?

Slartybart said:

I try not to trouble shoot an issue on a machine until it is completely up-to-date. Wastes my time and the other member's time.

Sometimes I forget to ask that simple question - thanks for posting that you are updating.

When Windows thnks it's done updating - run Windows update manually and look in the optional offers.
This is where WU provides HW drivers.
accept all offers, download and install.

There might be the driver you need in the list.

If the issue still exists, please PUBLISH another Speccy (you got it right the 2nd time )
Updating Windows obviously changes what's in the Speccy report.

Thanks,

Bill
.

Thanks Bill. I will publish the Speccy in a few.

Slartybart said:

maxie said:

Have a read at the Link below ... But do not do any thing as it could make things worse ...


Cannot repair tcpmon.ini - Microsoft OS Forum - Software & Operating Systems - Dell Community

The TCPmon.ini issue is very mior and doesn't affect the operation of the machine.

This was a good find maxie, but some of the 'solutions' are a bit off. The way Component Based Servicing works is from the SxS store - that's where the action is, not in System32 or Syswow64. Managing the Sxs store is meant to be difficult (TrsutedInstaller is really the only ID that can work with it - unless you start screwing around - not advised)

Anyway, let's forget about the TCPmon.ini - SFC for now and refocus on the BT issue.

Patrick: My trouble shooting methods are slow, but methodical. Please be patient and work step-by-step with maxie and me. Trying different things in between steps might fix the issue, or might cloud the issue. You never know until you take a step what suggestion worked. Know which step solved the problem makes correcting it in the future (a fresh install) all the easier.

That's the way I fix stuff - other members have other methods. Some are faster and some take longer because of the number of steps forward / steps backward / steps nowhere.

Trouble shooting is really just trying different solutions to find the one that works on your machine. There is a method though, an order of suggestions and attempted solutions. Doing them out of order might cloud the final solution. I don't always know the exact order, but I know an order - simplest to more difficult.

I always let members know that this is their thread, their machine, and their time. How you proceed is always your choice.

I'm busy setting up a new install - so I'll be in and out for most of the day - hang tight... step-by-step. I'll review what you post and go to the next step.

You don't have to rely solely on my input, maxie is very good.

Bill
.

Step (1)

PatrickRobinson said:

Slartybart said:

maxie said:

Have a read at the Link below ... But do not do any thing as it could make things worse ...


Cannot repair tcpmon.ini - Microsoft OS Forum - Software & Operating Systems - Dell Community

The TCPmon.ini issue is very mior and doesn't affect the operation of the machine.

This was a good find maxie, but some of the 'solutions' are a bit off. The way Component Based Servicing works is from the SxS store - that's where the action is, not in System32 or Syswow64. Managing the Sxs store is meant to be difficult (TrsutedInstaller is really the only ID that can work with it - unless you start screwing around - not advised)

Anyway, let's forget about the TCPmon.ini - SFC for now and refocus on the BT issue.

Patrick: My trouble shooting methods are slow, but methodical. Please be patient and work step-by-step with maxie and me. Trying different things in between steps might fix the issue, or might cloud the issue. You never know until you take a step what suggestion worked. Know which step solved the problem makes correcting it in the future (a fresh install) all the easier.

That's the way I fix stuff - other members have other methods. Some are faster and some take longer because of the number of steps forward / steps backward / steps nowhere.

Trouble shooting is really just trying different solutions to find the one that works on your machine. There is a method though, an order of suggestions and attempted solutions. Doing them out of order might cloud the final solution. I don't always know the exact order, but I know an order - simplest to more difficult.

I always let members know that this is their thread, their machine, and their time. How you proceed is always your choice.

I'm busy setting up a new install - so I'll be in and out for most of the day - hang tight... step-by-step. I'll review what you post and go to the next step.

You don't have to rely solely on my input, maxie is very good.

Bill
.

Step (1)

Step (2) http://speccy.piriform.com/results/n...j4t7P2nDJg33Yv

Heads up Bill and Maxie....\
After publishing the Speccy, I went back to the Broadcom Setup and it is working as it should. So I will proceed with the standard BT install and setup. However, at a more convenient time for the two of you, I would still like to address the file corruption (just for fun/knowledge). I will confirm results momentarily prior to closing this thread. Respectfully, Patrick