Some Steam tips and tricks for easy life

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in 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.

Users are reporting that randomly their screen will just go black for a second and come back. When this happens, it usually distorts any video currently on the screen; sometimes, they can resume working on the PC normally. However, when they view the event logs, they see the error message Display driver nvlddmkm stopped responding and has successfully recovered. In this article, we will address solutions to this issue and how to not have it again.

1. Remove Aura iCUE plugin (applies to only ASUS motherboards)

   Some PC users discovered that iCue adds an Aura plugin for ASUS MOBOs. That, combined with EVGA Precision X1, was causing the error it seems – this was determined when the screen would turn off and on when opening EVGA x1 software. In this case, the issue was resolved by removing the Aura iCUE plugins.

2. Change Power Management mode

   Right-click the battery icon on the notification area on the right of the Taskbar. Select Power Options. In the Power Options window, locate your current Power Plan. Select High performance, if that’s not your current power plan. Now, click on Change plan settings next to it. Now click on Change advanced power settings. Expand PCI Express section. Expand Link State Power Management. Now set power saving to Off for both On battery and Plugged in state. This would fix any issues caused by the low power of the video card. Click Apply > OK to save changes.

3. Update graphics driver

   Go into device manager Expand display adapter section Right-click on adapter Click on update driver Reboot

4. Rollback graphics driver

   Go into device manager Expand display adapter section Right-click on adapter Click on Roll back driver Reboot

5. Uninstall and reinstall graphics card driver

   Go into device manager Expand display adapter section Right-click on adapter Click on Uninstall device Reboot

6. Replace the graphics card

   If everything else failed, replace the graphic card

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.

STOP 0x00000000 Error Code - What is it?

Stop 0x00000000 error code is a type of a Stop error popularly known as a blue screen of death error code. This is a critical error. It can pop up while loading or using the Windows program on your PC. When this error occurs, the computer screen turns blue and you, the user, get locked out of the program. Furthermore, it can also result in sudden system shut down or system freeze. If not fixed timely, the error may start to pop up more and more frequently which then may lead to complete system corruption and system crash.

Solution

Error Causes

The two most common causes for the STOP 0x00000000 error code are:

• Malware infection
• Registry corruption

This is a fatal system error and must be resolved immediately. Delay may lead to system crashes and data loss. And recovering lost data is not easy.

Further Information and Manual Repair

Though this is a fatal error the good news is that it is easy to resolve. To repair the STOP 0x00000000 error on your system, here are some methods that you can try:

Method 1 - Use System Restore to Bring Your Computer Back to its Previous State

To resolve this error on your system, try using the System Restore tool. Use this tool to bring your computer back to its previous state. The Windows System Restore utility is one of the most valuable recovery tools. To use it, simply type System Restore in the search box. Once you find it, click on it and select a restore point to bring your PC back to its normal state. To activate changes, reboot the PC.

Method 2 - Scan for Viruses

If the underlying cause of the Stop 0x00000000 error code is related to malware infection, then you must download a powerful antivirus to resolve it. Run it to scan your entire PC. Make sure you remove all types of malware including adware, spyware, viruses, and Trojan. Once your PC is malware-free, the error will be fixed in no time.

Method 3 - Clean and Repair the Registry

The registry is an important part of the PC. It stores practically all the activities you perform on your system. It saves all the files including both important and unnecessary files such as junk files, cookies, internet history, bad and invalid entries. If these obsolete and unnecessary files are not deleted frequently and keep on accumulating it takes up all the registry space and corrupts it. This results in registry errors like runtime and BSoD errors and sometimes may also lead to disk fragmentation. To resolve it is advisable to repair the registry. This can be done manually but that will take too much time and also require technical expertise. However, another way to resolve it is to download Restoro. This is a user-friendly PC Fixer with a powerful registry cleaner. It removes all obsolete and unnecessary files, cleans the registry and repairs the damaged files, thereby removing the error right away. Click here to download Restoro and resolve Stop 0x00000000 today!

Bad or good news, depending on your view comes from RIOT for their game Valorant. It seems that Riot has decided to enforce Windows 11 TPM 2.0 feature into Valorant running on Windows 11 and there is a rumor that it will be de facto standard and that it will move to Valorant in general no matter on which system it runs. Furthermore, there is a rumor circling around that other developers are also talking about implementing TPM 2.0 requirements so they can harvest advanced security features of Windows 11 in order to prevent hacks and other cheats in their games. This is an interesting point to stand on, on one side, sure, advanced features that will prevent cheating and hacking is a great thing. On other hand denying access to many computers that do not support TPM 2.0 and removing them from the game can be a permanent loss of customers and therefore loss of money. It is a risk to be sure and I am not really sure that alienating gamers is a good choice for long-term income, especially when you will be able to install Windows 11 on an unsupported PC as stated by Microsoft. We will all see how this Riot decision will reflect on their business, as not a big Valorant player myself I am not impacted too much with this decision, but it will be interesting to see if others will indeed go with this trend or they will decide to wait a while until much more PC’s are upgraded.

What is Regsvr32.exe Error?

Regsvr32 (Microsoft Register Server) is a command-line utility in Microsoft Windows Operating System. This is used for registering and unregistering OLE controls such as ActiveX controls and DLLs in the Windows Registry. This is executed as Regsvr32.exe.  The filename extension .exe is the abbreviation for executable.   It is installed in the %systemroot%System32 folder in Windows XP and new Windows versions. The Regsvr32.exe is an error that occurs when you attempt to run Regsvr32.exe to register a 32 bit DLL (Dynamic Link Library) on a 64-bit version of Windows. The error message is displayed as the following:

• Filename.dll is not an executable file and no registration helper is registered for this file type.
• Unrecognized flag: /invalid_flag
• No DLL name specified
• Dll_Name is not an executable file and no registration helper is registered for this file type.
• The module "%1" failed to load.

Solution

Error Causes

There are multiple causes for the Regsvr32.exe error code. These include:

• Invalid entry (command) path
• Active X control errors
• Missing or Damaged .dll files
• Viral infection (Trojans) (.exe can easily get infected by viruses)
• Registry issues

If you come across the Regsvr32.exe error code, it is advisable to repair it immediately before the damage sets in. Since this may occur due to viral infection, it can pose privacy and data security risks to your PC.

Further Information and Manual Repair

Here are solutions that you can implement to resolve the Regsvr32.exe error code on your system:

1. If an invalid entry point is the cause of the error, then simply open an elevated command prompt. If the 32-bit DLL is in the %systemroot%System32 folder, then move it to the %systemroot%SysWoW64 folder. After that run the following command: %systemroot%SysWoW64regsvr32 <full path of the DLL>. This will help resolve the Regsvr32.exe error.
2. If the cause of the error is a viral infection, then you will need to run a powerful antivirus to detect and remove viruses from your system to resolve the Regsvr32.exe error on your system.
3. Nonetheless, if the causes for Regsvr32.exe are either Active X controls or registry corruption, then you will need to scan your computer with different tools to resolve each issue separately.

This can be time-consuming and too many program installations at one time can also slow down your system’s performance. This means you’ll also have to compromise on your PC’s speed.

Repair Regsvr32.exe Error With Restoro

To avoid all this hassle yet repair the Regsvr32.exe error, download Restoro. This is a multi-functional and innovative PC repair tool deployed with multiple utilities in one program including features like a registry cleaner and an Active X controls error fixer. It also functions as a system optimizer. It is a one-stop solution for all your PC-related errors including the Regsvr32.dll error. It is safe, efficient, and user-friendly. It is compatible with all Windows versions. When the RAM overloads it leads to damaged dlls and registry corruption. The registry cleaner utility repairs the damaged dll files and the corrupt registry. It wipes out all the unnecessary files cluttering the RAM including the junk files, invalid registry entries, and temporary files. Restoro also has an Active X controls scanning utility. This utility can be of great use if the Regsvr32.exe error is triggered by Active X control-related issues. Click here to download Restoro and resolve Regsvr32.exe on your computer right away.

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

Error 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.

4. In the Command Prompt, type taskkill /f /im explorer.exe. This will stop the blinking or flashing.
5. 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)
6. 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.
7. 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.
8. Type ren bushell.dll bushell-crash.dll
9. 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.

As you know, the Windows File Explorer is quite a responsive program and contains tons of features. It allows you to do various customizations by changing Settings or changing the value of a Registry key or Group Policy modification. Either way, you will be guided on how you can enable or disable the Status Bar in File Explorer on your Windows 10 computer. The Status Bar is located at the bottom of the File Explorer and shows you how many items are inside the folder and how many items you’ve selected. In addition, it also shows you information about each item and can display items using large thumbnails with just a single click. In order to enable or disable the Status Bar in File Explorer, you can use the two given options below as reference. You can either use the Folder Options or the Registry Editor.

Option 1 – Enable or Disable Status Bar via Folder Options

• Tap the Win + E keys on your keyboard to open File Explorer.
• Then tap the Alt + F keys and click on Options.
• From there, make sure that you are in the View tab and look for the “Show Status Bar” option in the list that gets populated.
• After that, check if the Show Status Bar option is enabled or disabled. It is supposed to be enabled by default so if it is enabled and you want to disable it, just simply uncheck its checkbox otherwise, leave it as it is.
• Now click on Apply and then OK to save the changes made

Option 2 – Enable or Disable Status Bar via Registry Editor

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to pull up Registry Editor.
• Next, navigate to this registry key: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerAdvanced
• Afterward right-click on Advanced and select New > DWORD (32-bit) Value and then input “ShowStatusBar as the name of the newly created DWORD.
• Now double click on the new DWORD and change its value to “0” if you want to disable Status Bar and “1” if you want to enable it.
• Then exit the Registry Editor and restart your computer to apply the changes made.

Mingwm10.dll Error Code - What is it?

Mingwm10.dll is a dynamic link library file. This file is associated with the gaming program called the Adventures of Tintin developed for Windows OS by Ubisoft. Like all other DLL files, Mingwm10.dll file also contains small programs that are used to load and run this gaming program on your PC and several other programs developed by Ubisoft. Mingwm10.dll error code may occur when this file fails to run and load the Adventures of Tintin, the game on your PC. This error may appear on your PC in different formats such as:

• "Mingwm10.dll not found."
• "The file mingwm10.dll is missing."
• "Cannot register mingwm10.dll."
• "Cannot find C:\Windows\System32\mingwm10.dll."
• "Mingwm10.dll Access Violation."
• "Cannot start The Adventures of Tintin The Game. A required component is missing: mingwm10.dll.Please install The Adventures of Tintin The Game again."
• "This application failed to start because mingwm10.dll was not found. Re-installing the application may fix this problem."

Solution

Error Causes

Mingwm10.dll error code is triggered due to a plethora of reasons. These include causes like:

• Registry damage or corruption
• Viral infection
• Hardware failure
• Corrupt or missing Mingwm10.dll file

Though this error is not fatal nonetheless it is advisable to fix it promptly to ensure you are able to access your desired program successfully without any restriction. Please note, this error can become a major PC threat as the underlying causes are registry corruption or viral infection.

Further Information and Manual Repair

Listed below are some of the best, proven, and easy DIY methods to help you resolve the Mingwm10.dll error code on your system. These are simple methods and require no technical expertise or know-how.

Method 1 - Restore the Missing File

As mentioned above DLL are shared files, there is a possibility that you accidentally deleted the Mingwm10.dll file on your system while uninstalling a program developed by Ubisoft. In such an event, the best and the easiest way to fix the error is to check your recycle bin and restore the deleted Mingwm10.dll file on your system.

Method 2 - Download Mingwm10.dll File from a Reliable Website

If you are unable to locate the missing Mingwm10.dll file in the recycle bin, then another method to fix the issue can be to download the Mingwm10.dll file from a trusted website. The reason why we say trusted is that viruses often enter computer systems when users download files from unreliable websites. So, to avoid bigger problems first make sure the site you select to download the Mingwm10.dll file is authorized and trusted.

Method 3 - Update Outdated Drivers

Hardware failure is related to outdated drivers. If the cause of the Mingwm10.dll error code is hardware failure, simply update the outdated drivers to resolve. Since the Mingwm10.dll file is used to run and load Adventures of Tintin, a gaming software program, then most probably the error is caused because of the outdated video card driver. Therefore update it to fix the issue. For this, go to the start menu, type Device Manager in the search bar. Once it opens use the driver update wizard to make updates. The wizard will walk you through the entire process, making the driver update task easy.

Method 4 - Repair the Corrupt Registry

The registry is the part that stores all the information and activities performed on your system. From important files to obsolete files it saves everything. If the obsolete files like the junk files, bad entries, invalid registry keys, and cookies are not removed from the registry frequently, these files accumulate in the registry and corrupt important system files like DLL files, popping error codes like Mingwm10.dll error. To resolve, download Restoro. It is a PC Fixer embedded with a  registry cleaner. The registry cleaner scans and removes all the obsolete files. It cleans the registry and the corrupted system files in just a few clicks, thereby fixing the problem. Click here to download Restoro to resolve the Mingwm10.dll error code on your PC

As you know, Microsoft Edge is the default web browser in Windows 10 operating system. It is a built-in browser that replaced the ancient Internet Explorer for its performance and features. Aside from being the default web browser, it is also set as a default PDF viewer in Windows 10. So if you open a PDF file, it will be automatically opened in the Edge browser even if you have installed a PDF reader on your computer. However, some users recently reported getting an error that says, “Couldn’t open PDF in Edge, Something’s keeping this PDF from the opening” when they tried to open a PDF file or view an internet link that has a downloadable PDF file in the Edge browser. If you are one of these users, read on as this post will help you troubleshoot the problem and fix it. This kind of error mostly occurs if you have installed other PDF viewers on your computer. They could be interrupting Edge while it tries to open the PDF documents. To fix it, check if Microsoft Edge is set as the default PDF viewer or you could also try to clear its browsing cache. In addition, you could also reset or repair Edge. For detailed instructions, refer to the given options below.

Option 1 – Check if Microsoft Edge is set as the default PDF viewer

The first thing you can do is to check if Edge is set as the default PDF viewer. If it’s not, you have to set it as one to fix the problem.

• Open Control Panel and go to Default Programs.
• Then click on the “Associate a file type or protocol with a program” option.
• Next, select the PDF file option and click on Change program.
• After that, select Microsoft Edge in the pop-up window and then select the “Always use this app to open .pdf” option.
• Now click the OK button to set Edge as the default PDF viewer and then check if you can now open the PDF file in the Edge browser.

Option 2 – Clear the browser cache of Microsoft Edge

• Open Microsoft Edge.
• Then click on the three horizontal dots to open the menu.
• From there, click on Settings. And under Settings, click the “Choose what to clear” button under the Clear browsing data section.
• Next, check all the checkboxes and then click the Clear button to clear the browsing data in the Edge browser.
• Restart Edge.

Option 3 – Reset, repair or reinstall Microsoft Edge via Settings

You can reset, repair or reinstall the Edge browser through Settings. If none of it helped, you can try the following:

• Open File Explorer and then go to this path – C:/Users/YourUsername/AppData/Local/Packages

Note: Before you type in the path in the Address bar, make sure that you put your user account name in place with the “YourUsername”.

• Tap Enter to proceed.
• Next, look for the folder named “MicrosoftEdge_8wekyb3d8bbwe” then right-click on it.
• Click on Properties and uncheck the option “Read-only” under the General tab in the Properties window.
• Click on Apply and then OK to save the changes made.
• After that, look for the MicrosoftEdge_8wekyb3d8bbwe folder again and delete it. And if a prompt stating “Folder Access Denied” appears on your screen, just click on the Continue button to proceed – doing so will delete most of the content inside the folder except for the folder named “AC”.
• Restart your PC.
• Now all you have to do is to re-register Microsoft Edge using PowerShell. In the Start Menu, search “Windows PowerShell”.
• Right-click on Windows PowerShell from the search results and select the “Run as administrator” option.
• Type in this command in the PowerShell windows and tap Enter – Cd C:/Users/YourUsername

Note: Once again, make sure that you key in your user account name in place of “YourUsername.

• After that, type in this command and tap Enter – Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml" -Verbose}
• Restart your PC.