Logo

The request failed due to a fatal device hardware error

When you are copying some files from your computer to your hard disk and vice versa or when you have several disks connected to your Windows 10 computer and you suddenly receive an error message saying, “The request failed due to fatal device hardware error”, then this means that there is some issue with the hardware of your computer. This issue might be caused by various reasons but whatever they may be, this post will guide you on how you can fix the “The request failed due to fatal device hardware error”. To fix the error, here are some suggestions that could help.

Option 1 – Check for any hard disk errors

  • On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
  • Next, click on Disk Management on the left side panel.
  • From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.

Option 2 – Run the CHKDSK utility

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including “The request failed due to fatal device hardware error”.

  • Tap the Win + S keys to open the Search box.
  • Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
  • After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

  • Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
  • If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
  • After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
  • Wait until the process is completed and then restart your computer

Option 3 – Verify the hard drive using SMART attributes

In case you don’t know, Windows has a built-in feature of SMART analysis which analyzes the hard drive/SSD and checks all the parameters by performing some minor operations. To use it, follow these steps:

  • Tap the Win + S keys and type “command prompt” in the field then right-click on the related search result and select the “Run as administrator” option.
  • After opening Command Prompt as admin, type the “wmic disk drive get status” command and hit Enter.
  • You should get a result after that, and if you see that it’s “normal”, proceed to the next option below.

Option 4 – Format your hard disk

You can try formatting your drive since this problem also occurs on removable hard drives. In addition, if your drive is not properly initialized, this error will really pop up. Thus, you need to make sure that the hard drive is initialized and that the correct partition style is selected.

  • To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
  • Next, right-click on the drive and select Format.
  • After that, uncheck the “Quick Format” option and then format your drive properly.
  • Now once the formatting process is finished, unplug the drive and plug it back in afterward.
  • Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
  • After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
  • From there, right-click on the drive volume and select Initialize Disk.
  • Next, select the correct partition type and proceed.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Fix Winload.efi file missing error
The Winload.efi file is an Extensible Firmware Interface or EFI file. EFI files are executable files for the firmware of the computers that are mainly based on UEFI and execute the tasks of loading the files to the bootloader of the computer. They are used for a specific set of tasks such as turning on the computer, installing Windows, restarting the computer or resetting it, and so on. This is why the Winload.efi file is a significant file so if it gets corrupted, lost, or damaged, it would be impossible for the Windows operating system to proceed. Here are some errors you can encounter that are related to the Winload.efi file:
  • efi is missing
  • efi cannot be found
  • efi is missing or contains errors
  • This program can’t start because winload.efi is missing from your computer
  • This application requires the file winload.efi, which was not found on this system.
  • There was a problem starting [path]winload.efi. The specified module could not be found.
In addition, the 0xc0000225 , 0xc00000e and 0xc0000001error codes are also associated with the Winload.efi file. Before you start troubleshooting the problem, you can try to perform System Restore first. This will help undo any changes you’ve made in your computer that might have triggered the Blue Screen error. To perform System Restore, here’s what you have to do:
  • First, press 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 your create a System Restore point first.

Option 1 – Try rebuilding the Boot Configuration Data (BCD) and repairing MBR

  • Once you get to the Welcome Screen part, click on Next.
  • Afterwards, click on the Repair your computer option located on the bottom-left part of the window.
  • Then click on Troubleshoot.
  • Next, select the Advanced Options and then Command Prompt.
  • Once Command Prompt has been pulled up, the following commands to rebuild BCD files and repair MBR. Don’t forget to hit Enter right after you type each command.
    • bootrec /repairbcd
    • bootrec /osscan
    • bootrec /repairmbr
  • Once the command line is successful in finding out a Windows installation, hit Y to let it boot from the list which will successfully rebuild BCD.
  • Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Option 2 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve errors related to the Winload.efi file. To disable Secure Boot, here’s what you have to do:
  • First, boot your computer into Windows 10.
  • Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
  • After that, go to the BIOS of your computer.
  • Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
  • Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery and UEFI Firmware Settings.
  • Select the UEFI Firmware Settings which will take you to the BIOS.
  • From there, go to Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
  • Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
  • Save the changes made and exit. Afterward, your computer will reboot.

Option 3 – Run System File Checker scan

You might also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:
  • Hit the Win + R keys 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 computer.

Option 4 – Disable the Early Launch Anti-Malware Protection

  • You need to restart your computer in the Start Menu first while holding down the Shift key on your keyboard.
  • After that, it will restart your computer to Startup Settings.
  • Now ensure that the 8th option is labeled as “Disable early launch anti-malware protection.
  • Then tap the F8 key since the aforementioned option above is listed at number 8. This should launch and load Windows on your PC with the Early Anti-malware protection disabled for that session only when you try to carry out the same task and then check if the error related to the Winload.efi file is now fixed.
Read More
Fixing PowerShell: File cannot be loaded ...
If you are using Windows PowerShell and it suddenly throws an error message saying, “File cannot be loaded because running scripts is disabled on this system”, then read on as this post will guide you on how you can fix this issue your Windows 10 computer. This kind of error in PowerShell is most likely due to the fact that your user account does not have the required permissions to execute the script. Although this does not mean that you need to have administrator-level permissions as it could also indicate that you have to be unrestricted to run these types of PowerShell scripts or cmdlets. Thus, to fix the error and carry out the task, you have to set the execution policy to be unrestricted. And to do that, you need to use the steps provided below as a reference. Step 1: To get started, you have to check what policies are set for the individual user groups on your computer by tapping the Win + X key combination or by right-clicking on the Start button and clicking on Windows PowerShell (Admin). You can also search for PowerShell in the Start Search and then right-click on Windows PowerShell and select Run as administrator. Step 2: If a User Account Control or UAC prompt appears, just click Yes to proceed. Once you’ve pulled up Windows PowerShell, type the following command to get the List of Execution Policy for all the scopes on your computer.
Get-ExecutionPolicy –List
Step 3: After you execute the command, it will give you a list of the User Groups as well as their Execution Policy status, and under the Scope column, look for “LocalMachine”. Once you find its Execution Policy you will notice that it’s either set to Undefined or Restricted. Step 4: Now that you’ve determined the Execution Policy, you need to set it to Unrestricted if it is set to Restricted. To do that, you have to enter the following command in the very same PowerShell window.
Set-ExecutionPolicy Unrestricted
Step 5: After you execute the command, you will see a message that asks for various permissions for which you either have to tap Y to say Yes to each one of the messages individually or tap the A key to say Yes to all the messages to once. However, if the command throws another error, you can just force the Execution Policy to change by executing the following command.
Set-ExecutionPolicy Unrestricted -Force
Step 6: Once you’re done, it will finally set the Execution Policy for the Windows PowerShell scripts as well as cmdlets to be Unrestricted and fix the “File cannot be loaded because running scripts is disabled on this system” error.
Read More
Edge DevTools An error occurred while ...
In case you don’t know, Microsoft Edge, the new default browser of Windows 10, is equipped with the essential tools that are needed to help web developers in testing their websites in the Edge browser. However, it is not without its flaws as there are instances when you could also encounter some errors when using DevTools. One of these errors is the “An error occurred while starting the profiling session” error. You can see this error message in the DevTools Memory Panel, worry not for this post will help you resolve it. A memory panel is one that primarily measures your memory resource usage and compares heap snapshots in different states of code execution. The Memory panel also provides profiling of three different types, such:
  • Head Snapshot
  • Record Allocation timeline
  • Record Allocation profiles
Using a memory panel, you can find issues that affect the page performance in the most common scenarios like bloats and memory leaks. There are two steps you need to carry out to fix this error that’s associated with the Memory Panel of Microsoft Edge (Chromium) DevTools. First, you need to access the Microsoft (R) Diagnostics Hub Standard Collector Service. Second, you need to restart this service. For detailed steps, follow the instructions provided below. Step 1: Access the Microsoft (R) Diagnostic Standard Collector Service To access the Microsoft (R) Diagnostic Standard Collector Service, follow these steps:
  • Tap the Win + R keys to open the Run dialog box.
  • Then type “services.msc” in the field and hit Enter or click OK.
  • This will open the Services Manager. Here, look for the Microsoft (R) Diagnostic Service from the Services panel that opens on the right-hand side.
Step 2: Now restart the Microsoft (R) Diagnostic Hub Standard Collector Service
  • After accessing the Microsoft (R) Diagnostic Standard Collector Service, right-click on it and select the Restart option.
  • Once it’s done, exit the Microsoft Edge Developer Tools as well as the tab.
  • Next, open a new tab and navigate to your page and tap the F12 key.
  • Now, try to check if profiling begins.
Read More
Fix DRIVER_VERIFIER_DMA_VIOLATION Error
In case you don’t know, Driver Verifier is a built-in utility in the Windows 10 operating system. It is the one that ensures the integrity of all the drivers in the system. It can detect any suspicious behaviors of the drivers and if it finds the driver signature of some suspicious activity during runtime, it stops the suspected action by triggering a BSOD or Blue Screen of Death error and one of these Stop errors is the DRIVER_VERIFIER_DMA_VIOLATION error. When you encounter such an error, you will see the following message on your screen:
“Your PC ran into a problem that it couldn’t handle, and now it needs to restart. If you’d like to know more, you can search online later for this error: DRIVER_VERIFIER_DMA_VIOLATION”
There are several ways you can fix this error. You can try to disable the Driver Verifier or run the Hardware troubleshooter. You could also try to update, roll back or uninstall the drivers on your computer. For more details, refer to each one of the options provided below.

Option 1 – Try to disable the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues.
  • Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
  • After that, select the option “Create custom settings”.
  • Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
  • Next, select the option “Select driver names from a list” option.
  • Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
  • Then click on the Finish button.
  • Open Command Prompt as administrator and execute this command – verifier /querysettings
  • The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
  • Open the Command Prompt as admin again and run this command – verifier /reset
  • The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 2 – Try to reinstall or update device drivers of recently installed hardware

If the first few options didn’t work for you, then it’s time 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.
  • 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 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 3 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like DRIVER_VERIFIER_DMA_VIOLATION. It can be found in 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.
Note: You could also run the Hardware and Devices troubleshooter as it could also help in fixing the DRIVER_VERIFIER_DMA_VIOLATION error.

Option 4 – Try running Microsoft’s online Blue Screen Troubleshooter

If running the built-in Blue Screen Troubleshooter didn’t work, you can also try running Microsoft’s online Blue Screen Troubleshooter. All you have to do is go to Microsoft’s website and from there, you will see a simple wizard that will walk you through the troubleshooting process.
Read More
Could not configure one or more components
If you are trying to install or upgrade your Windows 10 computer but suddenly encountered an error message saying, “Windows could not configure one or more system components”, read on as this post will show you how you can fix the problem. You are not alone in experiencing this problem as other users also reported having the same scenario. Some of them reported getting the following error message:
“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”
When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.

Option 1 – Try to remove the IIS from Windows Features

The IIS is installed from the Windows Features and you can find it at Control Panel > Programs. From there, uncheck the checkbox for the Internet Information Services. Once done, click on the OK button to save the changes. Note that this process will get rid of all the related programs, services, and folders from Windows 10. So if you want to, you can just install them later on or use an offline installer from the official site of Microsoft.

Option 2 – Try renaming the inetsrv folder

The next option you can check out to resolve the problem is to rename the “inetsrv” folder. If you have uninstalled IIS from the Windows Features, this should remove the folders as well, however, it didn’t remove the folder then you have to delete the folders that are related to the IIS by following these steps:
  • First, you have to boot into the Advanced Recovery Mode and from there, open Command Prompt.
  • Next, execute this command to rename the folder from this location, C:Windowssystem32inetsrv: rename C:/Windows/system32/inetsrv/inetsrv.old
  • Once done, boot into your computer normally and try to upgrade Windows 10 again, and check if the problem is fixed or not.

Option 3 – Try to move the folders related to IIS to a different drive

  • Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
  • Next, look for the Application Host Helper Service from the list of services and stop it.
  • Once done, take ownership of the “WinSxS” folder and then move the *windows-iis*.*” folders to another drive. You can just search using the “*windows-iis*.*” keyword in the Start Search.
  • Next, tap the Ctrl + X keys and paste the folders to another drive.
  • After that, start the update process for Windows 10 again.
Read More
There is insufficient disk space to ...
If you are trying to copy a folder or file in your Windows 10 computer but encountered an error that says, “There is insufficient disk space to complete operation”, then you’ve come to the right place as this post will walk you through how you can fix the error. This kind of problem could be due to lack of disk space, corrupted disk, and many more. In such cases, this error usually pops up when you move or copy a file or folder to a particular location. There are several potential fixes you can check out to fix this error. You can try to run the Storage Sense or Disk Cleanup or try copying or moving the file in a Clean Boot State. You could also try formatting the given partition to NTFS. For more information, refer to each one of the options provided below.

Option 1 – Try to delete the temporary files

The error could be caused by some temporary or junk files in your computer and so you need to clear them up to fix the problem. You can achieve that using the Storage Sense feature.
  • Open Setting > System > Storage from the WinX Menu.
  • From there, you will see a list of all the local and connected storage devices along with the details on the free space. Make sure that Storage Sense is on.
  • Next, find a link that says “Free Up Space” and click it to open.
  • After that, a screen which is the built-in program in Windows 10 will appear and will scan your computer for the following junk files so you can free up disk space:
    • Windows Upgrade Log Files
    • The system created Windows Error Reporting Files
    • Thumbnails
    • Temporary Internet Files
    • Previous Windows Installation Files
    • Delivery Optimisation Files
    • DirectX Shader Cache
  • Choose the files you want to get rid of and then click on the remove files option. Note that you’ll have an idea of the total size as you select any of the junk files listed above.
  • Now go to the “Free Up Space Now” section and click the Clean now button. This will get rid of all the temporary or junk files in your computer and should hopefully fix the “There is insufficient disk space to complete operation” error.

Option 2 – Restart your computer in a Clean Boot State

If the first options didn’t work and you still see the “There is insufficient disk space to complete operation” error when you copy folder or files, you can try putting your computer in a Clean Boot State and then again.
  • 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.)
  • Now try to connect copy the folder or file once more and check if the error is now gone.

Option 3 – Try formatting the given partition to NTFS

Even though this option may take a lot of your time, it is proven to fix the “There is insufficient disk space to complete operation” error as reported by many users who also went through the same dilemma. So if the removable disk is showing the same error message no matter which computer you insert it, you might have to format the drive with the help of Command Prompt. But before you do that, you must know that all the contents of your drive will be permanently deleted after you format it.
  • Tap Win + R to launch Run.
  • Type in cmd and then tap Enter or click OK to open the Command Prompt.
  • And in the elevated window of Command Prompt, type in the following command:
format F: /fs:ntfs
In the command given above, “F” is the drive letter and “NTFS” is the file system you want. Just remember to replace “F” with the drive letter you want to format as well as the file system you prefer. Brace yourself as this process might take quite a while even if you only have a 4 GB USB drive – so you must not close the window under any circumstances as the drive might get corrupted and wait for the process to finish.
Read More
Troubleshooting Fortnite Connection Issues
It is no secret that Fortnite is one of the most played games in the world. Epic has done a great job offering it to plenty of other platforms with cross-play feature meaning that you can play with your friends no matter on what platform they are on. But how Fortnite is a piece of software which is constantly updated and maintained it is pretty normal to have some bugs or issues from time to time. One of the before-mentioned issues is a connection issue or unable to connect to game servers. In our article, we will go through common fixes and solutions in order to get you back in-game as fast as possible. Keep on reading.

fortnite cannot connectCheck the Epic Games Status page

Check the Epic Games Server Status page to make sure all systems are operational. If the issue you’re experiencing is related to an outage or system-wide issue, you won’t be able to connect to the Epic Games Launcher or Fortnite until it's resolved.

Use a wired connection

Wireless connections are not as stable as wired connections. This means that the signal can be unreliable and result in packet loss, connection problems, or higher latency or ping. Connect directly to your modem or router with an Ethernet cable to eliminate this possibility and have the fastest connection possible.

Disable your firewalls

Often the quickest way to fix connection problems due to firewalls is to temporarily uninstall and/or disable it.

Windows Firewall disable guide:

  1. Click on Start.
  2. Click on Control Panel.
  3. Click on System and Security.
  4. Click on Windows Firewall.
  5. Click on Turn Windows Firewall on or off (You might need to provide the Administrator password at this step)
  6. Under each Network location, select the Turn off Windows Firewall option

Uninstall any other firewalls

Using a third-party firewall may prevent you from being able to connect to the Epic Games Launcher, Fortnite, or another Epic Games product. We recommend removing any third party firewalls temporarily to see if this resolves your issue. If it does resolve the problem, make sure to add the following executables as exceptions to your firewall:

Epic Games Launcher

  • C:\Program Files (x86)\Epic Games\Launcher\Engine\Binaries\Win64\EpicGamesLauncher.exe
  • C:\Program Files (x86)\Epic Games\Launcher\Engine\Binaries\Win32\EpicGamesLauncher.exe

Fortnite

  • C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping.exe
  • C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping_BE.exe
  • C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteClient-Win64-Shipping_EAC.exe
  • C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteLauncher.exe
Contact your firewall manufacturer for instructions on how to add these as exceptions to it as this varies between them.

Unblock your network ports

Network ports allow certain types of data to be successfully sent over a network that is used by our services. If you have any of these blocked, it may result in you being unable to connect to our games or use our services properly. To unblock your ports on your router do the following:

Windows

First, you will need to get your default gateway and internal IP address:

  1. Click on Start.
  2. Type cmd and press Enter.
  3. Type ipconfig and press Enter.
  4. Take note of your Default Gateway and IPv4.

Configuring your router to unblock the ports

  1. Open your web browser.
  2. Type your Default Gateway into the address bar and press Enter. (A common Default Gateway is 192.168.1.1)
  3. You may be asked for a username and password. This varies for each router. Before entering anything, try just hitting OK. If that doesn't work, try the common default username and password below: Username: admin Password: password If these don't work, you can check this website for a list of usernames and passwords based on your router model.
  4. Locate the Port Forwarding page in the administration tool and click on it.
  5. Make sure you have Port Forwarding selected and not Port Triggering as this is completely different.
  6. On this screen, you will need to enter the ports and port ranges below with the correct protocol and local IP of which you took note of above: 80 (TCP/UDP), 433 (TCP), 443 (TCP), 3478 (TCP/UDP), 3479 (TCP/UDP), 5060 (TCP/UDP), 5062 (TCP/UDP), 5222 (TCP), 6250 (TCP/UDP), and12000-65000 (TCP/UDP).
If you have any trouble doing the above on your router, make sure to check out the router manufacturer's support site for additional instructions as these will vary from router to router.

VPN and Proxy Servers

Do NOT use VPN or Proxy Servers. These cause issues that can't be resolved by us without having you disable them. Check out this article for information on how to disable your proxy server.

Switch Domain Name Systems (DNS)

Switching your DNS can result in better connectivity and performance for your internet connection. There are two different DNS services we recommend to have you try if you are having issues with your connection. Below are the followings links with instructions on how to change your DNS:

Epic Games Launcher: Edit your Engine.ini file (Windows only)

Editing these settings can result in better download speeds using the Epic Games Launcher:
  1. Click on Start.
  2. Type %localappdata% and press Enter.
  3. Open the EpicGamesLauncher
  4. Open the Saved
  5. Open the Config
  6. Open the Windows
  7. Open ini and add the following lines to it: [HTTP] HttpTimeout=10 HttpConnectionTimeout=10 HttpReceiveTimeout=10 HttpSendTimeout=10[Portal.BuildPatch] ChunkDownloads=3 ChunkRetries=20 RetryTime=0.5
  8. Save the file and open the Epic Games Launcher.
fortnite gameplay
Read More
Error 0x8007002C - 0x4001E, installation failed in the SECOND_BOOT phase
Recently, a lot of users reported getting several error messages when they upgraded their Windows 10 computers. One of these error messages users encountered during a Windows 10 upgrade is the Error 0x8007002C-0x4001E. if you are one of the users who is facing this error, read on as this post will help you fix it. When you encounter this error, you will see the following error message on your screen:
“We couldn’t install Windows 10 We’ve set your PC back to the way it was before you started installing Windows 10 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.”
To resolve the 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase error, here are some suggestions that might help.

Option 1 – Try flushing 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 flushing 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.

Option 2 – Select the Keep your files option

You can also select the option to perform an in-place upgrade and opt for the “Keep my files” option during an installation as it might make the process a lot smoother and if you need to perform a clean install, you can do so once the setup is completed.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase error. 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.

Option 4 – Try to run Microsoft’s online troubleshooter

Aside from the Windows Update Troubleshooter, you can also run the online troubleshooter of Microsoft as it can help you with Windows 10 upgrade errors.

Option 5 – Perform a clean install

If none of the options worked, you can try to clean install Windows 10. Just make sure that you have the ISO from the official Microsoft Website and then a bootable USB drive to install Windows 10 again. Take note that this will delete all the data from your drive where Windows 10 was installed previously.
Read More
Runtime Error How to Fix

A runtime error is commonly an error that's created after the PC is operating software and encounters a problem of some form. For instance, a runtime error like run-time error code 7 reveals an "out of memory" dilemma.

Solution

Error Cause

Run-time errors are normally brought on by clashes with TSR (Terminate and Stay Resident) applications or additional operating applications, software problems, storage problems, or pc viruses.

Troubleshooting a Run-time Error

First, enter the run-time error signal into a search engine to see what info you will get about the precise runtime issue you are receiving. Next, end - job all running applications and TSRs to make sure these aren't the origin of the issue. You can certainly do so by obtaining the job manager by striking Control Alt Delete.

In case your issue is regularly occurring with a unique program, go to that system programmer's site and obtain any upgrades and patches. If unavailable, try uninstalling the application involved and reinstalling it.

In the event the issue is occurring with the os, you may consider reinstalling it although it is a huge commitment. A much better idea would be to try a fix for both Windows XP or Windows 2,000. It is possible to fix and scan files by typing : sfc / scannow, heading to the Begin switch, Run, and then pushing enter. Make certain to put an area between sfc and the reduce.

You might have an equipment or storage dilemma if these measures have not resolved your run-time errors. If that is the situation, contact the support of the application under consideration for potential support accompanied by the pc or motherboard manufacturer.

Many run-time problems can be solved by upgrading the application that's creating the problem. This is only because the programmer's frequently releasing patches and improvements for their applications as insects are found and repaired.

Storage problems may frequently be fixed by rebooting the pc. Consider a reboot a short-term repair. Rebooting clears the memory but in case your COMPUTER does not have adequate memory for your applications you're operating, or sufficient hard-drive space you'll immediately run out of memory again. Something less than this sum may cause memory issues since the computer's swap file isn't in a position to expand in dimension as required.

To assess the quantity of free area, available My Computer and right-click on the HDD, generally the D: drive. Select Attributes in the menu and see the disc's ability. Perform the disk clean-up function by following prompts and pressing the Disk Clean-up button, if the room is reduced.

You may be getting run-time errors, in case your storage chip is really failing. Eliminating and changing the awful memory chip will solve the difficulty. If you're encountering other runtime-related errors, like an install runtime issue, try cleaning away the portions of the registry with some software solution. 

Read More
Blinking or Flashing Desktop After login - Windows 10 Upgrade

Blinking or Flashing Desktop After login - What does it mean?

Upon updating to Windows 10, some users might encounter a blinking or flashing desktop after logging in. This will result in a repetitive restarting of explorer or you won’t be able to make the start menu and shortcut keys work. In addition, the network icon might not appear in your taskbar as well. Other Windows 10 error messages include error code 0xc000021a.

Solution

Restoro box imageError Causes

Your blinking or flashing desktop after logging in might be the result of problems with the bushell.dll shell extension, which is a part of the Norton Security Suite. Another possible cause for this annoying problem is an issue with your display driver since not all systems will use the same display driver and will depend on what graphics card you use.

Further Information and Manual Repair

In fixing the bothersome blinking or flashing desktop after logging in problem, you can do a manual repair method to address the root problem. You need to be familiar with the Windows command line to successfully go through the process. However, if you are not knowledgeable or confident enough to do this on your own, it would be best to seek help from a professional. Or, you might want to consider using an automated tool to solve the issue.

You need to identify first what’s causing the blinking or flashing of your desktop after login to properly address the issue. The following methods can be done if your issue is caused by bushell.dll shell extension issue:

Method One: Forcefully Terminate Process

  1. Press on Ctrl+Alt+Del then select Task manager
  2. Start a Command Prompt as an administrator by choosing the File menu then Run New Task.
  3. Type exe. Make sure to tick the checkbox “Create this task with administrative privileges.”

NOTE: Text input is most probably affected by the explorer restarts so you might need to repeatedly type some letters or to carefully input texts.

  1. In the Command Prompt, type taskkill /f /im explorer.exe. This will stop the blinking or flashing.
  2. Type cd “Program Files” afterward, type dir /s bushell.dll to locate where the dll is. (For example, purposes, use c:\program files\Norton Security Suite\Engine6422.5.2.15 as the location)
  3. If the dll file is not found, you can try repeating step 5 but this time, use “Program Files (x86)” However, you can proceed with the next step if you already located where the bushell.dll is.
  4. Type cd ”c:\program files\Norton Security Suite\Engine 6422.5.2.15” to change the name of the directory you found the dll in.
  5. Type ren bushell.dll bushell-crash.dll
  6. Restart now the system by typing shutdown /r /f /t o in the command line.

Method Two: Uninstall Programs

  1. Log out then go to the sign in screen
  2. Press the Shift key as you simultaneously click on the Power button on the screen.
  3. Continue pressing on the Shift key as you click
  4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
  5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
  6. Click on the Startup Settings then select
  7. Boot on Safe Mode by pressing 4 on your keyboard.
  8. Log in then press Windows key + X.
  9. Select the Device Manager then expand Display Adapter.
  10. On your Display Adapter, right-click then select
  11. Exit Device Manager
  12. If in case you also have an older Antivirus utility, you should uninstall it as well.
  13. Restart

NOTE: You might need to download the latest Video Driver on a working computer. Save it in a thumb drive then copy and install it on your computer. If in case there is no native Windows 10 driver, you can also download the latest Windows 7 or Windows 8.1 video driver. Afterward, install it in compatibility mode.

Method Three: Use Microsoft System Configuration Utility

  1. Log out then go to the sign in screen
  2. Press the Shift key as you simultaneously click on the Power button on the screen.
  3. Continue pressing on the Shift key as you click
  4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
  5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
  6. Click on the Startup Settings then select
  7. Boot on Safe Mode but this time, choose 5 to start in Safe Mode with networking.
  8. Check if your problem is present or not in Safe Mode. If not, then you are on the right track.
  9. Press on the Windows key + R then type msconfig to start up your exe file.
  10. Click on the Services tab then choose Disable All. Afterward, click on
  11. Once you’re prompted to reboot your computer, go ahead and reboot in Normal Mode. Check if the issue is still present.
  12. If the blinking or flashing desktop after login is gone, then you can just do a process of elimination.
  13. Start-up on your exe again then begin bringing up services a few at a time.
  14. You can turn on all other services except for the following which causes the blinking or flashing desktop after login problem: Problem Reports and Solutions Control Panel Support •Windows Error Reporting Service.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status