Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский)
Español - Latinoamérica (латиноам. испанский)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский)
Português-Brasil (бразильский португальский)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
https://www.catalog.update.microsoft.com/Search.aspx?q=xbox%20one
Yes there will be forums with people saying their adapter works fine on windows 7 and that is because they have an older adapter, the new adapter is windows 10 only.
No, the 360 usb wireless adapter can not work with XBO controllers.
To get the wireless to work I installed all the optional updates that windows update had queued up since they weren't set to automatically install. Then windows said the driver wasn't signed, so I followed the steps here:
https://www.techspot.com/community/topics/how-to-install-use-unsigned-drivers-in-windows-vista-7-x64.127187/
in order to get windows to use the drivers shown in this pic:
http://s33.postimg.org/qxboizo6n/un3.png
Wireless on Windows 7 works great now.
https://www.catalog.update.microsoft.com/Search.aspx?q=xbox%20one
and manually change to that in device manager; very simple.
Hey Enoch,
I too can confirm I have the Xbox One Wireless Controller working wirelessly on Win7-x64.
I'm using the "Xbox Wireless Adapter for Windows 10"
The problem is I can't get audio through the on-board audio jack on the controller.
Are you getting audio?
I can get audio when testing on a Win10 machine.
My Xbox Wireless Adapter For Windows device is under Network Adapters.
Driver Provider: Microsoft
Driver Date: 1/1/2015
Driver Version: 6.3.9600.16384
It includes three driver files with unknown providers:
FW_ACC_00U.bin
mt7612US.sys
xboxgip.sys
I have Win7 64 Bit SP1 (With platform update)
I was using Jolt's video in-order to play wireless with my Xbox One controller.
His method requires you to enable/disable windows testsigning so that you can use unsigned drivers.
However, recently I've started playing Fortnite and Pubg, both of which use BattleEye and Battleye will not run/launch these games while those settings are applied.
So anytime I wanna use my wireless controller to play games like Rocket League, I have to switch testsigning on/off and restart my computer, when I want to play Pubg or Fort, I have to switch it back and restart again.
That is getting really, really annoying.
I uninstalled all my controller drivers, deleted the unsigned ones. Followed the steps in this thread. Made sure windows updates were turned on, installed all optional updates, everything is up to date.
Restarted, plugged in my controller with no batteries, it auto-detected and downloaded drivers. Said everything is good to go. Works in game. Under device manager it shows up as Xbox Peripherals (Legacy)
When I unplug my controller and put the batteries in, and try turn it on wirelessly, it shows up under Human Interface Devices, they connect but it doesn't actually work in any of the games.
Any ideas on how to get it to work wirelessly? It's the whole reason I bought a wireless controller...I don't want to have to use it wired :(
Windows 7 ( 64bit )
I seriously hate windows and their stupid useless updates, always screwing things up for me
Same thing happened to me with an update last night, were you able to fix it?
aand same for me. it's good to know I'm not alone :)
Same....
I'm starting to think Microsoft is doing this on purpose to force people to "upgrade" to Windows 10. The driver for Windows 7 is no longer available from Microsoft, and this is the second time an update has broken my Xinput compatible HID device. Please let me know if you find a solution, as reinstalling the driver does not solve the problem.
The problem seems to be that the drivers are not digitally signed. Hasn't been an issue until now... but that's the way it is now, it seems.
What I did was to follow the instructions of the link Enoch Root posted above:
Just follow the steps of 'Solution number 2'.