Fix W11 Installation assistant is not working

Setting up an FTP Server in Windows

File Transfer Protocol Server, also known as FTP Server, is a private or public service that can host files that can be accessed both locally and globally. It is a quick, flexible and seamless service that allows you to store any kind of files depending on the total size of the server. If you’ve always found an FTP server useful, then the good thing is you can now create your FTP server since Windows 10 now allows it. You can host this server locally and later on make it globally available via the internet. So if you are planning to set up an FTP server on your Windows 10 computer, read on as this post will guide you on how to do so.

To set up the FTP server, you need to configure it first and then configure the Windows Firewall for the connections to go through. For more details, refer to the following steps:

Step 1: You need to configure the FTP server on Windows 10.

In the Search box, type in “Turn Windows Features On or Off” to search for it.
Then click on the appropriate result which will open a mini window.
From this mini window, scroll down to the list and expand “Internet Information Services where you have to expand the FTP Server section.
Next, select all the checkboxes to enable all the entries under FTP Server and then click the OK button to apply the changes made.
And now, since your computer is now allowed to host an FTP server, you need to configure it. To do so, type “Internet Information Services (IIS) Manager” in the Search box and click on the appropriate entry.
Next, right-click on Sites under the navigation bar of Connections and select Add FTP Site. This will open a new window where you have to input some information about your FTP hosting.
Now enter the details and click on Next.
Upon clicking Next, you will be prompted to give some authentication details. Enter the following details in the screenshot below.
Now click on Finish. After that, you will get an FTP Server being hosted on your Windows 10 PC.

And now that you’ve successfully configured the FTP Server, the next thing you have to do is to allow connections from and to the FTP server. Refer to the next step below. Step 2: Configure the Windows Firewall for FTP connections to pass-through

In the Start Search, type “Allow an app or feature through Windows Firewall” and click on the related search result which will open a window with all the settings.
From there, click on the Change Settings button. This will display a list where you have to mark all the checkboxes for the FTP server to enable them in both the Private and Public configurations.
After that, click OK. This will allow you access to the FTP server on your local network.

Fix ATTEMPTED_WRITE_TO_READONLY_MEMORY

This post will help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen issue with an error code 0x000000BE. If you encounter this kind of BSOD error when you try to boot into your Windows 10 computer, note that there are various possible causes for this error. It could be caused by an error with a device driver, hardware issues, or some error in the BIOS of your computer. The ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error with a bug check of 0x000000BE appears when a driver tries to write a read-only memory segment. You’ll be able to see the name of the driver in the Blue Screen error if the driver that’s causing the error can be identified. You can also see it in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In most cases, this kind of error is usually caused by various files such as iusb3hub.sys, ntkrnlpa exe or vhdmp.sys, ntoskrnl.exe, ntfs.sys, dxgkrnl.sys, tcpip.sys, atikmdag.sys, and win32k.sys. There are several possible fixes you can try to fix this issue but the main issue lies within booting into Windows since the error occurs as soon as you boot into your Windows 10 computer. Refer to each one of the options provided below to resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY Blue Screen error.

Option 1 – Try to rollback, update or disable drivers

The first thing you can do to fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error is to roll back, or update, or disable 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.
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 install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try running the Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the ATTEMPTED_WRITE_TO_READONLY_MEMORY 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 and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update the BIOS

Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

Tap the Win + R keys to open the Run dialog box.
Next, type “msinfo32” in the field and press Enter to open System Information.
From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
After that, you should see the developer and version of the BIOS installed on your PC.
Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
Now double click on the downloaded file and install the new BIOS version on your computer.
Now restart your computer to apply the changes made.

Option 4 – Try disabling BIOS Memory Options

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the ATTEMPTED_WRITE_TO_READONLY_MEMORY Stop error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

Option 5 – Try running the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like ATTEMPTED_WRITE_TO_READONLY_MEMORY. 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.

How to fix disk signature collision problem

As you know, storage devices are an important part of the computer system for porting, saving, and extracting data files. And for you to differentiate between storage devices on your computer system, each one of the storage devices is labeled with a unique number referred to as Disk Signature for identification. The unique disk identifier is stored as a part of the MBR or Master Boot Record. Disk signature is used by operating systems in order to identify and set apart different data storage devices and hard disk drives in the computer for data access. These days, Disk cloning has become a regular practice in upgrading to larger hard disk drives. Drives are cloned in order to produce a similar copy to use both the original drive and cloned copy together. Moreover, lots of virtualization tools are being used to virtualize the physical hard disk drives to create virtual hard disk drives and several virtual machine clones that are created with the existing virtual hard disk drives. And since these are identical copies, chances these copies may have identical disk signatures. As a result, when you use both disks that have identical signatures at the same time you run into the Disk Signature Collision problem. This kind of problem does not often occur as the Windows system does not really allow two disks to function simultaneously when they have the same disk signature. When you encounter a Disk Collision problem in your Windows 10 computer, you may see the following error messages:

The boot selection failed because a required device is inaccessible
The disk is offline because it has a signature collision
This disk is offline because it has a signature collision with another disk that is online

You can fix the disk collision problem by changing the disk signature which you can achieve using the command line utility diskpart in Windows PowerShell or Command Prompt or using Windows Disk Management utility. To fix the disk collision problem, you can make use of the command-line utility called diskpart in Windows PowerShell or Command Prompt to view and change the signature, or can make use of Master Boot record in the Windows Registry. You can also make use of Windows Disk Management Utility to change the signature. Simply follow the given options below to change the disk signature either way.

Option 1 – Change Disk Signature via Diskpart

Type “command prompt” in the Windows Search bar and then right-click on the related search result and select the “Run as administrator” option.
After that, type the “diskpart” command and hit Enter to open Diskpart.
Next, type the “list disk” command to display all the disks available in the system.
Next, take note of the problematic disk number with the status Offline from the list and then type the “Select disk x” command where x is the offline disk to select the offline disk. For instance, if you type “select disk 1”, it will display the “Disk 1 is now the selected disk” message.
Now type the “Uniqueid disk” command to display the disk signature and to change the disk’s signature and set the disk online, type the “unique disk ID= (New signature)” where (New signature) is the new ID in hexadecimal. For instance, you can set the new id as “unique disk ID= 1456ACBD”.

Note: If you have given the wrong format ID, the command prompt will display the following error:

“The specified identifier is not in the correct format. Type the identifier in the correct format: in hexadecimal form for an MBR disk or as a GUID for a GPT disk.”

After you’re done, the disk will be online, and then restart your computer.

Option 2 – Change Disk Signature via Disk Management Utility

Tap the Win + R keys to open the Run dialog box and then type “diskmgmt.msc” and hit Enter or click OK to open Disk Management.
Next, right-click on the disk that is marked as Missing or Offline.
After that, select the Online command from the drop-down menu.
Then from the selecting option Online, Windows will generate a new disk signature.

How to Fix Explorer.exe System call failed

One of the most critical processes in the Windows 10 operating system is the Explorer.exe. And there are times when you might encounter an error that says, “System call failed”. You can encounter this error when you try to launch File Explorer, and in such case when the File Explorer does not work, it could cause issues in accessing folders and files on your computer. This kind of error pops up when the explorer.exe system file has become corrupted or if there is some process that interferes with its smooth functioning. To fix this error, you can try to restart the explorer.exe process, run both the System File Checker scan and DISM tool. You could also put your computer in a Clean Boot State or uninstall any programs you’ve installed recently. For more details, follow each one of the given suggestions below.

Option 1 – Try to restart the Explorer.exe process

The first thing you can do is try to restart the Explorer.exe process. To do so, refer to these steps:

First, right-click on the Taskbar and select the Task Manager.
Next, expand the Task Manager window to see all the active processes.
From there, look for the Windows Explorer process, right-click on it and select Restart.
After that, check if the error is now fixed.

Option 2 – Run System File Checker scan

If restarting the explorer.exe process didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

Hit the Win + R keys to launch Run.
Type in cmd in the field and tap Enter.
After opening Command Prompt, type in this command: sfc /SCANFILE=c:windowsexplorer.exe

Note: If you are using a 64-bit Windows operating system, enter the “sfc /SCANFILE=C:WindowsSysWow64explorer.exe” command instead.

Wait until the process is completed and then restart your computer.

Option 3 – Run the DISM tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “System call failed” 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 problem is now fixed.

Option 4 – Try running the Check Disk utility

In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
After opening Command Prompt, type this command and tap Enter: chkdsk c: /f /r
The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 5 – Put your computer in a Clean Boot State

As pointed out, there are some instances that some conflicting programs installed in your computer might be the one that triggers the “System call failed” error to appear when you try to open File Explorer. To identify which program is causing the problem, you need to put your computer in 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 in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 6 – Try to uninstall the programs you’ve installed recently

In case you don’t know, freeware software packages aren’t always free as some of them could contain malicious software that can cause serious damage to your computer. Thus, if you have installed a program recently prior to getting the “System call failed” error, then you have to uninstall that program.

Tap the Win + R keys to open the Run dialog box.
Then type “appwiz.cpl” in the field and tap Enter to open the Programs and Features in Control Panel.
Next, arrange the list of installed programs in the order of the installation date.
After that, look for the problematic program and right-click on it, and then select Uninstall.
Once the process is done, restart your computer and see if the error is fixed.

Fix Windows Activation Error 0x80070005

Windows uses 2 types of keys for its activation, KMS or MAK. These keys should work without any issues since they are elevated with higher permissions but in some cases, they are by accident run without their proper permission, and then we have access denied error or error 0x80070005 To resolve this issue please first check if not by any chance your antivirus or firewall is preventing slmgr.bs file to access the right permissions, that being said if the previous solution is not working note that you have to be an administrator of the system or have administrator privileges. As an administrator, you will have to use Software Licencing Management Tool or short SLMGR.VBS, a VBS file in Windows used for its activation purposes. As an administrator, open Command prompt with admin permissions and then run slmgr.vbs This will make sure that activation goes through, make sure to use proper options like:

/ipk <ProductKey> or /ato [<Activation ID>]

Quick Fix Guide to Error 2032

What Is Error 2032?

Error 2032 is essentially the hexadecimal format of the error caused. This error code is actually a code format used by the Windows operating system. Manufacturers use this code to determine the cause behind the problem. This error is usually the result of the issues that arise with different applications. When this error occurs, individuals are not able to view multimedia content on their PC. They may also experience system crashes and this makes it crucial to resolve it.

Solution

Error Causes

Error 2032 is caused by problems in Windows system files. Improper registry entries may also cause this problem. Some of the common causes that trigger Error 2032 are improper deletion of hardware or applications. Similarly, incomplete hardware or application installations or uninstallations may also cause issues. These file errors are actually caused when a computer has recently been attacked by a virus, spyware, or malware or if the system is trying to recover from an unanticipated shutdown. Such activities often result in the corruption or deletion of registry entries in Windows system files. The corrupt files will obviously cause problems and the application will fail to perform correctly.

Further Information and Manual Repair

While there are several ways to solve this problem, some of the most useful and practical solutions are listed below as follows.

If you are an advanced user, this workaround is for you. First and foremost, restart your computer and log on to it as the administrator. Now click on the ‘Start’ button. Now follow this path: All programs ->Accessories-> System Tools->System Restore. Once you choose to perform System Restore, you will come across options where you can select to ‘Restore your computer to an earlier time’. This option will appear in a new window. Click on it and then click Next. Click on the Next button again that appears in the confirmation window. Restart your computer after the restoration is finished. You have just resolved the error.
Another easier alternative to fix Error 2032 is for novice users. Download an Error 2032 repair utility. Install this program as you are most likely to come across a Scan button. If there is an option to fix and repair an error, select it after the scan is complete. You can then restart your computer again. Look for the error and you will realize that it has disappeared and that your system is now ready to use.

Fix System Interrupts high CPU usage

System Interrupts are operating system processes that function as an alert system for the CPU. So whenever a scenario needs the attention of the CPU, it alerts the CPU about it. In turn, the CPU suspends what it is doing, saves it, and then takes care of that important job and once that job is completed, it resumes back to what it was doing. This indicates that although System Interrupts appears as a process, it’s actually not. As a matter of fact, it is like a manager that reports to the CPU about all interrupts that happen on a hardware level, e.g. hardware interrupts. And if there are lots of interrupts, this means that there might be various errors occurring on a hardware level. As a result, it may take a lot of system resources. And if you consider disabling System Interrupts, stop right there as your computer will almost become useless without it. So if you see System Interrupts consuming high CPU usage in your Windows 10 computer, you can fix it without having to disable it and cause more problems. If System Interrupts takes up more than 5 to 10% of CPU, then you definitely have a problem. This could be happening due to some hardware or driver issue. The first thing you can do is to try rebooting your computer once and see if the issue comes back or not. High CPU usage of System Interrupts is a huge backlog for the CPU and it stays in the loop. If a simple system restart didn’t fix this issue, here are some suggestions you can try.

Option 1 – Try to update the hardware drivers

As stated, the problem might have something to do with hardware drivers so you can try to update these drivers and see if it works.

Reboot your computer into Safe Mode with networking support.
Tap the Win + R keys on your keyboard to open the Run dialog box.
After that, type “devmgmt.msc” in the field and hit Enter or click OK to open the Device Manager.
After opening the Device Manager, update all the outdated Hardware drivers on your computer.
Next, right-click on all the driver entries that are appropriately labeled, and then click the Update driver option.
Now restart your PC and check if the BSOD error is fixed or not.

Note: On the other hand, if a recent update has caused the System Interrupts high CPU usage, then you might want to roll back your hardware drivers to their previous versions. You can check with the Windows Update History to check out any recent updates as well as the previous ones.

Option 2 – Try to disconnect and reconnect all hardware and cables

A lot of users reported that they were able to fix the problem by disconnecting and reconnecting cables and hardware like scanners, printers, cameras can help in fixing the problem. In addition, you can also boot your computer in a Clean Boot State so that you can find the problematic hardware by hit and trial method. Refer to the steps below to do so:

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

Option 3 – Try to enable or disable Hardware

If you do not want to remove hardware, you can just disable them using the Device Manager. Note that this can also be applied to the internal hardware.

Tap the Win + X + M keys to open the Device Manager.
Next, navigate to the device you want to disable.
Then right-click on it and choose to disable the device.

Note: Make sure that you disable one device at a time and then give it a couple of minutes and check if there are any changes in the CPU usage to pinpoint the hardware. And if there is no change, you need to enable the device you’ve just disabled and then proceed to disable the next hardware device. If there are changes, then it’s probably the culprit. Just keep in mind that you must no disable any device that is needed to keep your system up and running.

Option 4 – Try to update the BIOS/UEFI

Updating the BIOS/UEFI can help you fix the high CPU usage of System Interrupts but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.

Tap the Win + R keys to open the Run dialog box.
Next, type “msinfo32” in the field and press Enter to open System Information.
From there, you should find a search field on the bottom where you have to search for the BIOS version and then press Enter.
After that, you should see the developer and version of the BIOS installed on your PC.
Go to your manufacturer’s website and then download the latest version of BIOS on your computer.
If you are using a laptop, make sure that you keep it plugged in until you have updated the BIOS.
Now double click on the downloaded file and install the new BIOS version on your computer.
Restart your computer to apply the changes made.

Option 5 – Run the Hardware and Devices Troubleshooter or the Performance Troubleshooter

Hardware and Devices Troubleshooter:

The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
After opening Settings, look for the Update and Security option and select it.
From there, go to the Troubleshoot option located on the left-hand side of the list.
Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Performance Troubleshooter:

Tap the Win + R keys to open the Run dialog box.
Type “exe /id PerformanceDiagnostic” in the field and hit Enter to open the Performance troubleshooter.
Then click on Next to get started. Wait until the process is completed.

What to do if Windows is stuck in Tablet Mode

To make the Windows 10 operating system a lot more user-friendly, Microsoft introduced the Tablet Mode for Windows 10 devices, especially the 2-in-1 devices like Surface Pro and Surface Book. Despite the Tablet Mode’s efficiency, it also encounters some errors from time to time. One of the issues users reported about tablet mode is that they can’t turn off or exit tablet mode. If you are one of these users, read on as this post will guide you in what you can do to fix the issue. To fix the problem with Tablet Mode, there are several suggestions you can check out. You can try to check the full-screen setting, or perform a full shutdown or perform two buttons to restart the Surface devices. You could also disable Tablet Mode via Registry Editor or perform System Restore or change the settings in the System tab or the Action Center.

Option 1 – Try to check the full-screen setting

Tap the Win + I keys to open the Windows Settings app.
Then navigate to this path, Personalization > Start.
Next, scroll down to toggle off the “Use Start Full Screen” option.
After that, restart your computer and see if the problem is fixed.

Option 2 – Perform a full shutdown

Open Command Prompt with admin privileges first.
Next, execute this command to perform a full shutdown: shutdown /s /f /t 0
The command you entered will shut down your computer and once it’s turned off, wait for a couple of minutes and then turn it back on.

Option 3 – Try to perform a two-button restart on your Surface device

Tap and hold the power button for about 30 seconds.
Then release them after 30 seconds.
After that, tap and hold the volume up + the power button for 20 seconds. This will cause the display to flash a few times but you have to keep those buttons pressed until your Surface device is turned off.
Wait for a couple of minutes and your Surface will turn back on. This should resolve the problem.

Option 4 – Try to disable the Tablet Mode via Registry Editor

In the Start Search, type “registry editor” and right-click on the Registry Editor from the results, and then select the Run as administrator option. This will open the Registry Editor with admin privileges.
Next, navigate to this registry key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionImmersiveShell
From there, look for the DWORD named “SignInMode” and double click on it.
Set its value to “1” and its base as hexadecimal.
After that, click on OK to save the changes made. This will make sure that you are signed in to the desktop mode when you log into your account.
Now look for the DWORD named “TabletMode” and double click on it and set its value data to “0” and it's base as hexadecimal.
Click on OK to save the changes made and then restart your computer.

Option 5 – Run System Restore

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 6 – Try changing the settings in the System tab or the Action Center

Go to Settings and navigate to System > Tablet Mode.
After that, scroll down to set the “Use desktop mode” from the drop-down menu under the “When I sign in” section.
Now restart your computer and see if the issue is fixed.

System Restore gets stuck or hangs up

As you know, System Restore is a useful tool in Windows operating system that helps users in fixing system issues by undoing any recent changes to the computer that may have caused the problem. However, there are times when you might encounter some issues when running this tool and one of these issues is when System Restore suddenly gets stuck or hangs up on initializing the restoration of the Registry in Windows 10. If you encounter a similar problem, read on as this post will guide you on what you can do in such cases. There are several things you can do when you face this kind of problem in System Restore. First, you can try to wait it out, give it more time to load, which should not take longer than 5 minutes. And if it’s still stuck after that time, give it another hour. However, if nothing changed after an hour, then you need to troubleshoot the problem further. Keep in mind that you must not interrupt System Restore by shutting it down abruptly, it could result in an unbootable system. To get started in troubleshooting the problem, you need to follow each one of the suggestions offered below.

Option 1 – Try to use the Windows Recovery Environment

The first troubleshooting option you need to try is to simply tap the power button for about 10 seconds. This is what you have to do when you have to interrupt System Restore or reset your Windows 10 computer. Tapping the power button for 10 seconds will perform a hard shutdown and once your computer shuts down, restart your computer again and follow the steps below but before you do that, make sure that you have a Windows bootable USB or DVD.

First, insert the bootable USB or DVD and boot into it, and select the “Repair your computer” option.
Next, once you see the manufacturer logo on your computer, tap the key to enter into Windows Recovery Environment.
After that, change the Boot sequence to DVD drive under the UEFI Firmware settings and restart your computer.
Once your computer has restarted, select the boot order and make changes accordingly as displayed in the BIOS.

Option 2 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

You can start by creating and booting from a bootable Windows 10 USB Stick.
After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 3 – Try to run System Restore in Safe Mode

If you can’t boot into your Windows 10 computer, you can try to run System Restore again in the Advanced Startup Options.

Boot your computer into Safe Mode.
After that, select an option > Troubleshoot > Advanced Options > Startup Settings > Restart.
Once your computer has restarted, tap the F6 key to enable Safe Mode with Command Prompt and to run System Restore from there.
Now in Command Prompt, type the “rstrui.exe” command to run System Restore in Safe Mode. This will help in fixing the problem since it would be safer to perform System Restore of the computer.

Fixing To use System Restore you must ...

There are cases when you want to undo some changes you’ve made to your computer and to do that you have to perform the System Restore task. However, if you encounter an error that states “To use System Restore you must specify which Windows installation to restore”, when doing so, read on as this post will help you fix the problem. This kind of error in System Restore could be due to corrupted files in the system. There are also situations where you are not able to boot up once you encounter this error which could be a big problem. On the other hand, this error might have something to do with corrupted BCD files. Whatever the cause is, here are some potential fixes you have to try.

Option 1 – Try to run System File Checker offline

Like pointed out, since the error might be due to corrupted system files, you can try to run System File Checker offline. How? Refer to these steps:

You need to go to the Advanced Startup Options and from there select Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
After opening Command Prompt, type the commands given below and tap Enter right after you type each one of them.
- Cd /
- Dir

If you can see the “Users” folder, that is your system’s drive. However, if you can’t see it, you can just change the drive-by assigning “D” as its alphabet volume.
Then execute this command where “C” is the system drive: sfc /scannow /offbootdir=C: /offwindir=C:Windows
Now repeat the given steps sequentially.

Option 2 – Try to run DISM tool

You can also run the DISM tool to repair the potentially corrupted system image. First, you have to check the health of the system like checking the integrity of the system files and Windows services. To run DISM, follow the given steps below sequentially.

Open Command Prompt from the Advanced Startup options.
After that, execute this command where “C:” is the system volume: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:C:WindowsWinSxS
If you encounter an error after executing the given command, insert the Windows USB or DVD and then execute this next command where “E:” is the USB or DVD drive: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:esd:E:SourcesInstall.esd:1 /limitaccess
In some cases, “install.esd” would be “install.wim” and in such case, you have to modify and execute this command: DISM /Image:C:Windows /Cleanup-Image /RestoreHealth /Source:wim:E:SourcesInstall.wim /limitaccess

Option 3 – Try to repair corrupted BCD

As mentioned, the error could also be due to corruption in BCD, and to fix it, you can use Bootrec.exe – a built-in command-line tool used to troubleshot issues related to boot up and Windows Startup. Before you run this tool, make sure that you have inserted a bootable USB or DVD into your computer. Once you have that covered, follow these steps:

You need to go to the Advanced Startup Options.
Then click on Troubleshoot.
Next, select the Advanced Options and then Command Prompt.
Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
- Bootrec /Fixmbr
- Bootrec /FixBoot
After you execute the commands given above, you should see a confirmation message that says, “The operation completed successfully”.
Now type the “Bootrec /RebuildBCD” command to rebuild BCD.
Finally, close Command Prompt and then restart your computer to successfully apply the changes made.

Option 4 – Try to run the Automatic Repair Utility