Fix Windows Update Error 0x80072EE2

TPM, also known as Trusted Platform Module, is a specialized chip used for security as well as encryption of users’ private data like Fingerprint, Facial data, and many more. TPM also comes with a Management Console and if you are not able to load the Management Console and you got the “Cannot load Management Console” error instead, read on as this post will guide you in fixing the problem. This type of issue usually happens when you clear or disable the TPM using the settings in the BIOS and so when you run the Trusted Platform Module Management console, you encounter the error. To fix the “Cannot load Management Console” error in your Windows 10 computer, here are some options you should check out.

Option 1 – If TPM is cleared in the BIOS:

If the Trusted Platform Module is cleared in the settings of the BIOS, you have to close and restart the TPM Management console or TPM.msc once again. It could be that the TPM Management has to reload the changes again after you’ve made them which is why you encounter the “Cannot load management console” error.

Option 2 – If TPM is disabled in the BIOS:

If you opted to disable TPM using the BIOS settings or you have turned it off by accident, then you have to enable it back and you have two options to do that – you can either enable TPM from the BIOS or using the Windows PowerShell. For more details, refer to the instructions below.

Enabling TPM from the BIOS:

• You need to first reboot your PC and then go to the BIOS.
• From there, look for TPM under the security options and in case the TPM management option has been disabled or greyed out, refer to the sub-steps given below to make it active again
  • Enable the Admin password in the BIOS.
  • Then go back to the TPM settings and check if the TPM management is already available.
• After that, you should now be able to enable TPM. Remember that it’s always a good idea to have an ADMIN password for your BIOS as it makes sure that no one can change the settings in your computer BIOS and Security level options.

Enable TPM via Windows PowerShell:

• This second option is a lot easier compared to the first one if you have admin privileges. So once you’ve opened the Windows PowerShell with admin privileges, you need to run the following command:
  • $tpm = gwmi -n rootcimv2securitymicrosofttpm win32_tpm
  • $tpm.SetPhysicalPresenceRequest(6)
• After you execute the commands given above, you need to restart your computer.
• Now, once your computer has restarted, you need to accept any BIOS prompts and then check if the “Cannot load management console” error is now fixed.

This post will guide you in fixing a particular problem where your Windows 10 computer does not even let you turn it on and it appears as soon as it starts to boot the operating system and it displays an error message that says, “The Boot Configuration Data for your PC is missing or contains errors, Error code 0xc0000185”. On the other hand, it may also display a different error message saying, “The operating system couldn’t be loaded because a required file is missing or contains errors”. There are various suggestions you can try to resolve this error. You could check the physical status of your hardware or rebuild the Boot Configuration Data, use the Automatic Startup Repair or System Restore, or better yet, reset your Windows 10 computer. Since your computer will not boot, you will have to either try to get into the Advanced Startup Options screen, boot Windows 10 in Safe Mode, or use a bootable Windows 10 media to boot your computer.

Option 1 – Try to rebuild the BCD files

The first thing you can do to resolve the issue is to Rebuild Boot Configuration Data or BCD files.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 2 – Try to run Automatic Startup Repair

In this option, you need to boot your computer into the Advanced Startup Options and from there, run the Automatic Startup Repair and then wait until the process is completed.

Option 3 – Try running System Restore in Advanced Startup Options

Since you probably can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.

Option 4 – Try to perform repair install by creating a Windows 10 installation media

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 5 – Try to physically check the hardware

You should also check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Network Card of the computer. You might want to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.

The error code 0X8019019A is shown when a user fails to add his Yahoo account to the Mail app due to the outdated or corrupt installation of the Mail app. Not using an App-specific but a normal Yahoo account password may also result in the error at hand. In this guide, we will show you how to effectively fix this error so you can set up Yahoo mail.

1. Reboot PC

   Perform a restart of your system to rule out a temporary glitch in the system. Also, check if you can successfully access your email through a web browser using the same credentials as you are using with the Mail app. Additionally, make sure that no VPN or proxy server is being used to access the internet (VPN/proxy may work fine with the web version of Yahoo mail but may hinder the access through a mail client).

2. Update Windows and the Mail App to the Latest Build

   If your system is not updated to the latest build it can create incompatibility between the OS modules. Updating the Windows and Mail app of your system to the latest build may solve the problem.

3. Re-add the Yahoo Account to the Mail App

   The Yahoo account issue could be a result of a temporary glitch in the communication modules of the system. The glitch may get cleared if you remove and then re-add the Yahoo account to the Mail app.

4. Reset the Mail App to the Defaults

   You may fail to add the Yahoo account to the Mail app if the installation of Mail itself is corrupt. In this scenario, resetting the Mail app to the defaults may solve the problem.

5. Generate an App Password and Use it to Add the Yahoo Account to the Mail App

   Yahoo has implemented tons of security features to its accounts. One such feature is the use of app-specific passwords for less secure apps like the Mail app. If your Yahoo username or password is not working with the Mail app, then using the App-specific password may solve the problem.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

Error Code 8024001F – What is it?

During the Microsoft Windows 10 upgrade, certain users have experienced an issue with error code 8024001F. Users should note that this error is also known as Windows Update 8024001F and 0x8024001F. This error code is relatively common and is usually caused by a faulty internet connection. Thanks to this common reasoning, the error is generally fixed easily, and users are able to restart their Microsoft Windows 10 upgrade. Common symptoms include:

• A dialog box appears with the Error Code 8024001F when attempting to upgrade to Microsoft Windows 10.
• Your current version of Windows is unable to recognize the need for an update to Microsoft Windows 10.

Solution

Error Causes

With only three issues causing error code 8024001F, it is relatively easy to determine your particular issue and then follow the steps below to rectify the situation.

• Your computer is not connected to the internet.
• The Windows firewall is interfering with the Microsoft Windows 10 update.
• Your third-party antivirus and firewall software is interfering with the Microsoft Windows 10 update.
• Your system is infected with the Conficker worm, which is preventing the Microsoft Windows 10 update from processing correctly.

Microsoft Support asks that you contact them directly for further assistance if you are able to rule out these three reasons for error code 8024001F.

Further Information and Manual Repair

Error code 8024001F is easily corrected using one of the following methods. Each of these methods should be convenient and comfortable for a basic computer user at home. If at any time you are unsure or feel you need more assistance, Microsoft Support asks that you contact them directly for more guided support.

Method 1- Access the Troubleshooter

1. Access the Windows Update Troubleshooter
2. When the dialog box pops up, click OK.
3. Click NEXT on the following dialog box.
4. Windows will then run the Troubleshooter, attempting to detect any known issues with your system.
5. Depending upon the results you should be able to follow the on-screen prompts which will alleviate the update issue.

Method 2- Correct your internet connections

1. Closeout of the error code 8024001F dialog box.
2. Close the Microsoft Windows 10 updater.
3. Attempt to access the internet through your normal browser.
4. ** If you can successfully access the internet, then an internet connection is not the cause for this error code.
5. If you are unable to access the internet verify that you are plugged into your network, both at the router/wall and at your computer jack.
6. If you use a router, verify that all of the lights are on and active (showing an active internet connection).
7. Establish an internet connection if possible. If you are unable to establish an internet connection, you may need to contact your internet provider.
8. If you are able to reestablish an internet connection, then you should have no problem running your Microsoft Windows 10 update.

Method 3- Adjust the Windows Update settings

1. Log into your current version of Windows as the Administrator (enter a password if prompted).
2. Click the START button on your keyboard or screen.
3. Search for the term “admin”, press ENTER
4. Click the “administrative tools” option
5. Select the “services” file, re-enter your password.
6. Open the Windows Update file by right-clicking on the name.
7. Choose the “properties” option
8. Under the GENERAL tab, make sure that the “startup type:” is set to AUTOMATIC (DELAYED START)
9. Under the “Service Status” header, click the START button.
10. Click OK
11. Restart the Microsoft Windows 10 update.

Method 4- Scan for the Conficker Worm

1. Access the web address to be directed to the Microsoft Safety Scanner.
2. Run this free scanner provided by Microsoft to verify if the Conficker Worm is your issue.
3. If this worm is causing your error, Microsoft will walk you through the steps necessary to remove the worm.

Method 5- Firewall and Anti-Virus software

1. If you are using the Windows firewall or a third-party anti-virus and firewall software, disable these programs.
2. Run the Microsoft Windows 10 upgrade.
3. After the upgrade is complete, turn your antivirus and firewall software back on.

Users should not have a problem employing the above methods. Start with the simplest solutions first, and then work your way to the more intricate methods. In some cases, depending on why this particular error code was caused, you may have to use a powerful automated tool to have it resolved.

Error Code 0x80070490 - What is it?

When downloading a Windows update, it is important to remember that these updates are what keeps your computer safe. Some users have reported seeing error code 0x80070490 when allowing updates for their Windows PC. This error code may appear when the user is trying to connect to the update site for Windows and maybe a result of a corrupted CBS manifest. Having this error code will not only stop the update of the system, but it will also certainly halt any work being done with the computer. Quite a few Windows users have written in complaints about this error while updating from any prior Windows update to Windows 10.

Common symptoms include:

• While a user is performing the updates, the Windows computer will stop running the updates, and it will show the error code 0x80070490.
• Windows updates will not install any new features and will not install security patches.
• The computer will not continue with the Windows update, and it may revert back to the previous state that the computer was in, prior to attempting the updates.

Error Causes

There is not a lot known about what exactly causes the error code 0x80070490, but it is something critical that makes Windows abruptly stop its updates. It could be caused by a simple glitch in the computer system, or it could be caused by a larger problem. One thought is that the CBS (Component-Based Servicing) manifest can be corrupt. Another thought is that the computer's anti-virus software may be interfering with the computer's ability to perform the necessary updates.

Further Information and Manual Repair

There is very little information known about error code 0x80070490 and why it exists, but there are a few methods in which to correct it. Users should be careful when trying to fix this error themselves. If the user feels that the methods are too complicated or they are uncomfortable taking it on themselves, they should contact a Windows repair technician to fix the problem. Not all methods listed will suit the user's needs, but it is dependent upon the problem at hand as to which method will be the best fit to fix the error code. If these steps are taken and the error is not corrected, it is vital to contact the Windows repair technician.

Method One: Creating a new local account

Create a new local account on the computer, and allow administrator privileges on it. Next, move all of your documents and personal files to the new account. Delete the old account (you will no longer be using this) and switch over to the new one. After switching to the new local account, add the Microsoft account to it.

Method Two: Delete user ID, Store cache from the registry

• You will need to open the Registry Editor. Do this by pressing the Windows Key and R, then typing in “Regedit”. After this is typed in, press Enter or click the OK button to start the registry editor.
• When this starts, you will need to navigate all the way to the following key on the left pane:
• HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAppxAppxAllUserStore After this, find the key that is similar to this: S-1-5-21-1505978256-3813739684-4272618129-1016
• NOTE: this is just an example. The keys will be in a similar format but will not look exactly like this.
• Select all the keys that look like this, and then delete them. After these keys are deleted, close the Registry Editor and restart the computer.

Method Three: Check to see if BITS, MSI Installer, Cryptographic, and Windows Update Services are running

Press the Windows key and R. Then, type in services.msc. After the Services window starts up, find the following services:  BITS, MSI Installer, Cryptographic, and Windows Update Services. When these services are found, make sure that they are up and running. If one or more of these services is not running, make sure that they are started. To do this, select the service and then click on Start the Service.

Method Four: Windows Update Troubleshooting

Press the Windows key plus W and then type in “troubleshooting”.  Select Troubleshooting. On the top left corner, select View All. Click on Windows Update troubleshooter. After this, follow the on-screen instructions in order to run the troubleshooter. After the troubleshooter has run, the issue should be fixed.

Error Code C0000135- What is it?

C0000135 is a blue screen of death error code (BSoD) also referred to as the ‘Stop’ error. This error code usually pops up on the screen at startup. The system stops and displays the error code:

Stop: c0000135 {Unable to Locate DLL} The dynamic link library FILE_NAME could not be found in the specified path Default Load Path

Solution

Error Causes

There are multiple reasons behind the error code C0000135 BSoD such as:

• Missing and damaged .DLL files which is linked to registry corruption
• Malware attack
• Viral infection

When this error code pops, the computer screen turns blue and hampers your ability to use Windows successfully. Nonetheless, if the error C0000135 is not repaired timely this error can cause a great deal of damage to your PC. It puts you at risk of:

• Data Loss with possibly no chances of recovery
• System Failure and crash
• Cybercrime if malware is the underlying cause of the occurrence of the error code C0000135

To avoid serious PC damages and inconvenience it is advisable to repair this error immediately.

Further Information and Manual Repair

There are two ways to fix the error code C0000135:

1. Hire a Professional
2. Download Error Tools PC Repair

Hire a Technician

Hiring a professional can be costly. You may have to pay hundreds of dollars to the technician to resolve this issue. However, the latter option is not only money-saving but also time-saving, convenient, and simple. In fact, it is so easy that even if you have no technical knowledge you can still work your way around it and repair the error in seconds.

Download Restoro

Restoro is a top-quality, efficient, and multi-functional PC fixer. It is integrated with cutting-edge technology. It has a comprehensive suite of advanced utilities like an intuitive registry cleaner, powerful anti-virus, and a smart system stability detector. All of these exciting and highly functional features are combined together in one. With this helper, you don’t need to search for the underlying cause of the error. When you experience the BSoD error code C0000135 on your system all you have to do is run it for a scan and its intuitive in-built technology will detect the issues and causes in no time and display them to you in the form of a comprehensive scan report. Once the scan is complete, you just have to hit the repair tab to resolve it. It’s that easy and fast! Restoro is powered by a highly functional registry cleaner. This cleaner helps detect all the errors related to the registry. It cleans the unnecessary files cluttering and damaging the hard disk including the junk files, invalid registry entries, internet history, and the files from the programs that you have uninstalled on your PC. These files acquire a lot of disk space and damage .dll files as well. Overloaded registry also slows down the system and the CPU and RAM then require more power to start and function. The registry cleaner embedded in the Restoro removes and wipes out all this unnecessary clutter, clears up the disk space and repairs the damaged files, and corrupted registry, and thus resolves the error code C0000135 on your system. Restoro also serves as a system optimizer. And when you repair issues on your PC with this helper, you’ll see a massive difference in the speed and performance of your computer. It will run smoothly and boot efficiently. Restoro is safe to use. It is bug-free and used widely by PC users experiencing different types of PC-related issues including the error code C0000135. It has easy navigation and a user-friendly interface. You can download and run Restoro on all Windows versions. Click here to download Restoro today!

As you can notice in Blue Screen errors, most of them point out a file that’s related to the errors. One of these files is the Storport.sys file which is a system file related to the storage of data in the storage unit of a computer. This file is created by the Microsoft Storage Port Driver. So if this file ends up getting dragged on Blue Screen errors, there can be a number of reasons for why it’s happened. Blue Screen errors related to the Storport.sys file may include conflicts with the hardware, incompatible firmware issues, corrupted drivers, missing or corrupted system files, to name a few. Here are some of the common Blue Screen errors related to the Storport.sys file:

• KMODE_EXCEPTION_NOT_HANDLED
• KERNEL DATA INPAGE
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL
• SYSTEM SERVICE EXCEPTION

Microsoft Windows is the one that provides the Storport.sys file a storage port driver that is suited especially for the use of high-performance buses like fiber channel buses and RAID adapters. There are a number of advantages in using Storport instead of the SCSI Port, according to Microsoft:

• “Improved performance, both in terms of throughput and the system resources that are utilized.
• Improved Miniport driver interface that addresses the needs of high-end storage vendors, particularly host-based RAID and fiber channel vendors.”

If you encounter any of the above-mentioned Blue Screen of Death errors, then here are some troubleshooting options that might help but before you get to them, you can try to perform a System Restore first especially if you have the habit of creating System Restore points. This might fix the problem. To perform a system restore, refer to these steps:

• First, 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.

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first. In addition, you also have to boot into Safe Mode with Networking before you carry out the troubleshooting steps below.

Option 1 – Try to update or rollback your device drivers

The first thing you can try to fix the Storport.sys Blue Screen error is to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties. Note that the main drivers that might be the cause behind the Storport.sys Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
• 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.

Note: You can also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver. Option 2 – Try to recreate the Storport.sys file If the first option didn’t work, the next thing you can do is to recreate the Storport.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named sys and rename it to Storport.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the Storport.sys Blue Screen error is now fixed.

Option 3 – Run System File Checker or SFC scan

System File Checker or 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 to 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.

 Reboot your PC.

Option 4 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the Storport.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Storport.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Booting Windows 10 in safe mode can solve many issues with your computer since Windows will boot just in its basic core and you can safely maintain it, find a solution for issues, etc. Before, entering safe mode was easy and pretty straightforward, during Windows evolution, entering safe mode was somewhat complicated and not being made so directly like once it was but do not worry. Starting Windows in safe mode today is even maybe easier than it was before, it is just not so obvious as it once was. In this article, we will go through several ways how you can boot up Windows in safe mode in order to solve whatever issue is troubling you.

1. Start safe mode from settings

   Open Settings by pressing the ⊞ WINDOWS + I or by just clicking on the Start button and clicking Settings. Go to Update & Security, then Recovery. In Advanced startup, click Restart now. Once your PC reboots, click Troubleshoot, then Advanced options. Select Startup Settings then Restart.

2. Go to safe screen from Sign-in screen

   Click the Shift on your keyboard while clicking on the Power button on the bottom right corner of the screen. Once your PC restarts, click on Troubleshoot, then Advanced options. Select Startup Settings then Restart. After the reboot, select 4 or the F4 on your keyboard to run in Safe Mode. If you choose to use Safe Mode with Networking, select 5 or F5.

3. Start Windows recovery Environment

   Go to the Windows Recovery Environment by doing the following steps: Press on the power button to turn off your device. Press on the button again to turn it on. Once Windows starts, press the power button again for 10 seconds to turn it off. Then press it on again. Upon the reboot, hold on to the power button for 10 seconds to turn it off, then turn it on again. Because you've repeatedly turned on and off your PC, you will be redirected to Windows Recovery Environment. On the pop-up window, click on Troubleshoot, then Advanced options. Select Startup Settings, then Restart. After the reboot, select 4 or the F4 on your keyboard to run in Safe Mode. If you choose to use Safe Mode with Networking, select 5 or F5.

4. Hold SHIFT while pressing RESTART on the start menu

   On the Windows 10 sign-in screen, hold on the SHIFT on your keyboard. While pressing on the key, click on the Power button, then choose Restart on the pop-up menu. Once your PC restarts, click on Troubleshoot, then Advanced options. Select Startup Settings then Restart. After the reboot, select 4 or the F4 on your keyboard to run in Safe Mode. If you choose to use Safe Mode with Networking, select 5 or F5

5. Boot from installation media and choose it in the command prompt

   Create a Windows 10 bootable installation media on any external storage media. Once you do this step, wait for the installation to load. Select your preferred language and click on Next. Click on Repair your computer at the bottom left of the menu. Click on Troubleshoot, then Advanced options. Select Command Prompt - Use the Command Prompt for advanced troubleshooting options. Type in the following command on the prompt: bcdedit /set {default} safeboot minimal Hit Enter and wait for it to tell you that "The operation completed successfully". Exit Command Prompt and click on Continue.

6. Use system configuration tool

   In the Search bar, type in msconfig. Select the Boot tab and under the Boot options, put a check beside Safe boot. Click OK. Reboot PC

7. Press SHIFT + F8

   Press SHIFT + F8 when turning on Windows. This redirects you to Advanced Boot Options Window, then choose to run Windows on Safe Mode

There you have it, 7 different ways to enter safe mode in Windows 10, we hope that any of these tips proved helpful and that you managed to enter the safe mode and fix your Windows issues.

Microsoft wants to escalate the situation from Australia to the EU, what a surprise. Hello all and welcome to another news article, this time we are focusing on Microsoft pushing the EU to accept law proposition from Australia. For all of you who are not familiar with the given situation let me quickly explain. The feud began when the Australian government proposed a new law that targeted Facebook and Google specifically. The government said that it believed that both of the tech giants were using content from news outlets without paying. Have you ever seen the little news snippets that Google or Facebook sometimes show its users to keep them up to date? These are lifted directly from news websites, and the Australian government claimed that this practice meant that people didn't bother visiting the news website. This then staved news websites of revenue. As such, the government put forward a new law that would mean Google and Facebook would have to pay the source website for every time they displayed a news snippet. Facebook responded by removing its Australian news coverage in light of the law. Google, however, put up a fight. It argued that its snippets encouraged people to click on it to read more, thus driving more traffic to the news website. It also said that such a law would be too expensive to maintain in the long run. As such, Google threatened to remove itself from Australia if the law passed. This was likely a scare tactic, as 95 percent of Australian web users use Google; however, it actually opened the door for its rival, Microsoft. Microsoft saw how it could push its own search engine BING to replace google. It of course went and reached the Australian government to assure them that BING is more than capable to fulfill its needs and fully abide by the proposed law. Now Microsoft knows that if this law passes it could see a similar situation happening in Europe and it is pushing it. US News reported on how Microsoft plans to encourage EU countries to adopt this new law too. The company has teamed up with the European Publishers Council and News Media Europe to make the following statement: Publishers might not have the economic strength to negotiate fair and balanced agreements with these gatekeeper tech companies, who might otherwise threaten to walk away from negotiations or exit markets entirely