Microsoft Mouse and Keyboard Center doesn't recognize Sculpt Comfort Keyboard (Windows 8.1 x64)

Anonymous
2013-10-26T18:58:25+00:00

I've recently upgraded my computer, bought Microsoft Sculpt Comfort Keyboard and installed Windows 8.1 x64.

I also installed Microsoft Mouse and Keyboard Center v.2.2, that's offered on the Microsoft Hardware website.

The keyboard works like a charm, but Mouse and Keyboard Center doesn't recognize it.

There's a driver for keyboard in device manager called "Microsoft USB Dual Receiver Wireless Keyboard (Mouse and Keyboard Center)", and there's also a mouse driver called "Microsoft USB Dual Receiver Wireless Mouse (Mouse and Keyboard Center)", though I don't have any wireless mice. There are also two devices under HID devices group, "Microsoft hardware - USB-keyboard" and "Microsoft hardware - USB-mouse". Disabling those mouse drivers doesn't help.

What's wrong and how can I make Mouse and Keyboard Center see my Sculpt Comfort Keyboard?

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

63 answers

Sort by: Newest
  1. Anonymous
    2013-12-29T17:23:36+00:00

    I just bought this keyboard and have the same problem.  There is no such thing as version 2.3.  The keyboard works fine, so I'll live with it, and maybe one day MS will decide to support it.

    It never will get supported if people experiencing such problems don't start posting their hardware information and detailed specs, along with screenshots of what is getting displayed in Device Manager and Microsoft Mouse and Keyboard Center.  Before programmers can fix something they need to see what that something is doing.

    They aren't seeing the problem.  I'm not seeing the problem.  No one I actually know is experiencing the problem, including those who actually own the same hardware.  But, if no one who actually is experiencing the problem posts helpful information to help track down the problem and the cause, programmers tend to think that such problems don't exist.

    Please help become part of the solution.  Post your information today.  Thanks for your time.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-12-29T01:32:22+00:00

    I just bought this keyboard and have the same problem.  There is no such thing as version 2.3.  The keyboard works fine, so I'll live with it, and maybe one day MS will decide to support it.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2013-11-24T06:35:51+00:00

    I took it from Microsoft Hardware website. It was available there at the moment. I'm not a newbie, btw.

    Now, I've bought Sculpt Comfort Mouse Bluetooth, and it is successfully recognized by Microsoft Mouse and Keyboard Center. But the keyboard still isn't recognized.

    You did not post your hardware specs and computer make and model so I assumed that you were.  Sorry I made that assumption.

    I have tried to download a 2.3 version from every link on the hardware website and cannot even see a download link for a 2.3 version.  The latest I see on any page is 2.2.  Please post a direct link to the page where you have found this 2.3 version.

    Also, please post a screenshot of Device Manager showing all your keyboard and mouse devices.

    Also, please post a screenshot of Microsoft Mouse and Keyboard Center and what it is displaying for your mouse and also for your keyboard.

    Thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-11-23T18:45:03+00:00

    I took it from Microsoft Hardware website. It was available there at the moment. I'm not a newbie, btw.

    Now, I've bought Sculpt Comfort Mouse Bluetooth, and it is successfully recognized by Microsoft Mouse and Keyboard Center. But the keyboard still isn't recognized.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-11-11T05:56:28+00:00

    Where did you get the 2.3 version of the software? Softonic or some other related website other than Microsoft? If so, you should never have run that file on your system.  You likely will come to regret it.

    On another note, where do you have the USB wireless device plugged in? Back of computer in default USB ports? On a USB 3.0 riser card? Front of computer? In a USB hub that is then plugged into a USB port on the computer?

    Some computers require the USB device to be plugged into either one of the first two ports nearest the network adapter on the back of the computer.  Some require the USB device to be plugged directly into the built-in USB ports and not on a riser card.  If you have it on an Intel-based riser card, you must have the proper driver installed for the card and then that driver must load first before the keyboard driver can work.  Most of the time that will not work properly.  If the USB hub into which you plugged in the device is not itself plugged into one of the first two USB ports, you must first do so or it may not work correctly to identify your device.

    Also, check to make sure that legacy mode is disabled in the BIOS.  Also make sure that the port you have plugged the USB device into is USB 2.0 capable.

    Before you do anything else, however, you should scan your computer for malware with a deep and advanced scan.  It is possible you installed some malware or a rootkit onto your computer using that 2.3 file you found.

    You also should remove that software and reinstall the 2.2 version software from the official Microsoft site.  Make sure it is the correct version for your OS.  If you have 32-bit Windows 8.1, you must install the 32-bit version.  If you have 64-bit Windows 8.1, you must install the 64-bit version of Microsoft Mouse and Keyboard Center.

    Can you provide more details as to your computer's make and model, and what your situation is regarding where you have plugged in the device?

    Was this answer helpful?

    0 comments No comments