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.
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.
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.
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.
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.
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.
If you have a Runtime Error 339 issue on your computer, here is a great way how you can fix it right away:
Error code 80070103 affects Windows users who attempt to access the latest updates for hardware drivers using Windows Update. Windows 10 users who are affected by this error code will be unable to complete the upgrade process. This error code usually occurs due to the Windows Update attempts to download an incompatible version of a driver or a driver that is already downloaded on one’s device.
The cause of error code 80070103 in Windows 10 is usually easy to determine. This is due to the fact that the error code only affects users who attempt to access updates related to hardware drivers. In such cases, the error code will only occur if the Windows Update website or tool on your machine attempts to install a driver that is already present on one’s machine or the version of the driver is unsuitable for one’s machine due to lower compatibility.
Manual repair methods are very effective in helping Windows users fix problems related to error code 80070103 as well as other errors. These repair methods can usually be implemented by users with very limited technical skills. In some cases, however, you may need to contact a Windows repair technician, i.e. if you have problems following the manual repair method instructions provided or if the repair methods prove unsuccessful.
In the case of error code 80070103, the problem can be rectified by either hiding the update or reinstalling the hardware driver. Windows users can hide an update on the Windows Update website or via Windows Update within their machine’s Settings. However, users will need to contact their device manufacturer to reinstall hardware drivers in most instances. See below for further details regarding these manual repair methods.
In the case where you are informed via an error message box that a driver, for instance, your graphics driver, is incompatible you may need to consider hiding the update to prevent error code 80070103 from reoccurring on your machine.
The incompatible issues will come about when the Windows Update website attempts to download a driver that is already on the device or one with a lower compatibility. When you hide the update, it is in essence, preventing Windows Update from offering this driver in the future. To complete this manual repair method, follow the steps below:
You may also complete this process by opening Windows Update within your computer’s settings, then selecting the Optional update or available link. Once you’ve done this, you may then select the updates you would like to install and hide the update that has resulted in the occurrence of error code 80070103.
In the case where you need to install a hardware driver, you will need to contact the manufacturer of your device. Once you’ve contacted the manufacturer or visit the manufacturer’s official website, you can then install the latest device drivers manually. Read the instructions for the installation of the latest drivers carefully. This will ensure you avoid any problems and improve your chances of successfully fixing error code 80070103.
After you’ve contacted your device manufacturer and completed the process of reinstalling the hardware driver, check Windows Update to see whether or not error code 80070103 has been rectified. If the problem was related to your hardware driver and you successfully reinstalled the driver, the error code will not reoccur when you attempt to download the latest updates for your hardware drivers.
However, you may need to take another approach if this manual repair method fails to fix error code 80070103. For instance, consider getting help from a Windows repair technician who is equipped with the skills and expertise necessary to offer a detailed inspection of your machine. Though the error code is related to one’s drivers, the fact that a Windows error code occurred may mean that your system needs a thorough evaluation as other issues may be present.
If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.
“It looks like you don’t have permission to save changes to this file. Try saving a copy instead.”There are several options you can explore to resolve this error. You can try updating the Microsoft Photos app or verify the ownership of the destination folder. You can also re-register and reinstall the app. For more detailed instructions, make use of the options provided below.
Set-ExecutionPolicy Unrestricted
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}Note: In the command given, do not forget to replace the “PackageFullName” with the actual package name for the Photos app. After executing the command, it will uninstall the Photos app from your computer so you need to install it again from the Windows Store by simply looking for it. Once you found it, just click on install to start the installation process.
“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.
“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit. As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices. Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that type in “cmd” and hit Enter to open the Command Prompt. Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option. Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager. Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned. Step 6: Next, select a non-present device and click Uninstall from the Driver tab. Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use. Step 8: Restart your computer. You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not. Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.