We would like to remind you that the best source for drivers is the Computer Manufacturer Support, the downloads available at Intel® Download Center are generic, and in some cases, the OEM's add customizations to the hardware and software that require their drivers.
For you convenience, please check the downloads available from Asus Support: https://www.asus.com/Notebooks/ROG-G73SW/HelpDesk_Download/
In most scenarios the Intel® Driver Update Utility will work to update the drivers properly, however, in some cases there may be some reporting issues; so, if you already installed a driver and the tool still reports an update is available, it is not necessary to update the driver again.
If you have any doubts, it is better to perform a manual installation of the driver.
The Intel® Centrino® Advanced-N + WiMAX 6250 has a regular WiFi component and a WiMAX component, each requires a different driver, this is the reason why you see an additional device. These are the locations for the current Windows® 7 drivers from Intel® Download Center:
Thanks for your help Jonathan, the link you provided to download the WiMax utility solved my problem and I was unable to locate it before. Regrettably ASUS did not provide a link to download this on their site. They had a mislabeled line item listed for WiMax drivers but it is actually just an installer for a WiMax tutorial and I was at a loss.
Could I trouble you for some help on this discussion that is similar in nature? It is related to USB 3.0 and the chipset drivers from ASUS did not seem to resolve the problem.
I am glad to know that our recommendations helped you resolve this issue.
Regarding the Chipset and USB question, doing a quick check in the Asus download page I provided before, there is a USB 3.0 driver that may help.
However, if this does not solve it, I would advise you to wait for the Chipset community to answer, or check with Asus support, since I am not familiar with this computer model.
I attempted to install the USB 3.0 driver before posting and it installed successfully. The problem appears to be that the device itself doesn't even show up in the device manager so that the drivers can be associated with it, which is what led me to the chipset drivers possibly being the issue. I'll add this info to my post in the other thread if it isn't there already, but thanks for the response.