I figured you may have just used the network reset from the Network & Internet cmdlet, and not the actual commands I mentioned.
If you have already tried the "netsh int ip reset" and "netsh winsock reset" commands and are still experiencing issues with your boyfriend's computer's internet connectivity, here are a few additional steps that you can try:
- Manually assign an IP address: You can try manually assigning an IP address to the computer's network adapter. Open the Network and Sharing Center in Windows and click on the "Change adapter settings" link. Right-click on the Wi-Fi adapter and choose "Properties", then select "Internet Protocol Version 4 (TCP/IPv4)" and click on "Properties". Choose "Use the following IP address" and enter an IP address that is within the same subnet as your router, but outside the range of addresses used by the router's DHCP server. An example of this might be setting an IP of 192.168.1.42 on a network where the default gateway is 192.168.1.1. Or for instance, 192.168.0.42 on a network where the default gateway is 192.168.0.1. This step eliminates the DHCP server within the router as a possible culprit.
- Try changing the wireless security protocol: If you are using WPA2 security on your Wi-Fi network, try changing it to WPA or WEP and see if the computer can connect to the network. Some network adapters may have compatibility issues with certain security protocols.
- Try disabling IPv6: Some network adapters may have issues with IPv6 connectivity. To disable IPv6, open the Network and Sharing Center in Windows and click on the "Change adapter settings" link. Right-click on the Wi-Fi adapter and choose "Properties", then uncheck the box for "Internet Protocol Version 6 (TCP/IPv6)".
If none of these steps work, it's possible that there is a hardware issue with the computer's Wi-Fi adapter.
One other command you could try running is the following:
DISM.exe /Online /Cleanup-image /Restorehealth && sfc /scannow
This will run two consecutive commands. One checks the Windows image files for issues and restores them back to the repository on your system. The second command runs scans of your system files off the Windows Side-By-Side repository and performs system file error correction/replacement. While its unlikely that this will solve the issue, if there is corruption somewhere in one of these files it will find it and correct it. It can take some time for the scans to run and complete.