Fix Printer driver issue in Windows

KMODE_EXCEPTION_NOT_HANDLED seems to be connected primarily to a third-party driver, e1d65x64.sys associated with the Intel(R) Gigabit adapter, NIC/Wired network NDIS (Network Driver Interface Specification) 6.x driver. Error is known to produce the dreaded blue screen of death or BSOD. Most usually error is connected with gaming on Windows 10 computer and it manifests itself during gaming sessions. If you are unlucky and you are faced with this unfortunate error we will be happy to try to help you and present with tips and tricks in order for you to find a solution for it. Before you proceed with the provided solutions, be sure you have sufficient disk space on the Windows drive, run Disk Cleanup and then run CHKDSK.

1) Run the Blue Screen Online Troubleshooter

Open Control Panel, change the view setting to icons. Click Troubleshooting, and click “View all” in the tasks pane. Click “Blue Screen”. This opens the Blue Screen Troubleshooter.

2) Run Driver Verifier

1. Start a Command Prompt window by selecting Run as an administrator, and type verifier to open Driver Verifier Manager.
2. Select Create standard settings (the default task), and select Next. You can also choose to Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
3. Under Select what drivers to verify, choose one of the selection schemes described in the following table.

   Driver verifier table:

   Option	Recommended use
   Automatically select unsigned drivers	Useful for testing on computers that are running versions of Windows that do not require signed drivers.
   Automatically select drivers built for older versions of Windows	Useful for testing driver compatibility with newer versions of Windows.
   Automatically select all drivers installed on this computer	Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system. This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
   Select driver names from a list	In most cases, you will want to specify which drivers to test. Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.

4. If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
5. Select Finish, and then restart the computer.

3) Update network device drivers

Go to the official Intel website and try to find newer versions of drivers, if there are none perhaps you will need to revert back to the previous version.

4) Scan memory for issues

Run a memory test on your system, sometimes these errors can be traced back to a faulty RAM bank.

5) Stop over-clocking your PC

If you have overclocked your PC please reverse it back to its original state and see if that would solve the issue

6) Perform System Restore to the previous restore point

If none of the previous solutions have bared fruit, roll back to a previous restore point and that should solve the issue.

Have you ever deleted a file by mistake? Do not feel bad, we all have, but what if you deleted the file by mistake and then you went to Recycle bin to restore it only to find out that the bin is empty? If you experienced this kind of issue then you know how unpleasant and frustrating it is but do not worry, we are here to help and provide you with solutions to this problem and hopefully get your file back. Follow the next steps from first to last since they are organized in a way to minimalize the permanent deletion of lost files.

1. Refresh Recycle bin view

   If you spend any amount of time on this site reading through articles, you know I am a big fan of simple and effective solutions and there is nothing simpler than a single press of a button. Open your recycle bin and press F5 to refresh view or right-click anywhere inside and choose refresh. If your file does not appear with this method go to the next step.

2. Set Windows to show hidden system files

   In order for this to work first, you will need to open File Explorer by pressing ⊞ WINDOWS + E When File Explorer opens go to VIEW > OPTIONS. Inside options select “Show hidden files, folders, and drives”, uncheck “Hide protected operating system files (Recommended)”, and click APPLY > OK Go to the recycle bin and check to see if files have managed to show up.

3. Check if Don't move the file to the recycle bin is enabled

   Right-click on recycle bin and choose properties, under properties, there is the option that says Don’t move files to the Recycle Bin, Remove files immediately when deleted. This option is not selected by default, but it could be turned on by someone else or by mistake. If you see that this option is enabled sadly your file is gone and you will have to get the file back by using some third-party undelete application, uncheck this option to prevent future deletion of files by mistake.

4. Increase recycle bin size

   This will not help you to get your file back sadly but it will help you in storing more files in recycle bin. This is helpful since if you reach your recycle bin limit all further files will be permanently deleted and not been able to get them back. So by increasing bin size you will have more space for deleted files to be saved. To do that, right-click on Recycle Bin, select Properties. Now, increase the Maximum size from the Custom size option, and click Apply and OK.

5. Reset recycle bin

   To reset and fix corrupted recycle bin do the following: Press ⊞ WINDOWS + X to open the secret Windows menu and click on command prompt (admin) In the command prompt type in the following: rd /s /q C:\$Recycle.bin Reboot your system

There is various Blue Screen of Death errors that you can encounter as you use your Windows 10 computer and some of these Stop errors have something to do with the win32kbase.sys file. This post will guide you in fixing the BSOD errors related to the win32kbase.sys file.

• A problem has been detected and Windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: Win32kbase.sys.
• Your PC ran into a problem and needs to restart. If you would like to know more, you can search online later for this error: win32kbase.sys.
• SYSTEM_SERVICE_EXCEPTION (win32kbase.sys)
• STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – win32kbase.sys
• STOP 0x0000001E:

KMODE_EXCEPTION_NOT_HANDLED – win32kbase.sys

• STOP 0×00000050:

PAGE_FAULT_IN_NONPAGED_AREA – win32kbase.sys

The win32kbase.sys file is a Windows operating system Base Win32 Kernel Driver file located in the System32 folder so if it ends up getting corrupted or if it went missing, your computer will throw up Blue Screen error. To fix BSOD errors that have something to do with the win32kbase.sys file, here are some possible fixes that could help. Worry not for these possible fixes are not complicated.

Option 1 – Run the Check Disk or CHDSK utility

One of the first things you can try to resolve the win32kbase.sys Blue Screen error is running the CHKDSK utility. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f C:

• Wait for the process to be completed and then restart your computer.

Option 2 – Run SFC or 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 to 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.

 Restart your PC.

Option 3 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the win32kbase.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 4 – Try to run the Blue Screen Troubleshooter

As you know, the Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing Blue Screen errors related to the win32kbase.sys file. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Recently, a number of Windows 10 users reported an issue wherein they try to print from their PCs but were unable to and got an error message instead that states, “Port in use, please wait”. However, no matter how long they waited, nothing changed and they were still unable to print from their computers. On the other hand, when some of the users attempted to print wirelessly from their mobile devices, the printing continues which indicates that there is some issue between the computer and the printer. So if you are one of the users who are currently facing this problem, then this post should help. To fix this issue with your Printer, here are some possible fixes you can try that might work.

Option 1 – Run the Printer Troubleshooter

The first thing you can do to fix the “Port in use, please wait” error is to run the Printer Troubleshooter. This built-in troubleshooter in Windows 10 can help you fix most print issues. It checks if you have the latest printer drivers and then tries to fix and update them automatically. Aside from that, it also checks if you have connectivity issues or if the Print Spooler and the required Services are running fine. To run it, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msdt.exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Option 2 – Try updating the Printer drivers

You might also want to try updating your printer drivers. All you have to do is locate the USB Composite Device. For complete details, follow the steps below.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the USB Composite Device option and right-click on it, and select the Update Driver from the options.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: You also have the option to download the latest version of your Printer from the manufacturer’s website.

Option 3 – Try selecting the correct port for your Printer

If the first two options given above didn’t work, then maybe it’s time to select a correct port for your printer since the wrong port has been selected which is why you’re getting the “Port in use, please wait” error.

• Open “Devices and Printers” from the Start search.
• Next, look for your printer from the list of devices and right-click on it, and then select Printer Properties.
• Now go to the Ports tab under the newly opened Properties window and make sure that the port type matches the connection on the list of ports currently in use.

Note: If your printer is using a USB connection then the port should have a USB or DOT 4 in its description but if your printer is using a network connection then it should have the following description:

• WSD
• Network
• IP

And if you notice that there are several listings for the same type of port, you have to change the selection to a different one and then click the OK button to save the changes made.

A lot of programs in Windows utilize the helper processes to ensure that they can get the job done as early as possible. And one of the programs that use these processes is Microsoft Edge. This built-in browser uses a process called the Edge Content process. The moment you start your computer, these system processes are loaded which makes the Edge browser load faster. To be specific, these are the three processes that are related to Microsoft Edge:

• MicrosoftEdge.exe
• MicrosoftEdgeCP.exe
• MicrosoftEdgeSH.exe

The process that ends with the “CP.exe” is the content process in Edge. However, when this process stopped working, this can affect the Edge browser. In such cases, when you check the Reliability Monitor, you will see that the state of the “Microsoft Edge Content Process” is “Stopped working” which keeps on appearing. To resolve this issue, you can try to clear the browsing data of Microsoft Edge or repair or reset it. You can also try re-registering Edge via Windows PowerShell as well as check your security programs that might be causing interference with the process.

Option 1 – Clear the browsing data 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 2 – Try to reset, repair or reinstall 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 computer

Option 3 – Re-register Edge via Windows 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
• 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.

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml” -Verbose}

Option 4 – Try to check your security program

It is possible that a security program installed in your computer is the one that’s causing the problem which is why you have to check it. According to security experts, there are some security programs that could be detecting the Edge’s content process as suspicious, blocking or terminating it as a result. Thus, you need to modify your security program’s settings to fix the problem.

If you have a BlueTooth device on your computer, you know that each time you need to receive or transfer the file you need to find the icon in the system tray, right-click on it and choose the desired option. But there is a simpler solution, create a Bluetooth icon on the desktop so it is always easy to access. Open File Explorer by pressing ⊞ WINDOWS + E Go to C:\Windows\System32 Find fsquirt.exe Right-click on it and choose copy Go to the desktop and right-click, choose paste Rename the file to Bluetooth And, you are done!

If you are trying to run Windows Update but encountered an Error 0x80070003, read on as this post will guide you on how you can fix it. This kind of error in Windows Update can occur when you activate Windows Firewall or download from the Windows Store. This kind of error indicates that the Windows Update service or WUAUSERV is not started or that the Background Intelligent Transfer Service or BITS can’t be started. Aside from that, you can also encounter this error with the other Windows Update components. To fix the Windows Update error 0x80070003, you can try to run the built-in Windows Update troubleshooter or replace the old Configuration file named “Spupdsvc.exe”. You can also try to reset the Windows Update components or check the status of all the Windows Update-related services, as well as run a System File Checker scan.

Option 1 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter is one of the things you can first check out as it is known to automatically resolve any Windows Update errors like error code 0x80070003. To run this troubleshooter, Refer to these steps:

• Tap the Win + I keys to open Settings.
• From there, click Update and Security and go to the Troubleshoot section.
• Next, select Windows Update and click the “Run the troubleshooter” button and wait until it’s finished, and then try to run Windows Update again.

Option 2 – Try replacing the old Configuration file named “Spupdsvc.exe”

The next thing you can do to fix the Windows Update error is to replace the Spupdsvc.exe file. This is a process file that comes under the Microsoft Update RunOnce service. So when an update becomes available for your computer, the process responsible for performing the upgrade is notified. In addition, the RunOnce entry is also added to the registry for the spupdsvc.exe and this process is executed when your computer restarts and when you log on.

• In the Start Search, type “command prompt” and from the search results, right-click on Command Prompt and select the “Run as administrator” option.
• Next, execute this command to replace the old configuration of the Spupdsvc.exe file with a new one: c m d (remove spaces on CMD) /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old
• After that, try to run Windows Updates again and check if the error is now gone.

Option 3 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer.

Option 4 – Check the status of some Windows Update Services

• Tap the Win + R keys to open the Run dialog box.
• Next, type “services.msc” in the field and hit Enter or click OK to open Services.
• From the list of Services, look for the following services and make sure that their Startup type is as follows:
  • Windows Update – Manual (Triggered)
  • Background Intelligent Transfer Service – Manual
  • Cryptographic Services – Automatic
  • Workstation Service – Automatic
• After that, check if the Service status of the listed services above are set to Running. If they’re not, click on the Start button to start these services and then check if the Windows Update error 0x80070003 is now fixed or not.

Option 5 – Run the System File Checker Scan

If manually resetting the Windows Update components didn’t work, you can run a System File Checker scan instead. It is a built-in command-line utility that replaces bad and corrupted system files with good system files that might be the cause why you’re getting the error when you try updating your computer. 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.

• Restart your computer.

Microsoft’s initial Windows 11 hardware requirements were not really well received by users and they were not really clearly represented from the start making a lot of potential customers slowly drift away from the hype. It seems that Microsoft has acknowledged this since they have changed their tune about system hardware requirements for the upcoming Windows 11. It seems that Windows 11 will be able to be officially installed on unsupported computers but with a little inconvenience.

What is a catch?

Windows 11 will still have the same hardware requirements and if the PC meets them, that computer will be officially supported, other ones (any that can run Windows 10) that do not meet system requirements can still run Windows 11 but the system will have to be clean installed. So no upgrade option for old computer users, just a clean install. This means of course that you will need to download the ISO image and make a bootable USB in order to install it. Also since you will be doing a clean install do a backup of the hard drive since it will need to be formatted. Also, Microsoft has stated that with unofficially supported PC some driver updates might not be delivered leaving you with either older driver versions or relying on your hardware manufacturer on them. This is still not confirmed by Microsoft, just stated as an option. We will see how it goes.

Conclusion

It is very good that Microsoft has reconsidered its system requirements and will not stubbornly push its initiatives over the top requirements allowing even older computers to install new OS. I am sure over time lot of users will upgrade their hardware and drive into officially supported waters, but it is good that they will be able to use new OS on their current hardware.

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

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

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

Option 2 – Disable driver signing via Group Policy Editor

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

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

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

In this post, you will be guided on how to import and export the WSL distros in your Windows 10 computer. WSL, also known as Windows Subsystem for Linux, is a compatibility layer needed to run Linux binary executable in Windows 10, as well as the Windows Server 2019. In case you don’t know, when you reinstall or reset Windows 10, all of its configuration data stored with the WSL distros gets deleted. Going back or restoring the configuration can be quite challenging but worry not for Microsoft has already got this covered as you can now import and export the WSL or Windows Subsystem for Linux distros. There are three aspects that you have to deal with when you import or export WSL distros in your Windows 10 computer, such as importing WSL distro, exporting WSL distro, and uninstalling the imported WSL distros. Before you proceed to the instructions provided below, make sure that all your installed distros are updated via Microsoft Store. Once you have this covered, follow the options below.

Option 1 – Import the WSL distro

• Type “command prompt” in the Start Search and from the search results, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, execute this command: wsl --list –all
• The command you entered will list all the installed WSL distros on your computer. And now it’s time for you to import a WSL distro by executing this command: wsl --import <Name of the distro> <Fill path to save the backup .tar file>

Note: In the given command above, replace “<Name of the distro>” with the name of the distro you want to import and replace “<Fill the path to save the backup .tar file>” with the location where you want to save the .tar file.

Option 2 – Export the WSL distro

• Type “command prompt” in the Start Search and from the search results, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, execute this command to see the list of all the installed WSL distros in your computer: wsl --list –all
• After that, execute this command to export a WSL distro: wsl --export <Name of the distro> <Fill path to save the backup .tar file>

Option 3 – Uninstall the imported WSL distro

• Open Command Prompt with admin privileges.
• Next, execute this command to view the list of all the installed WSL distros: wsl --list –all
• After that, execute this command to uninstall an imported WSL distro: wsl --unregister <Name of the distro>
• Once it’s done, close Command Prompt and restart your computer.