![]() The more languages you have to support, the most install media you will need. For example, if German is the default, you can upgrade from Windows 1511 German to Windows 1607 German. In feature upgrade scenarios, if you are upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default UI language.Adding additional language packs isn’t enough. The requirement for the Windows Setup is that the system UI language of the INSTALL.WIM being used for upgrade must match the system UI language of the running OS. It appears that when you apply a language pack as well as regional settings before operating system is fully online, your target language becomes your default language. ![]() 15:24:23, Info CONX CMismatchedLanguageChecker: checked MismatchedLanguage, found HardBlock. Running the setup.exe manually showed that the upgrade option is greyed out.ĭigging into the setupact.log I found following two lines: 15:24:23, Info CONX ConX::Compatibility::CSystemAbstraction::TargetLanguageIsCompatibleForUpgrade: Target language en-US is not compatible with the host language (lang.ini path: C:\$WINDOWS.~BT\Sources\lang.ini). One of the customers is using ZenWorks for OSD while the other one relies heavily on Microsoft Deployment Toolkit.ĭuring initial on site testing I ran into the following error message: C1900204, "MigChoice: Selected install choice is not available.".Base image is English (en-US) and then at least one language pack is applied during the deployment.Each customer has over 10.000 seats all around the world.First of all, Windows as a Service, as demo-ed at Ignite, works fantastic – as long as you don't have any language packs installed. ![]() Let's go back a couple of months: In late 2016 I advised two of my customers, who just started transitioning to Windows 10, to get an early start with Windows as a Service.
0 Comments
Leave a Reply. |