2.0.0.64 is a really bad un to be using... You can't alter the power from 100mw (20dbm), even in XP where you can change it around to 40mw using ACU it does nothing. The Atheros firmware is hard locked to 20dbm and is aggressive against any form of tampering with the output, and if so will limit the output power. Besides no eeprom utilities exist to edit the AR9721 to get around that restriction. Only options are higher gain antenna's or a booster inline. NHA has inside an external amp (Skyworks 2576L) which is capable of +26dbm in g/n (OFDM), and 29dbm in 11b (CCK). That's all you need to know. I wouldn't pay much attention to what that util says on output power as alfa put an external amp anyway. As for the drivers where "your internet stops working", is actually a random usb shutdown problem that plagues the Windows 7 drivers, it's not your hardware as TP-Link WN722N (AR9271) does exactly the same thing. All Windows 7 drivers are affected, and some are worse than others, use the vista or xp ones of which I already posted a full pack for. As the Windows 7 Atheros drivers (especially more so when combined with 64-bit) they be broke and randomly decide to disappear from working to not requiring a re-plug... The same adapter with the XP drivers however runs for hours and hours, days and months without a blip.
They're both bugged, infact the Windows 7 specific ones are all bugged (on 64-bit at least) as far back as I tested to 2.0.0.26 on x64 and will shutdown the device into an unknown USB device status and all your connections disappear on the tray icon ranging from hours to days requiring a re-plug. Note also that playing intense online gaming, or having too many peers connected in torrents will also trigger the AR9271 to shut down. The Windows 7 versions can be a little jumpy on the RSSI too and lag around a lot. It's obvious to me that Atheros and 64-bit clearly don't mix very well. No such problems under Windows XP. It's not a heat related issue, nor a hardware/cabling issue as the Windows XP drivers don't suffer the same fate. I haven't tested the Vista drivers on Windows 7 fully 100% say that they do or don't manifest the same bug, but I did get a few random blue screens using them under Windows 7 which is much worse than just re-plugging the device using the Windows 7 native ones. *Note Using the Windows XP drivers forced onto Windows 7 isn't an exact 100% solution in itself either, as apparently you lose access in 802.11N mode and everything connects at 11g or 11b instead. Only real solution is to use the Windows XP drivers on Windows XP itself. You can't pull these tricks on Windows 8/8.1 as the backwards compatibility support for NDIS 5.1 drivers were removed. When Qualcomm released new drivers for Windows 8/8.1 they should have released them for the older OS's as well, because as things stand these issues look likely now they won't be fixed, and while the drivers still work for the most part, they have numerous bugs like lag, RSSI jumping around, positive RSSI values, and not following the same behaviour as Windows XP ones.
hmm i wanna change nha with nhr or h. what do you think about nhr and h ? which one better and fully compatible with windows 7 ? and kali linux or xiaopan os for wifi pen tests
Hi Mr kevsamiga could you plz give link to Atheros Client Utility thats work with Windows XP driver 7.7.0.105
@ kevsamiga is this booster is good or not?i have 036nha but have poor signal. http://www.alfa.com.tw/products_show.php?pc=126&ps=168
http://download.ecsusa.com/dlfileecs/driver/mb/wlan/wlan_4.3I_Atheros.zip (82.3Mb) Contains the 7.7.0.105 driver and the utility combined. *note Start the setup from the Win8 folder not the Win7XP folder which is only 7.7.0.104. --- Double Post Merged, 10 Apr 2015, Original Post Date: 10 Apr 2015 --- I don't own it, therefore have no experience on it.
Kevsamiga, is there other stable driver for win7 64? I've used the XP 64 driver, I was unable to connect to (using mac address) for WirelessMon software, can connect with other drivers but very unstable. I need to connect to a specific access point under ESSID. Thanks in advance.
So just to be clear on the above, Windows 10 itself doesn't contain a native AR9271 driver or ? And we must use the Windows 8.1 ones to get it to work ?!? I also discovered recently that in very high humidity conditions where connections are not always possible with others, the 036NHA still kicks the ass of all the other ALFA's and has the advantage in humid environments. (Although 5Ghz wifi sidesteps the "water" content in the air and on the ground absorbing the signal problem in any case) * Not to say I haven't given Windows 10 x64 a go btw because I have (for 1 day), but I still didn't like the bastardised travel kiosk OS, wifi was buggy and kept disabling/dissappearing and I immediately downgraded back to Windows 7 x64 once I realised it's a bandwidth hog with privacy issues to boot. Yes it may be free, but no thanks anyway. I don't like where it's heading because sooner or later they will start charging for the "services" that used to be free. Paying for solitaire and DVD playing removed after the free upgrade period ffs. Not for me. Not in this life. * Incidentally if you own an ALFA 036NHA and plan to use it on Windows 10, then the correct driver that you should be looking at for Windows 10 is indeed the 10.0.0.28 driver for Windows 8.1 via manual install. * Furthermore, the AWiC Atheros diagnostic utility I uploaded in a previous post at the start of the thread, has been tested personally to work under Windows 10 and display statistics for the connection when used in conjunction with the 10.0.0.28 driver under Win10 x64. Later versions of AWiC extracted and tested are hit and miss and mostly don't work throwing an exception. So to be clear.... Windows 8 = 10.0.0.25 Windows 8.1 = 10.0.0.28 Windows 10 = 10.0.0.28 Are the final correct (non beta) drivers to use for AR9271 on modern OS variants. * The driver Windows 10 installs as default if your 036NHA is plugged in when installing is 2.0.0.64 which is the Windows 7 driver, has the disconnection/shutdown bug, and is incompatible with AWiC.
Hi, I'm running Windows 10 x64 with a TP-Link WN722N and by default Windows installs 2.0.0.32. Using Connectify I find after a few minutes I lose internet access on client devices while connected to the WN722N hotspot. The SSID is still broadcasted by the host and clients are still connected, but no data is exchanged. I realised it was due to the WN722N going into a sleep state, since restarting Connectify did nothing--only unplugging the WN722N physically and replugging it. And then it would only work for awhile before I would have to do it again. So I installed the latest TP-Link drivers for Windows 8.1 x64 (no 10 version available) and after a few minutes of high output streaming from the client devices (Youtube HD, etc), the host computer BSODs with (DRIVER_IRQL_NOT_LESS_OR_EQUAL) and fwpkclnt.sys as the cause. I rebooted but it BSOD'ed again with (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) and athuwbx.sys as the cause. So then I found this thread, and installed the recommended 10.0.0.28. But no luck. After a few minutes it BSOD'ed with (DRIVER_IRQL_NOT_LESS_OR_EQUAL) and msisadrv.sys as a cause. I'm using 10.0.0.20 now but I'm not holding my breath. Haven't tried putting it under load yet. I'm about at my wits end. Why are the BSODs all listing different causes when the only changes have been the Atheros drivers? Could it be compatibility issues with other network drivers? In addition to Connectify I'm also using Pulse Secure (formerly Junos Pulse) as it's required to obtain internet access on my local network. I've also had TunnelBear installed but not running during this ordeal. What should I try? Would 2.0.0.64 work better than .32? I don't mind lower transmission rates, so long as it stays up and doesn't cause the host to BSOD. EDIT: Just read the part where 2.x.x.xx are all bugged on 64-bit. What about the 9.x series from http://www.driverscape.com/download/atheros-ar9271-wireless-network-adapter ?
With my installation of Windows 10 Pro x64 and the 036NHA plugged in, Windows installs 2.0.0.64 instead by default not 2.0.0.32, how strange. I haven't encountered a single BSOD using 10.0.0.28 under Windows 10 x64 as yet. And I've been running this way for 2 weeks. Since I haven't any issues under 10.0.0.28 and Windows 10 x64 Pro, I didn't bother to test the others (10.0.0.23,10.0.0.25). 10.0.0.20 is a beta driver. But this is mostly on a single system alone however. Not clients connected to hotspot. There may (although I haven't checked) be an incompatibility with connectify and Atheros 9271, or just an incompatibility with connectify and Windows 10 in general. As an alternative to aid diagnosis, or you may even prefer to switch to using this app instead, give this excellent tiny portable program written by Cedric Poottaren (totally free of crapware or ads) called Wi-Host a try, which does the same as connectify does (manage the Virtual Wifi) to troubleshoot any potential compatibility issues. http://www.askvg.com/wi-host-freewa...wi-fi-host-spot-to-share-internet-connection/ (I have personally tested this Wi-Host software under Windows 10 x64 Pro and AR9271, qualify it as having no malicious nastiness or ads inside, and can verify that it works in combination with Win10 x64 pro, the AR9271, and driver 10.0.0.28 without error) If the errors still occur in that combination, then you need to be looking elsewhere like memtest86+, cycled overnight on block test #5 for bad ram. *EDIT I just found this post on another forum with similar conditions as your own and highlighted what was interesting : archives March 25, 2015 "OK , maybe I owe Qualcomm an apology: just tried a REALTEK device and it took less than a minute to pop a BSOD referring to REALTEK driver rtwlanu.sys (DRIVER_IRQ_NOT_LESS_OR_EQUAL). So, my problem is BDOS's in win 8.1 with every usb wifi device used involving both Qualcomm and REALTEK kit. Qualcomm kit results in BSOD DRIVER_IRQ_NOT_LESS_OR_EQUAL, athuwbx.sys; and, REALTEK results in BSOD DRIVER_IRQ_NOT_LESS_OR_EQUAL, rtwlanu.sys. I'm using usb wifi to share a connection (wifi hotspot) rather than to connect. i'm using an app called Connectify to do this, but as far as i know, it works and is well regarded. Everything is up to date." Source : http://tqaforum.net/discussion/240189/qualcomm-atheros-athuwbx-sys-and-bsods-in-win-8-1/p1 So It looks like connectify hotspot is the common denominator...
Thanks for the response! I got 10.0.0.20 (for Windows 8) to work without BSODs, but the connection for clients dropped after awhile too. I updated to 10.0.0.28 and uninstalled Connectify to troubleshoot, as you suggested. However I could not get Wi-Host to work. I got the hotspot up, and ICS enabled. On my clients Dropbox and Skype would connect, but web browsers would stall on 'resolving host', it looks like anything requiring a DNS doesn't seem to work when I use the Wi-Host method.. Perhaps this is because I'm trying to share a Pulse Secure VPN internet connection? In any case the BSOD only happens with high traffic load, and since I couldn't get DNS to function with Wi-Host I couldn't test it.. I'm going to try 10.0.0.25 now with Connectify in the hopes that its more stable than .20 and less bluescreeny than .28 e: saw the post that the TP-Link drivers are .25, and since that was the first driver to bluescreen it I'm going to try .23. In any case, if all of this doesn't work, what would be the most stable, bug-free chipset for Windows 10 x64 use? --- Double Post Merged, 17 Aug 2015, Original Post Date: 17 Aug 2015 --- So far 10.0.0.23 seems to be working. I noticed one thing though. Using device manager > update driver software to install different versions seems to keep the old drivers around. I could not install .23 over .28 because the latter is newer, so I went into properties > driver > uninstall (incl. software). After that I realised it had dropped back to .20 (the last installed version), and after uninstalling that it dropped back to 2.0.0.32 (the default Windows driver). Could my problems have been from installing .28 without uninstalling all other versions first?
They shouldn't conflict, but you should always tick the remove checkbox when uninstalling, otherwise you end up with loads of drivers in the file repository and you have to keep uninstalling them all to get UB91 bare device bk in device manager. I do believe it's a general compatibility issue with Win10+connectify. Right now the most appropriate for Windows 10 x64 in my book would have to qualify as 8812au 8188eu with 1029.xx + driver as these are the first drivers I found that fully supports the Windows 10 WDI architecture. Atheros and the Windows 8/8.1 drivers nor Ralink currently support the new Windows 10 WDI. They work as is, but you won't get the complete features of WDI.
I've been using the 10.0.0.28 and .23 drivers for my windows 10 x64 setup for a few days. I use it with ICS to share my university Enterprise wifi to my router because my building is in between ISPs. Long story short. The speeds were not good and i had bsod every 30 min (BAD_POOL_HEADER (or somthing)). It seems some of you are having OK experiences with the win 10 drivers. Maybe it the WPA enterpise thats killing it for me... Decided to use an old laptop to do the work instead. Running win ultimate 32 and using the 2.0.0.32 default drivers. The speed is now 4 times faster and i did't even have to change the driver... I was close to trying with linux, but now i see no point. Just hope my 8 year old laptop won't catch fire from all the dust its been collecting. Thanks for all the help so far kevsamiga. This is really the place to be regarding win drivers for AR9271.
There are too much bastards around I've ever known M$ own the half or the world (better one), but never known the M$ is owner of Atheros, Qualcomm, my WLAN adapter. Now I wouldn't be surprised if they will claim ownership on my pocket, my dog, my wife and me myself. Die moneyright bastards, please.
