From d48a3e6666c76e6c4a2d194a32e3c31d989e2b7a Mon Sep 17 00:00:00 2001 From: Kaushik Ainapure Date: Wed, 3 May 2017 00:30:13 +0530 Subject: [PATCH] Unintended usmt migration The usmt from the adk for windows 10 is meant to migrate settings from these lower operating systems to windows 10 and not among each other. --- windows/deployment/usmt/usmt-requirements.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/deployment/usmt/usmt-requirements.md b/windows/deployment/usmt/usmt-requirements.md index 14f8a1dd19..e96eb8e095 100644 --- a/windows/deployment/usmt/usmt-requirements.md +++ b/windows/deployment/usmt/usmt-requirements.md @@ -30,6 +30,7 @@ The User State Migration Tool (USMT) 10.0 does not have any explicit RAM or CPU The following table lists the operating systems supported in USMT. + @@ -83,7 +84,8 @@ You can migrate a 32-bit operating system to a 64-bit operating system. However, USMT does not support any of the Windows Server® operating systems, Windows 2000, Windows XP, or any of the starter editions for Windows Vista or Windows 7. -  +USMT for Windows 10 should not be used for migrating from Windows 7 to Windows 8.1. It is meant to migrate to Windows 10. +For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](https://go.microsoft.com/fwlink/p/?LinkId=246564).  ## Windows PE