Error Code 35 - What is it?
Error Code 35 is a typical Device Manager error. It indicates information missing to properly configure your device. Error code 35 is usually displayed in the following format:
“Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. Code 35”
Solution
Error Causes
The 2 common reasons for Device Manager error code 35 are:
- Outdated BIOS
- Mis-configured, corrupted, or outdated Drivers
No matter what the reason may be, it is advisable to resolve the problem immediately without any delay otherwise you will be unable to use your hardware device.
Further Information and Manual Repair
Below is the list of the most effective and easy to perform solutions to resolve error code 35 on your PC. These solutions do not require any technical knowledge or understanding. Simply follow the instructions to resolve this error code.
Method 1 - Update the BIOS
BIOS (Basic Input/Output System) is the embedded software on the computer’s motherboard.
Though not all PCs have the same BIOS manufacturer, but the steps for updating the BIOS are similar for all versions. Before you get started with the updating process, first identify your current BIOS version.
- For this, go to the start menu and type msinfo32, and press enter.
- Now click System Summary to view your BIOS version. Here you will see the version number and date.
- Now check your PC motherboard manufacturer’s website to download the BIOS update for the model you own. Also, download any Read Me Files and documentation. These contain guidelines and precautions that you should know before you update.
- Backup all your data and existing BIOS before you update the BIOS version. This will keep your data protected in case the attempt to update BIOS fails.
- Also, when updating, make sure to use an uninterruptible power supply. Remember power outage or even a small power fluctuation can corrupt the BIOS which is something you don’t want.
- Now it’s time to perform the update. Run the downloaded installer for the BIOS updating software. Double click on the executable file.
- Look for a button names Update, Flash, or Run.
- Click on it to start updating the new version
- After the update is complete, your computer will restart automatically.
This will hopefully resolve the problem. However, if the error still persists then there is a possibility that the error code is related to outdated drivers. To resolve, try method 2.
Method 2 - Download Driver Assist to Update Drivers Automatically
Update drivers to repair error code 35 on your PC by simply downloading DriverFIX. This is a cutting-edge program deployed with an intelligent programming system.
It is compatible with all Windows versions.
It scans your PC for problematic drivers and updates them with the latest and compatible versions automatically and in a few seconds thereby repairing all Device Manager error codes including error code 35 generated due to outdated/corrupted drivers.
In addition to this, it updates all device drivers on a regular basis, so you don’t have to stress over and keep a track of what drivers on your PC need to be updated and when.
Click here to download DriverFIX to resolve Device Manager error code 35 today!


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. 
The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains.
Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue.
A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers.
Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine. 