Fix DRIVER_CORRUPTED_EXPOOL Error

KMODE_EXCEPTION_NOT_HANDLED – What is it?

Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.

Solution

Error Causes

The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:

• Hardware incompatibility
• A faulty device driver or system service

Further Information and Manual Repair

You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.

If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.

After troubleshooting, below you’ll find a few solutions to rectify the issue.

Method 1 – Check The Cause of The BSOD Error

Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.

If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link. 

If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.

You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.

Method 2 – Disable (or preferably uninstall) Software Before Upgrading

If you’re upgrading Windows 10 from Windows 7 or Windows 8.1, you might need to disable or uninstall the software first. First, try uninstalling your Antivirus utility before starting the upgrade. Restart a few times before starting the Windows 10 installation. If you’re upgrading using the Windows 10 update, make sure that you disconnect from your Wi-Fi or Internet LAN (Ethernet) connection as soon as the download reaches 100% before attempting to start the set-up. Other users also reported that the cause of the KMODE_EXCEPTION_NOT_HANDLED issue is BitDefender. If this is what happened in your case, it will show in the error message such as KMODE_EXCEPTION_NOT_HANDLED (bdselfpr.sys). Users reported that a common solution for this is renaming the file. In the case of BitDefender, try renaming it to bdselfpr.s__. However, make sure to do this cautiously. Sometimes, renaming a file will even do more damage than good.

Method 3 – Disable/Disconnect From Hardware

If you’re connected to any general USB devices (such a smart card reader), disable it. If your computer is connected to other external devices, disconnect all of them. Examples of this include gaming controllers, printers, external hard disk, USB keys, and other non-essential devices).

Method 4 – Other Troubleshooting Steps

Other troubleshooting steps include:

• Upgrade using an .ISO file, instead of directly upgrading from Windows Update. When you do this, make sure you’re disconnected from the Internet during installation. If the process started and you forgot to disconnected, it’s best to restart the installation.
• If you’re connected to a domain while trying to set up Windows 10, disconnect and use a local account.
• If you’re using a SCSI hard disk, connect a thumb drive with the drivers for your storage device. While Windows 10 is setting up, click on the Custom Advanced Option. Using the thumb drive, use the Load Driver command to load the SCSI drive.
• Another possible cause of this error is due to BIOS incompatibility. BIOS issues can be solved by upgrading your version of your system BIOS. If you don’t know how to do this, refer to your BIOS manufacturer’s website.

Method 5 – Use A Trusted Automated Tool

If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.

nslookup is a command-line tool that helps in finding the DNS records of a website. It sends a name server query to the DNS and obtains the corresponding IP address. Aside from that, it can also perform some complex functionality such as finding details about FTP server, Mail server and many more but most of them are used by administrators. The best thing about nslookup is that it queries the DNS server directly and it does not rely on the cache. On the other hand, there is another tool called PING that is used to verify connectivity. PING sends a packet of information to the IP address or Domain and gets back a response in the form of packets. So if everything goes well, all packets are received but if not, it will help you find out where the delay in the network exactly is. However, the ping command does not always attempt a DNS lookup which means that it might be using the DNS cache and use the IP address available in that table. Although both nslookup and PING help you in identifying the host or IP address, however, they don’t always work and sometimes fail. So if your nslookup works but ping fails on your Windows 10 PC when querying the IP address of a website then it could be caused by many reasons. It could be that the nslookup queries work for you but when you try to use PING, it fails. For instance, if you open the abc.com website, here’s how it will look like:

nslookup xyz.com Server: dns.company.com Address: 192.168.1.38 C:> ping xyz.com Ping request could not find host xyz.com. Please check the name and try again.

The domain is converted into an IP address and then data is sent to that IP address when you use PING. So when a reply comes back it means that the data is going back and forth to that domain without any problem. However, if the DNS fails to resolve the IP address of the website or if your PC does not attempt a DNS lookup, you will receive a similar error message that says, “Could not find host” and so on. To resolve this issue, here are some options that might help.

Option 1 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue with nslookup and PING. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 2 – Force Windows to do a DNS lookup using FQDN

• Go to Settings > Network & Internet > Status > Change adapter options.
• From there, right-click on the network and select Properties.
• Next, in case you’re using IPv6, from the list of connections available in the list, select Internet Protocol Version 4.
• Then click on Properties and click Advanced.
• After that, switch to the DNS tab and select “Append these DNS suffixes (in order)” and click on the Add button and then add “.” as a suffix so that each time you query using PING and another tool, it will add a “.” at the end and will force the lookup.

Option 3 – Make sure that there is only one default gateway

If your computer has more than one NIC connected and there are multiple default gateways, then it will most likely create confusion which is why you need to remove the default gateway from the configuration of all NICs and make sure that there is only one default gateway.

Option 4 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the nslookup and PING issues. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why PING fails even when nslookup works. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 6 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles might help you in fixing the issue with nslookup and PING.

Option 7 – Reinstall the Network Adapter Drivers

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and select “Uninstall device”.
• Restart your PC.

If you are trying to log into your user account on your Windows 10 computer but encountered an error message instead that says, “Your account has been disabled, Please see your system administrator”, read on as this post will guide you on how you can fix this problem. In this kind of scenario, you won’t be able to access your data unless you have access to the administrator account. This problem could be caused by several problems. It is possible that malware has infected your computer and has changed some settings in your computer, especially if your system has been under a malware attack not too long ago. The malware could’ve changed the “Account is disabled” option. The only thing you can do to resolve this kind of problem is to log into your computer using another administrator account and then change the setting. However, if you don’t have a second administrator account, you can just enable the built-in hidden administrator account on your computer. You shouldn’t have any problem enabling the hidden administrator account as it is quite easy when you can log into your account. And in this post, you will be guided on how you can enable the hidden administrator account using the Registry Editor to fix the “Your account has been disabled, Please see your system administrator” error.

To get started, follow the instructions given below.

1. First, you need to start your computer and ensure that you are on the error screen. From there, you will see the Power options located on the right-hand side.
2. Click on the Power options and tap and hold the Shift key and then select Restart.
3. After that, the Advanced Boot Options will appear and from there select Troubleshoot > Command Prompt.
4. Next, you have to select your user account and enter the user account’s password to open Command Prompt.
5. After opening Command Prompt, open your screen and type “Regedit” and then tap Enter on your keyboard.
6. Now select the HKEY_LOCAL_MACHINE in the Registry Editor and go to File > Load Hive.
7. Afterward, you have to open the Windows installation drive and go to the location – WindowsSystem32Config
8. From there, you should find a file named “SAM” – select this file and click the Open button.
9. Next, you have to enter a key name. You can just input whatever you prefer.
10. Once done, navigate to this path: HKEY_LOCAL_MACHINEkey_nameSAMDomainsAccountUsers
11. From this path, you will see a key named “000001F4” – select this key and double click on the “F” entry that you can find on the right-hand side of the screen.
12. After that, look for the value data line labeled “0038” which should show 11 in the first column. You have to replace it with 10.
13. Once done, click on the OK button and close the Registry Editor and the Command Prompt to restart your computer.
14. Now once your computer has restarted, sign in to the Administrator account and open the Computer Management window. You can just search for it using the search bar in the Taskbar.
15. After you open Computer Management, go to Local Users and Groups > Users – where you can find all the user accounts. Look for your deleted user account and right-click on it and select Properties and then unmark the checkbox that says “Account is disabled”. This should fix the problem.

What exactly is the 2GB filesize Error?

The PST file could be around 2 gigabytes if you are using MS Outlook 2002 or any earlier versions for your own personal Folders. The 2GB filesize malfunction occurs when your PST memory both reaches or exceeds this limit. The 2GB size problem code is, in addition, referred to as an outsize PST file error. When this error happens you may be unable to deliver or receive e-mails via your Outlook account. Moreover, you'll likewise not be able to add any new data or even view your important calendar items, notes, and saved drafts. MS-Outlook shows several types of problem codes which indicate the 2GB file size dilemma. Listed below are some of the messages that can be displayed on your monitor:-

• The file could not be added to the folder. The action could not be completed.
• Task 'Microsoft Exchange Server - Receiving' reported error (0x8004060C): 'Unknown Error 0x8004060C'
• Can't copy the item
• Errors have been detected in the file xxxx.pst. Quit all mail-enabled applications.
• Task 'Microsoft Exchange Server' reported error (0x00040820):'Errors in background synchronization. In most cases, further information is available in a synchronization log in the Deleted Items folder.'
• xxxx.pst cannot be accessed - 0x80040116

Solution

Error Causes

The simple explanation for this malfunction is that you have maxed out the two gigabytes account limit. This happens in case you continue downloading fresh data and saving files and the old emails in your Outlook account. Over time, the space becomes limited and along with it the 2 GB file limit error. This error also presents a critical danger of data loss which is a possibility in your Outlook account, which hinders you as well from fully utilizing your email account. For regular Outlook customers, who utilize this program for practically all email communication within as well as outside the office, this error is annoying and frustrating as it causes a great deal of annoyance as well as decreases their performance and productivity.

What exactly are the Symptoms?

Below are a few signs that will help you recognize the 2GB file-size error:

• Inability to fill and open the OST and PST files
• Error messages pop-ups
• Failure to send emails
• Failure to make or edit new contacts
• Inability to synchronize the file

Further Information and Manual Repair

It is desirable to fix this error code right away especially if this is the preferred strategy to carry out communication in your office. Fix it immediately or else you might not receive e-mails that are important from your colleagues. There are 3 ways to solve this issue.

Method 1

One is to remove the old e-mails and connections and replace them with new ones. This may not be the best option for you in case you don't wish to lose emails and your old contacts.

Method 2

The second alternative would be to install a fresh version of MS-Outlook like 2010. The file-size limits of OST and PST files in these editions are larger than in ms-outlook 2002. On the other hand, this is a good idea for the long run but may not be the best idea for today as you will not have the ability to recover your previous e-mails and contacts that are outdated.

Method 3

The third and maybe the method that is best to resolve the 2GB file size limit error while ensuring the restoration of your old e-mails and contacts as well as increasing the limit to 4GB, is Restoro program's installation. Here may be the best recovery program on the market. It is really easy to use, safe, exceptionally functional, secure, and especially can resolve this issue. Technical expertise isn't needed by you to perform your way around this device.

All you should do is:

Click here to download and install the Restoro repair tool on your computer. In your MS Outlook account, you can restore all your data in just a couple of clicks. Talking of data recovery, this software can also help you recover all those other e-mails before the PST malfunction happened, or that you may have deleted. So, if you have deleted any significant email that you want to recover, this will undoubtedly be of use for you. By installing it on your system you can double your Outlook account's quality to twice as much as the standard size.

The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

1. Click on the Windows icon and go to settings.
2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
3. Choose Advance Option
4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

1. Open the Microsoft Edge browser.
2. Type in about: flags on the Address (URL) bar.
3. Under Networking, uncheck the Enable TCP Fast Open.
4. Close your Microsoft Edge browser and open a new one.

Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.

1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
2. A dropdown menu will show up, click on Command Prompt which is the first on the list.
3. Type in the code ipconfig /flushdns and press enter.
4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
5. Exit the CMD by typing exit and press enter.

The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.

If you suddenly find the middle mouse button not working as you use it on your Windows 10 computer, then you’ve come to the right place as this post will provide some suggestions that can help you fix the issue. This kind of problem can affect your experience in using your computer as the middle mouse button helps you in scrolling through long web pages and screens with a lot of data. So if that stops, you will end up using your keyboard instead which is kind of a hassle compared to using the middle mouse button. It is possible that this problem could have something to do with either the hardware or software. To isolate the possibility of a hardware failure, you can try to connect the mouse to a different computer and see if it works just fine there or if it still has the same problem. If the mouse works properly on a different computer, then the issue is software-related. It is possible that a software update, especially gaming software, could have been misconfigured in a way that the middle button does not respond like it’s supposed to. To resolve the problem, you might want to try reinstalling or updating the mouse drivers or run the Hardware and Devices troubleshooter. You can also install OEM-specific mouse drivers or modify some entries in the Windows Registry.

Option 1 – Reinstall or update the Mouse driver

The problem may be caused by a corrupted or an outdated mouse driver. To fix it, you have to update or reinstall the mouse driver. How? Follow these steps:

• Open the Devices Manager from the Win X Menu.
• Then locate the Mouse and other pointing devices and right-click on the mouse driver to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, disconnect the mouse and plug it back in to reinstall the mouse driver.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try running the Hardware Troubleshooter

The next thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem with these function keys. To use it, refer to these steps:

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Try to install OEM specific mouse drivers

Aside from updating or reinstalling the mouse drivers, you might also want to try installing OEM-specific mouse drivers. When you install Windows, it will use a generic driver for all its components. The disadvantage of generic drivers for the mouse is that it limits its functionality. In fact, some also configure the middle mouse button to respond to specific action which does not work without the correct drivers. In such cases, you need to visit the website of your computer’s manufacturers to download and install the latest drivers and then open the software and configure it the way it was before. Keep in mind that some OEMs also offer gestures, so you also have to check on that.

Option 4 – Try to modify some entries in the Registry

If a Windows Update is the one that caused the problem, you could correct it by making some modifications in the Registry but before you proceed, make sure that you create a System Restore point first.

• Tap the Win + R keys to open the Run utility.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_CURRENT_USERControl PanelDesktop
• After that, double click on the “WheelScrollLines” entry on the right pane to open its Properties.
• Now change its value data to “3” and exit the Registry Editor and then see if the issue with the middle mouse button is fixed or not.

Recently, a number of users reported that they were not able to use the “Run as administrator” context menu option when they tried using it or opening a program with administrator privilege. If you are one of these users facing this problem, then you’ve come to the right place as this post will guide you in fixing this issue. At the time of writing, it isn’t clear what the cause of the issue is but there are potential fixes you can try to fix the problem. You can try turning on the User Account Control or clean up the Context Menu items change the Group Membership. On the other hand, you can also perform both SFC and DISM scans via Command Prompt or troubleshoot the problem in a clean boot state as it is possible that some third-party programs are the ones that are causing the problem. You could also run an anti-malware scan using Windows Defender or your antivirus program.

Option 1 – Try to turn on the User Account Control

When you open a program with administrator privilege, the User Account Control or UAC prompt will pop up asking you to confirm the permission. However, if you have disabled the User Account Control by mistake or some malware has disabled it, then it’s no wonder why the “Run as administrator” option is not working. Thus, you need to check if UAC is turned on or not. All you have to do is go to the User Account Control settings.

Option 2 – Try changing the Group Membership

• First, you need to sign in with your administrator account or ask your administrator to sign in for you. So if you only have a Standard User account, you have to add that account to the Administrators group.
• In the taskbar search box, type “netplwiz” and check the search results.
• From there, select your user account and click the Properties button.
• After that, go to the Group Membership tab and select Administrator.
• Now click on the Apply and OK buttons to save the changes made and then sign in to your computer again and see if the “Run as administrator” option is working or not.

Option 3 – Try to create a new Administrator User account

If you have a standard account, you can try creating a new account but this time, you create an administrator user account and then see if you can now use the Run as administrator option or not. Note that you have to sign in with your main account before you can create an admin account.

Option 4 – Run the DISM tool

You can run the DISM tool as well to help fix the problem with the “Run as administrator” option. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the problem with the “Run as administrator” option on your Windows 10 computer. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Once done, restart your computer.

Option 6 – Put your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing you from using the “Run as administrator” option and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try to use the Run as administrator again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, try to check if the error is now fixed and that you can now view the Properties.

Option 7 – Try scanning your computer using Windows Defender

As mentioned, if your computer was recently infected with some malware, it is possible that the malware changed the User Account Control settings which is why you’re not able to use the Run as administrator option. Thus, you need to scan your computer using Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

This post will guide you on how you can fix the Error 0x80070079. This kind of error mostly occurs during the transfer of files across the networks. It could be caused by several factors which include the incorrect configuration of drivers or the network, as well as deadlock state or the server is loaded with a lot of tasks and if any location is not available. This error could also appear when you try to create a System Image or copy or move files on your computer. Here’s the full context of the error message:

“Error 0x80070079: The semaphore timeout period has expired.”

To fix this error, you can try to run the three built-in Network-related troubleshooters or update or reinstall the network adapter drivers or perform a network reset. For more details, follow the options laid out below.

Option 1 – Try to run the three built-in Network-related troubleshooters

The first thing you could do to fix the problem is to run any of the three built-in troubleshooters related to Networks such as Incoming Connections, Network Adapter, and Shared Folders troubleshooters. To access them, just open the Windows Settings app, and go to Update & security > Troubleshoot. From there, run any or each one of the aforementioned troubleshooters.

Option 2 – Update the Network Adapter drivers

You might also want to update the Network Adapter drivers by following these steps:

• Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand them.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing the “Windows could not find a driver for your network adapter” error, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly. To reinstall the network adapter driver, refer to these steps:

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Option 3 – Perform a Network Reset

Network Reset is a feature in Windows 10 that will help you reinstall the Network adapters as well as reset the Networking Components back to their original settings.

• Open the Start Menu and click on the Settings icon.
• Next, click on the Status link on the left side where you should see the status of your Network. Aside from that, you should also see a link that will let you open the Network Troubleshooter – click on that link to expand Network Troubleshooter.
• Under Network Troubleshooter, select the link for “Network reset”.
• After you click on Network reset, it should redirect you to the following page. From there, click on the Reset now button.

If you are trying to update or upgrade your Windows 10 computer using the Windows Update and suddenly an “Error 0x800f0900” appears, then you’ve come to the right place as this post will help you resolve this Windows Update issue. When you encounter this error, you will see the following error message on your screen:

“There were problems installing some updates, but we’ll try again later. If you keep seeing this and you want to search the web or contact support for information, this may help: 2018-03 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4088776) – Error 0X800F0900”

This kind of Windows Update error is most likely caused by some corrupted files in the system. It is also possible that the Windows Database might have become corrupted as well. So if you are currently experiencing this problem, refer to the options given below and see which one of them works best for you.

Option 1 – Try running the DISM Tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening are less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 2 – Try running the System File Checker or SFC scan

The SFC scan or System File Checker is a built-in command utility in Windows that helps in restoring corrupted files as well as missing files that cause several issues in the computer like the Windows Update Error 0x800f0900. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 3 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073712. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Perform a System Restore

You can also try to perform a System Restore as it can also help you fix the Windows Update Error 0x800f0900. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Reset both the SoftwareDistribution and Catroot2 folders

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Hello all the wonderful people and welcome to our new article where we take a little different turn than usual and discuss why keeping old electronics around the house is not such a good idea. We all have some drawer or in some bag around the house and in the end of the day if that electronic has battery inside it is probably not the smart thing to keep it.

So naturally, the question comes why it is a bad idea to have old electronics with batteries in them? Well unlike a battery failure with, say, some AA batteries jammed in the back of an old toy, the risk with a lithium-ion battery failing isn’t just some leaking and corrosion in the battery compartment, it’s a potential fire as the battery swells up and the gases (combined with the stored energy) turn the battery into a potential fire hazard.

Good thing is that the battery will not explode just like that, it will swallow over time and get bigger and bigger until the breaking point is reached and all the fire breaks lose. So if by any chance you have some old gadgets lying around you can check up on them and see if has swelling process started, if yes, dispose properly of that piece of the old device immediately.

How to keep old electronics

If you’re not ready to get rid of the gadget then it’s best to charge it properly for storage. Proper charging keeps the battery cells and circuits in optimum health.

While recommendations vary by manufacturer and application, the general consensus is that lithium-ion batteries should be charged to approximately 40%. (Some manufacturers recommend charging 50% or 60% instead.)

Really, the important part here isn’t the exact percentage. What’s important is ensuring that the battery is charged to roughly half capacity and not stored with a completely discharged or completely full battery.

Discharge rates on lithium-ion batteries in completely powered-off devices are very slow, but you should still plan to top off the charge every 12-18 months or so to keep it around 50%.

If you wanted to go above and beyond, a metal storage container with a snug lid on a basement shelf with a desiccant pack inside to control the moisture would offer optimum conditions.