Hotfix version ll.0.950 download

To continue receiving security and quality updates, Microsoft recommends that you update to the latest version of Windows For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 10, version , see its update history page. Note Follow WindowsUpdate to find out when new content is published to the release information dashboard.

Updates an issue an issue that might prevent subtitles from displaying for certain video apps and streaming video sites. Updates an issue that prevents Kana input mode users from inserting a question mark? Updates an issue that sometimes causes your lock screen background to appear black if you have set up a slideshow of pictures as your lock screen background.

Note: To view the list of addressed issues, click or tap the OS name to expand the collapsible section. Addresses an issue that prevents you from accessing the pre-provisioning page during the out-of-box experience OOBE. This issue occurs when the credentials page for signing in to Azure Active Directory appears, and you press the Windows key five times. Addresses an issue with Assigned Access kiosks that are configured with Microsoft Edge as a kiosk application.

These kiosks might sometimes fail to restart Microsoft Edge if users close the browser window. Addresses an issue in which the use of App-V intermittently causes black screens to appear when signing in on the credentials page. Addresses an issue that might prevent subtitles from displaying for certain video apps and streaming video sites.

Users receive unexpected authentication prompts for online resources that are configured for user sign-in frequency SIF in Azure Active Directory-Conditional Access. Addresses an issue that might cause Kerberos. Addresses an issue that prevents Kana input mode users from inserting a question mark? Addresses an issue that sometimes causes the lock screen to appear black if you set up slideshow.

Addresses a reliability issue with LogonUI. Addresses a memory leak issue in lsass. The SID-Name mapping functions leak memory when a request comes from another domain in the forest and crosses forest boundaries.

Addresses a known issue that might prevent the successful installation of printers using the Internet Printing Protocol IPP. If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates SSU ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge.

This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update SSU released March 29, or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Use the following steps to extract the using SSU:.

Extract the cab from the msu via this command line using the package for KB as an example : expand Windows Extract the SSU from the previously extracted cab via this command line: expand Windows Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge.

If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business. After installing the June 21, KB update, some devices cannot install new updates, such as the July 6, KB or later updates. For more information and a workaround, see KB After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication.

You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials. Please note that it might take up to 24 hours for the resolution to propagate automatically to non-managed personal devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster.

For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy.

Windows Server Windows 10, version , Windows 10, version 20H2 and Windows 10, version 21H1. Important Verify that you are using the correct Group Policy for your version of Windows. After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:. Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use.

Printing environments affected by this issue are more commonly found in enterprises and organizations. This issue is resolved in KB Until the update is applied to the site database, the site is in an unsupported state. Run the update script named update. For information about how to run a script to update a SQL Server database, see the documentation for the version of SQL Server that you use for your site database server.

When the update bundle installs, it extracts update. The only exception is the instance of the SMS Provider that was previously installed on the site server where you install the update bundle. The local instance of the SMS Provider on the site server is updated when you install the update bundle. When you install an update that includes updates for the Configuration Manager client, you can automatically upgrade clients with the update installation, or manually upgrade clients at a later time.

For more information about automatic client upgrade, see How to upgrade clients for Windows computers. You can deploy updates with Updates Publisher or a software deployment package.

You can also manually install the update on each client. For more information about how to use deployments to install updates, see Deploy updates for Configuration Manager. When you install updates for clients and the update bundle includes updates for servers, install the server updates on the primary site to which the clients are assigned. To manually install the client update, run Msiexec.

Include the platform-specific client update MSP file in the command line. For example, you can use the following command line for a client update:. To update a Configuration Manager console, install the update on the computer that runs the console. When you install updates for the Configuration Manager console, and the update bundle includes updates for servers, also install the server updates on the site that you use with the Configuration Manager console.

You can use a deployment to install the update. To manually install the Configuration Manager console update, run Msiexec. For example, you can use the following command line to update a Configuration Manager console:.

After you install the update bundle on a site server, you can use one of the following three methods to deploy updates to other computers. When you install the update bundle on a site server, the installation Wizard creates a catalog file for Updates Publisher.

You can use this file to deploy the updates to applicable computers. The wizard always creates this catalog, even when you select the option Use package and program to deploy this update. It can't be used on other site servers. After the wizard is finished, import the catalog to Updates Publisher. Then use software updates to deploy the updates. For more information, see System Center Updates Publisher. Close the wizard after it's finished.

When you install the update bundle on the site server of a primary site or CAS, you can configure the installation Wizard to create update packages for software deployment. Then deploy each package to a collection of computers that you want to update. To create a software deployment package, on the Configure Software Update Deployment page of the wizard, select each update package type that you want to update. The available types can include servers, Configuration Manager consoles, and clients.

A separate package is created for each type of update that you select. Next, on the Configure Software Update Deployment Method page of the wizard, select the option I will use software distribution.

After the wizard is finished, view the packages in the Configuration Manager console. Go to the Packages node in the Software Library workspace. Use your standard process to deploy software packages to Configuration Manager clients. When a package runs on a client, it installs the updates to the applicable components of Configuration Manager on the client computer. For more information about how to deploy packages to Configuration Manager clients, see Packages and programs.

You can deploy specific updates to applicable clients. The following information can help you to create device collections for the different components for Configuration Manager.

For more information, see How to create collections. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note Updates for site system roles are installed as part of the update for site servers. Note You can deploy updates only to computers that run the Configuration Manager client. Note When you choose to automatically update the site database, the process updates a database regardless whether the database is located on the site server or on a remote computer.

Important Before you update the site database, create a backup of the site database. Warning When the update includes updates to both the site server and the site database, the update isn't functional until the update is completed for both the site server and site database.

Tip When the update bundle installs, it extracts update. Important When you install updates for clients and the update bundle includes updates for servers, install the server updates on the primary site to which the clients are assigned.

Important When you install updates for the Configuration Manager console, and the update bundle includes updates for servers, also install the server updates on the site that you use with the Configuration Manager console.

Note To update a site database, deploy the update to the site server for that site. Submit and view feedback for This product This page. View all page feedback. In this article. This file is the update. The command line for this file is managed by Updatesetup. This MSI wrapper manages the installation of the update bundle. When you run the update, Updatesetup. By default, the user interface for the update is in English.