On Bluetooth-supported controllers, the plastic around the Xbox button is part of the face of the controller. On controllers without Bluetooth, the plastic around the Xbox button is part of the top, where the bumpers are.
When you connect an Xbox Wireless Controller to your Windows 8.1 or Windows 7 PC with a micro-USB cable, Windows will automatically download and install the drivers for the controller. If Windows is not set to automatically download device software, you can check for updates through Device Manager. “The driver detected a controller error on Device Harddisk1 D.” - posted in Internal Hardware: I have a machine built 5/23/2008, running Windows XP Home. The driver detected a controller error on Device Harddisk1 D.” - posted in. On our systems since it became available for download/install. Dec 14, 2017 - The driver detected a controller error on Device Harddisk2 DR2. And he burned them fine with a fresh download/install of cdburnerxp.
Notes
Bluetooth requires a PC running the Windows 10 Anniversary Update. See Windows Update: FAQ to learn how to get the latest Windows update.
For best performance, update your controller. See How to update your Xbox One Controller on Windows 10.
Bluetooth is supported on PCs, tablets, and laptops. It is not supported on mobile devices.
Bluetooth does not support any attachments, such as headsets, chatpads, or the Xbox Stereo Adapter.
We recommend connecting only one controller at a time using Bluetooth.
Follow these steps to pair your controller to your PC using Bluetooth:
Network Controller Device Driver
Make sure you have updated your PC to the Windows 10 Anniversary Update. See Windows Update: FAQ to learn how to get the latest Windows update.
For best performance, update your controller. See How to update your Xbox One Controller on Windows 10.
Turn on your Xbox Wireless Controller by pressing the Xbox button.
Press the controller Connect button for three seconds and release.
I have a machine built 5/23/2008, running Windows XP Home. It was supposed to take away all of my PC-related problems. It has ended up costing me a lot of time and stress. I have, unfortunately, lost some faith in the store that built and sold me the machine. If Windows 7 was out I would use the case (below) and start from scratch. Posting my problem on a few forums is my last resort…and something I wish I had done sooner. Please let me know what you think! I appreciate any responses. I want to be brief, but am going to end up leaning toward TMI... (Too Much Information) …after reading a few posts here. The system configuration originally included: • AMD® Athlon 64™ X2 4400+ Socket AM2 CPU • 2 GB PC2-6400 800 MHz DDR2 Memory • Seagate 80GB 7200RPM SATA-II Hard Drive (C drive) • Seagate 250GB 7200RPM SATA-II Hard Drive (F drive) • 1.44 Sony Floppy Drive • MSI NF6P-VSTA nVidia GeForce 6150SE Socket AM2 Mainboard • Antec NSK4480 case, (380W Power Supply) I asked the store to install “my” copy of XP Home (I had bought XP there originally, 1/10/03) and to install two used DVD drives, a Memorex 20x Multi Format DVD Recorder manufactured 11/07 and a TDK indiDVD recordable DVD/CD drive manufactured 11/03, during the build. I gave hardware manuals for both DVD drives to them, and knew one would need to be designated master, but that was never brought up during the process. I never asked. The system is used primarily for benign web surfing, e-mail, ripping music, and playing with photo and video software, like Nero and Roxio. The case is kept clean, inside, and the discs are cleaned and defragmented regularly. Less than 2 months later, I went to open or attach a file from the F drive (the 250GB “storage” drive) and the drive was “gone.” Not visible in Explorer. I looked at the event log, and found repeated pairs of disk error (26), followed by disk error (51): “Windows - delayed write failed : windows was unable to save all off the data for the file F:$mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.” “An error was detected on device DeviceHarddisk0D during a paging operation.” I took the machine in for troubleshooting…they (the builders) could not reproduce the error, but noted the system log and replaced the F drive under warranty.
One month later the same errors reappeared and they decided to replace the mainboard under warranty. Less than one month later the same errors re-appeared, I let them hang onto the machine for a full week, asked them to please determine the cause of the problem, and a third (“upgraded”) mainboard was installed…now I have an MSI K9N2GM-FD nVidia GeForce 8200 Socket AM2+ Micro ATX Motherboard #MS-7508-010. When I got the machine home, I ran Windows XP Service Pack 3. The issue went away, seemingly to never return. Unfortunately, I was never able to determine what the cause of the disappearing F drive was. Did the new motherboard “fix” the problem…or did Service Pack 3? At this point, I doubt if this “old” issue is related to my current problem…but there are some notably similar things going on. That is why I included the information directly above. 8 months passed. This May, everything froze up. I had a web browser open and an e-mail application, and was using Nero to create a DVD from videos I took on my Canon camera, something I do all the time. The system log shows a disk error (11), followed by an ATAPI error (15):
Download Controller Driver For Device Harddisk2 Dr2 3
“The driver detected a controller error on DeviceHarddisk1D.”
Device Harddisk2 Dr2 Identify
“The device, DeviceIdeIdePort3, is not ready for access yet.” I returned to the store that built the machine. ORTHOS stress test was run…chkdsk…etc. I was told I could use a larger C drive and that the issue was likely not that but related to one of my “outside” components, specifically one of the DVD drives, because of the “ATAPI” error. I was easily talked into a new C drive…which is now a Seagate 320GB 7200 RPM SATA II Hard Drive. I was advised to disable one and then the other DVD drive(s) if the issue returned. Which it did, with a vengeance.
Device Harddisk3 Dr3 Error
I removed both DVD drives. Of course the problem remained. I plugged the machine into a different circuit in my home. Fifteen minutes later, everything froze up. Here is how things are “working,” currently: I start the PC. Depending upon its status when it was shut down, it either starts effortlessly or does not. Meaning if there were disc and ATAPI errors showing when it was last shut down, it generally shows the mainboard/bios screen, then the windows “knight rider” screen, then a black screen indefinitely…and I do mean indefinitely. Eventually I manually shut down and try again. And usually on about the fifth try I get through to the “welcome” screen, which means I will get to the desktop and have some time to use the machine. This startup process can easily take over an hour. I then open the system log and watch it closely…if I walk away from the machine, I make sure to close all apps but the log, and when I return I refresh it to check for errors…it there are errors or if I do a periodic check while using the machine and find errors, I need to immediately save and close all apps, which may or may not work…and shut down. I am constantly checking it as I type this. Sometimes the machine will operate with no errors for 8 hours. Sometimes for days. If no disc errors are occurring when I shut down, it restarts without any problems. Sometimes it will start having problems immediately after startup. I cannot link it to any application…or process…in fact it may or may not occur when the PC is sitting idle. It is truly random. The log does seem to show a pair of service control manager information events, #7036, “The Google Software Updater service entered the stopped state,” and “The Computer Browser service entered the stopped state,” just prior to the disc errors, every time. I cannot help but think may be related.
Device Harddisk1 Dr3
Any ideas? Thanks for reading. Sorry for the length. I attempted to attach a Windows MPSR “cab” file, for your enjoyment, but it was not allowed.