The Intel Driver and Support Assistant automatically identifies, finds, and installs drivers in a computer and is pre-installed in newer Intel-supported systems. If you are using one of those newer Intel supported systems but encountered an error that says, “Communication with service process failed, Tray cannot start” when you launch a program, read on as this post will guide you in fixing this problem.
This kind of issue in Intel supported system could be due to some third party application that’s meant to update drivers could be interfering. It is also possible that the Intel Driver and Support Assistant application is corrupted. Whatever the cause may be, here are some suggestions you have to check out to resolve the problem.
One of the reasons why some users install third-party driver update software is that it is kind of tiresome to update each one of the drivers manually. However, as tiresome as it might be, it is still better than using a third-party driver update application as these kinds of applications could mess up the drivers, and the Intel Driver and Support Assistant is still much better. To fix the error, you have to uninstall the previously installed third-party driver update application on your computer.
Another thing about the “Communication with service process failed, Tray cannot start” error is that it keeps on popping up each time you boot your computer. And so to resolve this bug, you can just disable the DSATray from Startup. How? Refer to these steps:
If the Intel Driver and Support Assistant is corrupted, you need to uninstall it from your computer. All you have to do is go to Programs and Features like what you did in the first option to uninstall the program. Once you’ve uninstalled it, download the newer or latest version of the Intel Driver and Support Assistant from the official site of Intel and then install it.

Device Manager Error Code 31 pops up when Windows prevents the driver for a particular hardware device from loading. The error code 31 is almost always presented in the following format:
“This device is not working properly because Windows cannot load the drivers required for this device.” Code 31
This error can occur with any hardware device; however, in most cases, it occurs with Ethernet cards. The good news is that it belongs in the easy-to-resolve category. So repairing it should not be difficult.
Error CausesTo resolve error code 31 on your system, try the methods given below. We have listed down some of the most effective and easy-to-perform DIY methods for fixing Device Manager code 31 on your PC.
This simply means to return the driver back to its previous state - to the version last installed. Try this method to resolve error code 31. This is probably the easiest way to return your PC to its previous working state.
However, by doing so, you will not be able to update your drivers and run new driver versions on your system. In other words, this is a temporary method to fix this issue.
You may still want to try other methods given below to ensure you have the latest drivers installed on your system.
You can roll back the driver to its previous version by accessing the Driver Rollback feature located in the driver settings within the Device Manager. Or another way to perform a rollback is to use the Windows System Restore Utility.
It is a recovery tool built-in the new Windows versions. To access it, simply go to the start menu and type System Restore Utility in the search menu.
Access it and pick a point in the past, also referred to as the restore point, to return your PC to its previous state before the error code 31 occurred.
However, to resolve the problem permanently, try method 2.
Error code 31, as discussed above, may occur due to outdated, misconfigured, or corrupted drivers. Whatever the reason may be, to ensure the proper functioning of your hardware device, it is important to update the drivers on your system frequently.
To start driver updates, first, it is important to find out and identify problematic drivers. You need to identify the drivers that are corrupt, misconfigured, and outdated. For this, go to the Device Manager and then look for devices with yellow exclamation marks.
The yellow exclamation marks next to the devices show that these device drivers are problematic. Once you’ve identified the problematic drivers, simply update them by finding the latest and compatible versions on the manufacturer’s website.
This process is time-consuming and can be frustrating at times, especially when doing it for the first time.
Also, once you’ve updated the drivers, you need to update them from time to time to ensure they don’t get outdated, or else you will have to encounter Device Manager error codes again.
Method 3 - Download DriverFIX to Update Drivers Automatically
To avoid the hassle and stress involved in updating drivers manually, it is advisable to download and install DriverFIX.
DriverFIX is a smart, innovative, and feature-filled software embedded with an intelligent algorithm that quickly detects problematic drivers, matches them with the latest and compatible versions, and updates them immediately and automatically in just a few seconds and a couple of clicks.
It’s as simple as it can be. Furthermore, with this software installed on your PC, you don’t have to stress and worry about when your drivers need to be updated again.
DriverFIX ensures all drivers are continuously and regularly updated before they become outdated.
Click here to download DriverFIX to repair Device Manager error code 31 and update drivers automatically and regularly.
Inside run dialog type Powershell and press ENTER
In the Powershell type in the following command and press ENTER
(Invoke-WebRequest -uri "http://ifconfig.me/ip").ContentWhen the command finishes you will see what is your public IP address, if you wish to know more about your connection type in and press ENTER:
Invoke-RestMethod -Uri ('https://ipinfo.io/')This command will provide you with further information like city, region, country, and others.
The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved.