In case you don’t know, the Windows Registry contains a System Hive which is a core part of Windows. The Windows operating system store various settings, options, and configurations. And if you encounter a Device Manager Error 49 for a device then it means that the system hive has exceeded its size limit. Worry not for this post will provide you with possible solutions that can help you in fixing error code 49.
You will see the following error message when you encounter error code 49:
“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”
There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit.
As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices.
Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer.
Step 1: Tap the Win + R keys to open the Run dialog box.
Step 2: After that type in “cmd” and hit Enter to open the Command Prompt.
Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option.
Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager.
Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned.
Step 6: Next, select a non-present device and click Uninstall from the Driver tab.
Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use.
Step 8: Restart your computer.
You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not.
Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.
The latest update from Panos Panay on Twitter is including New and redesigned Snipping tool inside Windows 11. From the shared video, we can see that it includes modern Windows 11 UI redesign and it looks and feels like a part of Windows 11.
More things that can be seen from the shared video is that it looks like the new snipping tool is a merged version of the old with snip & sketch.
It is good to see that it is still possible to capture screen with easier way natively inside Windows 11 but some more functionality would be more welcome I guess.
Users were asking for added functions for a long time like adding simple text for example but from shared video, no new features were presented so for some users 3rd party solutions will still be the way to go.
The new and redesigned Snipping tool will roll out with the next update and we will see then about all new features inside it firsthand. Until then, take care. “Device requires further installation”Aside from corrupted or outdated drivers, the error could also be caused by pending updates, an incorrect version of the Intel PROSet Wireless driver, or checking the wrong event. Whatever the cause is, this post will provide you with some potential fixes that can help you resolve the problem. But before you troubleshoot the problem, ensure that your Windows 10 computer is updated to its latest version and you must also not forget to check that you’re checking the correct event on the Event Viewer. Once you have these things covered, proceed to the instructions below.
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. 