Choose the Scope of Random Wi-Fi Hardware Addresses in Windows
Windows can use random hardware addresses to make device tracking through Wi-Fi hardware identifiers harder. The useful decision is which networks should use that behaviour, particularly on a laptop that moves between public Wi-Fi and a managed workplace.
Start by identifying the network you intend to change. A household network, visitor network and workplace connection may have different enrolment requirements even if all three provide internet access.
Choose the setting’s scope
On supported Wi-Fi hardware, Windows 11 offers Random hardware addresses under Settings, Network & internet, Wi-Fi. That control covers network scanning and connections generally.
For one saved network, open Wi-Fi, Manage known networks, select its entry and enable Random hardware addresses there. Microsoft says the network-specific setting applies the next time you connect to that network.
Record which control you changed and its previous value. A note saying only “privacy enabled” will not tell you whether you changed every connection or one particular saved entry.
For a network administered by someone else, check its registration requirements before making the change. If the administrator identifies approved equipment by its hardware address, ask how this setting should be handled. Do not use address changes to work around access restrictions.
Test the next connection deliberately
Finish any transfer before disconnecting. Reconnect to the intended network and test the service you need, such as the normal sign-in page and an authorised work resource. Record the exact failure if a previously working service becomes unavailable.
If the change causes a problem, restore the recorded network-specific setting and consult the administrator with the network name and timing. Avoid repeatedly changing several network options while trying to interpret one result.
Treat the setting as one privacy control with a defined scope. It does not justify ignoring the network owner, sharing private credentials or assuming that all activity is anonymous. The accepted result is a deliberate setting on the intended network with the required connection still working.