Intel PROSet/Wireless Software

A wireless connection that drops in one corner of the house, or clings to a distant access point while a closer one sits idle, is almost never a fault. It is a setting, and the system’s own network interface does not expose the setting responsible. Intel PROSet/Wireless Software does, alongside the driver the adapter needs in the first place.

That combination is what the package actually is. A driver, plus a set of advanced adapter properties covering how eagerly the radio looks for a better connection, which frequency band it favours, how hard it transmits and what it does to save power.

Several of those settings will make things worse if you change them without knowing why. The useful ones are worth understanding, and this review is mostly about telling the two apart.

Driver first, tools optional

The installer offers a choice between the driver alone and the driver plus the management tooling, and most people should take the first option. The advanced settings described below live in the adapter’s properties and are available either way, so the extra tooling is aimed at organisations managing profiles and authentication rather than at somebody fixing a laptop.

One package covers a broad range of adapter models, provided the release supports the one you have, which is why a single download works across a mixed set of machines.

Identifying which release matches your hardware is the awkward first step, and Intel Driver & Support Assistant detects the adapter and points at the right build rather than leaving you to match model numbers by hand.

The same chip usually carries the Bluetooth radio, handled by Intel Wireless Bluetooth Driver as a separate package, and updating one without the other causes odd behaviour.

Roaming aggressiveness, the setting most people get backwards

This is the one setting in Intel PROSet/Wireless Software worth learning, because it explains a specific and maddening symptom. The value alters the signal strength threshold at which the adapter starts scanning for a better access point, and it arrives set to medium.

On a home network with a single access point, scanning achieves nothing and interrupts the connection while it happens, so the lowest setting is correct. On a large office or campus where you carry a laptop between floors, a higher value makes the adapter let go of a fading connection sooner and attach to something closer.

Setting it high on a single-router home is the classic mistake, producing exactly the stutter the user was trying to fix. Setting it low in a building full of access points produces the opposite complaint, a laptop clinging to one three rooms away.

Which situation you are in takes a moment to establish with a scanner showing the signal strength from every access point in range, and that measurement should come before any setting changes.

Band preference and transmit power

Intel PROSet/Wireless Software lets preferred band choose whether the adapter favours the lower frequency, one of the higher ones, or has no preference. The documented reason to use it is interference, since microwave ovens, cordless telephones and neighbouring equipment crowd the lower band while the higher ones stay clearer and travel less far through walls.

Modern routers already steer clients between bands, so forcing a preference here overrides a decision the network was making deliberately. Do it when you have measured a problem, not on principle. inSSIDer shows what the airspace around you actually looks like, including how crowded each channel is, which turns the decision into an informed one.

Transmit power is simpler than it appears. Medium is adequate for most situations, and the highest setting is for a long distance between the machine and the router. Raising it does not improve reception, since the adapter’s ability to hear the router is unaffected by how loudly it speaks.

Power saving, and the setting that can halve your throughput

Several Intel PROSet/Wireless Software properties trade a little performance for battery life. Interrupt moderation groups broadcast and multicast packets together to wake the processor less often. Discovery offload lets the adapter answer certain routine network requests on its own without bringing the machine out of sleep.

Both are sensible defaults on a laptop and both are worth switching off on a desktop that needs the lowest possible latency.

Then there is the throughput booster, which deserves its own warning. It is not a general accelerator, and users have reported their throughput halving after enabling it. The name promises what the setting does not deliver in most environments, and leaving it disabled suits almost everybody.

Pushing settings to more than one machine

For anyone managing a fleet, Intel PROSet/Wireless Software includes a configuration file that can be edited before deployment, so a chosen roaming value, band preference and authentication policy install unattended across every laptop rather than being set by hand on each one.

Two cautions belong with that. Machines from a laptop maker often carry a customised build of the driver, tuned for that hardware, and replacing it with the generic package occasionally changes behaviour in ways nobody expected. And not every property appears on every adapter, since availability depends on what the hardware supports, so a policy written for one model may silently do nothing on another.

For machines that move between networks with different addressing or proxy requirements, a profile switcher that changes network configuration in one click handles the part this package does not.

Conclusion

Intel PROSet/Wireless Software is the driver you need and a set of controls you mostly do not. The one valuable thing here is the roaming threshold, which explains and fixes both of the common wireless complaints, and band preference is useful once you have measured a reason to use it.

Approach the rest with suspicion. Nothing in the interface tells you which setting suits your situation, the throughput booster does the opposite of what its name suggests, and a laptop with a customised driver from its maker may not thank you for the generic replacement. Install the driver, measure your environment before changing anything, adjust roaming to match how many access points you actually have, and leave the remaining properties where you found them.