6 ways to fix 'Windows Can't Communicate With the Device or Resource' error

There's nothing worse than getting a Windows error preventing you from accessing the Internet. Having an error message that says Windows can't communicate with device or resource is not uncommon and can quickly get you into trouble one day.

If you get this error message, there's no need to panic. The following article will explain exactly what this error means and how you can fix it.

What is the error "Windows can't communicate with device or resource"?

You will often see the " Windows can't communicate with device or resource " error when you cannot connect to the Internet and run Network Diagnostics.

When you get this error, it means your computer is unable to connect to the Internet directory, also known as the Domain Name System (DNS). This system automatically translates website name into IP address, allowing you to browse the web easily.

Your computer's primary DNS server is usually provided by your Internet service provider. A secondary DNS server is also set up in case the primary server goes down. Even so, computer settings can sometimes fail, causing you to have problems connecting to the Internet.

If you can't get rid of the error " Windows 10 can't communicate with device or resource ", then here are some fixes that might help.

How to fix "Windows Can't Communicate With the Device or Resource" error

1. Make sure DNS and DHCP client are running

Before trying any of the following fixes, you will always need to make sure that your DNS and DHCP client are running. To do this, go to the Start menu's search bar and type "Services".

6 ways to fix 'Windows Can't Communicate With the Device or Resource' error Picture 1

Select the Services app and you'll see a list of all the services running on your device. Check for services labeled DNS and DHCP. If "Running" is not listed in the "Status" column for either of these services, you will need to fix that.

6 ways to fix 'Windows Can't Communicate With the Device or Resource' error Picture 2

Select Automatic from the "Startup type" drop-down menu.

Enable DNS and DHCP by double clicking on each service. If the service has stopped, just select Start. You should also make sure that you select Automatic from the "Startup type" drop-down menu .

When done, click Apply> OK .

2. Uninstall and reinstall the network device

Outdated or incorrect drivers can sometimes cause the error " Windows can't communicate with the device or resource ". In this case, it is best to wipe everything and uninstall the network device.

To access network devices, press Windows + X to open the Quick Link menu . Select Device Manager from the list and click Network adapters.

Select the network device and click Uninstall device. Once done, right-click on Network adapters and click Scan for hardware changes .

Windows will automatically detect "new" network devices. It will then install the default drivers that came with the device. You can now restart your computer and test your connection.

3. Manually update the network driver

Although network drivers are usually updated automatically on Windows 10, it doesn't hurt to try to update your network drivers manually. To do this, press Windows + X> Device Manager> Network adapters .

Find the network device in the drop-down menu, right-click on it and select Update driver.

Now, Windows will give you two ways to find new drivers. Select the option that says Search automatically for updated driver software .

From here, Windows will look for any updates on your computer and the Internet. If there are new drivers, install them.

4. Clear the DNS cache

A corrupted DNS cache can also cause error messages. To fix this, you will have to clear your DNS cache.

To get started, open a Command Prompt with admin rights.

When the program appears, type the following lines of code in turn:

ipconfig /flushdns ipconfig /registerdns ipconfig /release ipconfig /renew

This not only clears the DNS cache, but also causes the computer to reset any corrupted configurations that could cause an error message. Then press Enter and you can close Command Prompt.

5. Configure adapter settings

If the fixes above still don't work, the network adapter's settings may be affecting your connection. To start configuring the settings, go to Control Panel and choose View network status and tasks under the Network and Internet heading .

Then, select Change adapter settings from the menu on the left side of the screen.

6 ways to fix 'Windows Can't Communicate With the Device or Resource' error Picture 3

Right-click on the connection and select Properties.

Make sure the box next to Internet Protocol Version 4 (TCP / IPv4) is checked. From here, double-click on the IPv4 option.

6 ways to fix 'Windows Can't Communicate With the Device or Resource' error Picture 4

Check Obtain an IP address automatically and Obtain DNS Server address automatically . When you're done, click OK.

To work around this problem more effectively, you can also repeat the same steps with Internet Protocol Version 6 (TCP / IPv6) .

6. Switch to public DNS

If you still can't connect to the Internet, you might have a problem with DNS. Switching to public DNS, such as Google's DNS, can help solve this problem. In fact, you may even find that switching to a different DNS can help you speed up the Internet.

To get started, you will have to access network settings using the same method outlined in the previous step. Just open Control Panel, navigate to View networks status and tasks> Change adapter settings . Right-click on the connection and select Properties.

6 ways to fix 'Windows Can't Communicate With the Device or Resource' error Picture 5

Double-click Internet Protocol Version 4 (TCP / IPv4) again. This time, select Use the following DNS server addresses .

Now enter the address for Google's DNS. In the fields below, enter the following numbers:

  1. Preferred DNS server: 8.8.8.8
  2. Alternative DNS server: 8.8.4.4

After clicking OK , restart your computer to see if your Internet connection is working again.

« PREV POST
NEXT POST »