diff --git a/windows/deploy/images/upgrade-process.png b/windows/deploy/images/upgrade-process.png new file mode 100644 index 0000000000..b2b77708fc Binary files /dev/null and b/windows/deploy/images/upgrade-process.png differ diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 3002f1a5b2..5765d2849c 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -16,96 +16,169 @@ localizationpriority: high **Applies to** - Windows 10 -Some information about this topic +This topic provides a brief introduction to Windows 10 installation processes and provides resolution procedures you can use to resolve common problems. -## An intro topic +## The Windows 10 upgrade process -Maybe an image here +The Windows Setup application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings. When performing an operating system upgrade, Windows Setup uses the following phases: -- image - +1. Downlevel phase: The downlevel phase is run within the previous operating system. Installation components are gathered. +2. Safe OS phase: A recovery partition is configured and updates are installed. An OS rollback is prepared if needed. + - Example error codes during this phase: 0x2000C, 0x20017 +3. First boot phase: Initial settings are applied. + - Example error codes during this phase: 0x30018, 0x3000D +4. Second boot phase: Final settings are applied. This is also called the OOBE boot phase. + - Example error codes during this phase: 0x4000D, 0x40017 -## Some troubleshooting information +>The computer can also enter a fifth, rollback (uninstall) phase if the upgrade is unsuccessful. -Some text here +Four phases of a Windows 10 upgrade: -
Error code | -Cause | -Mitigation | +DU = Driver/device updates.
---|
|
+
|
+
|
+
Log file | Description | Location | +
setupact.log | Contains information about setup actions during the installation.
+ This is the most important log for diagnosing setup issues. |
+Down-Level phase: $Windows.~BT\Sources\Panther +Rollback phase: $Windows.~BT\Sources\Rollback +First & second boot phase: $Windows.~BT\Sources\Panther\UnattendGC +Pre-initialization: Windows +Post-upgrade: Windows\Panther + |
+
setuperr.log | Contains information about setup errors during the installation. | Same location as setupact.log | +
Setupmem.dmp | If OS bugchecks during upgrade, setup will attempt to extract a mini-dump. | $Windows.~BT\Sources\Rollback | +
miglog.xml | Contains information about the user directory structure. This information includes security identifiers (SIDs). | Windows\Panther | +
Appraiser XML logs | Contains application compatibility information. | $Windows.~BT\Sources\Panther | +
BlueBox.log | Contains information communication between setup.exe and Windows Update. | Windows\Logs\Mosetup | +
Error code + | Cause + | Mitigation | |
0xC1900101 - 0x20017 | +A driver has caused an illegal operation and Windows was not able to migrate the driver, resulting in a rollback of the operating system. | +To resolve this issue: - | |
0xC1900200 | -Setup.exe has detected that the machine does not meet the minimum system requirements. | -Ensure the system you are trying to upgrade meets the minimum system requirements. See [Windows 10 specifications](https://www.microsoft.com/en-us/windows/windows-10-specifications) for information. |
-|
0x8007002C - 0x4000D | -The user cancelled an interactive dialog. | -Start the upgrade process again again. | -|
0x80090011 | -A device driver error occurred during user data migration. | -Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process.
- Ensure that “Download and install updates (recommended)” is accepted at the start of the upgrade process. |
-|
0xC7700112 | -Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk. | -This issue is resolved in the latest version of Upgrade Assistant.
- Ensure that “Download and install updates (recommended)” is accepted at the start of the upgrade process. |
-|
0xC1900101 - 0x30018 | -A device driver has stopped responding to setup.exe during the upgrade process. | -Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers.
- Ensure that “Download and install updates (recommended)” is accepted at the start of the upgrade process. - |
-|
0x80190001 | -An unexpected error was encountered while attempting to download files required for upgrade. | -To resolve this issue, download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). - | -|
0xC1900101 - 0x20017 | -A driver has caused an illegal operation and Windows was not able to migrate the driver, resulting in a rollback of the operating system. | -To resolve this issue: 1. Make sure all that drivers are updated. 2. Open the Setuperr.log and Setupact.log files under the %windir%\Panther directory, and then locate the problem drivers. Refer: [Understanding Failures and Log Files](https://technet.microsoft.com/en-us/library/ee851579.aspx) 3. Update or uninstall the problem drivers. |
|
0x80246007 | -The update was not downloaded successfully. | -Attempt other methods of upgrading the operatign system. -Download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). - Attempt to upgrade using .ISO or USB. -**Note**: Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the [Volume Licensing Service Center](https://www.microsoft.com/licensing/servicecenter/default.aspx). + + | |
0xC1900101 - 0x30018 | +A device driver has stopped responding to setup.exe during the upgrade process. | +Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers.
+ Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. |
|
0xC1900201 | -The system did not pass the minimum requirements to install the update. | -Contact the hardware vendor to get the latest updates. | + + +|
0x8007002C - 0x4000D | +The user cancelled an interactive dialog. | +Start the upgrade process again again. | |
0x80240017 | -The upgrade is unavailable for this edition of Windows. | -Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator. | -|
0xC1900101 - 0x4000D | -A driver configuration issue occurred during the Windows setup process and a rollback occurred. | -Review the rollback log and determine the stop code. The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder. Look for text similar to the following: + + | |
0xC1900101 - 0x4000D | +A driver configuration issue occurred during the Windows setup process and a rollback occurred. | +Review the rollback log and determine the stop code. The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder. Look for text similar to the following:
Typically there is a a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures: |
|
0x80070020 | -The existing process cannot access the file because it is being used by another process. | -Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135). | -|
0x80070522 | -The user doesn’t have required privilege or credentials to upgrade. | -Ensure that you have signed in as a local administrator or have local administrator privileges. | -|
0xC1900107 | -A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade. + | ||
0xC1900101 - 0x40017 | +Windows 10 upgrade fails after the second reboot, which is most like to be caused by a faulty driver, for example antivirus filter drivers or encryption drivers. | +Clean boot into Windows, and then attempt the upgrade to Windows 10. + +For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135). + + Ensure you select the option to "Download and install updates (recommended)." |
-Reboot the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and cleanup the temporary as well as the System files. For more information, see [Disk cleanup in Windows 10](https://support.microsoft.com/en-us/instantanswers/8fef4121-711b-4be1-996f-99e02c7301c2/disk-cleanup-in-windows-10). |
0xC1900209 | -The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications. | -Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See [Windows 10 Pre-Upgrade Validation using SETUP.EXE](https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setup-exe/) for more information. + |
Error code + | Cause + | Mitigation + |
0xC1900200 | +Setup.exe has detected that the machine does not meet the minimum system requirements. | +Ensure the system you are trying to upgrade meets the minimum system requirements. See [Windows 10 specifications](https://www.microsoft.com/en-us/windows/windows-10-specifications) for information. |
+
0x80090011 | +A device driver error occurred during user data migration. | +Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process.
+ Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. |
+
0xC7700112 | +Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk. | +This issue is resolved in the latest version of Upgrade Assistant.
+ Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. |
+
0x80190001 | +An unexpected error was encountered while attempting to download files required for upgrade. | +To resolve this issue, download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). + | +
0x80246007 | +The update was not downloaded successfully. | +Attempt other methods of upgrading the operatign system. +Download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). + Attempt to upgrade using .ISO or USB. +**Note**: Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the [Volume Licensing Service Center](https://www.microsoft.com/licensing/servicecenter/default.aspx). + |
+
0xC1900201 | +The system did not pass the minimum requirements to install the update. | +Contact the hardware vendor to get the latest updates. | +
0x80240017 | +The upgrade is unavailable for this edition of Windows. | +Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator. | +
0x80070020 | +The existing process cannot access the file because it is being used by another process. | +Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135). | +
0x80070522 | +The user doesn’t have required privilege or credentials to upgrade. | +Ensure that you have signed in as a local administrator or have local administrator privileges. | +
0xC1900107 | +A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade. + | +Reboot the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and cleanup the temporary as well as the System files. For more information, see [Disk cleanup in Windows 10](https://support.microsoft.com/en-us/instantanswers/8fef4121-711b-4be1-996f-99e02c7301c2/disk-cleanup-in-windows-10). | +
0xC1900209 | +The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications. | +Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See [Windows 10 Pre-Upgrade Validation using SETUP.EXE](https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setup-exe/) for more information.
You can also download the [Windows Assessment and Deployment Kit (ADK) for Windows 10](http://go.microsoft.com/fwlink/p/?LinkId=526740) and install Application Compatibility Tools. |
0xC1900101 - 0x40017 | -Windows 10 upgrade fails after the second reboot, which is most like to be caused by a faulty driver, for example antivirus filter drivers or encryption drivers. | -Clean boot into Windows, and then attempt the upgrade to Windows 10. See [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135) for more information.
- Ensure you select the option to “Download and install updates (recommended).” + |
display is not compatible | +The display card installed is not compatible with Windows 10. | +Uninstall the display adapter and start the upgrade again. When setup completes successfully, install the latest display adapter driver using Windows Update or by downloading from the computer manufacturers website. Use compatibility mode if necessary. |
display is not compatible | -The display card installed is not compatible with Windows 10. | -Uninstall the display adapter and start the upgrade again. When setup completes successfully, install the latest display adapter driver using Windows Update or by downloading from the computer manufacturers website. Use compatibility mode if necessary. - | -
0x8007002 | -This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403) | -Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760) + |
0x8007002 | +This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403) | +Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760)
The error 80072efe means that the connection with the server was terminated abnormally. To resolve this issue, try the OS Deployment test on a client in same VLAN as the Configuration Manager server. Check the network configuration for random client-server connection issues happening on the remote VLAN. |
Error 800705B4: This operation returned because the timeout period expired. | -A time out issue set by the task sequence limitation to 180 mins of run time. This can also occur if the System Center client is corrupted. | -Review the SMSTS.log file and verify the following error is displayed: + |
Error 800705B4: This operation returned because the timeout period expired. | +A time out issue set by the task sequence limitation to 180 mins of run time. This can also occur if the System Center client is corrupted. | +Review the SMSTS.log file and verify the following error is displayed: Command line execution failed (800705B4) TSManager 3/30/2016 10:11:29 PM 8920 (0x22D8) Failed to run the action: Upgrade Windows. To resolve this issue, increase the default task sequence run time and change the task sequence to have the content downloaded locally prior to installation. |
-
- - | -
- Cause - |
-
- Mitigation - |
-
- Contact - your system administrator to upgrade Windows Server or Enterprise Editions - |
-
- This - issue occurs if you run the updater tool. The tool works only with the - Windows 10 Home, Pro, and Education editions. - |
-
- To - resolve this issue, use a different method to upgrade to Windows 10 version - 1607. For example, download the ISO, and then run Setup from it. - |
-
- When - doing an upgrade to Windows Version 1607 is it supported to use a custom - install.wim (sysprepped) instead of the default install.wim that comes with - Windows Version 1607 - |
-
- Unsupported - |
-
- It - is not supported to replace the install.wim with custom wim (sysprepped or - not). It is supported to do some minor changes to the default install.wim - such as injecting latest cumulative update or remove inbox apps. - |
-
- 0xC1420127 - |
-
- The
- typical conversion of the error means that the specified image in the
- specified wim is already mounted for read/write access. |
-
- This - error would be very rare on Upgrades of WIN10 specially when upgrading to the - Anniversary 1607 Build. This issue has been fixed with the Cumulative updates - released in June 2016 for Windows 10. When we perform an Upgrade, it is recommended - to Perform a Windows Update first and apply all important updates on the - current OS and then start the Upgrade process for Windows 10. - |
-
- 0x8004100E - |
-
- This - error code indicates that there is a problem with an Application that has an - Invalid WMI Namespace - |
-
- In - order to fix this problem, we need to open Application Event log and Check - for Errors for various applications that could be causing this - error. You can use WMIDIAG tool and make sure that the WMI is working - well. The step by step instructions are available at: - https://technet.microsoft.com/en-us/library/ff404265.aspx - |
-
- 0x80070003- - 0x20007 - |
-
- This - error occurs when there is problem with the Internet connection during the - Windows 10 upgrade. - |
-
- Since
- this error indicates that the internet connection ran into a problem, you may
- attempt to fix the connectivity issues and reattempt the download of the
- files. |
-
- 0x80070004 - - 0x3000D - |
-
- SYSTEM, - LOCAL, SELF, System, and Network are reserved names that can’t be used for - Computer Name. - |
-
- Ensure
- that you do not use the reserved names as the Computer names. Rename the
- system to a valid Computer name. |
-
- 0x80070004 - - 0x50012 - |
-
- The - Computer account for the system has an invalid name. - |
-
- Please - ensure that the machine name does not have any invalid characters (See - https://technet.microsoft.com/en-us/library/cc749460(v=ws.10).aspx). - Additionally, the names should not be any of the reserved names for systems. - Rename the system to a valid computer name and try the Setup again. See KB - 3086101 for more details. - |
-
- 0x80070005 - - 0x4000D - |
-
- This - error code means The installation failed in the SECOND_BOOT phase with an - error in during MIGRATE_DATA operation. - |
-
- This - issue may occur if we have any application / driver that is causing an issue - while the upgrade to Windows 10 is going on. Preform a clean boot on - the system. Refer https://support.microsoft.com/en-us/kb/929135 for steps to - perform a Clean boot. - |
-
- 0x80070057 - |
-
- This - error means that One or more arguments are invalid - |
-
- This - is a very generic error, and it could be due to any of the issues that we - would have on the machine. This error may not be related to Upgrade only. It - could be due to any programs; device drivers etc. There is no specific - resolution for this error - |
-
- 0x8007007e - |
-
- The - error indicates one of the modules required to upgrade to Windows 10 was not - found, some of these modules could be manifest files, COM Classes, DLL or any - app packages that may be missing. - |
-
- When
- we start the upgrade of the OS, the Setup engine is responsible to check and
- confirm that all OS components / modules are running in good health, so that
- the upgrade succeeds. When we have any issues being reported
- with manifest files, COM Classes, DLL or any app packages, the setup
- engine would give this error. In order to fix this error, we would suggest to
- follow the solutions as below and then start the upgrade again. |
-
- 0x8007025D - - 0x2000C - |
-
- This - error occurs if the ISO file's metadata is corrupt. - |
-
- Re-download
- the ISO/Media and re-attempt the upgrade. |
-
- 0x8007045d - |
-
- This - error indicates that we ran into an I/O device error. - |
-
- Please
- ensure that all I/O devices are working correctly. Please review the Device
- Manager for any errors and troubleshoot accordingly. |
-
- 0x80070490 - - 0x20007 - |
-
- The - error comes up during driver installation phase and it means that some - of the device driver is incompatible. - |
-
- Please
- ensure that all the devices are working correctly. Please review the Device
- Manager for any errors and troubleshoot accordingly. |
-
- 0x80070542 - |
-
- The - user executing the Setup.exe does not have all permissions required to - complete the upgrade. - |
-
- Please
- ensure the user performing the upgrade is part of Local Administrators group
- or is a Local Admin. |
-
- 0x80070652 - - |
-
- This - error occurs when another program is being installed at the same time as the - upgrade. - |
-
- Ensure - that the are no other installation currently in progress. If there is, wait - for the installation to complete. Restart the computer and do the upgrade to - Windows 10. - |
-
- 0x800F0923 - |
-
- This - error code indicates that the user entered Safe Mode during the upgrade - process. - |
-
- In - order to complete the upgrade successfully, we recommend that you reboot the - system in normal mode. If a roll-back occurs, re-initiate the upgrade. - |
-
- 0x80200056 - |
-
- This - error indicates when the upgrade attempts to use a security token for some of - the operations, but the token is not currently available. - |
-
- You - can attempt to re-login to the machine with a local administrator privileges - and attempt to re-run the upgrade. Ensure that you do not logoff until the - upgrade is complete. - |
-
- 0xC0000005 - |
-
- The - error indicates that the setup process lead to an access violation - |
-
- Please
- ensure the user performing the upgrade is part of Local Administrators group
- or is a Local Admin. |
-
- 0XC0000428 - |
-
- This
- error occurs when the digital signatures for one of the Boot Critical Drivers
- has not been verified. |
-
- In
- order to fix this error, we need to look for the file that is causing the
- issue. The file listed in the cause section may vary as well. When this
- error occurs, the machine / device will show a bluescreen and will not be in
- a useable state. At this point, we would need to perform Automatic
- Repair using Windows 10 installation media. The Drivers, conflicts with other
- programs, malware, and memory can all cause startup problems. |
-
- 0xC1900101 - - 0x2000B - |
-
- This - error occurs when the device drivers of the hardware connected to the - computer prevent the Windows 10 upgrade from building the migration file - list. - |
-
- We - recommended you disconnect the devices that aren't in use when you upgrade - the computer. - |
-
- 0xC1900101 - - 0x2000c - |
-
- The - Setup Platform has encountered an unspecified error during the WINPE Phase. - This is generally caused by drivers which are not updated at the time when - the upgrade was started. - |
-
- It - is recommended to select "Download and install updates - (recommended)" during the upgrade process. Additionally, you can contact - the Hardware Vendor and get the updates for the device drivers that - are connected to the system. Ensure all the devices other than the - Mouse; Keyboard and Display are disconnected during upgrade process. Then - start setup again. - |
-
- 0xC1900101 - - 0x40001 - |
-
- This
- error indicates that we saw an error in the OOBE Phase - Stop 9F. |
-
- The
- most common causes for this error would be the connected devices on the
- machine / device as below and it would have suggested that we disable /
- disconnect them from the device /machine before performing the upgrade: |
-
- 0xC1900101 - - 0x4001E - |
-
- This - error indicates that the installation failed in the SECOND_BOOT phase with an - error during PRE_OOBE operation. - |
-
- This - is a generic error that occurs during the OOBE phase of Setup. We recommend - you to review the FAQ for Upgrade to Windows 10 - (https://support.microsoft.com/en-us/help/12435/windows-10-upgrade-faq) - |
-
- 0xc1900106 - |
-
- This - indicate that upgrade process was forcefully terminated either by Rebooting - or forcefully canceling the setup. - |
-
- We
- recommended that when the Windows 10 Upgrade is initiated, one should not
- terminate the process at any time until the Setup completes. Before initiating
- the setup, we should make sure: |
-
- 0xC1900200 - - 0x20008 - |
-
- This - error occurs when the computer doesn’t meet the minimum requirements to - download or upgrade to Windows 10. - |
-
- Refer
- http://www.microsoft.com/en-us/windows/windows-10-specifications?OCID=win10_null_vanity_win10specs
- and make sure that the machine, on which the upgrade is being initiated,
- meets the minimum requirement. |
-
- 0xC1900208 - -1047526904 - |
-
- This - error occurs when the computer does not pass the compatibility check for - upgrading to Windows 10. - |
-
- This
- error comes when there is software/driver which is not yet certified to be compatible
- with windows 10. Hence you might want to re-run the compatibility check
- before initiating the Upgrade. |
-
- 0xC190020e |
-
- These - errors would occur if your computer doesn’t have enough free space available - to install the upgrade. - |
-
- Typically
- to upgrade to Windows 10, you need free space of 16 GB for 32-bit OS and 20
- GB for 64-bit OS. If there is not enough space refer the following article: |
-
- Couldn't - Update System Reserved Partition - |
-
- This - error occurs because the System Reserved Partition (SRP) is full. - |
-
- Free - up 15MB of space on the SRP using the appropriate method described in - Knowledge Base article 3086249, and then try the upgrade again. - |
-
- MismatchedLanguage, - found HardBlock - |
-
- This - error code indicates that the Current Language installed on the machine is - not Supported for the Upgrade to start. - |
-
- We - need to have English as the base Language in order to upgrade to Windows 10. - There is a Hard block for the Upgrade to be performed and the compatibility - scan data is saved to - %Systemroot%\$WINDOWS.~BT\Sources\Panther\CompatData_YYYY.txt - |
-
- Setup - couldn’t start properly. Please reboot your PC and try running Windows 10 - Setup again - |
-
- This - error occurs if the upgrade files are corrupt due to a failed Windows 10 - download. - |
-
- The
- Setup.exe initializes the temporary folders to copy the data and prepare the
- machine for upgrade. The specific folders that are initialized are: |
-
- Unable - to resurrect NewSystem object. hr=0x80070002 - |
-
- This
- error occurs when the setup.exe is unable to create the newsystem data file
- when the upgrade starts. |
-
- The
- NewSystem.dat is an operational file that is created at the beginning of the
- upgrade process and used at various points in the setup phase like driver
- migrations; disk space detections; Platforms detections and creating a base
- image of the new OS that is extracted from the INSTALL.WIM, which is the
- source file for the upgrade. |
-
+You can either create a USB drive or an ISO. +"
+You may alternatively, re-create installation media using ""Media Creation Tool"" Refer: https://www.microsoft.com/en-us/software-download/windows10 - +You can either create a USB drive or an ISO using the Media Creation Tool. +"