How to Fix Windows 10 Error Code 0x80070008

If you receive an error that says, “An unspecified error occurred during System Restore (0x800700b7)” when you tried to restore your Windows 10 PC, worry not, for this post will help you resolve the problem. This kind of error typically occurs when System Restore was not completed successfully and fails instead with this error. Before you start, you must not abruptly shut down your computer and wait for the error to occur. You may receive this error due to many possible reasons. It could be caused by your antivirus program that’s not letting the process complete or corrupted system files which causes the failure or it could also be caused by an unsuccessful installation of a Windows Update. Here are some fixes you can check out if you can still boot into your computer:

Option 1 – Try to disable your antivirus program

Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the System Restore process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and then run System Restore again, don’t forget to enable the antivirus program back again.

Option 2 – 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 the blank dialog boxes. 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 3 – 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 getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

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

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

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

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

Option 4 – Try to run the System Restore in a Clean Boot State

If the first three given options didn’t work and the service still keeps on failing even though the service is running, you can try putting your computer in a Clean Boot State and then try to run System Restore again.

• 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.)
• Now try to run System Restore again and see if the process goes smoothly.

Option 5 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing the problem with System Restore. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go. On the other hand, if you can’t boot into your Windows 10 computer, here are some fixes you can try instead:

Option 6 – Try running System Restore in Advanced Startup Options

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

• Boot your computer into the Advanced Startup Options screen.
• From there, you will see some options to troubleshoot when you can’t log in to Windows in the usual way.
• Now select Troubleshoot > Advanced Options > Command Prompt.
• After that, type “rstrui” and hit Enter to execute the command which will start the System Restore process.

Option 7 – Run the SFC scan and DISM via Advanced Startup Options

Like what you did in the first given option, you can use the Advanced Startup Options to run both System File Checker and DISM. All you have to do is boot into the Advanced Startup Options and from there select Troubleshoot > Advanced Options > Command Prompt. After accessing Command Prompt, you can run the System File Checker scan first by entering the “sfc /scannow”. As for DISM, you can run the “Dism /Online /Cleanup-Image /RestoreHealth” command.

Option 8 – 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 in 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.

Error Code 0x801901F7 – What is it?

Error code 0x801901F7, also known as “The Server Stumbled” error because it shows a message saying “The Server Stumbled. We all have bad days” is associated with Windows Store. Server Stumbled Error 0x801901F7 is an error related to the MS server. The error occurs due to damaged registry files, malware, virus, and corrupted data. You should fix this error to prevent a system crash or a BSOD error. There are some things you can do to fix it. These are not so complex. So, anyone can try these methods to fix error 0x801901F7. Common Symptoms for error 0x801901F7:

• Problems with Windows startup
• System becomes very slow or the system freezes
• Blue screen of death appears
• Windows fails to start some process due to Stop error code 0x801901f7

Solution

Error Causes

• This error is generally caused by corrupt registry files.
• Virus infection can cause this problem.
• Outdated driver, missing .DLL files may also cause this error.
• Microsoft server overload may cause this problem as well.
• Incorrect configuration may cause this problem.

Further Information and Manual Repair

To fix error 0x801901f7, there are four methods listed below. Some might work for you and some might not. Please try all of them to fix this error.

Method 1:

Basic method to fix error code 0x801901F7: Resetting Windows Store Cache Most of the time clearing or resetting the cache helps. It doesn't always work, but you should try this first before moving on to some advanced methods which are mentioned below. To reset the Windows Store cache please follow the simple steps below

• Open RUN by searching or pressing "Windows Key + R"
• Type "wsreset.exe" and press Enter or click on OK.
• Windows Store will open automatically along with a command prompt.
• This will reset Windows Store and you might see it loading as it should.

This method might work but if it fails to solve Error 0x801901F7 then follow the method below.

Method 2:

Advanced method of fixing error code 0x801901F7: Deleting Windows Store database file. By using this method, you will be deleting the database file for Windows Store. This file is located on your C drive or the drive where you installed your Operating System. Follow the steps below.

1. Navigate to C:WindowsSoftwareDistributionDataStoreDataStore.edb.
2. Delete DataStore.edb file from there.
3. Now Open Windows Store and see if you still get error code 0x801901F7.

The Datastore.edb file that you deleted will be automatically created once you perform Step 3 which is launching Windows Store. If you still cannot get this error away then Close Windows Store and Reboot your PC then Launch Windows Store Again.

Method 3:

Modifying Windows update properties: Perform the steps below only if the above-mentioned methods fail. You will be tweaking a few things in the Windows update to see if it helps.

1. Open Task Manager by right-clicking on Taskbar, then click on Task Manager.
2. Go to Services Tab. Click on Open Services at the very bottom of the Window.
3. Now a new window will pop up. Scroll down & find "Windows Update" from the list.
4. Double click on Windows update to open up its Properties.
5. Now from the Startup Type drop-down list, select Automatic. Click on Apply, Start, and then Ok.

Now you need to perform just one more step. Reset Windows Store again (Refer to method 1 for Steps). This should fix your Windows Store error that shows The Server Stumbled with 0x801901F7 Error Code.

Method 4: 

If the error is due to a problem with a driver, then follow the method below to uninstall the current driver:

1. Open the Run command and type “sysdm.cpl” in the text box.
2. Click Enter.
3. Open the Hardware tab on the system properties dialog box.
4. Then press on Device Manager.
5. Double press on Device type and then press on the hardware device that is reporting error code 0x801901F7.
6. Go to the Driver tab and press on Uninstall button to uninstall the device driver completely.
7. Now, install the new driver on your computer.
8. Restart your computer.
9. Run virus scan of your PC
10. Try using a different USB port.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

We have gathered and want to share with you all of the Windows 11 wallpapers if you would like to place them on your desktop now and now wait for the official W11 release. Hope that you will like some of them and I hope to see you again on errortools.com Download Windows 11 Wallpapers here!

And here is the preview of them

Besides Star Trek, Star Wars was one of my favorite movie franchises, as a kid, it was the first movie I have seen in Theatre and over the years I have rewatched and reached each entry in the franchise. It has significantly grown over the years, sometimes for worse, sometimes for better but what it always did is explored and expanded lore, characters and brought stories interesting and original enough. The Series has always been original and innovative enough with interesting characters and locations and it managed to capture the imagination of many viewers around the globe. If you or someone else is watching the franchise for the first time it is recommended actually to watch everything how it was released because of some information that is spoiled in prequels that could spoil some interesting revelations later. But if you have already watched everything and would like to follow the story from the beginning to end we are presenting you with the list of all TV series and movies in tar Wars canon in their chronological order so you can enjoy some good character developments and see the whole story unfold how it was meant to be. In the following list, as told, we are including TV series (both released and currently in production) in the Star Wars canon.

Chronological order of Star Wars franchise:

Star Wars: The Acolyte Acolyte is upcoming TV series exploring times in the old republic and the rise of the dark side within Star Wars Episode I: The Phantom Menace The first movie entry in the franchise introducing some key characters who will go through various adventures yet to come Star Wars Episode II: Attack of the Clones Continuation of story and deepening of the plot laid out in the previous movie Star Wars: The Clone Wars Animated TV series exploring war in more detail, set in the period between episodes 2 and 3, before series there is clone wars full length animated movie titles simply as Star wars clone wars serving as a pilot to series. Star Wars Episode III: Revenge of the Sith Last movie in so-called prequel trilogy finishing some stories and finalizing some character arcs Star Wars: The Bad Batch Upcoming animated series Bad batch will focus on few troopers find their way in changing the galaxy Solo: A Star Wars Story Story of everyone loved Han Solo character, this origin story will introduce you to some key characters in the later entry of series Obi-Wan Kenobi Upcoming series that will focus on everyone's favorite JEDI master Obi-Wan Star Wars Rebels Animated series exploring first sparks of forming rebel alliance against dreaded empire Andor Upcoming series set five years before the events of Rogue One, the series follows rebel spy Cassian Andor during the formative years of the Rebellion. Star Wars Rogue One Full feature movie setting up events for episode 4 Star Wars Episode IV: A New Hope First Star Wars movie, little outdated today with special effects but with a strong story and introducing some new characters which will become main icons of franchise Star Wars Episode V: The Empire Strikes Back Arguably the best movie in the whole series, leaning more to serious note and darker than previous entries. Besides Episode 3 this is the most serious and dark movie of the series. Star Wars Episode VI: Return of the Jedi Last movie entry in the so-called original trilogy, finishing some stories and wrapping up one era. Star Wars The Mandalorian Set after episode 6 show focuses on a Mandalorian bounty hunter character following his adventures in the galaxy. The Book of Boba Fett Upcoming Mandalorian spin-off TV series focusing on Bobba Fet, one of most loved bounty hunter characters in the Star Wars universe Ahsoka Star Wars: Ahsoka is an upcoming live-action television limited series exploring the character of Ashoka Tano first seen in Clone Wars Rangers of the New Republic Set within the timeline of The Mandalorian, Rangers of the New Republic is a new upcoming live-action series. Star Wars: Resistance Animated series exploring resistance against first-order setting up events to be followed in the newest trilogy of movies. Star Wars Episode VII: The Force Awakens First full feature movie set in the post-empire era introducing new characters and bringing back some fan favorites. Star Wars Episode VIII: The Last Jedi The second movie in the last order trilogy, continuing stories of previously establishes characters Star Wars Episode IX: The Rise of Skywalker Last entry in new order trilogy of movies, finishing some open stories and concluding arcs for characters previously introduced in Force Awakens. That's it, chronological order of canon TV shows and movies of the Star Wars franchise. We are sure there will be more movies and shows in the future and someday we will revisit this list to include them as well. Until then, may the force be with you. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

One of the biggest annoyances in Windows 10 is that it’s upgrading from one version to another. Although these upgrades are necessary to fix some bugs or improve user experience, some of them actually bring bugs into the computers instead. And in one of the recent Windows 10 updates, a lot of issues were found especially for users who use Remote Desktop on a daily basis. The error stacks up as Windows 10 Remote Desktop Protocol client is not working or won’t connect and can’t find the computer HOSTNAME generally. Based on the reports by users who experienced this issue, there are two cases around it:

1. Users who try to reach a specific website or folder on the network

Some users encounter this error when they try to run the Network Troubleshooter. Even when they add the server name inside it, it still won’t identify the problem, and unpredictably, the driver seems to appear and disappear every now and then. And even after connecting, the network commands don’t work at all. This is really troublesome for users who have lots of PCs and all the other systems do not appear on the network.

2. Remote Desktop isn’t able to find the computer HOSTNAME

Some other users reported that the error appeared when they use the classic remote desktop software. It keeps on failing and throwing the error message, “Remote Desktop can’t find the computer “HOSTNAME”. If this is the same scenario you are having, it means that “HOSTNAME” does not belong to the specified network. So you need to verify the computer name and domain where you are trying to connect to. There are times when it used to work after some users tried connecting to the domain a couple of times. However, when users try to use the UWP version of Remote Desktop, it seems to connect most of the time. This kind of problem is definitely a DNS issue. It could be that there are two different records on the DNS server which is why it connects and other times it doesn’t. When it is able to resolve the correct address, the drives connect to the PC however, after a couple of minutes, they will suddenly go missing. Using “nslookup” for the hostname, multiple times, you can check this and see if you’ll get identical results all the time.

nslookup [–SubCommand …] [{ComputerToFind| [–Server]}]

If you’ve determined that the drives disappear each time, you may have to change the DNS server or ask your admin to resolve the problem for you. Alternatively, you can also check out another option that has worked for a lot of users. This second option is disabling the IPv6 on the network adapter. In case you don’t know, Windows 10 prefers IPv6 over IPv4 so if you now have issues using IPv6 to connect to the servers, you can change your computer’s settings so that it’ll only use IPv4 instead of IPv6. To do so, follow these instructions:

• Open Settings > Network and Internet > Ethernet > Change Adapter options.
• From there, right-click on the adapter for where you want to disable it and then select Properties.
• Next, look for the checkbox labeled, “Internet Protocol Version 6 (TCP/IPv6)” then uncheck it.
• Now click on OK and restart your PC to save the changes made.

What is Error 0x8024a11a or 0x8024a112 ? If you are trying to update your Windows 10 computer and just when you were done downloading the feature update and about to install it, you encounter an error message saying:

“We’re having trouble restarting to finish the install, Error 0x8024a11a, 0x8024a112, 0x80070005 or 0x80070032”

And so to fix this problem, this post will give you a couple of possible solutions. Refer to the options given below to get started.

Option 1 – Restart your computer many times

This is the first thing you can try since there are instances when the Windows Update process gets stuck for a minor thing and restarting the computer usually helps in resolving the issue. All you have to do is click the Restart now button. However, if it does not work, you can use the Power buttons from the Start Menu or WinX Menu. Aside from that, you can also use your power buttons such as Alt + Ctrl + Del to restart your computer. And during the boot process, it is recommended that you restart your computer in Safe Mode or even in a Clean Boot State. After that, you can restart your computer in normal mode. This will make sure that no third-party processes will be able to interfere with the Windows Update process. To put your PC in a Clean Boot State, here’s what you have to do:

• 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.)
• After that, try to install the Windows Updates or upgrade again.

Option 2 – Try running the Windows Module Installer

The Windows Module Installer is a built-in service in the Windows operating system that could help you resolve the Windows update error 0x8024a11a or 0x8024a112. You need to make sure that this service is Started and that its Startup type is set to Automatic – you can do this via Services Manager or by executing the command given below in an elevated Command Prompt.

• Tap the Win + R keys to open the Run dialog box.
• Then type “command prompt” in the field and hit Enter to open Command Prompt.
• And in the elevated Command Prompt type in the following command and hit Enter:

SC config trustedinstaller start=auto

• After executing the command successfully, you should see the “[SC] ChangeServiceConfig SUCCESS” message on the Command Prompt window.

Option 3 – Run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the Windows update error 0x8024a11a or 0x8024a112.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 4 – 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 getting the errors 0x8024a11a and 0x8024a112. 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.

Option 5 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows update error 0xca00a000. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 6 – Run Microsoft’s online troubleshooter

Running Microsoft’s online troubleshooter might also help you fix the Windows update error 0x8024a11a or 0x8024a112. This online troubleshooter is known to help in fixing Windows Update errors, it scans your computer for issues that might be causing the problem and then fixes them automatically.

One of the important functions in the Windows operating system is the Task Scheduler. It can automatically run various tasks at a certain time where you’ll have to add a task that needs to be executed and then choose the time it has to run at. So when that time comes, the Task Scheduler will run the task automatically. However, some users reported getting an Error 0x80070057 where the Task Scheduler fails to start. This kind of error may be due to a disabled service that prevents the service from running. It is also possible that the antivirus program interfered with the task – it could be that the Task Scheduler is somewhat in the block list since the antivirus adds it to the list automatically when it’s installed. On the other hand, it could be that you lack administrator-level privilege which is why the Task Scheduler was not able to carry out the task. To fix this issue, here are some suggestions you can try.

Option 1 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
• After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
• Click on the “RUN” option and select the “Restart the Service” option.
• And click on the “After Second Failure” option and then select the “Restart-Service” option again.
• Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
• Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 2 – Try to temporarily disable the anti-virus program

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

Option 3 – Run the Task Scheduler with an administrator account

Like pointed out, the Task Scheduler Error 0x80070057 may be due to the lack of admin privileges. Thus, you have to log in to an administrator account and try running the Task Scheduler again. It is also recommended that the administrator account you’re going to use as a password when logging in.

Option 4 – Repair the Task Scheduler by deleting corrupted tasks

Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

• Tap the Win + R keys to open the dialog box for Run.
• Next, type in Regedit and click on OK or tap Enter to open the Registry Editor.
• Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

• Right-click on the task name and then delete it.
• After that, delete the very same GUID which you have copied earlier from these folders:
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

• Next, navigate to this location: C:/Windows/System32/Tasks
• Delete the very same tasks you just deleted from the Registry Editor.
• Restart your PC and check if the Task Scheduler is back to its normal state or not.

Recently, a number of users reported that they were not able to use the “Run as administrator” context menu option when they tried using it or opening a program with administrator privilege. If you are one of these users facing this problem, then you’ve come to the right place as this post will guide you in fixing this issue. At the time of writing, it isn’t clear what the cause of the issue is but there are potential fixes you can try to fix the problem. You can try turning on the User Account Control or clean up the Context Menu items change the Group Membership. On the other hand, you can also perform both SFC and DISM scans via Command Prompt or troubleshoot the problem in a clean boot state as it is possible that some third-party programs are the ones that are causing the problem. You could also run an anti-malware scan using Windows Defender or your antivirus program.

Option 1 – Try to turn on the User Account Control

When you open a program with administrator privilege, the User Account Control or UAC prompt will pop up asking you to confirm the permission. However, if you have disabled the User Account Control by mistake or some malware has disabled it, then it’s no wonder why the “Run as administrator” option is not working. Thus, you need to check if UAC is turned on or not. All you have to do is go to the User Account Control settings.

Option 2 – Try changing the Group Membership

• First, you need to sign in with your administrator account or ask your administrator to sign in for you. So if you only have a Standard User account, you have to add that account to the Administrators group.
• In the taskbar search box, type “netplwiz” and check the search results.
• From there, select your user account and click the Properties button.
• After that, go to the Group Membership tab and select Administrator.
• Now click on the Apply and OK buttons to save the changes made and then sign in to your computer again and see if the “Run as administrator” option is working or not.

Option 3 – Try to create a new Administrator User account

If you have a standard account, you can try creating a new account but this time, you create an administrator user account and then see if you can now use the Run as administrator option or not. Note that you have to sign in with your main account before you can create an admin account.

Option 4 – Run the DISM tool

You can run the DISM tool as well to help fix the problem with the “Run as administrator” option. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Perform a System File Checker scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the problem with the “Run as administrator” option on your Windows 10 computer. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

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

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.

• Once done, restart your computer.

Option 6 – Put your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing you from using the “Run as administrator” option and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try to use the Run as administrator again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• 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.)
• After you’ve set your computer into a Clean Boot State, try to check if the error is now fixed and that you can now view the Properties.

Option 7 – Try scanning your computer using Windows Defender

As mentioned, if your computer was recently infected with some malware, it is possible that the malware changed the User Account Control settings which is why you’re not able to use the Run as administrator option. Thus, you need to scan your computer using Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

If you encounter the “Setup has failed to determine supported install choices” error when trying to downgrade or upgrade your Windows 10 computer, this signifies that there are some compatibility issues with the installation process and that Windows was not able to either downgrade or upgrade to another version. Usually, this error occurs when you are using the built-in options in Windows 10 upgrade or downgrade to another version of Windows. This option is mostly used as it keeps the user settings as well as data intact. Thus, you need to keep in mind a lot of parameters before you proceed with the installation because if there is any conflict in the process, you certainly won’t be able to downgrade or upgrade your Windows computer. To resolve the issue, here are some suggestions that might help.

Option 1 – Try running in Compatibility mode

This is the first thing you can try to resolve the issue instead of going right ahead on making a bootable device. So if you are downgrading Windows, you can try to run the installer in the compatibility mode for that specific Windows version.

• Look for the setup file.
• Once you find it, right-click on it and select Properties from the context menu.
• After that, go to the Compatibility tab and mark the checkbox for “Run this program in compatibility mode for:” and from the drop-down list, select either Windows 7 or Windows 8.
• You also have to check the “Run as administrator” option.
• Now click the Apply button and then click OK to save the changes made and check if it has resolved the issue or not.

Option 2 – Option 2 – Try troubleshooting compatibility

This option is almost the same as the first one except it is an alternative way of fixing the “Setup has failed to determine supported install choices” error in case the first one didn’t work. In this option, you will troubleshoot the compatibility issue.

• Look for the setup file.
• Then right-click on it and select the “Troubleshoot compatibility” from the context menu.
• After that, click on the “Try recommended setting” option. Once the process is done, the error message should be gone.

Option 3 – Try to use the setup file instead of an image

If you are running the Windows ISO image for the installation, you can try running the setup file instead. This is because when you try to install Windows from an image file directly, it has to be loaded into a virtual CD drive first, and then from there, further operations are carried out. And so, you can just bypass this mechanism to avoid getting the “Setup has failed to determine supported install choices” error.

• First, you need to extract the disk file to an accessible location.
• After that, go to Sources > Setup.exe.
• Now run the setup file to upgrade or downgrade the Windows version. Just make sure that you do run the setup file as an administrator.

Option 4 – Try to do the upgrade or downgrade in a Clean Boot state

Putting your PC in a Clean Boot state can also help when you want to upgrade or downgrade your version of Windows without any trouble because, during this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• 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” checkbox 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” checkbox.
• 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.)
• After that, try to install the Windows Updates or upgrade again.

Option 5 – Try to use the Media Creation tool

The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.