BCM20702A0 driver

[maxie]

Well done Patrick ... I would make a Restore point before making any changes ...Is it really worth bother with considering every thing is working well now ? ...

 

[Slartybart]

Excellent news Patrick!

From what I read in the link maxie posted about tcpmon.ini - it might just require a printer install.
I just logged on and have not read your Speccy, but if you have a wireless printer see if there is a driver update for it on the mfr site. (some printers carry the ini even if it's not wireless)

If it comes to it, there are a few other things to try, last is just to tell SFC to stop reporting it (sounds easy, but requires a bit of doing).

Always start with the simple and work up (printer driver update -> stop SFC from reporting it)

It isn't an integral part of Windows as far as I know and shouldn't affect normal operation. The only time it would even be noticed is in a SFC report.

I'll catch up again - look at Speccy and maybe look for an easy way to fix the SxS store (SURT can grab files off install media if you know what cabinet tcpmon.ini is in - the link also seemed to indicate that it was from the Dell install - so it might have originated on the starter edition. Lots of research few answers.

It's not something a novice should attempt though. I was a novice once and royally screwed up a few systems learning that I shouldn't do stuff until I knew more

As maxie said: make a restore point while the system is working well. If you have external drives, it would also be a good idea to make a System image.

When you get the chance, the earlier the better:
Set up all your applications and when you're happy with the system as a good base in case revovery is needed - create a System image. Then all you have to do is back up your personal data on a regular schedule (a copy of your folders is the easiest backup). Any applications installed after the System image was created will have to be installed again if you restore the system image. Think of a system image as a snapshot of your system (reserved partition and C:\ ).

Create a System image: ; http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html
Restore a System image: http://www.sevenforums.com/tutorials/675-system-image-recovery.html

An external HDD is preferred in case your main HDD fails - you can replace the main HDD and restore the system image in very little time.

Bill
.

 

[PatrickRobinson]

Re: your good advice

Looking back, it's sad that I must admit Bluetooth issue are exclusive from each other. I'm confident that had I simply installed ALL updates before installing the BT device, there would not have been a problem. As I had mentioned (in disbelief) that the same BT device had been working fine with Pro 7, I failed to take into account that it was completely up to date. This time, I restored to factory image, re-upgraded to the Pro, and without taking a breath, attempted to install the Bluetooth emulater immediately. Obviously there will be hundreds of updates necessary when the initial "ISO" is from Windows Starter @ 2009. I'm thinking to myself.....STUPID!!!! thanks so much for everything.
Respectfully, Patrick

 

[maxie]

Hindsight is a wonderful thing the we small word IF only which means so much .... There is no point in looking back as there is no future there ... All one can do is learn from their mistakes ....

 

[Slartybart]

Miss steps - that's all they are.

Now you know why I go step-by-step.

 

[NoelDP]

As Slart suggested, there is a minor problem with the SFC result...

 Line 28894: 2015-01-29 11:35:12, Info                  CSI    000003ab [SR] Repairing 1 components
 Line 28895: 2015-01-29 11:35:12, Info                  CSI    000003ac [SR] Beginning Verify and Repair transaction
 Line 28898: 2015-01-29 11:35:13, Info                  CSI    000003ae [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

This is actually a fairly common error - possibly due to a badly-written install script, but also possibly the result of malware.
Although the problem is almost certainly mostly cosmetic, if not fixed, SFC will always show as 'failing', so you'll never know if something else has changed without diving into the CBS data for yourself.

I'll post a fix protocol a little later.

 

[NoelDP]

Since this is a fairly common error, I've created a semi-permanent patch file....
THIS PATCH IS ONLY FOR 32-BIT MACHINES! DO NOT USE ON 64-BIT!!


I've uploaded a file - tcpmon32.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\tcpmon32
hit the enter key - if you get a 'Not Found' error try
DIR D:\tcpmon32
or
DIR E:\tcpmon32



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\tcpmon32 <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[Slartybart]

Thanks Noel ...