Fixing “The .NET Framework 4.7 is not supported on this operating system” Error in Windows 10

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.

Windows 11 release date is closing in, some people have tried it via insider build, some have decided not to. It has come to our attention that there is a little website made by BlueEdge that offers a virtual Windows 11 desktop. Opening the Website will put you right inside Windows 11 desktop, now take note that this is not Windows 11, it is a simulation of Microsoft’s newest OS and therefore many things will not work like File Explorer, etc. One thing you can make sure it is working is UI itself, you can see how you do like the new Taskbar, start menu, widgets, and some other things. You can just pop up on the site and check how you do like the overall new look and feel of Windows 11 UI before installing it or trying it. We are sure that many more options will come in time but even now you can get a feel of the newest OS. Windows 11 BlueEdge site: https://win11.blueedge.me/

As you know, Windows PowerShell is a useful command-line utility in Windows 10 that can be used to manage the Local Users and Groups which affirms the multiuser operating system principle of Windows 10. Although there are other GUI-based utilities used to manage the Local Users and Groups, there are some system administrators that would still like to use the command-line utility to manage these Local Users and Groups. So in this post, you will be guided on how exactly you can manage the Local Users and Groups using PowerShell on your Windows 10 computer. To get started, refer to the options provided below to manage both the Local Users and Groups using Windows PowerShell.

Option 1 – Manage the Local Users via Windows PowerShell

• You need to first open Windows PowerShell as an admin. To do that, just tap the Win + X keys and select the Windows PowerShell (Admin) option.
• After opening PowerShell, you need to execute the “Get-LocalUser” cmdlet so that you can find all the details about all the local user accounts in your computer which would include the Account Name, Enabled status, as well as description.

Note: On the other hand, you can also get the customized data about several objects that are related to your account. For instance, if you want to check when was the last time the Local account’s password was set, then you need to execute the “Get-LocalUser -Name root | Select-Object PasswordLastSet” cmdlet. Thus, the structure for this cmdlet is “Get-LocalUser -Name root | Select-Object *”. Here are the objects you can use to get different sorts of data:

• AccountExpires
• Description
• Enabled : True
• FullName
• PasswordChangeableDate
• PasswordExpires
• UserMayChangePassword
• PasswordRequired
• PasswordLastSet
• LastLogon
• Name
• SID
• PrincipalSource
• ObjectClass

Option 2 – Manage the Local User Groups using Windows PowerShell

• Like what you did earlier, open Windows PowerShell as admin and then execute the “Get-LocalGroup” cmdlet so you can get all the information about all the groups of all the local user accounts.
• Now if you want to create a new Local User Group, just execute the “New-LocalGroup -Name <NAME OF THE GROUP> -Description '<ENTER THE DESCRIPTION OF THE GROUP HERE>'” cmdlet.
• And if you want to add Local User Accounts to a specific group, just execute the “Add-LocalGroupMember -Group '<NAME OF THE GROUP' -Member ('NAME 1','NAME 2','<ROLE>') -Verbose” cmdlet. You could also use the “Get-Localuser -Name john | Add-LocalGroupMember -Group '<NAME OF THE GROUP>'” cmdlet for the same purpose.
• If you want to display all the User Accounts of a specific group, just use the “Get-LocalGroupMember –Group ‘ ’” cmdlet.
• Now if you want to remove a local user account from a group, all you have to do is use the “Remove-LocalGroupMember -Group '<NAME OF THE GROUP>' –Member <NAME OF THE LOCAL USER ACCOUNT>” cmdlet.

The TWCU.EXE or TP-LINK Wireless Client Utility is a configuration application required to run wireless adapters successfully. The TP-LINK Wireless Client Utility application only exists on computers that are using the TP-LINK adapters. Upon the installation of this application, the service will be automatically added to the Windows service list that will continuously run in the background. The Twcu.exe is placed at the C:\Program Files\TP-LINKTP-LINK\Wireless Utility folder and is used by TP-LINK to connect to the internet. The name of the main executable file is twcu.exe and can be viewed in the Services tab of the Task Manager. If you are one of the users who just upgraded to Windows 10 from the previous Windows versions, then you’ll most likely see an error saying, “Failed to load the library file!” that has something to do with twcu.exe or TWCU. This error pops up when you go to your desktop and every time you log into your Windows 10 PC. Like pointed out, this error is related to the TP-LINK Wireless Client Utility and every user who is using the TP-LINK Wireless Client Utility is experiencing this problem which may be due to some compatibility issues especially when you start getting this error right after you upgraded to Windows 10. To fix this problem, follow each one of the options given below.

Option 1 – Try running in Compatibility Mode

The best thing you can do is to run the TP-LINK Wireless Client Utility in the compatibility mode since the problem is due to some compatibility issue. To run this utility in the compatibility mode, here’s what you have to do:

• Look for the TP-LINK Wireless Client Utility which should be located on your desktop.
• Once you find it, right-click on it and select Properties from the context menu.
• After that, go to the Compatibility tab and mark the checkbox for “Run this program in compatibility mode for:” and from the drop-down list, select either Windows 7 or Windows 8.
• Click the Apply button and then click OK to save the changes made and check if it has resolved the issue or not.

Option 2 – Try troubleshooting compatibility

This option is almost the same as the first one except it is an alternative way of fixing the TP-LINK Wireless Client Utility in case the first one didn’t work. In this option, you will troubleshoot the compatibility issue of the TP-LINK Wireless Client Utility.

• Look for the TP-LINK Wireless Client Utility which as mentioned, is on your desktop.
• Then right-click on it and select the “Troubleshoot compatibility” from the context menu.
• After that, click on the “Try recommended setting” option. Once the process is done, the error message should be gone.

Universal PnP or plug-and-play monitors use a generic PnP Windows driver. Whenever a user plugs a USB device or monitor into a PC the system will automatically identify the device and it will install the proper driver for smooth running. Generic PnP Monitor in Windows 10 means that Windows 10 installed a monitor driver as the PNP did not recognize the device. This generic PnP monitor driver may not work perfectly like the manufacturer’s one. It can lead to issues like unable to set the best monitor resolution and the screen refresh rate. Therefore, it is important to fix this issue. All of that being said let us fix your PnP display driver issue.

1. Reconnect monitor

   Always try this first, just by unplugging the monitor and then plugging it back may resolve the issue, if the monitor was not detected properly the first time, there are very high chances that this method will resolve the issue.

2. Check if the Device Manager is reporting an error and update the driver

   If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

3. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically install the latest driver for your device, then reboot.

4. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

5. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

Following a two-year investigation by the California Department of Fair Employment and Housing, the state has filed a lawsuit against Activision Blizzard for fostering a "frat boy" culture in which female employees are allegedly subjected to unequal pay and sexual harassment. As reported by Bloomberg, Activision Blizzard is being accused by the state of California of discriminating against female employees at nearly all levels of employment, including in regards to compensation, promotion, assignments, and termination. The state alleges Activision Blizzard’s leadership has failed to address any of these outstanding issues or prevent them from occurring within the workplace. You can read the full details of the lawsuit here. The suit, filed Tuesday in the Los Angeles Superior Court, says Activision Blizzard, which is made up of about 20 percent women, assigns women, and women of color, to "lower paid and lower opportunity levels" with lower starting pay for similar work as their male counterparts. The documents also accuse Activision Blizzard of fostering a "pervasive 'frat boy' workplace culture in the office. Male employees are said to drink "copious amounts of alcohol" as they make their way through cubicles and "often engage in inappropriate behavior toward female employees." Male employees are said to come to work hungover, play video games during work "while delegating their responsibilities to female employees, engage in banter about their sexual encounters, talk openly about female bodies, and joke about rape." The lawsuit also cites one particular incident where a female employee, who was already subjected to intense sexual harassment at the company, committed suicide during a work trip with a male supervisor who allegedly brought inappropriate, sexual items with him on the trip. The lawsuit is asking for an injunction that will force Activision Blizzard to comply with workplace protections, as well as deliver unpaid wages, pay adjustments, back pay, and lost wages and benefits for female employees.

An Activision Blizzard spokesperson sent the following statement in response to the allegations:

We value diversity and strive to foster a workplace that offers inclusivity for everyone. There is no place in our company or industry, or any industry, for sexual misconduct or harassment of any kind. We take every allegation seriously and investigate all claims. In cases related to misconduct, the action was taken to address the issue. The DFEH includes distorted, and in many cases false, descriptions of Blizzard’s past. We have been extremely cooperative with the DFEH throughout their investigation, including providing them with extensive data and ample documentation, but they refused to inform us what issues they perceived. They were required by law to adequately investigate and to have good faith discussions with us to better understand and to resolve any claims or concerns before going to litigation, but they failed to do so. Instead, they rushed to file an inaccurate complaint, as we will demonstrate in court. We are sickened by the reprehensible conduct of the DFEH to drag into the complaint the tragic suicide of an employee whose passing has no bearing whatsoever on this case and with no regard for her grieving family. While we find this behavior to be disgraceful and unprofessional, it is, unfortunately, an example of how they have conducted themselves throughout the course of their investigation. It is this type of irresponsible behavior from unaccountable State bureaucrats that are driving many of the State’s best businesses out of California. The picture the DFEH paints is not the Blizzard workplace of today. Over the past several years and continuing since the initial investigation started, we’ve made significant changes to address company culture and reflect more diversity within our leadership teams. We’ve updated our Code of Conduct to emphasize a strict non-retaliation focus, amplified internal programs and channels for employees to report violations, including the “ASK List” with a confidential integrity hotline, and introduced an Employee Relations team dedicated to investigating employee concerns. We have strengthened our commitment to diversity, equity, and inclusion and combined our Employee Networks at a global level, to provide additional support. Employees must also undergo regular anti-harassment training and have done so for many years. We put tremendous effort into creating fair and rewarding compensation packages and policies that reflect our culture and business, and we strive to pay all employees fairly for equal or substantially similar work. We take a variety of proactive steps to ensure that pay is driven by non-discriminatory factors. For example, we reward and compensate employees based on their performance, and we conduct extensive anti-discrimination training including for those who are part of the compensation process. We are confident in our ability to demonstrate our practices as an equal opportunity employer that fosters a supportive, diverse, and inclusive workplace for our people, and we are committed to continuing this effort in the years to come. It is a shame that the DFEH did not want to engage with us on what they thought they were seeing in their investigation.

Conclusion

We will see how things work out, but I am not too optimistic for Activision Blizzard, truth to be told these reports are really bringing up some disturbing news on the sunlight. I just hope that all responsible will be brought to justice.

One of the common causes of Blue Screen of Death or BSOD errors is system driver files due to varying reasons. So if you encounter a Stop error caused by some system driver files such as isapnp.sys, gv3.sys, storahci.sys, or myfault.sys, on your Windows 10 PC, then this post should help you fix the problem. These system driver files are associated with different error codes. The isapnp.sys file is related to the following error codes:

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

While the gv3.sys file is related to the following BSOD error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

On the other hand, the storahci.sys file is related to these error codes:

• IRQL NOT LESS EQUAL
• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN NONPAGED AREA.

And the myfault.sys file is associated with this error code: SYSTEM SERVICE EXCEPTION. Although this system driver file causes different kinds of Blue Screen errors, some of their potential fixes are quite the same so you need not carry out tons of troubleshooting steps. But before you troubleshoot the problem, you might want to check out System Restore first, especially if you create a System Restore point from time to time. To perform System Restore, follow these steps:

• 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 and boot your computer into Safe Mode.

Option 1 – Use the System Configuration utility

Note that this first fix is only applicable for Blue Screen errors associated with the myfault.sys file.

• In the Cortana Search box, type “MSConfig” and click on the “System Configuration” entry to open it.
• After opening System Configuration, go to the Processes tab.
• Then scroll down and look for the “Digital Line Detection” process and disable it.
• Now restart your computer and check if the Stop error is fixed or not.

Option 2 – Try to update, rollback or disable related device drivers

Incompatible and outdated drivers can also cause computer malfunctioning or crashing as well as Blue Screen errors. To fix that, you can update, roll back or disable the device drivers in your computer.

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• After opening the Device Manager, from the list of device drivers, look for the “WIN ISA Bus Driver” if you are facing a Stop error related to the isapnp.sys file. While you have to look for the Sony Recovery CDs PCG-Z1RAP Series device drivers if you face a Stop error concerning the gv3.sys file. For the storahci.sys, on the other hand, look for any outdated drivers and update them.
• To update or roll back or disable these drivers, just right-click on each one of them, and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the Blue Screen error.

Option 3 – Use System File Checker

One of the built-in tools in Windows that you can use to fix Blue Screen errors is the System File Checker. This built-in command utility can help you restore corrupted or missing files as well as replace bad and corrupted system files. Chances are, any of the aforementioned system driver files might be corrupted so to fix them, use System File Checker.

• First, right-click on the Start button and click on the “Command Prompt (Admin) option.
• Next, type in the sfc /scannow command and hit Enter to execute it.

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.

• Now restart your computer.

Option 4 – 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. You can find it in Settings, under the 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.

Device drivers are needed in order for the hardware and software to communicate in an operating system. Some of these drivers are digitally signed. These kinds of drivers are drivers that are signed by their issuing authority in a way that the end-user or any third party won’t be able to modify them. And there are times when you encounter an error that says, “Windows requires a digitally signed driver” when you try to install or update device drivers. Driver Signing is the process of associating a digital signature with a driver package. Digital signatures are used in Windows device installations to verify the identity of the vendor providing the driver packages as well as to verify the integrity of the driver packages. All the drivers you usually install on your PC from Windows Update, Original Equipment Manufacturers, or some other third-party driver download software and so on must be verified digitally by Microsoft through the digital signature. A digital signature is an electronic security mark that verifies the publisher for the driver and all the relevant information related to it. That’s why Windows won’t run a driver if it isn’t certified by Microsoft, be it a 32-bit or 64-bit system – this is called the Driver Signature Enforcement. The only Kernel-mode drivers that Windows 10 will load are the ones that are digitally signed by the Dev Portal. However, the changes only affect the new installations of the operating system with Secure Boot on while the non-upgraded fresh installations would require drivers that are signed by Microsoft. The “Windows requires a digitally signed driver” error indicates that the driver you are trying to update or install hasn’t been signed digitally by the issuing authority, preventing you from installing or updating it. To resolve this issue, you can try to update the drivers directly from the manufacturer’s site. You could also disable driver signing via Group Policy Editor.

Option 1 – Update the device drivers directly from the manufacturer’s site

The reason why you’re getting the “Windows requires a digitally signed driver” error in the first place is that you might have downloaded the drivers from external media. It could also be that the drivers didn’t update for some time now and the issuing authority changed its policies. Thus, you can try to update the drivers straight from the manufacturer’s website and install them. If this option didn’t work, then you’ll have to disable the driver signing or its recognition in Windows 10. Keep in mind that doing so is not advisable if you have to use the concerned driver.

Option 2 – Disable driver signing via Group Policy Editor

• Tap the Win + R keys to open the Run utility and type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• After that, navigate to this policy setting: User configuration > Administrative templates > System > Driver installation
• Next, double click on the “Code signing for device drivers” entry located on the right pane to open its properties where you’ll see the following description:

“This setting determines how the system responds when a user tries to install device driver files that are not digitally signed. It establishes the least secure response permitted on the systems of users in the group. Users can use the System in Control Panel to select a more secure setting, but when this setting is enabled, the system does not implement any setting less secure than the one the setting established. When you enable this setting, use the drop-down box to specify the desired response. “Ignore” directs the system to proceed with the installation even if it includes unsigned files. “Warn” notifies the user that files are not digitally signed and lets the user decide whether to stop or to proceed with the installation and whether to permit unsigned files to be installed. “Warn” is the default. “Block” directs the system to refuse to install unsigned files. As a result, the installation stops, and none of the files in the driver package are installed. To change driver file security without specifying a setting, use System in Control Panel. Right-click My Computer, click Properties, click the Hardware tab, and then click the Driver Signing button.”

• Now select the radio button for “Enabled” and select Ignore from the drop-down menu under “When Windows detects a driver file without a digital signature”.
• Then click on the Apply and OK buttons to save the changes made. This will get rid of the “Windows requires a digitally signed driver” error but take note that this will also make your system less secure.

Error Code 0x80240020 – What is it?

Error code 0x80240020 is a Windows 10 upgrade error code that affects users who attempt to upgrade their Windows operating system. This may occur due to a particular program that blocks the upgrade from completing. It can also result when other PC issues interfere with the upgrade process by disrupting the ability of Windows Update to download updates on one’s machine. Common symptoms of error code 0x80240020 include the following:

• Message box detailing the presence of error code 0x80240020
• Inability to complete Windows 10 upgrade process

Solution

Error Causes

Upgrade error codes occur when Windows users experience upgrade failure while using Windows Update, the Microsoft Windows Update website, the Microsoft Update website, or the Windows Server Update Services (WSUS) server. Disruption may cause this process to fail, for instance, due to system file corruptions or problems related to the Windows Update services.

Further Information and Manual Repair

To correct issues related to error codes, it is often best to apply manual repair methods. These help Windows users determine the root causes of the error code and provide solutions that permanently fix these issues. For instance, if error code 0x80240020 on your machine is due to an issue within the Windows Update tool, you will need to first verify that this is the problem by using a troubleshooter option found within your machine’s settings. The troubleshooter will detect and fix the issue.

Most of these manual repair methods can be implemented by any Windows user, regardless of their background, technical abilities, or lack thereof. However, in certain cases, technical skills are required. If you have trouble implementing the procedures highlighted below or in any other error code article found on this site, consider getting help from a Windows repair technician or use a powerful automated tool.

Below are details regarding the manual repair methods for fixing error code 0x80240020. Ensure you follow the instructions correctly. After all, any error you make will likely cause further problems on your machine and prevent you from resolving error code 0x80240020 in Windows 10.

Method One: Run Windows Update Troubleshooter

One way to fix error code 0x80240020 is to troubleshoot Windows Update. To do this you will need to access Settings within your machine then simply select the relevant troubleshooting options available. Follow the instructions below:

• Step one: Type Settings within search box near Start button then press Enter
• Step two: In the search box within Settings, type Troubleshooting
• Step three: Select the troubleshooting option
• Step four: Under System and Security, select Fix problems with Windows Update
• Step five: Under Windows Update, select Resolve problems that prevent you from updating Windows.
• Step six: Click Next and wait for the troubleshooter to detect and fix problems

If there are problems with Windows Update, the troubleshooter will be able to fix them. Once this process is complete, restart your PC and then reopen Windows Update. Attempt to upgrade your Windows operating system. If Windows Update completes the process and your machine downloads and runs the upgrade, you have successfully resolved error code 0x80240020.

If, however, there is another upgrade failure and the message box detailing the presence of error code 0x80240020 in Windows 10 appears, you will need to apply another manual repair procedure. Please see below for further details regarding manual repair method two.

Method Two: Use SFC to Scan and Fix Corrupted System Files

Corrupted or missing system files may interfere with your machine’s ability to successfully download an upgrade. For this reason, scan and fix any problems related to system files on your machine using Command Prompt. This manual repair method is often called a System File Check/ Checker (SFC).

• Step one: Right-click Start Menu
• Step two: Select Command Prompt (Admin)
• Step three: Type sfc /scannow

To ensure you follow this procedure correctly, enter the command as it is written above, with a space between “sfc” and “/scannow”. Once missing, corrupted or damaged files are present on your machine, the SFC command will enable Command Prompt to scan and fix these issues.  Wait until the process is complete then reboot your PC.

With your system successfully rebooted, reattempt the Windows 10 upgrade process in Windows Update or on the Windows Update website. If the issue causing error code 0x80240020 was related to problems with system files, you should be able to complete the upgrade after using the SFC tool.

Method Three: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

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.

Check 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:

• GoogleDNS
• CloudflareDNS

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.