
Usually when online service is not working or when something goes wrong online it is DNS, well that is what most of the time is the case. And yes, DNS or Domain Name Server seems to be an issue with Facebook being completely down along with Instagram and wassap.
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.
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftSystem
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess
net stop wuauserv net start cryptSvc net start bits net start msiserver
Error Code 38 is a device driver error that users encounter on any Windows 2000 operating system and its following versions.
It occurs when the peripheral device that you connect to your PC cannot be accessed due to an inability of the Windows system to acknowledge the driver as a previous record of the driver being loaded is found in its memory.
It is a common error that users come across and appears on your PC with the following message:
“Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)”
Error Code 38 is prompted when incomplete program files are left in the Windows system which damage or corrupt its files. There are various factors that contribute to this, some of which are:
The above triggers are very likely to create incomplete files within the Windows registry thereby leading to its damage and corruption.
This is especially true in the case of your PC when it has recovered from viruses when using anti-virus software. The anti-virus in its effort to remove the virus also could remove the files which contain them thereby increasing the risk of the error code.
These damaged files can severely impact the health of your PC and are imperative to fix it immediately to prevent further problems.
Although this error code may pose serious problems for your PC, thankfully, it is very similar to other PC driver errors and thus is an easy one to get rid of. Here are various methods that you can use to get your PC running smoothly again.
If restarting your PC does not help, you will have to find the exact nature of the problem by running the troubleshooting wizard for the device and then address the problem accordingly. To do this, proceed with the following steps:
After following the directions of the Troubleshooting wizard, make sure to restart your PC for the changes to take effect. Now check if your device is still causing problems.
If the error persists, you can use system restore to eliminate the problem. Here is how to do so:
By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system files that can help resolve the error code.
If using system restore does not work either, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem.
This would be necessary since the remaining incomplete files due to a partial removal or installation of programs are responsible for the error code. By uninstalling and reinstalling the device driver program, it would lead to the completion of the files.
You can do this by firstly logging in as Administrator and opening Device Manager. Select the device that is causing the problem and double click it; make sure that the peripheral is connected properly to the PC.
Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.
Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming especially when you would have to resort to your hardware user manual.
Using a program such as DriverFIX can save you a lot of time and frustration in having your device to work properly on your computer.
DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically.
It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 38, or any other driver-related errors for that matter.
It also has the added advantage of being able to backup and restores your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly.
Click here to download DriverFIX to fix Error Code 38 quickly and effectively!
Nectar Toolbar is a Browser addon for Internet Explorer developed by AIMIA Coalition Loyalty. This addon changed your default search provider to Yahoo UK. While installed, you might see additional unwanted ads and sponsored links injected in the search results.
From the Author: We all search the web every day for information from handy how-to’s, must know news about shopping. So wouldn’t it be great if you could collect extra Nectar points just for doing something you do already? Like to shop online? Nectar Search will also tell you when you’re on a shopping website (like Argos, Debenhams, Next, Play.com, and Apple) where you can collect points too.
Several anti-virus scanners have marked this addon as a Browser Hijacker and are therefore not recommended to keep on your computer.
@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on
dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart
Dism.exe /online /Cleanup-Image /StartComponentCleanup
net stop wuauserv net start cryptSvc net start bits net start msiserver
net start wuauserv net start cryptSvc net start bits net start msiserver
“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.