-->![C C](https://www.numerama.com/content/uploads/2017/04/windows-10-creators-update-mode-nuit.jpg)
![C C](https://1.bp.blogspot.com/-k7nlOWHkGYk/WNz6JdhTd6I/AAAAAAAAA0A/VOsM2NcGkXcySqpUmB5kideNpX-kK04HACLcB/s1600/qu%2527est%2Bce%2Bque%2Bmicrosoft%2Bedge-3.jpeg)
Applies to
Epson Software Updater allows you to update Epson software as well as download 3rd party applications. Note: Your Epson product must be turned on and connected to a computer with Internet access. See our Updating your Printer's Firmware Using Epson Software Updater page for update instructions.
- Windows 10, version 1909
This article lists new and updated features and content that are of interest to IT Pros for Windows 10, version 1909, also known as the Windows 10 November 2019 Update. This update also contains all features and fixes included in previous cumulative updates to Windows 10, version 1903.
- Windows10UpgraderApp.exe file information Windows10UpgraderApp.exe process in Windows Task Manager. The process known as Windows (version 10 Update Assistant, 10 Upgrade Assistant) belongs to software Windows (version 10 Update Assistant, 10 Upgrade Assistant) by Microsoft (www.microsoft.com). Description: Windows10UpgraderApp.exe is not essential for the Windows OS.
- Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.
- Get tools and insights IT can trust to simplify deployment and updates, and free up resources to drive more business value. Start by evaluating your options. Windows 10 provides new deployment capabilities, scenarios, and tools by building on technologies introduced in previous versions.
- Creative - MEDIA - 6.0.240.26 even listed as an insatll through windows update. My card sb X-FI Titanium Fatality Pro. Last time win10 did this it caused issues with the driver and accompanied.
Servicing
Windows 10, version 1909 is a scoped set of features for select performance improvements, enterprise features and quality enhancements.
To deliver these updates in an optimal fashion, we are providing this feature update in a new way: using servicing technology. Users that are already running Windows 10, version 1903 (the May 2019 Update) will receive this update similar to how they receive monthly updates. If you are running version 1903, then updating to the new release will have a much faster update experience because the update will install like a monthly update.
If you are updating from an older version of Windows 10 (version 1809 or earlier), the process of updating to the current version will be the same as it has been for previous Windows 10 feature updates. For more information, see Evolving Windows 10 servicing and quality: the next steps.
Note: Devices running the Enterprise, IoT Enterprise, or Education editions of Windows 10, version 1909 receive 30 months of support. For more information about the Windows servicing lifecycle, please see the Windows lifecycle fact sheet.
Windows Server Update Services (WSUS)
Pre-release Windows 10 feature updates are now available to IT administrators using WSUS. Microsoft Endpoint Manager version 1906 or later is required. For more information, see Publishing pre-release Windows 10 feature updates to WSUS.
The Windows 10, version 1909 enablement package will be available on WSUS as KB4517245, which can be deployed on existing deployments of Windows 10, version 1903.
![C C](https://www.numerama.com/content/uploads/2017/04/windows-10-creators-update-mode-nuit.jpg)
Windows Update for Business (WUfB)
If you are using WUfB, you will receive the Windows 10, version 1909 update in the same way that you have for prior feature updates, and as defined by your feature update deferral policy.
Security
Windows Defender Credential Guard
Windows Defender Credential Guard is now available for ARM64 devices, for additional protection against credential theft for enterprises deploying ARM64 devices in their organizations, such as Surface Pro X.
Microsoft BitLocker
BitLocker and Mobile Device Management (MDM) with Azure Active Directory work together to protect your devices from accidental password disclosure. Now, a new key-rolling feature securely rotates recovery passwords on MDM managed devices. The feature is activated whenever Microsoft Intune/MDM tools or a recovery password is used to unlock a BitLocker protected drive. As a result, the recovery password will be better protected when users manually unlock a BitLocker drive.
Key-rolling and Key-rotation
Windows 10, version 1909 also includes two new features called Key-rolling and Key-rotation enables secure rolling of Recovery passwords on MDM managed AAD devices on demand from Microsoft Intune/MDM tools or when a recovery password is used to unlock the BitLocker protected drive. This feature will help prevent accidental recovery password disclosure as part of manual BitLocker drive unlock by users.
Transport Layer Security (TLS)
An experimental implementation of TLS 1.3 is included in Windows 10, version 1909. TLS 1.3 disabled by default system wide. If you enable TLS 1.3 on a device for testing, then it can also be enabled in Internet Explorer 11.0 and Microsoft Edge by using Internet Options. For beta versions of Microsoft Edge on Chromium, TLS 1.3 is not built on the Windows TLS stack, and is instead configured independently, using the Edge://flags dialog. Also see Microsoft Edge platform status.
Virtualization
Windows Sandbox
Windows Sandbox is an isolated desktop environment where you can install software without the fear of lasting impact to your device. This feature is available in Windows 10, version 1903. In Windows 10, version 1909 you have even more control over the level of isolation.
Windows Virtual Desktop
Windows Virtual Desktop (WVD) is now generally available globally! 10 4 wikipedia.
Windows Virtual Desktop is a comprehensive desktop and app virtualization service running in the cloud. It’s the only virtual desktop infrastructure (VDI) that delivers simplified management, multi-session Windows 10, optimizations for Microsoft 365 Apps for enterprise, and support for Remote Desktop Services (RDS) environments. Deploy and scale your Windows desktops and apps on Azure in minutes, and get built-in security and compliance features. Windows Virtual Desktop requires a Microsoft E3 or E5 license, or a Microsoft 365 E3 or E5 license, as well as an Azure tenant.
Deployment
Microsoft Endpoint Manager
Configuration Manager, Intune, Desktop Analytics, Co-Management, and Device Management Admin Console are now Microsoft Endpoint Manager. See the Nov. 4 2019 announcement. Also see Modern management and security principles driving our Microsoft Endpoint Manager vision.
Windows 10 Pro and Enterprise in S mode
You can now deploy and run traditional Win32 (desktop) apps without leaving the security of S mode by configuring the Windows 10 in S mode policy to support Win32 apps, and deploy them with Mobile Device Management (MDM) software such as Microsoft Intune. For more information, see Allow Line-of-Business Win32 Apps on Intune-Managed S Mode Devices.
SetupDiag
SetupDiag version 1.6.0.42 is available.
SetupDiag is a command-line tool that can help diagnose why a Windows 10 update failed. SetupDiag works by searching Windows Setup log files. When searching log files, SetupDiag uses a set of rules to match known issues. In the current version of SetupDiag there are 53 rules contained in the rules.xml file, which is extracted when SetupDiag is run. The rules.xml file will be updated as new versions of SetupDiag are made available. .
Windows Assessment and Deployment Toolkit (ADK)
A new Windows ADK will not be released for Windows 10, version 1909. You can use the Windows ADK for Windows 10, version 1903 to deploy Windows 10, version 1909.
Desktop Analytics
Desktop Analytics is now generally available globally! Desktop Analytics is a cloud-connected service, integrated with Configuration Manager, which gives you in performance. These cores are called 'favored cores' as they can offer better performance than the other cores on the die.
With Intel Turbo Boost Max Technology 3.0, an operating system will use information stored in the CPU to identify which cores are the fastest and then push more of the CPU intensive tasks to those cores. According to Intel, this technology 'delivers more than 15% better single-threaded performance'.
![C C](https://1.bp.blogspot.com/-k7nlOWHkGYk/WNz6JdhTd6I/AAAAAAAAA0A/VOsM2NcGkXcySqpUmB5kideNpX-kK04HACLcB/s1600/qu%2527est%2Bce%2Bque%2Bmicrosoft%2Bedge-3.jpeg)
Debugging
Additional debugging capabilities for newer Intel processors have been added in this release. This is only relevant for hardware manufacturers.
Efficiency
General battery life and power efficiency improvements for PCs with certain processors have been added in this release.
See Also
What's New in Windows Server: New and updated features in Windows Server.
Windows 10 Features: General information about Windows 10 features.
What's New in Windows 10: See what’s new in other versions of Windows 10.
What Windows 10, version 1909 Means for Developers: New and updated features in Windows 10 that are of interest to developers.
Features and functionality removed in Windows 10: Removed features.
Windows 10 features we’re no longer developing: Features that are not being developed.
How to get the Windows 10 November 2019 Update: John Cable blog.
How to get Windows 10, Version 1909: Enablement Mechanics: Mechanics blog.
What’s new for IT pros in Windows 10, version 1909: Windows IT Pro blog.
-->Windows 10 Features: General information about Windows 10 features.
What's New in Windows 10: See what’s new in other versions of Windows 10.
What Windows 10, version 1909 Means for Developers: New and updated features in Windows 10 that are of interest to developers.
Features and functionality removed in Windows 10: Removed features.
Windows 10 features we’re no longer developing: Features that are not being developed.
How to get the Windows 10 November 2019 Update: John Cable blog.
How to get Windows 10, Version 1909: Enablement Mechanics: Mechanics blog.
What’s new for IT pros in Windows 10, version 1909: Windows IT Pro blog.
Windows Recovery Environment (WinRE) is a recovery environment that can repair common causes of unbootable operating systems. WinRE is based on Windows Preinstallation Environment (Windows PE), and can be customized with additional drivers, languages, Windows PE Optional Components, and other troubleshooting and diagnostic tools. By default, WinRE is preloaded into the Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) and Windows Server 2016 installations.
What's new with WinRE for Windows 10?
- By default, if you install Windows using media created from Windows Imaging and Configuration Designer (ICD), you'll get a dedicated WinRE tools partition on both UEFI and BIOS-based devices, located immediately after the Windows partition. This allows Windows to replace and resize the partition as needed. (If you install Windows by using Windows Setup, you'll get the same partition layout that you did in Windows 8.1.)
- If you add a custom tool to the WinRE boot options menu, it can only use optional components that are already in the default WinRE tools. For example, if you have a app from Windows 8 that depended on the .NET optional components, you'll need to rewrite the app for Windows 10.
- If you add a custom tool to the WinRE boot options menu, it must be placed in the SourcesRecoveryTools folder so that it can continue to work after future WinRE upgrades.
- When adding languages to the push-button reset tools, you'll now need to add the WinPE-HTA optional component.
Tools
WinRE includes these tools:
- Automatic repair and other troubleshooting tools. For more info, see Windows RE Troubleshooting Features.
- Push-button reset (Windows 10 for desktop editions , Windows 8.1 and Windows 8 only). This tool enables your users to repair their own PCs quickly while preserving their data and important customizations, without having to back up data in advance. For more info, see Push-Button Reset Overview.
- System image recovery (Windows Server 2016, Windows Server 2012 R2 and Windows Server 2012 only). This tool restores the entire hard drive. For more info, see Recover the Operating System or Full Server.
In addition, you can create your own custom recovery solution by using the Windows Imaging API, or by using the Deployment Image Servicing and Management (DISM) API.
Entry points into WinRE
Your users can access WinRE features through the Boot Options menu, which can be launched from Windows in a few different ways:
- From the login screen, click Shutdown, then hold down the Shift key while selecting Restart.
- In Windows 10, select Start > Settings > Update & security > Recovery > under Advanced Startup, click Restart now.
- Boot to recovery media.
- Use a hardware recovery button (or button combination) configured by the OEM.
After any of these actions is performed, all user sessions are signed off and the Boot Options menu is displayed. If your users select a WinRE feature from this menu, the PC restarts into WinRE and the selected feature is launched.
WinRE starts automatically after detecting the following issues:
- Two consecutive failed attempts to start Windows.
- Two consecutive unexpected shutdowns that occur within two minutes of boot completion.
- Two consecutive system reboots within two minutes of boot completion.
- A Secure Boot error (except for issues related to Bootmgr.efi).
- A BitLocker error on touch-only devices.
Boot options menu
This menu enables your users to perform these actions:
- Start recovery, troubleshooting, and diagnostic tools.
- Boot from a device (UEFI only).
- Access the Firmware menu (UEFI only).
- Choose which operating system to boot, if multiple operating systems are installed on the PC.
Note
You can add one custom tool to the Boot options menu. Otherwise, these menus can't be further customized. For more info, see Add a Custom Tool to the Windows RE Boot Options Menu.
Security considerations
When working with WinRE, be aware of these security considerations:
- If users open the Boot options menu from Windows and select a WinRE tool, they must provide the user name and password of a local user account with administrator rights.
- By default, networking is disabled in WinRE. You can turn on networking when you need it. For better security, disable networking when you don't need connectivity.
Customizing WinRE
You can customize WinRE by adding packages (Windows PE Optional Components), languages, drivers, and custom diagnostic or troubleshooting tools. The base WinRE image includes these Windows PE Optional Components:
- Microsoft-Windows-Foundation-Package
- WinPE-EnhancedStorage
- WinPE-Rejuv
- WinPE-Scripting
- WinPE-SecureStartup
- WinPE-Setup
- WinPE-SRT
- WinPE-WDS-Tools
- WinPE-WMI
- WinPE-StorageWMI-Package (added to the base image in Windows 8.1 and Windows Server 2012 R2)
- WinPE-HTA (added to the base image in Windows 10)
Note The number of packages, languages, and drivers is limited by the amount of memory available on the PC. For performance reasons, minimize the number of languages, drivers, and tools that you add to the image.
Hard drive partitions
When you install Windows by using Windows Setup, WinRE is configured like this:
- During Windows Setup, Windows prepares the hard drive partitions to support WinRE.
- Windows initially places the WinRE image file (winre.wim) in the Windows partition, in the WindowsSystem32Recovery folder.Before delivering the PC to your customer, you can modify or replace the WinRE image file to include additional languages, drivers, or packages.
- During the specialize configuration pass, the WinRE image file is copied into the recovery tools partition, so that the device can boot to the recovery tools even if there's a problem with the Windows partition.
When you deploy Windows by applying images, you must manually configure the hard drive partitions. When WinRE is installed on a hard drive, the partition must be formatted as NTFS.
Add the baseline WinRE tools image (winre.wim) to a separate partition from the Windows and data partitions. This enables your users to use WinRE even if the Windows partition is encrypted with Windows BitLocker Drive Encryption. It also prevents your users from accidentally modifying or removing the WinRE tools.
Store the recovery tools in a dedicated partition, directly after the Windows partition. This way, if future updates require a larger recovery partition, Windows will be able to handle it more efficiently by adjusting the Windows and recovery partition sizes, rather than having to create a new recovery partition size while the old one remains in place.
To learn more, see Configure UEFI/GPT-Based Hard Drive Partitions or Configure BIOS/MBR-Based Hard Drive Partitions.
Memory requirements
In order to boot Windows RE directly from memory (also known as RAM disk boot), a contiguous portion of physical memory (RAM) which can hold the entire Windows RE image (winre.wim) must be available. To optimize memory use, manufacturers should ensure that their firmware reserves memory locations either at the beginning or at the end of the physical memory address space.
Updating the on-disk Windows Recovery Environment
In Windows 10, the on-disk copy of Windows RE can be serviced as part of rollup updates for the OS. Not all rollup updates will service Windows RE.
Unlike the normal OS update process, updates for Windows RE do not directly serviced the on-disk Windows RE image (winre.wim). Instead, a newer version of the Windows RE image replaces the existing one, with the following contents being injected or migrated into the new image:
- Boot critical and input device drivers from the full OS environment are added to the new Windows RE image.
- Windows RE customizations under SourcesRecovery of the mounted winre.wim are migrated to the new image.
The following contents from the existing Windows RE image are not migrated to the new image: Standard flash drive format.
- Drivers which are in the existing Windows RE image but not in the full OS environment
- Windows PE optional components which are not part of the default Windows RE image
- Language packs for Windows PE and optional components
The Windows RE update process makes every effort to reuse the existing Windows RE partition without any modification. However, in some rare situations where the new Windows RE image (along with the migrated/injected contents) does not fit in the existing Windows RE partition, the update process will behave as follows:
- If the existing Windows RE partition is located immediately after the Windows partition, the Windows partition will be shrunk and space will be added to the Windows RE partition. The new Windows RE image will be installed onto the expanded Windows RE partition.
- If the existing Windows RE partition is not located immediately after the Windows partition, the Windows partition will be shrunk and a new Windows RE partition will be created. The new Windows RE image will be installed onto this new Windows RE partition. The existing Windows RE partition will be orphaned.
- If the existing Windows RE partition cannot be reused and the Windows partition cannot successfully be shrunk, the new Windows RE image will be installed onto the Windows partition. The existing Windows RE partition will be orphaned.
Important To ensure that your customizations continue to work after Windows RE has been updated, they must not depend on functionalities provided by Windows PE optional components which are not in the default Windows RE image (e.g. WinPE-NetFX). To facilitate development of Windows RE customizations, the WinPE-HTA optional component has been added to the default Windows RE image in Windows 10.
C'est Quoi L'amour
Note The new Windows RE image deployed as part of the rollup update contains language resources only for the system default language, even if the existing Windows RE image contains resources for multiple languages. On most PCs, the system default language is the language selected at the time of OOBE.
Known Issue
If the GPO 'Windows Settings/Security Settings/Local Policies/Security Options/Accounts: Block Microsoft accounts' is set to enable the policy 'User can’t add or log with Microsoft account', attempting to restore the System in WinRE will fail with the error message 'You need to sign in as an administrator to continue, but there aren't any administrator accounts on this PC.'
This is a known issue and the workaround is to either avoid setting the 'Accounts: Block Microsoft accounts' to 'User can't add or log with Microsoft Account' or set the MDM policy Security/RecoveryEnvironmentAuthentication to 2.
See also
C Est Quoi Windows Update
Content type | References |
---|---|
Deployment | Customize Windows RE | Deploy Windows RE |
Operations | |
Troubleshooting | |
Add-on tools | Add a Custom Tool to the Windows RE Boot Options Menu | Add a Hardware Recovery Button to Start Windows RE | Push-Button Reset Overview |