none
Microsoft bluetooth mouse and Windows 7

    Question

  • Hello.

    I've upgraded my Vista-based notebook Acer Aspire 3810t to Windows 7 build 7100 and cannot use my Microsoft Bluetooth Notebook Mouse 5000 any more. When trying to pair the mouse (after I enter 0000 as a passcode) I get an error:

    Adding this device to this computer failed

    The attempt to add the device resulted in an unknown error.
    The error code is:0x8007048f
    Contact your device manufacture for assistance

    Bluetooth adapter is Broadcom 2045. Mouse worked great with Windows Vista. Other devices (2 cell-phones) work great with Windows 7.

    Tuesday, July 14, 2009 4:10 AM

Answers

All replies

  • Hi Andrey

    Check here for the latest Windows 7 information.

    Microsoft Hardware Support for the Windows® 7 RC Release

    Hope this helps.

    Thank You for testing Windows 7

    Ronnie Vernon MVP
    Tuesday, July 14, 2009 5:20 AM
    Moderator
  • Hi Ronnie

    I have the same problem with my Mouse 5000

    I am running Vista Bussiness.

    I had the mouse working but unfortunately removed it by accident. When I try to pair it again with 0000 the error message comes up.

    I can pair anything else but not the mouse


    PLEASE HELP ME

    Regards

    Theo
    Tuesday, August 25, 2009 6:43 AM
  • I also upgraded my Vista (x64) notebook, an Asus G50V, to Windows 7 build 7100, but my BNM 5000 worked fine. The other day I wiped the drive and performed a fresh installation of Windows 7 RTM. When I tried to connect the mouse, I received the same error message.
    I pulled over the Wireless Console and Bluetooth drivers from Asus, and still couldn't add the mouse.
    I pulled over the Intellimouse driver/app as suggested by Ronnie, even though this mouse is not in the list of supported mice. It didn't help. Even rebooted and tried again, still just errors or wouldn't detect the mouse at all.
    Even though the mouse has sat unused for a couple months, off, I decided to change the batteries. Mouse was detected, connected, drivers got loaded automatically, and it works like it should now. Removed the Intellimouse stuff, and it still works.

    Maybe this will help someone else out.

    Wednesday, September 16, 2009 8:41 PM
  • I'm running Windows 7 Ultimate (64-bit) - final version - using a Microsoft Mouse 5000.  I'm getting errors when I pair my mouse with another device and then come back to this machine.  I don't understand how this can possibly happen, but if I set up the mouse with another computer - or even another O/S on the same machine (dual booting), then come back to the original configuration, this message pops up.

    The only way to correct it is to remove the mouse from the Bluetooth list of devices, and then start the pairing process all over again - every time! 

    I hope there's a better way...!
    Friday, November 06, 2009 9:40 PM
  • Hi,
    I had the same problem with my MS Bluetooth Notebook Mouse 5000 after update to Win7.
    Look what I have done:
    1 - Remove the batteries from mouse
    2 - Re install the batteries and be sure they are good (if not, install new pair)
    3 - follow the steps from http://support.microsoft.com/kb/952818

    Good luck!
    Saturday, November 21, 2009 7:14 AM
  • Excuse me, can you help me with my problem with desktop? I write msg. in catt. desktop
    Thank you 

    Saturday, November 21, 2009 7:43 AM
  • This worked for me!
    Saturday, January 30, 2010 12:26 AM
  • Yes... removing the batteries worked for me too.  But I had to leave them out for several minutes.
    Tuesday, February 23, 2010 2:37 PM
  • Hello.

    I've upgraded my Vista-based notebook Acer Aspire 3810t to Windows 7 build 7100 and cannot use my Microsoft Bluetooth Notebook Mouse 5000 any more. When trying to pair the mouse (after I enter 0000 as a passcode) I get an error:

    Adding this device to this computer failed

    The attempt to add the device resulted in an unknown error.
    The error code is:0x8007048f
    Contact your device manufacture for assistance

    Bluetooth adapter is Broadcom 2045. Mouse worked great with Windows Vista. Other devices (2 cell-phones) work great with Windows 7.


    I'm getting this error code when pairing my enV Touch and Sony Vaio.  The Vaio has bluetooth (printer setup was a snap) but I can't get it to pair with the cell phone.  I have Win7 Premium Home 64-bit.  Any suggestions would be appreciated. 
    • Proposed as answer by matsuhar Sunday, October 03, 2010 4:11 PM
    Friday, April 30, 2010 1:59 AM

  • I'm running Windows 7 Ultimate (64-bit) - final version - using a Microsoft Mouse 5000.  I'm getting errors when I pair my mouse with another device and then come back to this machine.  I don't understand how this can possibly happen, but if I set up the mouse with another computer - or even another O/S on the same machine (dual booting), then come back to the original configuration, this message pops up.

    The only way to correct it is to remove the mouse from the Bluetooth list of devices, and then start the pairing process all over again - every time! 

    I hope there's a better way...!

    Hey Red Hagar,

     

    how did you solved the problem?

     

    Thx

     

    Patrick

    Saturday, January 01, 2011 10:58 PM
  • I had the same hangup too with the repeated error code and failure to pair.  Yes, you need to push the "other button" under the mouse but if the top mouse LED indicator isn't flashing red/green after you push that Locate button, it just isn't resetting correctly.  I found it's not enough to just remove the batteries for several minutes.  You have to turn off the mouse, remove the batteries, then switch the power switch on again (yes, without the batteries!) and I even spun and clicked the mousewheel a few times for good measure.  In other words, there is enough capacitance in this thing to hold charge and a scrambled ID setting for a long time so you have to go out of your way to truly discharge this thing.  Anyway, after I did this Extreme Reset routine, then when I replaced the batteries, used the normal Find Device in the Bluetooth window, turned on the mouse switch, and then clicked the other (Locate) button, only then did I see the red/green flashing LEDs.  It then found a generic Bluetooth mouse, and proceeding with install made it pair up correctly with a MS5000, just like the very first time.  No problems since!  
    Monday, January 03, 2011 2:05 AM
  • You're right, BillCal, that works!

     

    MY problem is the following: I use the Bluetooth-Mouse on 2 systems (Vista and Win7, dual-boot).

    When I switch between the 2 systems, the mouse is just working on one system. I think, the mouse uses a special ID to be connected to one of the two systems. When I switch to the other system, the mouse needs to be reseted in the way you discribed above to get a new ID.

    As I switch very often, this procedure is to much ;)

    Does anybody know a way to connect the mouse to both systems?

    I don't think it's possible....

     

    Thx

    Patrick, Cologne

    Monday, January 03, 2011 9:40 AM
  • This is the most useful answer.  The key point here is that you have to see the led on the top of the mouse flashing red/green when you press the Bluetotth button on the bottom of the mouse - otherwise you get the error message.

    I tried all the previous recommended steps

    • pulling the battery and reinstalling
    • pulling the battery, leaving for a while and reinstalling

    and neither of these worked and I didn't get the red/green light and I got the error message

    I then did the following

    • pulled the battery
    • switched mouse and off several times
    • with the mouse switched on,  pushed the Bluetooth button and rolled the scroll button
    • left mouse for 5 minutes
    • put new, fresh batteries back with mouse switched off
    • switch on the mouse
    • I immediately got the message saying a Bluetooth device was trying to connect (led on mouse was green)
    • selected this option and tried to connect - got the same error
    • opened the Bluetooth Add Device panel and clicked Add Device
    • pressed the connect button on the mouse - nothing happened
    • pressed and held the connect button on the mouse - got the red/green flashing light
    • mouse appeared in list of visible devices
    • clicked on the mouse
    • it connected!!!  (without asking for pin no)
    • after device drivers were installed, it worked!!!!!

    So which of

    • doing the 'extreme reset'
    • fitting new batteries
    • pressing and holding the Bluetooh button until the red/green light flashes

    fixed the problem, I don't know but one of these did.

    Hope this helps

    PS:   I would just make the observation that this is pretty poor work by Microsoft.  Why does the mouse get into this state where it still appears to be working but cannot pair with the computer?   And why can't the Microsoft Bluetooth software recognise that the mouse has got itself into this state and handle the error properly and give some decent information that allows the average user to fix the problem.   Zero out of 10 on this one I think.

    Thursday, January 20, 2011 7:51 PM
  • Richard:

    Given that the pairing instructions shipped with the mouse, (essentially the only thing they tell you is required...), is to press the connect button until the LED flashes in alternate red-green, I'd say your post is a bit of blowhard-izm.  Wouldn't you agree?

    And you want to rally on about poor code from Microsoft?  Complaining that they didn't write a driver or mouse firmware that would handle people not following instructions?

    How about a post where you tried all of these various things because of an ingrained "Microsoft must be at fault" mindset, but you were pleasently surprized and humbled to find out that merely following the instructions got things working as they should?

    So, who deserves that Zero out of 10 you mentioned?  Oh, I know, ME because I took the time to challenge your assertions.  I'm OK with that, but people need to realize dignity is tied to always doing the right thing, and in this case, the right thing is to admit you simply had to follow directions to get your mouse working.

    Its not about what other people think, how do YOU feel about berating anything and everything BESIDES YOURSELF?

    Why did I post?  Because your post hit a nerve.  It pretty much encapsulates one of the most consistent, most prevalent major flaws in society worldwide today.  Blame someone else, shake off personal culpability at all costs.

    Have a super wonderful day.

    DAS

    Friday, January 21, 2011 12:53 PM
  • Win7Tester:

    You know what? I have been a champion and defender of Microsoft for years. I actually like the company's work, I have at various times owned the stock, and I find myself pulling for them consistently - even in their darkest moments, such as having to abandon the rewrite of the Win codebase and start from scratch.

    But you know why I'm here?

    Because I'm having the same problem with this mouse as the other posters here. I installed Windows 7 and then found I had to go out of my way to get Bluetooth set up on the machine. Then, after some fiddling with little feedback from either the OS or the mouse, I managed to get the mouse paired.

    Then I installed Ubuntu on that machine, and what do you know? Ubuntu set up bluetooth automatically. Then, Ubuntu told me my mouse was looking to connect. I put in the code, and I was done. No fiddling with buttons or batteries.

    Then I come back into 7, and what do you know? "Adding the device failed resulting in an unknown error. The reported error code is: 0x8007048f. Contact your manufacturer for assistance."

    And so I search on that message, find this page, find people discussing the various manipulations required to get mouse to work, and there at the end is your snide, insulting message to Richard.

    Here's the bottom line:

    1) Microsoft Windows 7 and Microsoft Bluetooth Notebook Mouse 5000 stumble all over each other trying to negotiate a connection.

    2) Ubuntu had no problem whatsoever, and it cost me precisely nothing.

    3) Some percentage of the Microsoft community takes the haughty, sanctimonious attitude you evidence.

    4) Microsoft is in big, fat, trouble.

    Sorry Richard's post rubbed you the wrong way. Yours rubbed me just as wrong. I'm rather sick of people getting all huffy in the face of reality. The reality here is that Microsoft ought to be able to manage better than this, and the best thing that can happen is for people to call them out on it - particularly when they are surrounded by excuse-makers and rationalizers like yourself.

    I don't care what kind of day you have, sir. Put a check on your attitude.

    Thursday, January 27, 2011 6:14 AM
  • <SARCASM>

    I guess you are right, it IS a whole lot of extra work to follow directions and press a button provided for expressed purpose.

    :)

    LOL

    So, are you saying that you had to do something more than follow the directions and press the link button?  I had to do exactly the same thing to "pair" my Logitech wireless keyboard and mouse, it never once occured to me that I should have been upset that I had to follow directions to get something working. 

    You've educated me for sure, I now know I've been wasting my time reading, when I could have hooked it up, then spent hours searching for a fix, when 9 times out of ten the "fix" is to follow those lowly instructions I now know I'm too smart to follow. 

    </SARCASM>

    DAS

    Thursday, January 27, 2011 3:24 PM
  • I don't know who you are responding to, given how totally irrelevant your commentary seems to be. I'll assume you were arguing against the voice in your head that you imagine is continually assaulting Microsoft unfairly. You keep on with that. It will serve you well.

    For other readers, for the sake of clarity, I should have been more clear. Pressing the button in a fashion consistent with the instructions did NOT result in a paired mouse. Following the instructions again didn't remedy the situation.

    But installing Ubuntu resulting in a paired mouse right off the bat.

    The point is so simple I assumed Win7Tester would get it --> Microsoft is in charge of their OS. Microsoft is in charge of their mouse. Microsoft is in charge of the drivers between the two. Ubuntu is in charge of precisely nothing.

    And yet ... it was Ubuntu that worked correctly. Anyone who cares about Microsoft sees a problem here.

    Friday, January 28, 2011 8:00 AM
  • Miranda:

    You were not clear in your first post, it took you a while to "clarify" that the button did not acheive the pairing.  I'll give the the benefit of the doubt and assume that's the truth, but I have a question for you:

    Where is this "high road" you sought to establish in your first reply AT ME (as opposed TO me, (a not so subtle difference))???

    You came in like a knight in shining armor telling me to keep my attitude in check, presumably to set an example of professional discourse in typewritten communication.

    But I see that was a smokescreen,  you got your knickers in a knot, and so now the premise of "attitude" is no longer in play, its become something more.

    Let me break the mold and see if you follow suit.  I apologize for the sarcasm.  You simply weren't clear in your first post, from what I was able to gather from the words you typed, it could have very well been that pressing the button solved your issue. 

    Let me explain my first experience with Ubuntu on a workmate's laptop.  On the way to a a client site, he decided he hadn't had his mornings dose of caffeine, so we stopped at Starbucks to spend far too much money on some really good coffee.  He carried in his personal laptop, and proceeded to boot it up while we were waiting for his mocca-blah blah.  As the machine booted, he was presented with a series of prompts about all of these "new connections" he could choose to connect to or not.  Looking around the seating area, there were 6 or 7 other laptops in use, and as you probably guessed by now, had 7 or 8 prompts to dismiss.  He only wanted one connection, to the Starbucks router of course, so what was he dismissing?  Connections to other laptops BT radios.

    Same Starbucks, 3 days later (Saturday) my Win7 laptop.  About 11 other customers with laptops this time.  No prompts to dismiss.  I knew I wanted to connect to a network, so I did what I knew had to be done, clicked on the wireless tray icon, found the correct network, connected, checked email, logged off, shutdown the machine. 

    I think MS made the connections a bit less automatic because they know their users could very well be complete newbies, and might answer yes to every connection request in their desire to get online.  An Ubuntu user?  Very much more likely WAY beyond the "appliance operator" type user, can handle a few prompts knowing that words mean things and the goal is not to click everything that has an {OK} in it.

    Have a good day, I promise to do the same.

    DAS

    Friday, January 28, 2011 12:58 PM
  • I hear you, Tester. I get the point. Yes, I got my "knickers in a knot". But look back at your post. Your response to Richard that was WAY over the top and uncalled for. The guy was having a problem with his mouse pairing (as was I). He may even have been following the directions (as was I).

    And then you showed up to drive the bum into the ground. Not only did you grab him by the back of the head and scream RTFM in his ear, you then proceeded to call his entire character into question (avoidance of personal responsibility) and ensured that he knew good and well that his personal, fundamental character flaw was a signficiant contribution to the decay of society in general.

    Come on, man. Think about what you accused him of, and then consult a mirror. Don't spend your time defending yourself against me - take a smaller moment and apologize to Richard.

    Friday, January 28, 2011 6:58 PM
  • Miranda:

    Not going to happen, because Richard went off on a bent all his own, and ended with not knowing if following the instructions solved his problem or not.

    Don't worry though, I had no misconceptions about you backing off either, you came in with cape unfurelled, and now you will sit back and be "ride the high road" in your own mind, while continuing to drive with your rims in the mud (where you've place me).  Presumably, Richard might be capable of defending himself, he sure lit into MS, only he can know whether he tried the instructions first, or last. 

    No surprize, don't sweat it.

    DAS

    Friday, January 28, 2011 7:32 PM
  • Hi Miranda

    Your latest post was removed.

    Abusing other forum members and using foul language is a violation of the  Community Code of Conduct  for these forums.

    Any further violations will put you at risk of being banned from all Microsoft online properties.

    Regards,


    Ronnie Vernon MVP – Windows Desktop Experience
    Friday, January 28, 2011 11:36 PM
    Moderator
  • Thanks a lot BillCal,

    Finally I managed to get my mouse to connect. I had not been taking in account the capacitance that is built in this mouse! Afte I went through this 'Extreme Reset' routine as you proposed, and asked my winodws 7 /64 pc to discover new bluetooth devices, it finally offered me the choice to proceed without password, and connected! (please, note that i only succeeded after the light was blinking green / red when the button underneath was pressed)

    Thanks again!

    Sunday, August 14, 2011 2:21 PM
  • thanks a lot !

    i worked for me !

    Friday, February 17, 2012 9:00 AM
  • hi, i think you have to choose pair with out code, for a mouse you don't need a code. Aslo maybe you have to do some changes to you computer, see more information here http://varudanik123.blogspot.com/2012/03/is-virtual-reality-good-place-for.html
    Saturday, April 07, 2012 9:18 PM