Fix Windows Update Error 0x8024000B

One of the selling points of Windows 11 was the ability to run Android apps natively in it without the need for any third-party software. It is not a big surprise that even after its release Microsoft is evolving and expanding Windows 11 and its features.

Microsoft is now rolling out an update for the Windows Subsystem for Android on the Dev Channel of the Windows Insiders program. The new version upgrades the core operating system from Android 11 to Android 12.1 (also known as Android 12L), which means the new system and app features in Android 12 and 12.1 are now available on Windows for the first time. However, not the new features in those updates apply to the modified version that runs on top of Windows. For example, one of the main improvements in 12.1 was a dual-pane notification panel for larger screens, but Android app notifications on Windows just show up in the Windows notification panel.

The upgrade also improves how Android apps integrate into Windows. The Windows taskbar will now show which Android apps are currently using the microphone, location, and other system services — similar to many native Windows applications. Toasts messages (the small popups that some apps use for temporary messages) are now displayed as Windows notifications, and the titlebar on Android apps will use the current activity name for the title.

Full changelog

• Windows Subsystem for Android updated to Android 12.1
• Advanced networking on by default for newer x64 Windows builds
• Updated Windows Subsystem for Android Settings app: redesigned UX and diagnostics data viewer added
• Simpleperf CPU profiler recording now works with Windows Subsystem for Android
• Windows taskbar now shows which Android apps are using microphone and location
• Improvements to Android app notifications appearing as Windows notifications
• Reduced flicker when apps are restored from minimized state
• Apps are not restarted when devices come out of connected standby on recent Windows builds
• New video hardware decoding (VP8 and VP9)
• Fixes for on-screen keyboard in apps
• Fixes for full-screen Android apps and auto-hidden Windows taskbar
• Windows Subsystem for Android updated with Chromium WebView 100
• Added support for Android NetworkLocationProvider in addition to GpsLocationProvider
• Improved general stability, performance, and reliability

The new update is limited to Windows Insiders for now, but once Microsoft fixes all the bugs, it should start rolling out to everyone on Windows 11 that has the Android Subsystem enabled.

If you encountered an error message saying, “We couldn’t find any drives, To get a storage driver, click Load driver” when you try to install Windows in a VirtualBox machine, then you’ve come to the right place as this post will guide you in fixing this error. This error message is displayed on the screen where you have to choose a partition to install the guest operating system. This error is most likely due to the lack of correct settings as well as a corrupted virtual disk. To fix this error, you have to remove existing storage devices, create a new storage device and select the correct ISO file.

For complete instructions, follow the given steps below.

Step_1: The first thing you have to do is remove all the existing Storage devices and since this option is already available in VirtualBox by default, there is no need for you to install any third-party software. Step_2: After that, open VirtualBox and select the virtual machine and then click the Settings button. Step_3: Next, switch to the Storage section and on your right-hand side, you will see “Controller: SATA” and two other sub-labels. From there, select Controller: SATA and then click on the red cross button that says, “Remove selected storage controller”. Step_4: Now click on the Add new storage controller icon and select the “Add SATA Controller” option from the given list. Step_5: Afterwards, click the “Add hard disk” button and select the “Create new disk” option, and then you have to create a new virtual disk for your virtual machine. Step_6: Verify if you have selected Dynamically allocated while you create the virtual hard disk. Once the process is completed, you will get a “.vdi” file in the list. Step_7: Next, click on the “Add optical drive” button and select the “Choose disk” option. Here, you have to select the ISO file and if you can find an ISO file in the given list, select it from there, else, you have to click the Add button and navigate to the folder where the ISO file is located. Step_8: Once you’re done, click the OK button and boot your virtual machine. You should see options instead of the “We couldn’t find any drives, To get a storage driver, click Load driver” error message. If you see the options, you can now create a new partition and start the installation process of the Windows operating system in the VirtualBox machine without any problem.

A command is not recognized Error, what it is? If you are constantly using programs like CMD or DISM directly from the Run prompt, you might have wondered how they launched instantly and how is it that the Windows operating system is able to find them right away. For instance, when you create a shortcut of a program, the shortcut knows where exactly the program is located and launches it quickly. The Windows operating system keeps a list of paths where the most common system programs are located so when you use the Run prompt, it opens easily. The list kept by Windows is called the Windows Environment Variables. If something goes wrong with this list, the programs won’t work. So in this guide, you will be guided on how you can troubleshoot the problem where any command you use is not recognized as an internal or external command, operable program, or batch file. Before you start troubleshooting the problem, you need to make sure that the program you are trying to run really exists. In fact, this can also happen to the Run program which is pulled up using the Win + R shortcut. To check, go to C:\Windows\System32 and there, check if the program exists or not or you can also try searching for the EXE in the System 32 folder. After making sure that the program exists, refer to the instructions given below.

Modify the Windows Environment Variables:

• Step 1: Tap the Win + X keys and then select System. After that, it will open the section where you can see all the properties on your computer.
• Step 2: Next, select the Advanced system setting located on the left pane and click on the Environment Variables.
• Step 3: After that, locate Path under the System Variables and select EDIT.
• Step 4: Before you edit, you need to copy the entire string and paste it into the Notepad app so that in case something went wrong, you can paste it back.
• Step 5: Next, look for the directory path, “C:\Windows\System32”. If you can’t find it, try adding a semi-colon at the end.
• Step 6: Afterwards, click OK to save the changes made and then exit.
• Step 7: Now restart your computer as all the paths are picked up when your computer restarts.

Note: Now all you have to do is to try executing the programs once again – the ones where you got the error, “ is not recognized as an internal or external command, operable program or batch file” every time you open them and then see if you can now open these programs or not.

Google Chrome 94 is here and it has introduced a controversial idle detection API. For those people that do not know what idle detection API is, well basically Chrome can be asked by a website to report when a user of the site has a site open and is idle on the device. The issue that people have with this is that this particular feature can be used to report when the user is not using a computer at all. Good thing is that website or web application will prompt you to allow it to use this feature like when a site/application wants to use your microphone or web camera. Developers are on board with this feature since it can provide them with more telemetric data on how users are interacting with their website/application but there are some that are strongly voicing against this. Tantek Çelik, Mozilla Standards Lead, commented on GitHub, saying:

As it is currently specified, I consider the Idle Detection API too tempting of an opportunity for surveillance capitalism motivated websites to invade an aspect of the user’s physical privacy, keep long-term records of physical user behaviors, discerning daily rhythms (e.g. lunchtime), and using that for proactive psychological manipulation (e.g. hunger, emotion, choice)… Thus I propose labeling this API harmful and encourage further incubation, perhaps reconsidering simpler, less-invasive alternative approaches to solve the motivating use-cases.

Others who have spoken against this feature are people from the WebKit development team inside Apple. Ryosuke Niwa, an Apple software engineer who works on WebKit said:

That doesn’t seem like a strong enough use case for this API. For starters, there is no guarantee that the user won’t immediately come back to the device. Also, who is such a service supposed to know what another device user might be using at any given point? We’re definitely not going to let a website know all the devices a given user might be using at any given point. That’s a very serious breach of the said user’s privacy. It seems to me that such a suppression/distribution mechanism is best left for the underlying operating systems/web browsers to handle.

Of course, technology itself as always can be used for good or for bad and time will tell if this feature has brought good stuff or it has paved another brick in surveillance and privacy manipulation. As said for now option will prompt for agreement and let's hope that it will be used for good causes from this day into the future.

Error 118 - What is it?

Error 118 is a typical Google Chrome error. It pops up when Google Chrome fails to load websites like Facebook. It is usually displayed in the following format:

‘Error Message: Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out.’

Solution

Error Causes

Error 118 may be triggered due to several reasons. This includes:

• Problems with DNS setting
• IP Address is filtering websites
• Cookies and invalid registry entries

Further Information and Manual Repair

To ensure smooth internet browsing on Google Chrome, it is advisable to repair the error 118. If error 118 is not resolved you will be unable to load and access your desired websites. To avoid inconvenience and resolve the issue immediately, try the methods suggested below. These are easy and effective do-it-yourself methods that require no technical skills.

Method 1 - Change Proxy Settings

If your IP address is filtering websites, then you might experience error 118 while using Google Chrome. When this is the error cause, then it is advisable to add a proxy for your PC. To change proxy settings and add a new proxy, simply click on Customize and Control Google Chrome menu. Now click the options button. Under the Google Chrome Options window select the Under the Hood tab. After that in the Network, section click the change proxy settings button. Check Show Suggestions for navigation errors and Use DNS pre-fetching to improve page load performance boxes. Now under Internet Properties, click LAN Settings. Under LAN settings you will see the Proxy Server box, check it, and enter your new proxy settings. Click OK to confirm and save settings. This will hopefully resolve the issue.

Method 2 - Change to Google DNS

When the error is related to DNS settings then try this method to resolve it. Simply set DNS to use Google DNS. Here’s how it’s done:

1. Go to the start menu, click Windows Control Panel, Network and Internet, and change adapter settings. Here you will see Local Area Connection.
2. Right click to select properties at the bottom.
3. Check Internet Protocol Version 4 and click properties.
4. Now check the ‘Obtain an IP address automatically’ box and also select the option that says ‘Use the following DNS server addresses’.
5. Change Preferred DNS to 8.8.4.4 and Alternate DNS server to 8.8.8.8 now click OK to confirm.

Method 3 - Remove the Bad Entries and Cookies Damaging the Registry

Bad entries and cookies saved in the registry can also trigger error 118. To fix the issue immediately download Restoro. This is PC Fixer with multiple utilities including a registry cleaner. The registry cleaner removes all bad entries and cookies in seconds and repairs the damaged registry. Click here to download Restoro and resolve error 118.

Typical use of file explorer will probably not need any kind of elevated privileges, but from time to time you might encounter some tasks that will require administrator rights in order to perform them. If this is the case you will need to run file explorer with these rights but inside Windows 11 that is somewhat hidden and not 1 click away. How this is the case we have decided to put a little tutorial on how to accomplish this very task and run file explorer with administrator privileges.

Open File Explorer via EXE file

1. Open File Explorer typically
2. Navigate to This PC > Windows (C:) > Windows
3. Locate file explorer application
4. Right-click on it and select Run as Administrator
5. Run File Explorer

A new instance of file explorer will pop with elevated administrator privileges.

Run it as an administrator using the Task Manager

1. Open the Task Manager ( CTRL + SHIFT + ESC )
2. Click on More details (at the bottom)
3. After the task manager expands click on the File tab
4. Click on Run New Task
5. Type in explorer.exe and check the box next to it that says Create this task with administrative privileges
6. Click on OK

File Explorer will now run as administrator.

Hello everyone, in today's tips and tricks we will focus on providing you with various solutions on how to solve the Device not migrated error that appears after the Windows update has been performed. Sometimes sadly updates to our operating systems can introduce us to various issues that look scary but in reality, they are solvable and not so scary at all. After all who would not find this message concerning, especially when it happens in the middle of work. The first thing that would pop into my mind is that I have lost tons of work and that something in my hardware has gone very wrong and it is dead. Luckily that is not the case and this error means that due to Windows update drivers were not properly transferred due to some compatibility issues, maybe it was a corrupt update file, etc. Of course, the reason could be hardware malfunction as well, but if everything was working fine before the update, it is a software issue, and I must say it is a common one and fixable. Please keep reading this guide in order to fix the Device not migrated error.

1. Update the Driver

   You should always try this first, if the device is not recognizable, try updating its driver and see if the problem vanishes. In order to update the driver, we will need first to locate which device has not been migrated properly, we will do this with help of a search engine on the internet like google for example. So open your browser of choice, go to a search engine (google for example) and type in the search box first line from your error message, yes, that scary one. You will be given which device has malfunctioned and was not migrated properly, now we will locate the device and update its drivers. To do this press WINDOWS + X on your keyboard to bring up Windows secret menu and choose device manager. Find device inside device manager, right-click on it, and choose properties. Go to the events tab and make sure that the device has migration issues. You have now 3 options for updating the driver, you can do it manually, automatically, or with the driver installer. We will cover all 3 options so you choose which one best suits you. OPTION 1: Manually. Close the Properties tab, go to the device manufacturer website and download the latest driver, if there are no drivers there, the only executable installer for the device skip this step and try the other 2. After you have downloaded the driver package from the website, right-click on the device and choose update driver. Now navigate to the folder where you have downloaded your driver package and update the driver. Reboot your system. OPTION 2: Automatic update. Close the Properties tab, right-click on the device and choose to uninstall. Once the device is uninstalled, restart your system, and Windows will automatically search and install the latest driver for the device. OPTION 3: Via driver installer. If you have downloaded .EXE or executable driver installer from device manufacturers web site try installing it, if the installation fails, try using compatibility mode for the installer. Navigate where the installer is located, right-click on it, and choose properties. Go to compatibility TAB and try installing it with administrator privileges in Windows 8 mode. Reboot your system after this step. This should solve the issues, however, if the issue still persists, follow the next steps.

2. Verify the Corrupted System Files

   Press WINDOWS + X on the keyboard to open the hidden system menu and choose Command prompt (administrator) In the command prompt type in: sfc /scannow and press ENTER. The scanning process and repair of files will take around 15 min. Leave it to finish completely, do not restart, work on the computer or shut it down while the process is active, and only after it is finished reboot your system.

3. Update Windows.

   If your Windows is not updated sometimes this issue can be resolved by updating it on the latest version. Click on start and then on settings. Once the settings screen is opened, find and click on Update and Security. Go to the Windows update tab and click on DOWNLOAD or click on check for updates for the latest Windows fix.

4. Reset BIOS to factory settings.

   Sometimes BIOS not being properly configured can cause issues in Windows itself and prevent it from detecting PnP devices thus creating this error. Restoring BIOS back to the factory setting can help. Turn off your computer and turn it back on. Press delete, f12, f11, or any other key which will take you to BIOS (default key is delete but sometimes manufacturers map this to another one. Once your screen turns ON you will see in the bottom message which key needs to be pressed in order to enter BIOS). Sadly since every BIOS could be different we can not cover step by step guide for each but you need to find the option where you load BIOS defaults, click on it save, and exit. Your computer will restart and boot into Windows, check to see if the problem still persists.

5. Update BIOS

   BIOS can cause issues with certain PnP devices when the newest Windows update is rolled. If reverting BIOS to the factory setting has not been successful try update. Go to your motherboard manufacturer website, find the update and read step by step guide there since updating BIOS differs from version to version and from manufacturer to manufacturer. After the update is done, restart the computer and hopefully, the error is gone.

6. Perform a System Restore

   If everything else fails, perform a system restore to get Windows back into the state before the update was installed and when everything was working fine. Press WINDOWS + R on the keyboard to open the run dialog. In the run dialog, type control panel and press enter to enter control panel, locate recovery and click on it. Inside the recovery screen click on Open System Restore. Choose a date when everything was working in order, the best bet is the date before Windows update and roll it back. Click on date, and then on next.

Rundll Error - What is it?

Rundll Error, DLL is also known as Dynamic Link Library is a Window library that basically consists of instructions and codes used and shared by multiple programs installed on your system. It helps programs load and run smoothly. Rundll error is generated when the system fails to access DLL files thereby hampering your ability to successfully run your desired program.

Solution

Error Causes

The rundll error code is triggered due to multiple reasons such as:

• DLL file affected by virus and malware
• Poor program installation
• Invalid Windows registry entries

It is advisable to fix the run.dll error immediately without any delay because this error exposes your PC to serious threats such as system crash, freeze, failure, data loss, and even privacy threats like cybercrime, data breaches, and identity thefts.

Further Information and Manual Repair

To resolve the rundll error on your system, here are some solutions that you can try:

Solution 1: Reboot your System

Sometimes rebooting your system can also resolve the issue. However, if it doesn’t then you need to try some other solution to fix it.

Solution 2: Identify the Program Triggering the Error

To fix rundll error, the first thing that you need to do is to identify the program generating this error and check it for validity. For this, simply analyze the rundll error dialog box. Let’s say you get the following run.dll error on your system Error loading

C:\WINDOWS\system32\usvdgpo.dll.

This error message indicates that the program ‘usvdgpo’ is causing the run.dll error on the system. Once the program is identified, the next step is to stop it manually. For this, you go to the start menu and click run, now type ‘services.msc’ in the dialog box, and press ‘Enter’. After that right-click the related process to your rundll error and then click the ‘Stop’ button to stop the program. Now close the window. Though this action will stop the process it will not remove the reference to the bogus items. To remove that you will have to remove the program from the Windows Registry. This can be done by typing ‘Regedit’ in the Run dialog box. This will open the registry editor. From the keys listed in the left panel, navigate to the following key: HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Run. Now right-click on this key and click delete and then simply close the windows registry and reboot your system. After this, you will then have to uninstall the program to completely eradicate the rundll error. To do this, go to the control panel, Add/remove programs, and right-click to uninstall the program causing the run.dll error on your system. Click yes to confirm your decision. Once the program is uninstalled, reinstall the program using the program CD to get yourself an error-free program. This procedure is tricky, time-consuming, and maybe slightly challenging for you especially if you are not a computer programmer.

Solution 3: Run an Antivirus

If the cause of the run.dll error is a malware attack then you need to download an antivirus and run it on your system. However, this may impact the speed of your PC. Antivirus is notorious for slowing down PC speed.

Solution 4: Download Restoro.

If you are not a computer programmer, then running Restoro is possibly the easiest way for you to resolve rundll errors on your system in seconds. Restoro is an innovative, cutting edge, and multi-functional feature-filled PC repair tool that can be used to repair all kinds of system-related errors including rundll errors. The registry cleaner utility cleans up the RAM by removing unnecessary and obsolete files like junk files, invalid registry entries, and files from the uninstalled programs. It resolves disk fragmentation issues, repairs dll files, and the registry. In just a few clicks you can easily repair the registry and remove malware thereby resolving rundll errors on your system. Operating Total System Care is quite simple. It has a user-friendly interface and easy navigation. It is safe, efficient, bug-free, and compatible with all Windows versions Click here to download Restoro and resolve ‘rundll errors’ and access/run programs on your system smoothly.

If you have encountered the NO_USER_MODE_CONTEXT Blue Screen error when using your computer, read on as this post will walk you through a couple of suggestions you can try to resolve this Stop error. This kind of Blue Screen error can occur when a program is trying to leverage the use of a system driver but fails to do so. Some of the common causes of this BSOD error are incompatible or corrupted drivers, incorrect configuration of entries in the Registry, damaged memory locations, malware infection, and many more. In addition, this Stop error does not often occur and indicates that an attempt to enter user mode with no context was made. If this is the first time you’ve restarted your computer after you’ve installed additional hardware, you have to remove the hardware and then restart your computer once again and then check the Microsoft Hardware Compatibility List to confirm that the hardware and its drivers are compatible with your operating system. If it doesn’t help, you can check out the given suggestions below to fix the NO_USER_MODE_CONTEXT Blue Screen error in Windows 10.

Option 1 – Try to update or rollback your device drivers

The first thing you can try to fix the NO_USER_MODE_CONTEXT Blue Screen error is to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties. Note that the main drivers that might be the cause behind the NO_USER_MODE_CONTEXT Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver.

Option 2 – Try running System File Checker or SFC 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.

 Reboot your PC.

Option 3 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the NO_USER_MODE_CONTEXT Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them.

Option 4 – Perform System Restore

• First, tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like NO_USER_MODE_CONTEXT. It can be found on 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.

Windows 10 is has a lot of features that help a user in optimizing a computer. So when the operating system encounters a problem, it is able to provide users with proper resources to get the problem fixed. There are even times when a user is not notified and an issue is either being repaired or dodged in the background. This kind of feature is known as the Diagnosis of the Automatic Repair feature that starts when your computer is booting. In such times, you will either see the “Diagnosing your PC” or “Preparing Automatic Repair” message on your screen. Although this feature is useful and has proven to be effective, some users reported that the process gets stuck. If you experience the same problem, read on as this post will guide you on what to do to fix it but before you start troubleshooting the problem, you might want to perform a Hard Boot first. All you have to do is to power down your computer, remove the battery and the AC adapter and then reconnect them. After that, tap and hold the power button for about 20 seconds and see if your computer boots up properly. If it doesn’t, follow the given fixes below.

Option 1 – Try disabling the automatic Startup Repair

The Automatic Startup Repair window will automatically open during boot when you have some system driver-related problem. So if you think that this is where the problem lies, you can try to disable the automatic Startup Repair.

• Click on Troubleshoot and go to the Advanced options.
• After that, select Command Prompt and execute the following command:

bcdedit /set recoveryenabled NO

• Restart your computer after that and then check.

Option 2 – Run the System File Checker

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 that might be the cause why you’re facing this problem. 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 3 – Run CHKDSK to check your disk for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

chkdsk /r /f

• Now if you are prompted to run CHKDSK after your reboot your computer, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.
• Once your computer has restarted, try accessing the file and check if the error persists.

Option 4 – Run the DISM tool

The next thing you can do is run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like your computer getting stuck in the “Diagnosing your PC” or “Preparing Automatic Repair” screen.

• 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 problem is now fixed.

Option 5 – Try to use installation media to boot and repair your computer

Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:

• You need to first create an installation media which has the dame version of the operating system installed in your computer.
• After that, once you reach the Install Windows screen, click on the “Repair your computer” link.
• Wait until the repair is completed and then shut down your computer
• Now once your computer has restarted, check if it can now boot properly.