Troubleshooting Error 1722

Reddit is one of the most popular websites in the world and how Microsoft is opening doors to everyone in its new store Reddit took a logical step and made a Progressive web application and placed it in it. Being a Progressive web app makes it more familiar and feels like a home experience using it for a lot of Reddit users. Reddit itself has a large community and active topics discussions all the time about anything. Bringing it to Windows as an application is, in my opinion, a great move since as an application it is independent, more light-weighted, and offering some other advantages specifically tied to being a standalone windows application. Everyone familiar with and using the Reddit website will feel right at home in this app and you can start using it right away.

When it comes to downloading and installing games in the Windows operating system, Steam is one of the well-known sources. You can find many big titles in Streams such as PUBG, Heaven Vaults, and a whole lot more. It is undeniably a great source of getting games in the Windows operating systems. However, just like other software, Steam is not immune to errors as you could encounter errors while using it. This isn’t caused by a bad code but also due to reliance on various factors in both respects to the software and hardware. One of these errors is the Application Load Error 5:0000065434. This kind of error can appear when you launch numerous game titles on your Windows 10 computer like Skyrim, Oblivion, Bully, Morrowind, Vortex, and many more. To fix this application error in Steam, you can try to copy the Steam executable file or use the Command Prompt. You could also try to verify the integrity of the game files feature or delete any conflicting files on your computer.

Option 1 – Try copying the Steam executable file

The first thing you can do to fix the error is to copy the executable file of Steam.

• First, right-click on the desktop shortcut of steam located on your Desktop and click on the “Open file location” option.
• After that, copy the executable file for Steam and navigate to the folder of the library of the games which is usually located in SteamSteamAppsCommon
• Now paste the Steam executable file you just copied inside the folder of the game and see if it fixes the error or not.

Option 2 – Try to use the Command Prompt

• In the Start Search, type “command prompt” and right-click on Command Prompt from the search results and then select the “Run as administrator” option.
• After opening Command Prompt as administrator, execute the following command:

cd "C:Program Files (x86)Steamsteamappscommon" mklink "steam.exe" "C:Program Files (x86)Steamsteam.exe"

• The command you entered will create a link between the executable file of Steam to the operating system. Once you see a message that states, “Operation completed successfully”, restart your computer.

Option 3 – Try to use the “Verify integrity of the game files” feature

The next thing you can do to get rid of the error is to use the “Verify integrity of the game files” feature. How? Refer to these steps:

• Open Steam and right-click on the entry of the game where you encountered the error in the Library and then select Properties.
• After that, navigate to the LOCAL FILES tab and click the “VERIFY INTEGRITY OF GAME FILES” button.
• Wait for the process to be completed and see if the feature has helped in fixing the error or not.

Option 4 – Try to delete any conflicting files

The error might be caused by some conflicting files on your computer which is why you have to delete them. To do that, follow these steps:

• Open the Documents folder and look for the folder created by the game that’s throwing the error. For instance, it could be stored in the “My Games” folder.
• Next, delete the folder and then try to launch the game again and see if the error is now fixed.

What is Runtime Error 339?

Runtime Error 339 is a common error code format that appears when a computer overloads with too much data. However, in some cases, it may occur due to the missing registry keys, DLL files, or during installation. It may lead some programs to shut down all of a sudden and may also corrupt files on the system.

Solution

Download Available to Completely Repair Runtime Error 339

Error Causes

This error code is alarming as it is a critical sign of an unstable system followed by improper maintenance of the computer. The potential risks associated with the Runtime Error 339 include:

• System startup issues
• Slow PC performance
• System crash and failure
• System file corruption

Therefore, to avoid these risks and system failure, it is advisable to fix the runtime error 339 immediately.

Further Information and Manual Repair

If you have a Runtime Error 339 issue on your computer, here is a great way how you can fix it right away:

Scan For Viruses

Improper maintenance of the computer indicates that your system might be exposed to viruses and malware. Viruses can modify the Windows registry and lead to Runtime Error 339. Therefore, first, it is important to scan for viruses on your PC.

Identify Software that Causes Errors

Scanning will help you identify software that produces this error on your PC. Once you identify them, either uninstall them or update the program. To uninstall the program, go to the Control Panel and then click on the Add/Remove program if you have Windows XP, if not then click on the Programs and Features item. Now delete the program from your system.

Obtain the Latest Version of the Installer and Re-install the Deleted Program

Once you get your hands on the latest version of the installer, run it on your system by following the on-screen instructions. Install the program. There is also another way to fix Runtime Error 339 and that is by downloading the Runtime Error tool.

Use a Professional Runtime Error Fixer Tool

To fix the error you can also use a professional Runtime Error fixer tool to scan for viruses on your PC. It is available for free download here. Download the tool and install it on your computer. Simply scan your PC after installation. Click the repair button once the scan is complete. This tool fixes problems in just a few minutes.

Update and Shutdown/Restart is not working. As you have probably noticed, every time a new update is released and is downloaded on your Windows 10 computer, the operating system replaces the Restart and Shut down button with “Update and Restart” as well as “Update and Shut down”. This is most likely done so that you won’t miss the update. However, some users noticed that there are times when these buttons still continue to display the same message even if they’ve already performed the required operations such as shutting down or restarting their PCs. Cases like this happen when an update wasn’t installed properly or has failed which is why your computer keeps on prompting you to Update and Shutdown every time. To fix this dilemma, follow the options laid out below.

Option 1 – Try restarting the File Explorer

Restarting the File Explorer can definitely help you fix lots of issues especially when there is some issue with the user interface including this one.

• On the right side of the Taskbar, right-click on any open spot.
• Then click on Task Manager.
• Next, scroll down until you see Windows Explorer.
• After that, right-click on it and select Restart.
• If you are able to kill its process, you have to tap the Win + R keys to open the Run dialog box and type “explorer.exe” in the field, and hit Enter to launch the Windows Explorer.

Option 2 – Try running the Windows Update Troubleshooter

As you know, Windows 10 has various auto-repair built-in tools to help users fix small issues which used to get fixed manually. And in this case, you will need the Windows Update Troubleshooter to fix the issue.

• Go to Settings and click on Update and Security.
• From there, click Troubleshoot and click on Windows Update and then click the “Run the troubleshooter” option.
• After that, it will try to detect and automatically fix common issues in the Windows Updates which can be resolved by Windows itself. Note that the process may take several minutes before it completes so you need to wait until it’s done. Once it’s done, in case you have some pending update that wasn’t realized by the system early on, it will apply the fix right away and restart the Windows Update service.

Option 3 – Try setting the Power button to Shut down

In case the first two options didn’t work out, you can try changing what the power button does. To do that, refer to these steps:

• Go to Control Panel > Power Options.
• From there, select the “Choose what the power buttons do” option from the left side.
• Then set the Power button setting the “When I press the power button” option to “Shut down”. After that, it will shut your computer down without installing the updates but obviously, this is only a temporary fix.

Option 4 – Turn off your PC instantly without updating it

• Tap the Win + R keys to open the Run dialog box.
• Type in “shutdown -s -f -t 0” in the field and hit Enter if you really want to turn off your computer without any delay.
• You could also tap the Ctrl + Alt + Del keys and select Shut down from the bottom right menu.

Just like the third option, this is also only a temporary fix.

Option 5 – Try running the Windows Module Installer

The Windows Module Installer is a built-in service in Windows 10 that allows you to fix the stuck Windows Updates in your computer. To use it, follow these steps:

• In the Cortana search box, type in “cmd” and from the search results that appear, right-click on Command Prompt and select the “Run as administrator” option from the context menu.
• Once you’ve opened Command Prompt as admin, type the SC config trustedinstaller start=auto command and tap Enter.
• After the command is executed, you will see the “[SC] ChangeServiceConfig SUCCESS” message displayed on the Command Prompt console.
• Now exit Command Prompt and then check if the buttons are now back to normal.

Option 6 – Put your PC in a Clean Boot State

• 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” checkbox and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)

After putting your PC in a Clean Boot State, try creating a system restore point and see if the problem still occurs. Clean Boot troubleshooting is designed to help you isolate the problem. For you to execute a clean boot troubleshooting, you must do a couple of actions (the steps are given above) and then restart your PC after every action. You might have to disable one third-party app after the other to really isolate the issue. And once you’ve narrowed down the problem, you can either disable the third-party app that’s causing the problem or remove it. Note that you must switch your PC back into the Normal Startup mode after you’re done troubleshooting the problem. Here’s how you can do it:

• From the “Start” menu, go to System Configuration.
• After that, switch to the General tab and click the option for “Normal Startup”.
• Next, go to the Services tab and clear the checkbox for “Hide all Microsoft services”.
• Then find and click “Enable all” and if prompted, you have to confirm.
• Afterward, go to the Task Manager and enable all the Startup programs and confirm the action.
• Restart your PC when prompted.

As you know, games with good graphics and fast play are definitely resource-intensive and can consume a lot of storage space on your computer. Because of that, they have to be compressed before it gets downloaded to your computer and then unpacked to the hard drive before it gets installed. However, if an error occurs in your computer’s RAM during the installation process or if your hard disk does not have enough memory to handle the process, then you might encounter the isDone.dll error which states:

“An error occurred when unpacking, Unarc.dll returned error code -1, ERROR: archive data corrupted (decompression fails).”

If you encounter the isDone.dll error message on your Windows 10 computer, then read on as this post will show you how you can fix it. This error has something to do with the incomplete installation of PC games or files of larger size. The ISDone.dll error appears due to faulty Unarc.dll file residing in the System32 folder on 32-bit operating systems and the SysWOW64 folder on 64-bit systems. So, if you see this error message, then, it means your computer was not able to read installation archive files.

What is Unarc.dll file?

Unarc.dll is a dynamic link library for Windows. Some applications or games require this file to function properly. So, if it goes missing or, an error occurs when you start a game or an application, you may get various kinds of errors. ISDone.dll error while playing games on PC

Option 1 – Try to reinstall the game

The isDone.dll error could also be caused by the installation of an unknown application. Or it could also be caused by an outdated or corrupted application. In other words, if the game you are trying to install is broken or corrupted, then it’s no wonder why you’re getting the isDone.dll error. To fix this, make sure that you download the latest updated version of the game and then try to install it again and see if the problem is resolved or not.

Option 2 – Try to re-register the .dll file using the Regsvr32 tool

• The first thing you have to do is to locate the DLL file named dll on your computer and rename it to Unarc-bak.dll.
• Next, copy the Unarc.dll file from another well-functioning computer and save it on your desktop.
• After that, move the DLL file you just copied to the System32 folder if you are using a 32-bit operating system, or the SysWOW64 folder if you are using a 64-bit operating system.
• Now you have to register the new DLL file and you can do that using Windows PowerShell.
• Open Windows PowerShell and then execute this command if you have placed the DLL file in the System32 folder: regsvr32 %systemroot%System32unarc.dll
• On the other hand, if you have placed the DLL file in the SysWOW64 folder, then execute this command: regsvr32 %systemroot%SysWOW64unarc.dll
• Once you’re done, a message will be displayed saying that the DLL file was registered.
• Restart your computer and check if the problem is now fixed.

Option 3 – Troubleshoot the isDone.dll error in a Clean Boot State

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

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

Option 4 – Try updating or reinstalling your Graphics drivers

Updating or reinstalling the Graphics drivers in your computer can also help in resolving compatibility issues between the operating system and the driver that might have caused the isDone.dll error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 5 – Try scanning your computer using Windows Defender

The isDone.dll error might also be infected with malware or virus and to eliminate it, you have to scan your computer using security programs like Windows Defender.

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

From photo editing and compositing to digital painting, animation, and graphic design you can do it all in Photoshop. Bring ideas to life across desktop and iPad. Magically transform images with the power of AI. Learn new skills and share your projects via Livestream. Started as a photo editing application, photoshop has surpassed the original ideas and designs in the following years growing with each release and including more tools and flexibility not matched in other applications. Photoshop was the first to introduce many new features and set standards for other applications. How years have passed product grew and innovation was pushed forward, it took some time but eventually, photoshop was able to set itself as the industry-standard application for pixel editing and it holds that position even today. Throughout the world artist all over the globe are using it to create digital art in various fields be that illustrations, film, photography, texturing, etc. Its vast majority of tools and possibilities as well as its extensibility with plugins, actions, brushes have cemented it in the highest place in any designer or artist toolkit. Today you can get it as a part of a creative suite for a monthly fee on the official adobe website and even if you do not need other creative suite applications photoshop is worth the fee alone. Simply you have to try it, learn it, and then harvest its power. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

One of the most common brands of GPUs that comes in a large number of computers is AMD’s Radeon Graphics processing units. AMD included the Radeon Settings panel so that users can control how the hardware functions. However, as of late, a lot of users reported that the Radeon Settings panel throws an error that says, “Radeon Settings are currently not available. Please try again after connecting AMD graphics” when they try to use it. This kind of error in the Radeon Settings panel is most likely caused by either corrupted drivers or incompatible drivers. If you are one of the users who are facing this problem, worry not for this post will guide you in fixing this error. You can either use the Device Driver Uninstaller or change the driver version. For more details, make use of the options provided below.

Option 1 – Try to use the Device Driver Uninstaller

The first thing you can do to fix the problem is to uninstall the AMD Radeon drivers by using the Device Driver Uninstaller software. After you’ve uninstalled the AMD Radeon drivers using this software, go to the official website of AMD to download the AMD Radeon drivers. Once you’ve downloaded them, you can install them by simply running the executable file. Once the installation of the new AMD Radeon drivers is done, try to open the Radeon Settings panel and see if the error is now fixed or not. If not, refer to the next given option below.

Option 2 – Try changing the Driver version

If you have followed the instructions in the first option then you can proceed to the next given steps below.

• Now that you’ve completely uninstalled the AMD Radeon drivers and reinstalled their latest working versions, check if the drivers are still updating. If they are, you need to stop them.
• To disable the drivers being automatically updated, you need to go to the Group Policy Editor by tapping the Win + R keys to open the Run utility and then type “gpedit.msc” in the field and tap Enter or click OK.
• After opening the Group Policy Editor, navigate to this policy setting: Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions
• From there, double click on the “Prevent installation of devices that match any of these device IDs” policy setting to open a new window, and from this window, you will see the following description of the setting:

“This policy setting allows you to specify a list of Plug and Play hardware IDs and compatible IDs for devices that Windows is prevented from installing. This policy setting takes precedence over any other policy setting that allows Windows to install a device. If you enable this policy setting Windows is prevented from installing a device whose hardware ID or compatible ID appears in the list you create. If you enable this policy setting on a remote desktop server the policy setting affects the redirection of the specified devices from a remote desktop client to the remote desktop server. If you disable or do not configure this policy setting devices can be installed and updated as allowed or prevented by other policy settings.”

• Now set the radio button of the policy setting to “Enabled”. This will turn off the delete confirmation prompt. Note that setting the radio button to either Not Configured or Disabled will turn off the driver being automatically updated.
• Next, click on the Show button under the Options section. And in the field that pops up, type in the Hardware ID of your GPU and click OK. You can find the GPU’s Hardware ID under this location: Device Manager > <DEVICE NAME> Properties > Details > Hardware IDs
• Once you’re done, click the Apply and OK buttons to save the changes made.
• Close the Group Policy Editor and restart your PC and see if the “Radeon Settings are currently not available. Please try again after connecting AMD graphics” error is now fixed.

Strangely enough, Windows 11 does not feature any typical icon on its desktop when installed. No My PC, no Recycle Bin, nothing, just plain and clean wallpaper. Personally, I like this clean look and feel but of course, there are a lot of users that are used to have some system-related icons on their desktop for easy access. Do not sweat, we will turn them back on with ease. The best part is that you can choose which one would you like. So let’s dive right into it and get the icons back for the old Windows feel and look.

Showing selected Icons desktop

1. Right-click on Desktop and select Personalize
2. Select Themes from the list of personalization items
3. Inside themes scroll down and click on Desktop Icon Settings
4. Desktop Icon Settings will open and inside it, place checkmarks beside icons that you would like to appear on the desktop and click OK
5. Close settings

As always settings and choices will be automatically applied and icons will appear right away on the desktop.

If you are trying to install or update Microsoft Edge on your Windows 10 computer but ended up getting HTTP Error 500 or Error 0x8004xxxx or 0x8007xxxx, then you’ve come to the right place as this post will help you sort this problem out. The aforementioned errors when either installing or updating the Edge browser occur due to a Network issue. There is actually a range of error codes that are associated with the network connection issue. These error codes include Error 500 or 0x80010108, 0x80040801, 0x80042193, 0x80042194, 0x800421F4, 0x800421F6, 0x800421F7, 0x800421F8, 0x80072742, 0x80072EE2, 0x80072EE7, 0x80072EFD, and 0x80072EFE. To fix them, there are several options you can try. You can try to run the Network Adapter troubleshooter or update or reset the Network Adapter as well as check and the proxy configuration.

Option 1- Try updating the Network Adapter Driver

Follow the steps below to update your Network Adapter Driver:

• Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
• From there, expand the list of all the network drives and update each one of them.

Note: If updating the network drivers didn’t help in fixing the problem, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.

Option 2 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 3 – Try to reset the Network Adapter

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Option 4 – Try to fix the Proxy Settings

• In the Cortana search box, search for Internet Explorer and then click on the related search result.
• After that, tap the Win + T keys on your keyboard and click on Internet Options.
• Next, navigate to the Connections tab and click on LAN Settings.
• Then click on the Advanced button and delete all the entries in the list generated in the Exceptions section. And if the Advanced button is disabled because the “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)” option is disabled then you are good to go. Now proceed to the next step.
• Tap the Win + X keys or right-click on the Start button and select Command Prompt (Admin) or you could also search for “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• If a User Account Control appears, click on Yes to proceed. After that, type each one of the commands listed below, and don’t forget to hit Enter after you type each one of them.
  • netsh winhttp reset proxy
  • net stop wuauserv
  • net start wuauserv

• Now restart your computer and check if the problem is fixed or not by installing or updating Microsoft Edge again.