mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
fixes
This commit is contained in:
@ -20,7 +20,7 @@ This topic provides a summary of available upgrade paths to Windows 10. You can
|
||||
|
||||
>**Windows N/KN**: Windows "N" and "KN" editions follow the same upgrade paths shown below. If the pre-upgrade and post-upgrade editions are not the same type (e.g. Windows 8.1 Pro N to Windows 10 Pro), personal data will be kept but applications and settings will be removed during the upgrade process.
|
||||
|
||||
>**Free upgrade**: Some upgrade paths qualify for a free upgrade using Windows Update. For a list of upgrade paths that are available as part of the free upgrade offer, see [Free upgrade paths](#bkmk-free-table).
|
||||
>**Free upgrade**: Some upgrade paths qualify for a free upgrade using Windows Update. For a list of upgrade paths that are available as part of the free upgrade offer, see [Free upgrade paths](#Free-upgrade-paths).
|
||||
|
||||
✔ = Full upgrade is supported including personal data, settings, and applications.<BR>
|
||||
D = Edition downgrade; personal data is maintained, applications and settings are removed.
|
||||
@ -330,7 +330,7 @@ D = Edition downgrade; personal data is maintained, applications and settings ar
|
||||
<td>✔</td>
|
||||
</tr>
|
||||
</table>
|
||||
## <a href="" id="bkmk-free-table"></a>
|
||||
|
||||
## Free upgrade paths
|
||||
|
||||
Windows 10 is offered as a free upgrade for the first year after launch of Windows 10, with the following restrictions:
|
||||
@ -406,7 +406,8 @@ The following table summarizes the free upgrade paths to Windows 10.
|
||||
|
||||
## Related Topics
|
||||
|
||||
[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)
|
||||
[Windows 10 deployment scenarios](windows-10-deployment-scenarios.md)<BR>
|
||||
[Windows upgrade and migration considerations](windows-upgrade-and-migration-considerations.md)
|
||||
|
||||
|
||||
|
||||
|
@ -8,13 +8,13 @@ ms.sitesec: library
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
# Windows Upgrade and Migration Considerations
|
||||
# Windows upgrade and migration considerations
|
||||
Files and application settings can be migrated to new hardware running the Windows® operating system, or they can be maintained during an operating system upgrade on the same computer. This topic summarizes the Microsoft® tools you can use to move files and settings between installations in addition to special considerations for performing an upgrade or migration.
|
||||
|
||||
## Upgrade from a Previous Version of Windows
|
||||
## Upgrade from a previous version of Windows
|
||||
You can upgrade from an earlier version of Windows, which means you can install the new version of Windows and retain your applications, files, and settings as they were in your previous version of Windows. If you decide to perform a custom installation of Windows instead of an upgrade, your applications and settings will not be maintained. Your personal files, and all Windows files and directories, will be moved to a Windows.old folder. You can access your data in the Windows.old folder after Windows Setup is complete.
|
||||
|
||||
## Migrate Files and Settings
|
||||
## Migrate files and settings
|
||||
Migration tools are available to transfer settings from one computer that is running Windows to another. These tools transfer only the program settings, not the programs themselves.
|
||||
|
||||
For more information about application compatibility, see the [Application Compatibility Toolkit (ACT)](http://go.microsoft.com/fwlink/p/?LinkId=131349).
|
||||
@ -29,13 +29,13 @@ With Windows Easy Transfer, files and settings can be transferred using a netwo
|
||||
### Migrate with the User State Migration Tool
|
||||
You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. You can use USMT for both *side-by-side* migrations, where one piece of hardware is being replaced, or *wipe-and-load* (or *refresh*) migrations, when only the operating system is being upgraded.
|
||||
|
||||
## Upgrade and Migration Considerations
|
||||
## Upgrade and migration monsiderations
|
||||
Whether you are upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations:
|
||||
|
||||
### Application Compatibility
|
||||
### Application compatibility
|
||||
For more information about application compatibility in Windows, see the [Application Compatibility Toolkit (ACT)](http://go.microsoft.com/fwlink/p/?LinkId=131349).
|
||||
|
||||
### Multilingual Windows Image Upgrades
|
||||
### Multilingual Windows image upgrades
|
||||
When performing multilingual Windows upgrades, cross-language upgrades are not supported by USMT. If you are upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English.
|
||||
|
||||
If you are using a single-language Windows image that matches the system default UI language of your multilingual operating system, the migration will work. However, all of the language packs will be removed, and you will have to reinstall them after the upgrade is completed.
|
||||
@ -43,7 +43,7 @@ If you are using a single-language Windows image that matches the system default
|
||||
### Errorhandler.cmd
|
||||
When upgrading from an earlier version of Windows, if you intend to use Errorhandler.cmd, you must copy this file into the %WINDIR%\\Setup\\Scripts directory on the old installation. This makes sure that if there are errors during the down-level phase of Windows Setup, the commands in Errorhandler.cmd will run.
|
||||
|
||||
### Data Drive ACL Migration
|
||||
### Data drive ACL migration
|
||||
During the configuration pass of Windows Setup, the root access control list (ACL) on drives formatted for NTFS that do not appear to have an operating system will be changed to the default Windows XP ACL format. The ACLs on these drives are changed to enable authenticated users to modify access on folders and files.
|
||||
|
||||
Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Because of these performance concerns, you can change the following registry value to disable this feature:
|
||||
|
Reference in New Issue
Block a user