Fix Windows Update Error Code 0x80246017

Error 0x8000ffff prevents you from using the Microsoft store. Altho it is not a critical error that will break Windows, it is annoying enough that will require fixing so we can use the store once again and install apps when we want to. Interesting thing is that this error was present inside Windows 10 as well causing some annoyance, you think Microsoft would learn, and then you see reality. Anyway, we have not come here to bash Microsoft, we came to solve errors. So there are several problems that can cause this error like issues with accessing the Microsoft servers, corrupt system files, settings being misconfigured, malware infections, or conflicting applications. We will cover all solutions for each scenario taking approaches from most simple solutions to more complex ones. Follow the guide and let's fix this annoyance.

Wait for Microsoft's servers to become accessible

Yes, just wait. If the problem is tied to Microsoft servers having heavy load or being temporarily down there is not much you can do except for their tech team to resolve the issue. Go to Twitter or Facebook and check the Microsoft page to see if anyone else has this issue, if several people are reporting the same error then it is due to server problems. In this case, the only thing you can do is to wait.

Run troubleshooter

If servers are working fine then the issue is within your system so let's get down to fixing. Most simple and easiest solution is to let Windows try and resolve the problem by itself. We will use troubleshooter for this, Windows's integrated fixing solution: Press ⊞ WINDOWS + I to open the settings app Click on System in the left panel, then on Troubleshoot on the right Click on Other troubleshooters In most Frequent section find Windows Update and click on the Run button Wait for the troubleshooter to finish and follow on-screen instructions

Clear Store cache

If the troubleshooter has not found the issue or was unable to repair it, the next step is cleaning the Microsoft store cache in order to eliminate corrupted or partial cache files. Press ⊞ WINDOWS + R to open the run dialog In run dialog type in: wsreset and press OK or press ENTER A black screen will appear and it will not give any kind of feedback about progress, so it might seem like Windows has frozen, but do not panic nor try to do anything, this kind of behavior is normal, just wait for the process to finish and once it is done Microsoft store will launch with the cleared cache.

Disable Proxy

Proxy setting can interfere with establishing a connection to the store servers and if previous solutions have not worked we will check proxy next. Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type: inetcpl.cpl and hit ENTER or press OK button Inside Internet Properties click on the Connections tab and then on LAN settings Uncheck the box next to Use a proxy server for your LAN and click on OK

Turn off antivirus

If nothing worked so far, turn off your anti-virus software, there is a slight possibility that your antivirus is misconfigured or preventing the system from accessing the store. Turn off antivirus and firewall to make sure that this is not an issue.

Delete the software distribution folder

So, we have tried a lot of things, and the error still persists? Let's then go to the next step and delete the software distribution folder in order to be remade new so we can eliminate corruption in the folder itself. To do this follow the guide: Press ⊞ WINDOWS + S to open the search menu Inside search type in Windows terminal, right-click on the terminal and click on Run as administrator. Confirm with YES on UAC prompt pop up Inside terminal press CTRL + SHIFT + 2 to open command prompt inside command prompt type in: net stop wuauserv and press ENTER Then type in: net stop bits followed with ENTER Next press ⊞ WINDOWS + R to open the run dialog Inside run dialog type in C:\Windows\SoftwareDistribution and press the OK button or ENTER File Explorer will open and you will find yourself inside SoftwareDistribution folder. Press CTRL + A to select all files inside Press on the delete icon or press DEL, confirm with YES Once all files are deleted, the system will redownload new ones.

Enable Cryptographic service

Windows 11 has come with a cryptographic service that aims to make your computer more secure but if the service is turned off it can be the cause of 0x8000ffff error. In order to turn this service back ON, follow the guide: Press ⊞ WINDOWS + R to open the run dialog In run dialog type in services.msc and press ENTER or click on the OK button In the list find Cryptographic Services and double click on it Inside properties click on Startup type dropdown menu and select Automatic from the list Click on the Start button to run service and then on the OK button to save the changes

Run SFC scan

SFC is an internal Windows tool for fixing corrupt system files, application will scan all system files and repair ones that are corrupted. To run an SFC scan do the following: Press ⊞ WINDOWS + S to open the search menu Inside search type in Windows terminal, right-click on the terminal and click on Run as administrator. Confirm with YES on UAC prompt pop up Inside terminal press CTRL + SHIFT + 2 to open command prompt inside command prompt type in: SFC /scannow and press ENTER Wait for the whole process to finish and reboot your system

Run DISM scan

Similar to SFC, DISM scan will scan your system Windows image and if required it will repair it. Press ⊞ WINDOWS + S to open the search menu Inside search type in Windows terminal, right-click on the terminal and click on Run as administrator. Confirm with YES on UAC prompt pop up Inside terminal press CTRL + SHIFT + 2 to open command prompt inside command prompt type in: DISM /Online /Cleanup-Image /RestoreHealth and press ENTER Wait for the whole process to finish and restart your computer

If you receive an error message saying, “Windows Update cannot currently check for updates because updates on this computer are controlled”, while trying to change the Windows Update preferences or manually update, then read on as this post will guide you in fixing it. You can mostly encounter this error in managed systems where an Administrator controls the permission on the operating system. The reason why you are not able to modify the Windows Update preferences or manually update your system is that a group policy prevents you from doing so and that the only user who can do these things is none other than the administrator of the system. Troubleshooting this kind of problem is the same as when you troubleshoot an error message that says, “Some settings are managed by your organization”. In such cases, you need to check both the Windows Update Group Policy and Registry settings. If you’re just a standard user, you have to contact your system administrator regarding this issue and if you are the administrator, you can make adjustments to the system settings via the Registry Editor and the Group Policy Editor. Refer to the instructions given below for detailed instructions.

Option 1 – via the Registry Editor

If you are using the Home edition of Windows 10 and you want to change the policy for non-admin users on your local computer, then you can use the Registry Editor for that. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows

• From there, look for the key named “WindowsUpdate” in the Windows folder and if it does not exist, you can just right-click on the Windows folder and select New > Key.
• Now name the new key “WindowsUpdate” and create a new sub-key under the newly created key and input “AU” as its name.
• Keep AU selected and then right-click anywhere in the right pane and select New > DWORD (32-bit) Value.
• Then name the Value as “AUOptions” and right-click on AUOptions and select Modify.
• Next, change the value of the Value data to “5” and click OK to save the changes made to the settings. Note that the Value Data of 5 refers to the policy to allow the local admin to choose the setting.
• Now restart your computer once you’re done and check if non-admin users can now modify the Windows Update settings or update Windows.

Option 2 – via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” and hit Enter to open the Group Policy Editor.
• Next, navigate to this folder: Computer Configuration > Administrative Templates > Windows Components > Windows Update.
• Now look for the “Configure Automatic Updates” policy on the right pane and double click on it to open its Properties.
• After that, shift the Radio button to “Enabled” and from the drop-down menu for Configure automatic updating, select option 5: Allow local admin to choose the setting.
• Then click on Apply and OK to save the changes made to the settings.
• Restart your computer and check if the problem’s fixed or not.

If you open any program in your Windows 10 PC such as Outlook and suddenly get an error message saying, “Failed to register a VB Script dll. Reinstall or run Regsvr32.exe Vbscript.dll to self-register”, read on, as this post will guide you on what you can do to fix it. The obvious solution to this problem is by re-registering the “vbscript.dll” file on your computer. Refer to the instructions given below to re-register the VB Script DLL file and to fix the error.

• Step 1: Open the Command Prompt as an administrator from the WinX Menu.
• Step 2: After opening Command Prompt, type in the following command and tap Enter on your keyboard.

regsvr32.exe vbscript.dll

• Step 3: Once you enter the command, it will re-register the VB Script DLL file using the Windows OS tool called Regsvr32 or regsvr32.exe. This tool is a command-line utility used to register and unregister OLE controls such as DLL and ActiveX (OCX) controls in the Windows environment. After the execution of the command, you should see the following pop-up on your screen which means the re-registering of the concerned DLL file has succeeded.

On the other hand, if re-registering the DLL file didn’t work, then you can try logging in using an administrator account and then register the DLL file again or you could also use the System File Checker to figure out what the problem really is and automatically fix it. System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

The Snapping feature was introduced as an essential part of Windows 11 and I like it very much, it lets you organize your opened windows much faster and with more control. However, some people do not like the feature, worry not because you can turn it off, or if you prefer you can just remove the showing layout option that is shown when hovering over Minimize/Maximize button.

Removing options all together

To completely turn off Snap layout in Windows 11 follow these steps

1. Open Windows 11 settings by pressing ⊞ Windows + I
2. Select System on the left part of the screen
3. In System options select Multitasking
4. At the top of Multitasking Click on the switch next to Snap Windows
5. Close settings

Changes will be automatically applied and you will no longer have Snap layout functionality.

Removing layout graphic from Snapping feature

If you like the snap Layouts feature but are not very fond of the layout graphic that is popping up each time you hover over Minimize/Maximize button do not worry, there is an option to turn just that off and keep the feature itself.

1. Open Windows 11 settings by pressing ⊞ Windows + I
2. Select System on the left part of the screen
3. In System options select Multitasking
4. Click on the Snap Windows menu
5. Deactivate Show Snap Layouts When I Hover over a Window’s Maximize button
6. Close settings

Now you will be able to use the Snap Layout feature without layout graphics showing. If you want to reverse any of these options and go back to standard-setting, just follow the steps and turn features ON.

In case you don’t know, new support has been added by Microsoft to Windows 10 that now allows users to turn off or on the Mobile Hotspot remotely. The Mobile Hotspot feature, known earlier as “Virtual Networks”, was first introduced with the initial release of Windows 10. With this new feature to remotely turn on or off the Mobile Hotspot in Windows 10, users can just use the Bluetooth on their mobile phones to turn off or on the Mobile Hotspot even when their Windows 10 computers are out of their reach. To turn off or on the Mobile Hotspot feature in your Windows 10 computer remotely, there are two options you can try. First, you can do it using the Windows 10 settings app or using the Registry Editor. To get started, refer to the following options.

Option 1 – Turn off or on the Mobile Hotspot remotely via Windows 10 Settings app

• First, you need to open the Windows 10 Settings app and from there go to Network & Internet and then go to the Mobile Hotspot section.
• After that, scroll down to the “Turn on remotely” section.
• Once done, make sure that the toggle button is set to ON and that the Bluetooth of both devices is turned on and paired as well. This should enable the feature to turn on or off the mobile hotspot remotely.

Option 2 – Turn off or on the Mobile Hotspot remotely via Registry Editor

Before you get started with the second option, make sure that you create a System Restore point first. Once done, proceed to the following steps:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor.
• Next, navigate to this registry path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWcmSvcTethering
• From there, look for the DWORD named “RemoteStartupDisabled” and set its Value data to be “0”. This will enable the feature that will allow you to remotely turn on or off the mobile hotspot in your Windows 10 computer. To disable it, just set its Value data to “1”.

Error 0x8004210A - What is it?

0x8004210A is a typical POP3 email error message. This error may sometimes occur when you try to check your Post Office Protocol 3 (POP3) email account. 0x8004210A error code hampers your ability to both send and receive e-mails on your Outlook account. Error 0x8004210A is displayed in any one of the following formats on your PC:

The operation timed out waiting for a response from the receiving (POP) server 0x8004210a Task 'SMTP server name - Sending and Receiving reported error' (0x8004210A): 'The operation timed out waiting for a response from the receiving (POP) server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

Error Causes

Error 0x8004210A occurs due to several reasons. However, some of the most common reasons include:

• Wrong port number for the POP incoming server
• Your connection to the mail server is too slow
• Incoming and outgoing emails are being scanned and stopped by an antivirus installed on your system
• The Outlook send and receive job is being blocked by Firewall
• You are sending and receiving large series of emails or large email attachments
• Registry issues

No matter what the cause of this error is, to resume email communication via Outlook and to ensure your work productivity is not affected, it is recommended that you resolve this 0x8004210A error code on your PC immediately.

Further Information and Manual Repair

To fix error 0x8004210A, here are some of the most efficient and easy manual methods that you can try:

Method 1

If the cause of the error is related to the internet connection then here’s what you need to do. Try freeing up your internet connection by closing any other online activities in progress or downloads being carried on your system.

Method 2

Try to increase your server time-out periods. To do this, go to the Outlook File menu and choose account settings. Now double click on your email account and more settings. Now click advanced and increase your server timeout period to resolve.

Method 3

If you are trying to send or receive large and heavy emails on your Outlook account, the error 0x8004210A may pop up. This happens because when transferring heavy files the email account automatically locks until the task is complete, however, if it takes more time the next Send and Receive job starts while the first one is still not complete. In such an event, the email server then times out and shows you the error. Therefore to resolve, you will have to show patience. Simply wait for the large email to be sent or received before you start sending another email.

Method 4

If the antivirus installed on your system is the reason for the error pop up, then disable it for a while until the operation is complete. Then enable it once the task is performed successfully.

Method 5

Similarly, if the Firewall installed on your system is preventing Outlook from reaching your mail server, then simply disable the Firewall to resolve.

If you encountered an error message that says, “Unhandled exception has occurred in your application”, when you start your Windows 10 computer, read on as this post will guide you on how you can fix it. This kind of error usually appears in a Microsoft .NET Framework window and it mostly pops up as soon as you turn on your computer. Here’s the complete context of the error message:

“Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.”

When this error occurs, your computer may freeze or display other suspicious behavior at times. Either way, there are several options you can check out in this post to resolve this issue, so read on. This kind of error could be caused by several factors. It could be due to your antivirus program or other third-party programs installed on your computer. It is also possible that the installation of the Microsoft .NET framework id corrupted or some of its installation files are corrupted. Thus, to fix the error, there are a few suggestions you need to follow such as:

Option 1 – Try to temporarily disable your anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive in your computer. There are times when you encounter problems like the “Unhandled exception has occurred in your application” error due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program in the meantime and check if it fixes the error or not.

Option 2 – Put your computer in a Clean Boot State

As pointed out, it is possible that some third-party program or service is the one that’s behind the problem. To isolate this possibility and to identify the culprit, you have to put your computer into a Clean Boot State. To do so, follow the steps below.

• 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.)
• Once your computer has restarted, check if the error is now gone. If it is, then the culprit is some third-party program. Thus, you have to enable the third-party programs one by one to find out which one of them is causing the the “Unhandled exception has occurred in your application” error.

Option 3 – Try to run a System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the cause why you’re getting the “Unhandled exception has occurred in your application” error. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Now restart your computer and see if the problem is fixed or not.

Option 4 – Install and update Dependencies

There are times when programs and applications need to have drivers and supporting software installed for them to properly work. Although the installation usually takes care of it, it’s time for you to do some manual check especially if you are getting this issue of abnormal program termination.

• Install some qualified drivers – A number of high-end games and applications need to have correct and valid drivers for them to work. They just don’t work with general drivers though. Microsoft has this Windows Hardware Quality Labs testing also known as WHQL testing which makes sure that drivers meet the correct experience and pass through the proper testing before certification. Thus, when installing drivers, you need to ensure that they are qualified drivers for your Windows 10 PC.
• Download and install or Update DirectX – As you know, Microsoft DirectX is a suite of technologies developed by Microsoft to provide hardware acceleration for heavy multimedia applications like HD videos and 3D games. Since you are using Windows 10, you have the DirectX 12 version while the earlier Windows versions use the DirectX 11 version.
• Install the Microsoft DirectX End-user runtime – The Microsoft DirectX end-user runtime gives updates to version 9.0c as well as previous versions of DirectX. To install it, click on this link and download it.
• Update or install the .NET framework – The .NET framework is used by games and applications during development which means that without the runtime files that are installed in your computer, it definitely won’t work. Thus, you need to install or update this framework. You can also use the .NET setup verification tool to verify it.

CLR20R3 error is received when you are launching an application in Windows 10. It can happen because of two reasons, a corrupted application file or missing system components. Keep on reading in order to find solutions to fix this error.

1. Run the program in compatibility mode

   Locate problematic application executable file Right-click on executable Click on properties Go to the compatibility tab and try running the application in the previous version of Windows or as an administrator.

2. Reset Windows media component

   Right-click on Start, then left-click on command prompt (admin) In command prompt type next command and after each line of command press ENTER regsvr32 atl.dll cd C:\WINDOWS\eHome ehSched /unregServer ehSched /service ehRecvr /unregServer ehRecvr /service ehRec.exe /unregServer ehRec.exe /regserver ehmsas.exe /unregServer ehmsas.exe /regserver

3. Reinstall Windows media player

   Go to control panel Click on Program and Features > Turn Windows feature on or off. Expand Media Features, uncheck Windows Media Player, and click Ok. Restart your PC, go through the same steps, tick Windows Media Player, and restart your computer once again.

4. Reinstall .NET framework

   Go to control panel Click on Program and Features > Turn Windows feature on or off. Uncheck “.NET Framework 3.5” and “.NET Framework 4.8”, and click Ok. Restart your computer, go through the same steps, check “.NET Framework 3.5” and “.NET Framework 4.8”, and restart your computer once again.

5. Update Windows

   Go to settings and check for updates

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given options below.

Option 2 – Ensure that all the supporting processes and services are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Compute Service
  • Container Manager Services
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 3 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox error.

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.