2019 reporting services

Microsoft Power BI Blog

• Announcements
• Report Server

What’s new for SQL Server 2019 Reporting Services RC1

We are pleased to announce the first release candidate of SQL Server 2019 Reporting Services is now available in the download center.  While the team has previously released several updates for SQL Server customers via Power BI Report Server , this is the first feature update to the core SQL Server Reporting Services product for the 2019 release wave.

Download SQL Server 2019 Reporting Services

With this release, we’ve added new features to help customers meet their changing business needs around cloud-readiness and accessibility.  These include –

• Support for hosting your database catalog with Azure SQL Managed Instance
• Support for Power BI datasets hosted in Power BI Premium
• Using Azure AD Application Proxy with Reporting Services
• A new version of Microsoft Report Builder updated for use with SSRS 2019
• AltText (alternative text) in support of WCAG and 508 compliance for your report elements
• PDF/UA support for PDF documents (coming soon)
• Rollup of several security updates and bug fixes previously released in Power BI Report Server

Azure SQL Managed Instance support

Managed instance is a new deployment option of Azure SQL Database, providing near 100% compatibility with the latest SQL Server release.  Now, for the first time, you may use a Managed Instance to host your database catalog used for SQL Server Reporting Services that is hosted either in a VM or in your data center.  Please note that support is limited to using database credentials for the connection to SQL MI.

Power BI Premium dataset support

In March, the Power BI team announced support for connectivity via the XMLA endpoint to Analysis Services models hosted in Premium workspaces.  For the first time, customers can connect to those models using either Microsoft Report Builder or SQL Server Data Tools and publish those reports to SSRS 2019 using the SQL Server Analysis Services connectivity option.  Users will need to use a stored Windows Username/Password to enable the scenario.

Microsoft Report Builder update

Later this week, we’ll have an update to the SQL Server 2016 Report Builder release.  This release updates all existing installs of that product.  It is fully compatible with the 2016, 2017, and 2019 versions of Reporting Services, along with all released and supported versions of Power BI Report Server.  New features include the ability to connect to a Power BI Premium dataset and enter data directly in a report .

AltText (alternative text) support for report elements

Meeting customers accessibility needs is an important part of the software development process here at Microsoft.  We’ve enhanced several accessibility items for report authors and viewers in this release, including official support for Alternative Text for report elements.  Using tooltips, authors may specify text for each element on the report and have this properly identified by screen reader technology as such.

Beyond what we’ve called out here, some additional features will be available prior to our GA release, including  PDF/UA support for PDF documents.  We will announce those as soon as they are available.

As many of you know, we recently released paginated reports in Power BI , and are continuing to add more features there.  We continue to see Reporting Services as a key part of the SQL Server value proposition, and much like the Analysis Services team has done in this 2019 release, we’ll look to bring new RDL capabilities introduced in the cloud to the on-premises product in future releases.

Thanks for reading, and don’t forget to leave us your feedback in the comments below.

• Report Builder
• Reporting Services

08 April 2019

33,260 views

• Reporting Services Basics: Overview and Installation

SQL Server Reporting Services has changed quite a bit since it was introduced in 2004. Despite new analytic services like Power BI, SSRS is still a popular tool for paginated reports. In this article, Kathi Kellenberger explains the architecture of SSRS and walks you through installing an SSRS development environment on your workstation or laptop.

The series so far:

• Reporting Services Basics: Creating Your First Report
• Reporting Services Basics: Data Sources and Datasets
• Reporting Services Basics: Parameters
• Reporting Services Basics: Adding Groups to Reports

SQL Server Reporting Services (SSRS) is a server-based reporting platform that allows you to create and manage a wide variety of different types of reports and deliver them in a range of formats. You can create basic reports containing tables and graphs, or more complex data visualizations, using charts, maps and sparklines. You can even create dashboards that will run on your phone! Reports can draw their data from SQL Server databases, but also from other relational database such as Oracle or Azure SQL Database, and other types of data sources such as Analysis Services.

You can present your finished reports from the Reporting Services website typically running on premises, called the Web Portal, or users can view them within web- or Windows-based applications. Reports can also be viewed in SharePoint with a special webpart. (In earlier versions of SSRS, there was also a SharePoint integrated mode.) End users can run reports on demand or schedule them as subscriptions. This article is the first in a series that will provide in-depth coverage of the basics of report development with SSRS.

The report development examples in this series will work for SSRS 2017 and later. Many of the examples will also work for earlier versions. If you are still using SSRS 2005, please refer to Steve Joubert’s original SSRS series . If you are working with 2008 to 2012, look at the series I wrote a few years ago.

SSRS Through the Ages

SSRS has been around since 2004, first shipping as an “add-on” for SQL Server 2000, and then fully integrated into SQL Server 2005. I first saw it demonstrated at the 2003 PASS Summit and had the Beta version installed and running at work as soon as I could get my hands on the media. Back in 2003, the SQL Server community were very excited about SSRS as it made available, for the first time, built-in reporting capabilities for SQL Server. If you owned SQL Server, you owned SSRS.

Since its integration into SQL Server 2005, Microsoft has made a number of improvements over the years and gave it a complete overhaul in 2016. One big change in 2016 was the renaming of the website from Report Manager to Web Portal. In 2017, SharePoint integrated mode was discontinued, but a special version for hosting Power BI dashboards called Power BI Reporting Services became available.

SSRS Architecture

An SSRS deployment must be associated with a SQL Server instance. On the instance will be two databases, named by default:

ReportServer – contains the report definitions, configuration, history, security of deployed reports and more

ReportServerTempdb – much like tempdb, it is used as a workspace for building reports and doesn’t maintain any objects permanently.

You will also need a location for the Report Server Web Service , which can be on the same server as the databases, as in the simple deployment architecture shown in Figure 1, or on a different server. On whichever server you choose, you will have access to the Web Portal that allows you to deploy and manage the reports. The data sources will typically be found on other servers throughout the network. End users can run reports from the Web Portal, create subscriptions, and publish their own reports if they have permission.

Figure 1: A simple SSRS deployment

The end user sends an HTTP request for a report, providing any required parameters. The SSRS server finds the metadata of the report and sends a request for data to the data sources. The data returned by the data sources is merged with the report definition into a report. As the report is generated, it is returned to the client. There are two layers of security to get past before viewing the report.

SSRS Security

You have many options for securing the reports. The first layer of security is built into the Web Portal. You can control access to folders and individual reports based on network groups or user accounts. The second layer of security is to the database. You can either base the security on the individuals running the report or store an account within the data source that can be passed on to the database system. Security will be covered in more detail in a later article on deploying reports.

Tools for Building SSRS Reports

SSRS reports are XML files with the extension RDL. If you were a robot instead of a human, you might be able to just create the RDL files with a text editor. Instead, there are a number of tools from Microsoft for building reports that can be hosted in the SSRS Web Portal depending on the type of report and who is building the report.

Traditional SSRS reports, which also might be called paginated reports, can be build using an extension for Visual Studio (VS) or Report Builder. Developers will be more comfortable working in the VS environment. VS is based on a solution/project model and integrates with version control software such as Azure DevOps formerly known as Visual Studio Team Services. This is the tool you will use for this series of articles.

Report Builder is meant more for power users to create their own reports, but developers in some shops use this tool in place of VS. Instead of a project model, each report is independently created. One advantage of Report Builder is that it has an Office look and feel which makes it more comfortable for non-developers to use. It also has more wizards to help beginners get started. Users of Report Builder can take advantage of published report parts to make building a dashboard simple. Figure 2 shows what Report Builder looks like when it’s launched:

Figure 2: Report Builder

A new type of report available with SSRS 2016 is called Mobile Reports. Mobile Reports must be created with the Mobile Report Publisher which is launched from the Web Portal. These reports are dashboards which can run on phones and tablets as well as the Web Portal. (If you are a previous developer or user of Datazen reports, these will look familiar to you as Microsoft acquired the company and brought the technology into SSRS). Figure 3 shows what the Mobile Report Publisher looks like:

Figure 3: Mobile Report Publisher

Power BI dashboards can also run in a special type of SSRS Web Portal called Power BI Report Server. The tool for creating Power BI dashboards is called Power BI Desktop. Power BI is out of scope for this series, but if you would like to learn more about this topic, take a look at the article series written by Robert Sheldon.

Installing and Configuring SQL Server and Reporting Services

Since this series is focused on report development, it will cover just enough about installation and configuration to help you get things set up on your development computer. This section is not intended to provide information for installing SQL Server or SSRS in a production environment. 

To follow along with this series of articles, you will need to install the following:

• A SQL Server instance
• SQL Server Management Studio (SSMS)
• Visual Studio (SSDT with VS 2017 or an extension with VS 2019)
• Report Server 2017 

You should be running a Windows 10 computer, making sure that there is at least 50 GB free on the hard drive. You will also need to restore the AdventureWorks sample database to follow along with the examples.

At the time of this writing, SQL Server 2019 is available as a Community Technology Preview (CTP), which is a fancy way of saying Beta version. The following instructions are based on SQL Server 2017, the latest generally available version. One big change made in the installation of SSRS in 2017 is that the SSRS media must be downloaded and installed separately.

SQL Server Instance Installation

If you already have a SQL Server instance in place, version 2008 or later, you can skip this section. The instance is used to host the two databases used by SSRS and the sample databases used in the examples.

To install the SQL Server instance, you will need to first download the media. I will not provide a link here, because invariably it will change, so just search for “SQL Server 2017 downloads.” The page that was current as of this writing had links for a free trial and for a Developer Edition shown in Figure 4. Choose the Developer edition and save the downloaded file.

Figure 4: The SQL Server media download page

I’m not going to show you every step of installing SQL Server because that information can be found elsewhere. Here are the important things to note:

• The page mentioned above allows you to download the actual media. Do that first.
• Once you have downloaded the media, run setup.exe to launch the SQL Server Installation Center . You’ll need to click New SQL Server stand-alone installation on the Installation page shown on Figure 5.

Figure 5: Launch the installation

Make sure to choose the Developer Edition shown in Figure 6.

Figure 6: The Developer edition

The only instance feature you will need for learning SSRS is the Database Engine Services shown in Figure 7.

Figure 7: Features

To make things simpler, just install the Default instance shown in Figure 8. If you have already installed an instance, you’ll see it listed. If that’s the case, you may want to just cancel out of the wizard at this point and use the previously installed instance.

Figure 8: Install the Default instance

Be sure to click Add current user to make your account an administrator. You may also want to set the security to Mixed mode . Figure 9 shows these options.

Figure 9: Security settings

Review the summary shown in Figure 10 and go make yourself a cup or coffee or tea after clicking Install because it could take 10 or 20 minutes for the installation to run.

Figure 10: The Summary

Figure 11 shows that the installation was a success!

Figure 11: Success!

SSMS Installation

SQL Server Management Studio (SSMS) is the tool you will use to connect to the SQL Server instance to restore the sample databases and run queries. If you already have this tool in place, you can skip to the next section.

Microsoft is now releasing new versions of SSMS on a frequent basis, so it is no longer installed during the database engine installation. You can search for “SSMS download” to find the latest version. You can also find a link on the Installation page of the SQL Server 2017 Installation Center, if you used this to install your instance. You can launch it again from the Windows Start menu. Figure 12 shows where you can find the link.

Figure 12: Launching the download page for SSMS

Once you have downloaded the media for SSMS, just run the installation wizard accepting the defaults.

SSRS Service Installation and Configuration

Previous versions of SQL Server allowed you to include SSRS during the installation of the database engine, but that is no longer the case beginning with 2017. Installing them together was quite convenient since the installation took care of the SSRS configuration for you automatically. Now, you must download the media separately and configure SSRS yourself. It’s not difficult, but I’ll walk you through the steps.

Begin by searching for “Download SSRS” or you can also find a link to the download page from the SQL Server 2017 Installation Center shown in Figure 13.

Figure 13: A link to the download page for SSRS

Save and run the downloaded file. To get the installation started, click Install Reporting Services shown in Figure 14.

Figure 14: Install Reporting Services

Click through the installation wizard. The most important question for you to answer is to specify the edition. Make sure that you select the Developer edition.

Once the installation is complete, you’ll be asked to configure the report server. If you are required to restart, do that first. After you restart, you will need to launch the Report Server Configuration Manager. You can do this from the item found in the Windows Start menu or from the final page of the SSRS installation shown in Figure 15 if you didn’t have to restart.

Figure 15: The final page of the SSRS installation wizard

Either way you launch Report Server Configuration Manager, you will need to connect as shown in Figure 16.

Figure 16: Connect to SSRS

There are three items that must be set up when configuring SSRS just to get it running:

• Web Service URL
• Web Portal URL

Click Database on the left menu. Click Change Database shown in Figure 17.

Figure 17: Click Change Database

This will launch the Report Server Database Configuration Wizard . Leave Create a new report server database selected and click Next as shown in Figure 18.

Figure 18: Create a new database

On the following screen, make sure that the local computer name is filled in. If you are using a named instance, then the Server Name will be computer\instance . If you’re not sure, take a look at the “Connecting to Your SQL Server Instance” section later in this article. Leave the Authentication type set at Current User – Integrated Security and click Next as shown in Figure 19.

Figure 19: The server name

On the next page, you will specify the SSRS database name. The default database name is ReportServer . Figure 20 shows that you can leave it at the default and click Next .

Figure 20: The database name

Leave the Authentication Type set at Service Credentials and click Next as shown in Figure 21.

Figure 21: The authentication type

That’s the last question you’ll be asked about the database. Complete the wizard to create the database. Once the database is in place, click Web Service URL .

Leave the defaults in place and click Apply as shown in Figure 22.

Figure 22: The Web Service URL

Click Web Portal URL . Again, leave the defaults in place and click Apply as shown in Figure 23.

Figure 23: The Web Portal URL

Make a note of the URL. This is what you’ll use to connect to the Web Portal after deploying reports. Once done, exit out of the Report Server Configuration Manager. Now that the SSRS service is in place, the next step is installing the development tool.

Installing in Visual Studio

NOTE: At this time, you can install in one step with VS 2017 using SSDT. If you have VS 2019 installed, add the SSRS extension. The instructions in this section cover the 2017 instructions.

You’ll use the SSRS extension for VS to develop reports, and this is the last item to install. You can search for “SSDT Download” or launch the page from the SQL Server 2017 Installation Center shown in Figure 24.

Figure 24: The link to the SSDT download

You will need to scroll down the web page to find the link for SSDT standalone installer as shown in Figure 25.

Figure 25: The SSDT installer

Once downloaded, run the file. Make sure that SQL Server Reporting Services is selected and click Install as shown in Figure 26.

Figure 26: Install SSDT

Accept any other defaults and complete the installation.

Connecting to Your SQL Server Instance

You may have trouble connecting to your local SQL Server instance for a couple of reasons. First, you may not know the actual server name needed to connect to it, especially if you have installed a named instance. The other problem may be that it’s just not running. I’ve seen that happen quite often with laptops.

To solve both problems, launch SQL Server Configuration Manager . You may find it in the SQL Server programs section of the Windows Start menu. If not, take a look at this post for more information. With this tool, you can see the instance name as well as start up an instance that isn’t running. Click SQL Server Services and take a look at the items on the right as shown in Figure 27.

Figure 27: The SQL Server Configuration Manager

Default instances are called SQL Server (MSQLSERVER) . When connecting to the default instance locally, you just need the computer name or an equivalent:

• . (That’s just a period!)

If you see something else in parentheses after the words SQL Server, that’s a named instance. To connect to a named instance, you’ll need the computer name followed by a backslash and the instance name. Here are some examples assuming that my computer is called MyComputerName :

• MyComputerName\SQL2017
• Localhost\SQL2017
• (local)\SQL2017

Notice in the previous image that the default instance is stopped. Just right-click the instance and choose Start to get it running.

Now that you know the name of your SQL Server and have ensured that it’s running, launch SSMS and connect to it as shown in Figure 28.

Figure 28: Connect to the SQL Server

You’ll see the SQL Server and several folders in the Object Explorer window shown in Figure 29.

Figure 29: The Object Explorer

Restoring a Sample Database

To follow along with the examples in this series of articles, you’ll need to restore one or more sample databases. The main database that will be used for the examples is called AdventureWorks2017 . At the time of this writing, Microsoft is hosting the sample databases on GitHub, a well-known software repository site. Search for the AdventureWork2017.bak file. A bak file is a backup file, and that’s what you need. Figure 30 shows the download page.

Figure 30: Download AdventureWorks

Do not download the file to your Desktop , Documents , or Downloads file. Since SQL Server is running under an identity that is not you, it can’t see files in those locations. I recommend just downloading to a file in your C:\ drive such as C:\Temp .

Follow these steps to restore the database:

Connect to the SQL Server instance by launching SSMS and connecting to it. If you have trouble, review the “Connecting to Your SQL Server Instance” section.

Right-click on the Databases folder and select Restore Database… as shown in Figure 31.

Figure 31: Choose Restore Database

Select Device and click the ellipses as shown in Figure 32.

Figure 32: Click the elipses.

This brings up the Select backup devices window. Click Add shown in Figure 33.

Figure 33. Click Add

Navigate to the folder where the bak file is stored as shown in Figure 34.

Figure 34: Navigate to the backup file

Select the file and click OK . You’ll click OK two more times to fire off the restore.

Once the database has been restored, you’ll see the message shown in Figure 35. Click OK two more times to dismiss the dialogs.

Figure 35: A successful restore

If you have followed the instructions in this article, you now have a development environment for SSRS set up on your workstation or laptop. In the next article, I’ll show you how to create some basic reports.

Subscribe for more articles

Fortnightly newsletters help sharpen your skills and keep you ahead, with articles, ebooks and opinion to keep you informed.

Kathi Kellenberger

Kathi Kellenberger is a Customer Success Engineer at Redgate and a Microsoft Data Platform MVP. She has worked with SQL Server for over 20 years and has authored, co-authored, or tech edited more than 20 technical books. Kathi is a volunteer at LaunchCode, the St. Louis based organization providing free training and paid apprenticeships in technology. When Kathi isn’t working she enjoys spending time with family and friends, cycling, singing, and climbing the stairs of tall buildings. Be sure to check out her courses on Pluralsight .

Follow Kathi Kellenberger via

View all articles by Kathi Kellenberger

Load comments

Related articles

PowerBI premium capacity administration: dataset monitoring and tuning

Installing Reporting Services

Reporting Services is a component of Microsoft SQL server 2019. Click on this link to download Reporting Services separately: https://www.microsoft.com/en-us/download/details.aspx?id=100122 . The Microsoft Download page appears.

Use the following procedure to download Microsoft SQL Server 2019 Reporting Services and install it:

Scroll down to Microsoft SQL Server 2019 Reporting Services .

Click Download . The dialog box shown in Figure 2 appears.

Click Run . A security scan is run. When that is successfully completed The dialog box shown in Figure 3 appears.

Click Install Reporting Services . The dialog box shown in Figure 4 appears.

Select the Enter the product key button and type the product key in the appropriate field.

Click Next . The Review the license terms dialog appears.

Select I accept the license terms and click Next . The Install Database Engine dialog appears.

Click Next . The Specify an install location dialog appears.

Use the default location shown here or click Browse to select a different install location.

Click Install . When the set-up procedure is complete, the dialog box shown in Figure 8 appears.

Click Configure report server . The Report Server Configuration Manager dialog appears.

Click Find to select a different server name.

Click the down arrow in the Report Server Instance field to select a different Report Server Instance.

Click Connect to connect to the appropriate server. The dialog box shown in Figure 10 appears.

Click Start . You can modify or define settings for the Report Server. Click Stop to stop the Report Server.

In addition to selecting the Reporting Services option, you can select Analysis Services that provides graphing and charting functionality.

SSRS 2022 Install, Setup and Configuration

By: Joe Gavin   |   Updated: 2024-02-21   |   Comments (3)   |   Related: > Reporting Services Installation

SQL Server Reporting Services (SSRS) is still one of the major components of the Microsoft Business Intelligence (MSBI) stack used to generate interactive and automated reports. It's part of Microsoft SQL Server services, along with SQL Server Analysis Services (SSAS) and SQL Server Integration Services (SSIS).

SSRS 2022 includes enhanced Windows Narrator support, security enhancements, browser performance improvements, and accessibility bug fixes.

The SSRS installation process has changed slightly since it was first released in 2004 as an add-on to SQL Server 2000. We saw in a previous tip: SSRS Install, Setup and Configuration , where the SSRS installation used to be part of the SQL Server installer up through SQL Server 2016. As of SQL Server 2017, the installation now has its own downloadable installer. There are only some minor differences between installing SSRS 2019 and SSRS 2022, but knowing where to get the installer and what to expect before you go through the installation process is helpful. This tip will walk through the various screens and options for the installation process.

We'll look at the minimum hardware and software requirements, see where to get the installer, and walk through each step of installing and configuring a new installation of SSRS 2022. The installation documented here was done on a SQL Server 2022 running on Windows Server 2022.

SSRS 2022 Requirements

You'll likely have more resources than this, but the following are the minimum requirements for installing SSRS 2022:

• 6 GB of available hard drive space
• 512 MB (1 GB is recommended)
• 1 GB (4 GB recommended)
• X64: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support
• 1.4 GHz (2 GHz recommended)
• Windows Server 2016/2019/2022, Windows 10 / 11
• SQL Server Database Engine 2014 SP3 or later
• .NET Framework 4.8 or later

SSRS 2022 Installation

Download the installer.

Go to Microsoft SQL Server 2022 Reporting Services Installer Download

• Click Download .

Retrieve and Run Installer

• Run SQLServerReportingServices.exe from your Download folder.

Welcome Screen

The installer opens, and you're presented with one option on the Welcome screen.

• Install Reporting Services.

Choose Edition and Install

There are four edition options for SSRS. The first three do not require a Product Key:

• Evaluation Edition – Full edition that is good for 180 days.
• Developer Edition – Full edition that can be used for non-production, e.g., test, development, training, or demonstration purposes.
• Express Edition – Limited edition with fewer features than the full edition.
• Paid Edition - The fourth option requires a product key. Click Learn more , which will take you to Find the product key for SQL Server Reporting Services .

Install Paid Edition

• Click the Enter the product key radio button and enter the key in the box.
• Click Next .

Review Licensing Terms

• Read and accept license terms by checking the 'I accept the license terms' checkbox.

Install Database Engine

Specify Install Location

• Choose the drive and directory to install SSRS.
• Click Install .

The SSRS application has been installed, and now it's time to configure it.

Configure SSRS

• Click Configure report server , which runs RSConfigTool.exe to open the Report Server Configuration Manager.

Connect to the SSRS Server

• Click Connect .

Configure Service Account

If the SSRS server requires access to remote servers, a Windows domain account can be specified to run the SSRS service.

• Click on Service Account in the Report Server Configuration Manager.
• Select the 'Use another account' radio button. Enter the domain account information and password.
• Click Apply .

Configure SSRS Databases

Here, we configure the SSRS databases.

• Click Database in the Report Server Configuration Manager.
• Click Change Database .

Create New Database

The new SSRS installation can be pointed to an existing set of SSRS databases. However, since this is a new installation, the default 'Create a new report server database' is left selected, and the installer will create the new databases.

Test the Connection

We must test the connection to the SQL Server to ensure connectivity before attempting to create the SSRS databases.

• Click Test Connection .
• If the connection is successful, click OK .

If the connection is unsuccessful, verify that the SQL Server service is running and accepting connections, and then run the test again.

Name the Database

Unless a name other than the default database names must be used, leave the defaults as ReportServer and ReportServerTemp.

Specify Credentials

Review Summary

Review the install configuration on the Summary screen.

• Click Next if all information is correct.

Progress and Finish

Verify all tasks completed successfully.

• If all tasks are successful, click Finish .

At this point, we have the SSRS service installed and databases created.

It's time to create the Web Service and the Web Portal.

Create the SSRS Web Service

• Click on Web Service URL .

Validate Web Service

Open the Report Server Web Service URL to validate. There are no folders shown because no reports have been deployed yet.

Create Web Portal

• Click Web Portal URL .

Validate Web Portal

To validate, open the Report Server Web Portal URL. Again, the root folder is empty because no reports have been deployed yet.

We now have a fully functioning SSRS server that's ready for reports to be deployed to it.

Email Settings

If Subscriptions to email reports will be created, we'll need to configure the email settings.

• Click E-mail Settings .
• Enter a Sender Address in the form of [email protected] .
• Enter the SMTP Server name.
• Select the Authentication dropdown menu to enter the account and password information if your SMTP server requires authentication.

Email has been configured.

• Click Exit .

You may run into failures, sometimes sporadically, related to TLS 1.2, where subscriptions are not sending emails and generating errors like this:

ERROR: Error sending email. Exception: System.Net.Mail.SmtpException: Failure sending mail. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.

Adding the following registry keys will force TLS 1.2:

The following links have more information on SQL Server Reporting Services:

SSRS Install, Setup and Configuration

• SQL Server Reporting Services 2017 Installation and Configuration
• Install SSRS ReportServer Databases on Azure SQL Managed Instance

Installing SQL Server Reporting Services 2017

SQL Server Reporting Services Standalone Installation

• How to Add SSRS to Existing SQL Server Clustered Instance
• PowerShell Commands for SQL Server Reporting Services
• Visual Studio 2019 Install and Configure for the SQL Server DBA
• How to Install and Configure SSRS with Amazon RDS SQL Server
• Side by Side SSRS Install and Upgrade to Minimize Downtime

About the author

Comments For This Article

Related Content

How to add Reporting Services to an existing SQL Server Clustered Instance

Adding Reporting Services to an existing SQL Server 2005 installation

Install SQL Server Reporting Services 32 bit on a 64 bit Windows Server

Install and Configure SQL Server Reporting Services 2012 SP1 and 2014 in SharePoint Integrated Mode Part 1

Related Categories

SQL Reference Guide

Reporting Services Administration

Reporting Services Best Practices

Reporting Services Configuration

Reporting Services Installation

Reporting Services Migration

Reporting Services Monitoring

Reporting Services Network Load Balancing

Reporting Services Performance

Reporting Services Security

Development

Date Functions

System Functions

JOIN Tables

SQL Server Management Studio

Database Administration

Performance

Performance Tuning

Locking and Blocking

Data Analytics \ ETL

Microsoft Fabric

Azure Data Factory

Integration Services

Popular Articles

Date and Time Conversions Using SQL Server

Format SQL Server Dates with FORMAT Function

SQL Server CROSS APPLY and OUTER APPLY

SQL Server Cursor Example

SQL CASE Statement in Where Clause to Filter Based on a Condition or Expression

DROP TABLE IF EXISTS Examples for SQL Server

SQL Convert Date to YYYYMMDD

Rolling up multiple rows into a single row and column for SQL Server data

SQL NOT IN Operator

Resolving could not open a connection to SQL Server errors

Format numbers in SQL Server

SQL Server PIVOT and UNPIVOT Examples

Script to retrieve SQL Server database backup history and no backups

How to install SQL Server 2022 step by step

An Introduction to SQL Triggers

Using MERGE in SQL Server to insert, update and delete at the same time

How to monitor backup and restore progress in SQL Server

List SQL Server Login and User Permissions with fn_my_permissions

SQL Server Loop through Table Rows without Cursor

SQL Server Database Stuck in Restoring State

• Windows 10 PC Apps & Games
• Windows Leaks & Rumor
• Privacy Policy
• Select Theme: Light Dim Dark

Microsoft tests modern system setting dialogs for Windows 11

Windows 11 Build 26217 hints at AI Component updates via Windows…

Microsoft PC Manager wants you to ‘repair’ Windows 11 by turning…

Microsoft wants devs to add AI in Windows 11 apps for…

Windows 11 KB5037771 out with Start menu features (direct download)

Microsoft aware of Windows Server KB5037765 0x800f0982 error

Windows 10 KB5037768 out with reliable Search (direct download .msu)

Windows 10 finally offers a direct upgrade to Windows 11 23H2…

Microsoft confirms KB5036909 issues in Windows Server with NTLM traffic, LSASS

• Windows 11 24H2
• Windows 11 LTSC
• Snapdragon X Elite
• Windows 11 issues
• Windows 10 issues
• New Outlook
• Get Moment 5
• Windows 10 ISO
• Windows 11 ISO
• Windows 10 PC

As part of Windows May 2024 Patch Tuesday, Microsoft is rolling out two updates for Windows Servers: KB5037782 (Server 2022) and KB5037765 (Server 2019). While the update fixes the NTLM issue , KB5037765 for Windows Server 2019 fails to install with error 0x800f0982.

KB5037765 is a security update for Windows Server 2019 that includes several quality bug fixes, including a fix for an issue where some VPN connections could fail . However, some users told us they could not install the KB5037765 update due to error 0x800f0982.

In a statement, Microsoft told Windows Latest that it is aware of reports where Windows Server KB5037765 could fail to install with 0x800f0982 in regions like Germany, France, Spain, and more. The server-side issue is experienced only when an English language pack is not installed. Thankfully, a fix will be rolled out to everyone in the coming hours.

If you can’t wait for the automatic fix, you can manually install the language pack to fix the 0x800f0982 error:

• Start searching for English, and select English (United States) from the list, and click Next .
• Select Install Language Pack  and click Install to download the US Language Pack.
• Go to Settings > Updates & Security , and start checking for updates. You’ll be able to install the updates normally.

How to fix 0x800f0982 error when installing KB5037765 manually

If you do not have access to internet connection in Windows Server 2019, you can also try these steps:

• Download the Server ISO file multi-language from Microsoft’s website .

• As shown in the screenshot above, you’ll need to install the selected language pack. To do this, copy it to the desktop and open lpksetup.exe using search or Windows Run (Win key + R).
• Manually select the .cab file of the language file saved on the desktop and install it. A reboot is not required.
• Finally, you can download the .msu file of the May 2024 Patch from the Microsoft Update Catalog or directly from Microsoft’s website . Double-click the .msu package to finish applying changes.

According to a thread on Reddit, many Windows administrators have also experienced similar problems with the May 2024 Patch Tuesday update.

Microsoft has already told me it’s working on a fix, so you can wait or try the above steps.

May 2024 Patch for Windows Server 2022 and 2019 fixes several bugs

In an update to its Windows health documentation , Microsoft confirmed that May 2024 updates for Windows Server 2022 and 2019 should patch a bug that causes NTLM traffic spikes in Domain Controllers (DCs). NTLM is used for authentication , and it’s a part of Microsoft’s security portals for the Server, but the April 2024 patch broke it.

“This issue was resolved by Windows updates released May 14, 2024 (KB5037782), and later,” Microsoft confirmed in the support document .

This fix also applies to other supported editions and versions of Windows, including KB5037765.

In addition to NTLM traffic spikes (performance issues), LSASS issues were observed in the April 2024 patch , but Microsoft never acknowledged them.

It’s unclear if LSASS (responsible for Windows login) still crashes on consumer and Windows server editions.

Microsoft May 2024 Patch fixes several bugs, but watch out for two issues

According to the official changelog for KB5037765 and KB5037782, Microsoft has fixed an issue where IE mode (Internet Explorer) may not work as expected. Another bug has been fixed, where Internet Explorer mode stops responding when the left arrow key is pressed during caret browsing.

This month’s security updates include some nice improvements, but Microsoft has confirmed that it’s investigating two issues: installation failures and a bug where changing an account profile picture fails with error code 0x80070520.

You can fix it by manually copying the picture to the profile folder or just logging out and logging in again.

About The Author

Mayank Parmar

Mayank Parmar is an entrepreneur who founded Windows Latest. He is the Editor-in-Chief and has written on various topics in his seven years of career, but he is mostly known for his well-researched work on Microsoft's Windows. His articles and research works have been referred to by CNN, Business Insiders, Forbes, Fortune, CBS Interactive, Microsoft and many others over the years.

RELATED ARTICLES MORE FROM AUTHOR

Windows 10 finally offers a direct upgrade to windows 11 23h2 for more users.

Microsoft says it won’t fix Windows 10 KB5034441’s 0x80070643 error

Microsoft removes the Copilot app from Windows Server after installing it accidentally

Microsoft finally tests “more reliable” Windows Search on Windows 10

Windows 11 Build 26217 hints at AI Component updates via Windows Update

Microsoft PC Manager wants you to ‘repair’ Windows 11 by turning on Bing search

Microsoft wants devs to add AI in Windows 11 apps for “real things”

Featured in

• Terms Of Use

Advertisement

Supported by

C.I.A. Informant Extracted From Russia Had Sent Secrets to U.S. for Decades

• Share full article

By Julian E. Barnes ,  Adam Goldman and David E. Sanger

• Published Sept. 9, 2019 Updated Sept. 17, 2019

WASHINGTON — Decades ago, the C.I.A. recruited and carefully cultivated a midlevel Russian official who began rapidly advancing through the governmental ranks. Eventually, American spies struck gold: The longtime source landed an influential position that came with access to the highest level of the Kremlin.

As American officials began to realize that Russia was trying to sabotage the 2016 presidential election, the informant became one of the C.I.A.’s most important — and highly protected — assets. But when intelligence officials revealed the severity of Russia’s election interference with unusual detail later that year, the news media picked up on details about the C.I.A.’s Kremlin sources.

C.I.A. officials worried about safety made the arduous decision in late 2016 to offer to extract the source from Russia. The situation grew more tense when the informant at first refused, citing family concerns — prompting consternation at C.I.A. headquarters and sowing doubts among some American counterintelligence officials about the informant’s trustworthiness. But the C.I.A. pressed again months later after more media inquiries. This time, the informant agreed.

The move brought to an end the career of one of the C.I.A.’s most important sources. It also effectively blinded American intelligence officials to the view from inside Russia as they sought clues about Kremlin interference in the 2018 midterm elections and next year’s presidential contest.

CNN first reported the 2017 extraction on Monday. Other details — including the source’s history with the agency and the cascade of doubts set off by the informant’s refusal of the initial exfiltration offer — have not been previously reported. This article is based on interviews in recent months with current and former officials who spoke on the condition that their names not be used discussing classified information.

Officials did not disclose the informant’s identity or new location, both closely held secrets. The person’s life remains in danger, current and former officials said, pointing to Moscow’s attempts last year to assassinate Sergei V. Skripal , a former Russian intelligence official who moved to Britain as part of a high-profile spy exchange in 2010.

The Moscow informant was instrumental to the C.I.A.’s most explosive conclusion about Russia’s interference campaign: that President Vladimir V. Putin ordered and orchestrated it himself. As the American government’s best insight into the thinking of and orders from Mr. Putin, the source was also key to the C.I.A.’s assessment that he affirmatively favored Donald J. Trump’s election and personally ordered the hacking of the Democratic National Committee.

The informant, according to people familiar with the matter, was outside of Mr. Putin’s inner circle, but saw him regularly and had access to high-level Kremlin decision-making — easily making the source one of the agency’s most valuable assets.

Handling and running a Moscow-based informant is extremely difficult because of Mr. Putin’s counterintelligence defenses. The Russians are known to make life miserable for foreign spies, following them constantly and at times roughing them up. Former C.I.A. employees describe the entanglements as “Moscow rules.”

The informant’s information was so delicate, and the need to protect the source’s identity so important, that the C.I.A. director at the time, John O. Brennan, kept information from the operative out of President Barack Obama’s daily brief in 2016. Instead, Mr. Brennan sent separate intelligence reports, many based on the source’s information, in special sealed envelopes to the Oval Office.

The information itself was so important and potentially contentious in 2016 that top C.I.A. officials ordered a full review of the informant’s record, according to people briefed on the matter. Officials reviewed information the source had provided years earlier to ensure that it had proved accurate.

Even though the review passed muster, the source’s rejection of the C.I.A.’s initial offer of exfiltration prompted doubts among some counterintelligence officials. They wondered whether the informant had been turned and had become a double agent, secretly betraying his American handlers. That would almost certainly mean that some of the information the informant provided about the Russian interference campaign or Mr. Putin’s intentions would have been inaccurate.

Some operatives had other reasons to suspect the source could be a double agent, according to two former officials, but they declined to explain further.

Other current and former officials who acknowledged the doubts said they were put to rest when the source agreed to be extracted after the C.I.A. asked a second time.

Leaving behind one’s native country is a weighty decision, said Joseph Augustyn, a former senior C.I.A. officer who once ran the agency’s defector resettlement center. Often, informants have kept their spy work secret from their families.

Listen to ‘The Daily’: The C.I.A. Spy Inside the Kremlin

Hosted by michael barbaro, produced by theo balcomb, jonathan wolfe and michael simon johnson, and edited by lisa tobin and m.j. davis lin, we look at the story of an informant who, through his access to president vladimir v. putin, helped deliver explosive revelations about russian election meddling in 2016..

From The New York Times, I’m Michael Barbaro. This is “The Daily.”

Last week, CNN broke the story that the U.S. had secretly exfiltrated a top spy from Russia back in 2017. What that means now for U.S. intelligence.

It’s Monday, September 16.

So, Julian, tell me about this story that you had been reporting out.

A few months ago, my colleague Adam Goldman and I started doing some reporting about a key C.I.A. asset who had been offered exfiltration from Russia by the C.I.A., and we knew that this source was the main person who told the C.I.A., who told the entire intelligence community, that Vladimir Putin interfered in the election and favored Donald Trump. So this person was really important, and what happened to this person was a little bit of a mystery.

Julian Barnes covers national security for The Times.

Any time you’re trying to report about sensitive intelligence, it’s extremely slow going.

I had one conversation with a person who, as I was asking the question, he said, stop, I do not want to hear that question. I do not want you to ask me that question. So it’s very painstaking work. But last week, as I was doing reporting, I learned that a cable network was onto one of the stories I was working on. But it was Friday, and I was nervous, but I let that go.

[LAUGHS] Crossed your fingers and went home for the day.

Cross your fingers, go home. And Monday morning, I got a call that CNN was going to report the story.

Good morning. I’m Jim Sciutto in New York.

And I’m Poppy Harlow. We’re so glad you’re with us this Monday morning, and we do begin with a really significant CNN exclusive.

And I was like, uh-oh.

And Jim, this is your reporting. You have learned about a highly secretive intelligence operation by the United States.

That’s right, Poppy. Multiple Trump administration officials with direct knowledge tell me that in a previously undisclosed secret mission in 2017, the U.S. successfully extracted from Russia one of its highest-level covert sources inside the Russian government.

And then what happens?

So it was not long after CNN broke the news that Russia apparently released the spy’s name.

We have not confirmed the name of the spy, nor will we repeat the name the Russians revealed.

At first, when this happens, you think, oh, it’s Russian disinformation. But then you start a quick Google search, and looks like this guy was a diplomat, looks like this guy was a diplomat in the United States at some point, and lo and behold, there’s a deed for a house in the Virginia suburbs.

So you just Googled the name of this spy, and oddly enough, an address pops up for what appears to be a senior Russian official working with the U.S. What do you actually do with that information?

So it’s sort of shocking to find that. It’s just profoundly weird. This is not how it’s supposed to work. Russia’s not supposed to release the name of the spy. You’re not supposed to Google the spy in your backyard.

But what you do with that information is you drive out and pay a visit.

And so the next morning, the family car was in use, so I rented a Car2Go, which is this very small smart car, which you’re not supposed to take on the highway.

But I discovered you can achieve speeds of 65 miles an hour with a very, very small smart car.

You’re in a classic spy thriller car, right?

You know, it’s not like you’re sneaking up when you drive in basically a clown car to somebody’s house.

But I needn’t thought, as I was weaving through the curvy roads of Virginia subdivisions, that I was going to surprise anyone, because when I arrived at the house, there was a half dozen other reporters there.

So I parked my car, said hello to my rival at The Washington Post, and then I walked up the driveway.

I’m walking down to the cul-de-sac, where you can see the house has a big porch, three stories, very large house.

I just remember being surprised. These are huge houses. It’s pretty good to be a spy, I guess.

The lawn has been freshly mowed, and the little cuttings are still on the driveway here.

So I walked up to the house.

A lot of windows right here on the porch. You know, someone has been in here and has drawn the shutters. I walked up earlier, and you could see inside, and now you can’t. They’ve drawn the drapes. Children’s toys visible in the backyard. Wading pool. There’s the card from another reporter left in the door. I’m going to ring the bell.

And then, without thinking, I put my hand on the doorknob, and then I just instantly thought, oh man, Russia is known for going after spies by coating doorknobs with nerve agents.

Right. And you just touched the doorknob.

And I just touched the doorknob.

But of course, you’re fine.

I’m fine. Momentary scare.

The garbage bin is left out front. The neighbors had said that there was a dog left behind, and the sheriff was supposed to come look.

But nobody was home. But I wanted to figure out what happened, so I walked down the driveway, crossed the cul-de-sac, and tried to meet some of the neighbors.

Hi, I’m with The New York Times. I’m Julian Barnes. I’m doing some reporting about the neighbor.

I don’t know if you saw the press reports or whatnot, but there was — reports broke out in my paper and CNN yesterday about the informant who told about Russian meddling, and Russian media, Russian government, is reporting it is your next-door neighbor.

And what did they know?

Well, when you’re reporting about somebody and talking to the neighbors, the classic journalistic joke was, they were very quiet.

I remember them being new neighbors. We hadn’t even met them. Been meaning to get over, didn’t get over.

And of course, stereotypically, we heard they were very quiet. But one of the neighbors described —

July 4, we’re shooting off fireworks, and I’m like, oh crap, there’s the neighbor, the wife and the kid sitting on the front porch. So I said, let me go over and invite them.

Inviting them over for the Fourth of July fireworks.

So I went over to invite them, and she said she didn’t speak English. So her husband came out and said that they would just watch from the steps.

The interactions were a little bit few and far between.

That was the only interaction with them other than just waving when we passed on the street and if he was walking the dog, or I’d wave when I’d see him home in the yard. And I did stop when his wife was walking the dog, and I stopped and just said, hi, how you doing? And I don’t think she understood me because she said, fine, fine, fine. I said, how do you like the house and the neighborhood? And she’s like, fine, fine, fine. So I’m like, I don’t think you understand me or not. But that was the only time I’d ever talked to either one of them.

But the details they did provide really seem to confirm that this was our guy, that this was the spot.

It was a Russian couple, and I remember two kids, a toddler boy that may have been 3, I don’t know.

The family moved in June of 2018. They were vague about where they came from, just saying they had moved from Northern Virginia.

But I know there was at least one little kid, and then the other kid was — I don’t know if he was junior high or high school.

The husband was friendly, but spoke in what everyone knew was a heavy Russian accent.

He was a diplomat for many years, so I presume his English was pretty good. Was that right?

Yeah, I mean, he definitely had an accent, but I could understand him real good.

And one of the neighbors told me that they had been whisked away the night before. A van came up, loaded them up, and took them to a location unknown.

Did these neighbors that you were talking to seem shocked by this seeming spy in their midst?

You know, oddly, they didn’t.

It’s a little bit spy novel-ish, but it’s how the world works. So, I mean, we do it to them, they do it to us.

One person was like, we live near Washington, there are a lot of spies around here.

It’s government, you know? It’s every government.

And they seem to very quickly process that this neighbor, who they didn’t know very well, that he had been a spy, and one of the neighbors was pretty outspoken and turned out to be pretty proud of his neighbor and said —

My only concern is, if the guy is on our side, I don’t know that y’all are doing him any favors.

This guy was doing important work for America, and he had really risked his own life to do good for our country.

Hmm. So we didn’t know our neighbor was a spy, but now that we know he was a spy for us, for the good guys, rah, rah.

Exactly, which is a pretty quick mental somersault to do, I think. But yeah, that’s what happened. They quickly thought, all right, he’s on our side, let’s rally around the flag for him.

Hmm. So then what happens?

After a few hours, the postman drives up, and he is immediately mobbed by six reporters. And then I just look at that scene, and I think, the postman doesn’t know anything.

This is over. So I got back into my car, and I headed back to The New York Times Washington bureau to keep reporting.

And presumably drop off your Car2Go at its Car2Go place?

You can just leave them anywhere in the District of Columbia.

We’ll be right back.

All right, Julian, how did we get here? What’s the story?

So decades ago, the C.I.A. approached a low-level or mid-level Russian diplomat with an offer to spy for the United States. Now, we don’t know exactly when or where that occurred, but we do know that it was outside Russia, because it’s very difficult to approach, to cultivate, a potential source inside Russia. Inside Russia, American spies are followed everywhere. So this approach occurred overseas. And with this informant, the C.I.A. really struck gold.

The informant rose to be an aide to a key diplomatic figure. The informant’s patron was the chief diplomatic adviser to Putin.

And for the C.I.A., this is the critical thing. It’s very hard to understand Vladimir Putin’s thinking or his strategy. Vladimir Putin is a former spy himself.

He is very careful. He does not communicate over cellphones, over landlines. He does not write a lot of stuff down. He just knows those kinds of things are what get intercepted, recorded, photographed. And so when we’re talking about Vladimir Putin, human intelligence — spies, informants — are really, really critical. By the time we get to the Obama administration, the reports coming from the informant are handled with the utmost sensitivity. There are reports for the president’s eyes only put into sealed envelopes, delivered to the Oval Office, and required to be returned to the C.I.A., extraordinary levels of secrecy and protection that show how important this spy’s information was. And by nurturing this informant over decades, watching him get ever better access, they developed what some people say is the C.I.A.‘s most important source in 2016.

The New York Times reports on the growing F.B.I. investigation into the Democratic National Committee email hack. The agency reportedly is also trying to determine if aides and groups close to Hillary Clinton were targeted as well. Secretary of State John Kerry this morning raised the issue with Russia’s foreign minister. The Russians scoffed at reports Moscow was behind the hack.

So this is where we are when the most difficult challenge to the American intelligence agencies in a generation develops, where a adversarial power begins to interfere in an American election.

What specifically do we know about the intelligence that this spy is able to get the U.S. in 2016?

There are two pieces of intelligence that we know about that were really important, one of which is that —

Tonight, the Central Intelligence Agency is confident that a Russian hacking plot tried to influence the U.S. presidential election in favor of Donald Trump.

— Putin affirmatively wanted Donald Trump to be president. There was something about Trump that Putin liked, and this ultimately became a key finding of the C.I.A. They had multiple sources for it, but this was the first source. This was the most important source, we believe, for that finding. The other thing is that the source confirmed that the D.N.C. hack, the Russian cyber penetration of the Democratic National Committee, had been ordered and approved by Vladimir Putin, that it was part of Putin’s larger strategy, and to have this informant confirm that finding really allowed the C.I.A. to have a high level of confidence in that. That really shaped the understanding in 2016 about what had happened.

In a memo to C.I.A. staff, director John Brennan said that he, F.B.I. director James Comey, and director of national intelligence James Clapper were now all on the same page about the scope, nature and intent of the Russian interference in our presidential election.

But there is a downside. When you are delivering the most explosive, the most important intelligence, and that intelligence is entering the political debate —

I think it’s ridiculous. I think it’s just another excuse. I don’t believe it.

— there is a level of scrutiny.

So we have to be very careful right now. We cannot make these wild assumptions that the Russian government was behind this, because right now, we do not have all of the evidence.

Reporters start asking questions.

We haven’t been given a shred of evidence to substantiate the claim that the Russians were behind this.

Members of Congress start asking questions. People want to know, how does the C.I.A. know this?

And there are hints at the end of 2016 that the C.I.A. has a source in Russia.

New information derived from diplomatic sources and spies working for U.S. allies points directly to the Russian president.

So despite all the secrecy and the care around this informant, his existence is suddenly something people understand.

Yes. Now, if you go back and look at the stories at the end of 2016, they’re just the lightest hints, but the C.I.A. is getting nervous, because the C.I.A. knows when reporters are asking questions, so, too, are the Russians. And Putin is ruthless about people he considers traitors, so they begin to write a plan to extract the informant from Russia.

And as the news stories increased in early 2017 —

This morning, a Washington Post investigation focuses on Russian government interference in our election. In August, the C.I.A. gave then-President Obama a report, quote, “drawn from sourcing deep inside the Russian government.”

— the C.I.A. went to the spy and said, it’s time to go. You need to come to America. That offer was accepted.

So, Julian, the spy is in the United States. I guess we didn’t know it at the time, but he’s in Virginia. How do you come to get on this story a few months back?

So in 2018, I started reporting about why the U.S. seemed to have not a very good understanding about what Russia’s intentions or strategy for interfering in the midterm elections would be. There was assumptions that they were going to do it, but the intelligence community didn’t have a high level of confidence about exactly what would be going on. So we wrote a story about how the C.I.A.‘s assets in Russia had gone dark and that they no longer had eyes on the Kremlin. Now, at that time, we didn’t know exactly why that was, and that story sort of speculated that there was a number of different reasons why the spies could have gone silent. But what we didn’t know is that the really good spy had been brought out.

Mm-hmm. It’s sort of amazing that you could tell even from the outside that something had changed, and that what had changed turned out to be the absence of a single person. So how common is that, for a country like the U.S. to be so reliant on a single source in a place as important strategically as Russia?

Now, of course, there are multiple sources. You can’t have high confidence in a conclusion and still have one source, but this source is probably the most important one because of the access to the Kremlin. And the reality is, in this day and age, it is very hard to develop good sources. As this story shows, it takes decades. It took years to cultivate this person, to get this person into a place where they could offer the highest and most valuable level of intelligence. You don’t turn around and develop a spy in a year. You don’t get a high-ranking Kremlin official to just turn and give you the crown jewels. And in Russia, the kind of technical intelligence that the U.S. relies on in so many places — eavesdropping, signals intelligence, spy satellites — the Russians are very sophisticated at sort of blocking some of that stuff. And so that puts so much importance on the old-school human spies.

Everything you just said does not seem to bode very well for our intelligence on Russia with the 2020 election approaching.

That’s right. That’s what’s really important about this story going forward, looking at the 2020 election, when everyone believes that Russia will mount another interference campaign. We know that they’ll do that, but we don’t know how they’ll do it. They’re going to use different tactics than they used before. And if you don’t have the eyes on the ground, you don’t have an early warning system. You don’t know what Russia is going to do. You don’t know what Putin himself is ordering.

Julian, thank you very much.

Thank you. It’s been a pleasure.

In an interview with The Times, James Clapper, the director of national intelligence under President Obama, said there was little doubt that this past week’s revelations were going to, quote, “make recruiting assets in Russia even more difficult than it already is.”

Here’s what else you need to know today. On Sunday night, President Trump said he was prepared to take military action in response to a series of devastating attacks on Saudi Arabia’s oil production system over the weekend, which knocked out about half the kingdom’s oil output and sent global oil prices soaring. Responsibility for the attacks was claimed by the Houthi rebels in Yemen, who have been engaged in a yearslong battle with Saudi Arabia. But U.S. intelligence suggested that the attack was actually conducted by Iran, potentially escalating an already tense standoff with the Trump administration. Iran denied any role in the attack. But in a tweet, President Trump wrote that the U.S. was, quote, “locked and loaded depending on verification” of Iran’s role. And an investigation by two reporters at The Times has further corroborated the allegation that while a student at Yale, Supreme Court Justice Brett Kavanaugh pulled down his pants at a party and thrust his penis at a female classmate, Deborah Ramirez. Kavanaugh denied the claim during his confirmation hearings, but the reporters found that at least seven people, including Ramirez’s mother, had heard about the incident before Kavanaugh became a federal judge, two of them just days after the incident had occurred. The reporters also found a Yale classmate who said that Kavanaugh had thrust his penis into the hand of a different female student. That classmate reported the incident to the F.B.I. before Kavanaugh was confirmed, but the F.B.I. did not investigate the claim. On Sunday, The Times reported that the Justice Department will present one of its most prestigious awards for distinguished service to the lawyers who worked to confirm Kavanaugh.

That’s it for “The Daily.” I’m Michael Barbaro. See you tomorrow.

“It’s a very difficult decision to make, but it is their decision to make,” Mr. Augustyn said. “There have been times when people have not come out when we strongly suggested that they should.”

The decision to extract the informant was driven “in part” because of concerns that Mr. Trump and his administration had mishandled delicate intelligence, CNN reported. But former intelligence officials said there was no public evidence that Mr. Trump directly endangered the source, and other current American officials insisted that media scrutiny of the agency’s sources alone was the impetus for the extraction.

Mr. Trump was first briefed on the intelligence about Russian interference, including material from the prized informant, two weeks before his inauguration. A C.I.A. spokeswoman responding to the CNN report called the assertion that Mr. Trump’s handling of intelligence drove the reported extraction “misguided speculation.”

Some former intelligence officials said the president’s closed-door meetings with Mr. Putin and other Russian officials , along with Twitter posts about delicate intelligence matters , have sown concern among overseas sources.

“We have a president who, unlike any other president in modern history, is willing to use sensitive, classified intelligence however he sees fit,” said Steven L. Hall, a former C.I.A. official who led the agency’s Russia operations. “He does it in front of our adversaries. He does it by tweet. We are in uncharted waters.”

But the government had indicated that the source existed long before Mr. Trump took office, first in formally accusing Russia of interference in October 2016 and then when intelligence officials declassified parts of their assessment about the interference campaign for public release in January 2017. News agencies, including NBC , began reporting around that time about Mr. Putin’s involvement in the election sabotage and on the C.I.A.’s possible sources for the assessment.

The following month, The Washington Post reported that the C.I.A.’s conclusions relied on “sourcing deep inside the Russian government.” And The New York Times later published articles disclosing details about the source .

The news reporting in the spring and summer of 2017 convinced United States government officials that they had to update and revive their extraction plan, according to people familiar the matter.

The extraction ensured the informant was in a safer position and rewarded for a long career in service to the United States. But it came at a great cost: It left the C.I.A. struggling to understand what was going on inside the highest ranks of the Kremlin.

The agency has long struggled to recruit sources close to Mr. Putin, a former intelligence officer himself wary of C.I.A. operations. He confides in only a small group of people and has rigorous operational security, eschewing electronic communications.

James R. Clapper Jr., the former director of national intelligence who left office at the end of the Obama administration, said he had no knowledge of the decision to conduct an extraction. But, he said, there was little doubt that revelations about the extraction were “going to make recruiting assets in Russia even more difficult than it already is.”

An earlier version of this article referred incorrectly to the timing of the initial reporting on the C.I.A.’s 2016 exfiltration offer to a Russian informant. An offer that appears to be the same one that The New York Times described was reported in 2018 in Bob Woodward’s book “Fear.”

How we handle corrections

Our Coverage of the Trump Documents Case

The justice department has filed federal criminal charges against former president donald trump over his mishandling of classified documents..

The Indictment: Federal prosecutors said that Trump put national security secrets at risk  by mishandling classified documents and schemed to block the government from reclaiming the material. Here’s a look at the evidence .

The Co-Defendants: While Trump plays the leading role in the case, the narrative as laid out by prosecutors relies heavily on supporting characters  like Carlos De Oliveira  and Walt Nauta .

Obstruction: The Mueller report raised questions about whether Trump had obstructed the inquiry into the ties between the former president’s 2016 campaign and Russia. With prosecutors adding new charges  in the documents case, the subject is back .

The Judge: Judge Aileen Cannon , a Trump appointee who showed favor to the former president earlier in the investigation, has scant experience  running criminal trials. Can she prove her critics wrong ?

A Slow Pace: Cannon has allowed unresolved issues to build up on her docket, and that appears to have kept her from making a prompt decision on the timing of the case. It is one of several factors that have stirred concern about her decision-making .

A Global Leader in Labor Market Analytics

Clear, actionable insight.

Lightcast (a merger of Emsi and Burning Glass Technologies) has over two decades of experience in finding solutions and delivering the competitive edge our clients demand. We have superior data analysis capabilities with a wide range of data sources, sophisticated analytical tools, and intuitive reporting features. Lightcast delivers the world's best labor market data through our software products, APIs, and consulting projects.

As featured in

Lightcast Talent Intelligence

In today’s fast-paced and competitive business environment, talent intelligence plays a pivotal role in shaping the success of organizations. It allows companies to gain a comprehensive understanding of their workforce and the broader labor market, serving as the bridge between internal and external data. Our approach to Talent Intelligence is centered around aggregating the most extensive data sources and applying open-sourced and market recognized data standards to enrich and validate this data. 

OUR CLIENTS AND PARTNERS INCLUDE:

Labor Market Data Pros On Your Side

With world-class customer service and over two decades of expertise, we're committed to helping you make better, faster decisions—driven by data.

Lightcast Skills

Labor market analytics solutions:, enterprise & staffing.

Strategically recruit the workers you need

Prepare students for a fast-changing labor market

Workforce Development

Unlock success by connecting workers with jobs

Economic Development

Attract and retain business based on your community's strengths

Latest from the Blog

Lightcast Joins The Snowflake Marketplace

Lightcast data sets the industry standard for talent intelligence, And now, we’ve expanded access to a new platform : Lightcast has joined the Snowflake Marketplace .

The Future of the Future of Work

Award-Winning Education With Lightcast Data

How Global Organisations use Lightcast Data to Power their Research

New In Analyst: Sectors and Future Projections

In the news.

• Windows 10, version 22H2 update history
• May 14, 2024—KB5037768 (OS Builds 19044.4412 and 19045.4412)
• April 23, 2024—KB5036979 (OS Build 19045.4355) Preview
• April 9, 2024—KB5036892 (OS Builds 19044.4291 and 19045.4291)
• March 26, 2024—KB5035941 (OS Build 19045.4239) Preview
• March 12, 2024—KB5035845 (OS Builds 19044.4170 and 19045.4170)
• February 29, 2024—KB5034843 (OS Build 19045.4123) Preview
• February 13, 2024—KB5034763 (OS Builds 19044.4046 and 19045.4046)
• January 23, 2024—KB5034203 (OS Build 19045.3996) Preview
• January 9, 2024—KB5034122 (OS Builds 19044.3930 and 19045.3930)
• December 12, 2023—KB5033372 (OS Builds 19044.3803 and 19045.3803)
• November 30, 2023—KB5032278 (OS Build 19045.3758) Preview
• November 14, 2023—KB5032189 (OS Builds 19044.3693 and 19045.3693)
• October 26, 2023—KB5031445 (OS Build 19045.3636) Preview
• October 10, 2023—KB5031356 (OS Builds 19044.3570 and 19045.3570)
• September 26, 2023—KB5030300 (OS Build 19045.3516) Preview
• September 12, 2023—KB5030211 (OS Builds 19044.3448 and 19045.3448)
• August 22, 2023—KB5029331 (OS Build 19045.3393) Preview
• August 8, 2023—KB5029244 (OS Builds 19044.3324 and 19045.3324)
• July 25, 2023—KB5028244 (OS Build 19045.3271) Preview
• July 11, 2023—KB5028166 (OS Builds 19044.3208 and 19045.3208)
• June 27, 2023—KB5027293 (OS Build 19045.3155) Preview
• June 13, 2023—KB5027215 (OS Builds 19044.3086 and 19045.3086)
• May 23, 2023—KB5026435 (OS Build 19045.3031) Preview
• May 9, 2023—KB5026361 (OS Builds 19042.2965, 19044.2965, and 19045.2965)
• April 25, 2023—KB5025297 (OS Build 19045.2913) Preview
• April 11, 2023—KB5025221 (OS Builds 19042.2846, 19044.2846, and 19045.2846)
• March 21, 2023—KB5023773 (OS Builds 19042.2788, 19044.2788, and 19045.2788) Preview
• March 14, 2023—KB5023696 (OS Builds 19042.2728, 19044.2728, and 19045.2728)
• February 21, 2023—KB5022906 (OS Builds 19042.2673, 19044.2673, and 19045.2673) Preview
• February 14, 2023—KB5022834 (OS Builds 19042.2604, 19044.2604, and 19045.2604)
• January 19, 2023—KB5019275 (OS Builds 19042.2546, 19044.2546, and 19045.2546) Preview
• January 10, 2023—KB5022282 (OS Builds 19042.2486, 19044.2486, and 19045.2486)
• December 13, 2022—KB5021233 (OS Builds 19042.2364, 19043.2364, 19044.2364, and 19045.2364)
• November 15, 2022—KB5020030 (OS Builds 19042.2311, 19043.2311, 19044.2311, and 19045.2311) Preview
• November 8, 2022—KB5019959 (OS Builds 19042.2251, 19043.2251, 19044.2251, and 19045.2251)
• October 28, 2022—KB5020953 (OS Builds 19042.2194, 19043.2194, 19044.2194, and 19045.2194) Out-of-band
• Windows 10, version 21H2 update history
• October 25, 2022—KB5018482 (OS Builds 19042.2193, 19043.2193, and 19044.2193) Preview
• October 17, 2022—KB5020435 (OS Builds 19042.2132, 19043.2132, and 19044.2132) Out-of-band
• October 11, 2022—KB5018410 (OS Builds 19042.2130, 19043.2130, and 19044.2130)
• September 20, 2022—KB5017380 (OS Builds 19042.2075, 19043.2075, and 19044.2075) Preview
• September 13, 2022—KB5017308 (OS Builds 19042.2006, 19043.2006, and 19044.2006)
• August 26, 2022—KB5016688 (OS Builds 19042.1949, 19043.1949, and 19044.1949) Preview
• August 9, 2022—KB5016616 (OS Builds 19042.1889, 19043.1889, and 19044.1889)
• July 26, 2022—KB5015878 (OS Builds 19042.1865, 19043.1865, and 19044.1865) Preview
• July 12, 2022—KB5015807 (OS Builds 19042.1826, 19043.1826, and 19044.1826)
• June 28, 2022—KB5014666 (OS Builds 19042.1806, 19043.1806, and 19044.1806) Preview
• June 20, 2022—KB5016139 (OS Builds 19042.1767, 19043.1767, and 19044.1767) Out-of-band
• June 14, 2022—KB5014699 (OS Builds 19042.1766, 19043.1766, and 19044.1766)
• June 2, 2022—KB5014023 (OS Builds 19042.1741, 19043.1741, and 19044.1741) Preview
• May 19, 2022—KB5015020 (OS Builds 19042.1708, 19043.1708, and 19044.1708) Out-of-band
• May 10, 2022—KB5013942 (OS Builds 19042.1706, 19043.1706, and 19044.1706)
• April 25, 2022—KB5011831 (OS Builds 19042.1682, 19043.1682, and 19044.1682) Preview
• April 12, 2022—KB5012599 (OS Builds 19042.1645, 19043.1645, and 19044.1645)
• March 22, 2022—KB5011543 (OS Builds 19042.1620, 19043.1620, and 19044.1620) Preview
• March 8, 2022—KB5011487 (OS Builds 19042.1586, 19043.1586, and 19044.1586)
• February 15, 2022—KB5010415 (OS Builds 19042.1566, 19043.1566, and 19044.1566) Preview
• February 8, 2022—KB5010342 (OS Builds 19042.1526, 19043.1526, and 19044.1526)
• January 25, 2022—KB5009596 (OS Builds 19042.1503, 19043.1503, and 19044.1503) Preview
• January 17, 2022—KB5010793 (OS Builds 19042.1469, 19043.1469, and 19044.1469) Out-of-band
• January 11, 2022—KB5009543 (OS Builds 19042.1466, 19043.1466, and 19044.1466)
• December 14, 2021—KB5008212 (OS Builds 19041.1415, 19042.1415, 19043.1415, and 19044.1415)
• November 22, 2021—KB5007253 (OS Builds 19041.1387, 19042.1387, 19043.1387, and 19044.1387) Preview
• Windows 10, version 21H1 update history
• End of service statement
• November 9, 2021—KB5007186 (OS Builds 19041.1348, 19042.1348, and 19043.1348)
• October 26, 2021—KB5006738 (OS Builds 19041.1320, 19042.1320, and 19043.1320) Preview
• October 12, 2021—KB5006670 (OS Builds 19041.1288, 19042.1288, and 19043.1288)
• September 30, 2021—KB5005611 (OS Builds 19041.1266, 19042.1266, and 19043.1266) Preview
• September 14, 2021—KB5005565 (OS Builds 19041.1237, 19042.1237, and 19043.1237)
• September 1, 2021—KB5005101 (OS Builds 19041.1202, 19042.1202, and 19043.1202) Preview
• August 10, 2021—KB5005033 (OS Builds 19041.1165, 19042.1165, and 19043.1165)
• July 29, 2021—KB5004296 (OS Builds 19041.1151, 19042.1151, and 19043.1151) Preview
• July 13, 2021—KB5004237 (OS Builds 19041.1110, 19042.1110, and 19043.1110)
• July 6, 2021—KB5004945 (OS Builds 19041.1083, 19042.1083, and 19043.1083) Out-of-band
• June 29, 2021—KB5004760 (OS Builds 19041.1082, 19042.1082, and 19043.1082) Out-of-band
• June 21, 2021—KB5003690 (OS Builds 19041.1081, 19042.1081, and 19043.1081) Preview
• June 11, 2021—KB5004476 (OS Builds 19041.1055, 19042.1055, and 19043.1055) Out-of-band
• June 8, 2021—KB5003637 (OS Builds 19041.1052, 19042.1052, and 19043.1052)
• May 25, 2021—KB5003214 (OS Builds 19041.1023, 19042.1023, and 19043.1023) Preview
• May 11, 2021—KB5003173 (OS Builds 19041.985, 19042.985, and 19043.985)
• Windows 10, version 20H2 and Windows Server, version 20H2 update history
• April 28, 2021—KB5001391 (OS Builds 19041.964 and 19042.964) Preview
• April 13, 2021—KB5001330 (OS Builds 19041.928 and 19042.928)
• March 29, 2021—KB5000842 (OS Builds 19041.906 and 19042.906) Preview
• March 18, 2021—KB5001649 (OS Builds 19041.870 and 19042.870) Out-of-band
• March 15, 2021—KB5001567 (OS Builds 19041.868 and 19042.868) Out-of-band
• March 9, 2021—KB5000802 (OS Builds 19041.867 and 19042.867)
• February 24, 2021—KB4601382 (OS Builds 19041.844 and 19042.844) Preview
• February 9, 2021—KB4601319 (OS Builds 19041.804 and 19042.804)
• February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789) Preview
• January 12, 2021—KB4598242 (OS Builds 19041.746 and 19042.746)
• December 8, 2020—KB4592438 (OS Builds 19041.685 and 19042.685)
• November 30, 2020—KB4586853 (OS Builds 19041.662 and 19042.662) Preview
• November 19, 2020—KB4594440 (OS Builds 19041.631 and 19042.631) Out-of-band
• November 10, 2020—KB4586781 (OS Builds 19041.630 and 19042.630)
• October 29, 2020—KB4580364 (OS Builds 19041.610 and 19042.610) Preview
• Windows 10, version 2004 and Windows Server, version 2004 update history
• October 13, 2020—KB4579311 (OS Build 19041.572)
• October 1, 2020—KB4577063 (OS Build 19041.546) Preview
• September 8, 2020—KB4571756 (OS Build 19041.508)
• September 3, 2020—KB4571744 (OS Build 19041.488) Preview
• August 11, 2020—KB4566782 (OS Build 19041.450)
• July 31, 2020—KB4568831 (OS Build 19041.423)
• July 14, 2020—KB4565503 (OS Build 19041.388)
• June 18, 2020—KB4567523 (OS Build 19041.331)
• June 9, 2020—KB4557957 (OS Build 19041.329)
• Windows 10, version 1909 and Windows Server, version 1909 update history
• May 10, 2022—KB5013945 (OS Build 18363.2274)
• April 12, 2022—KB5012591 (OS Build 18363.2212)
• March 8, 2022—KB5011485 (OS Build 18363.2158)
• February 8, 2022—KB5010345 (OS Build 18363.2094)
• January 17, 2022—KB5010792 (OS Build 18363.2039) Out-of-band
• January 11, 2022—KB5009545 (OS Build 18363.2037)
• December 14, 2021—KB5008206 (OS Build 18363.1977)
• November 9, 2021—KB5007189 (OS Build 18363.1916)
• October 12, 2021—KB5006667 (OS Build 18363.1854)
• September 21, 2021—KB5005624 (OS Build 18363.1830) Preview
• September 14, 2021—KB5005566 (OS Build 18363.1801)
• August 26, 2021—KB5005103 (OS Build 18363.1766) Preview
• August 10, 2021—KB5005031 (OS Build 18363.1734)
• July 29, 2021—KB5004293 (OS Build 18363.1714) Preview
• July 13, 2021—KB5004245 (OS Build 18363.1679)
• July 6, 2021—KB5004946 (OS Build 18363.1646) Out-of-band
• June 15, 2021—KB5003698 (OS Build 18363.1645) Preview
• June 8, 2021—KB5003635 (OS Build 18363.1621)
• May 20, 2021—KB5003212 (OS Build 18363.1593) Preview
• May 11, 2021—KB5003169 (OS Build 18363.1556)
• April 22, 2021—KB5001396 (OS Build 18363.1533) Preview
• April 13, 2021—KB5001337 (OS Build 18363.1500)
• March 25, 2021—KB5000850 (OS Build 18363.1474) Preview
• March 18, 2021—KB5001648 (OS Build 18363.1443) Out-of-band
• March 15, 2021—KB5001566 (OS Build 18363.1441) Out-of-band
• March 9, 2021—KB5000808 (OS Build 18363.1440)
• February 16, 2021—KB4601380 (OS Build 18363.1411) Preview
• February 11, 2021—KB5001028 (OS Build 18363.1379) Out-of-band
• February 9, 2021—KB4601315 (OS Build 18363.1377)
• January 21, 2021—KB4598298 (OS Build 18363.1350) Preview
• January 12, 2021—KB4598229 (OS Build 18363.1316)
• December 8, 2020—KB4592449 (OS Builds 18362.1256 and 18363.1256)
• November 19, 2020—KB4594443 (OS Builds 18362.1199 and 18363.1199) Out-of-band
• November 19, 2020—KB4586819 (OS Builds 18362.1237 and 18363.1237) Preview
• November 10, 2020—KB4586786 (OS Builds 18362.1198 and 18363.1198)
• October 20, 2020—KB4580386 (OS Builds 18362.1171 and 18363.1171) Preview
• October 13, 2020—KB4577671 (OS Builds 18362.1139 and 18363.1139)
• September 16, 2020—KB4577062 (OS Builds 18362.1110 and 18363.1110) Preview
• September 8, 2020—KB4574727 (OS Builds 18362.1082 and 18363.1082)
• August 20, 2020—KB4566116 (OS Builds 18362.1049 and 18363.1049) Preview
• August 11, 2020—KB4565351 (OS Builds 18362.1016 and 18363.1016)
• July 21, 2020—KB4559004 (OS Builds 18362.997 and 18363.997)
• July 14, 2020—KB4565483 (OS Builds 18362.959 and 18363.959)
• June 16, 2020—KB4567512 (OS Builds 18362.904 and 18363.904)
• June 9, 2020—KB4560960 (OS Builds 18362.900 and 18363.900)
• May 12, 2020—KB4556799 (OS Builds 18362.836 and 18363.836)
• April 21, 2020—KB4550945 (OS Builds 18362.815 and 18363.815)
• April 14, 2020—KB4549951 (OS Builds 18362.778 and 18363.778)
• March 30, 2020—KB4554364 (OS Builds 18362.753 and 18363.753)
• March 24, 2020—KB4541335 (OS Builds 18362.752 and 18363.752)
• March 12, 2020—KB4551762 (OS Builds 18362.720 and 18363.720)
• March 10, 2020—KB4540673 (OS Builds 18362.719 and 18363.719)
• February 27, 2020—KB4535996 (OS Builds 18362.693 and 18363.693)
• February 11, 2020—KB4532693 (OS Builds 18362.657 and 18363.657)
• January 28, 2020—KB4532695 (OS Builds 18362.628 and 18363.628)
• January 14, 2020—KB4528760 (OS Builds 18362.592 and 18363.592)
• December 10, 2019—KB4530684 (OS Builds 18362.535 and 18363.535)
• November 12, 2019—KB4524570 (OS Builds 18362.476 and 18363.476)
• Windows 10, version 1903 and Windows Server, version 1903 update history
• October 24, 2019—KB4522355 (OS Build 18362.449)
• October 8, 2019—KB4517389 (OS Build 18362.418)
• October 3, 2019—KB4524147 (OS Build 18362.388)
• September 26, 2019—KB4517211 (OS Build 18362.387)
• September 23, 2019—KB4522016 (OS Build 18362.357)
• September 10, 2019—KB4515384 (OS Build 18362.356)
• August 30, 2019—KB4512941 (OS Build 18362.329)
• August 13, 2019—KB4512508 (OS Build 18362.295)
• July 26, 2019—KB4505903 (OS Build 18362.267)
• July 9, 2019—KB4507453 (OS Build 18362.239)
• June 27, 2019—KB4501375 (OS Build 18362.207)
• June 11, 2019—KB4503293 (OS Build 18362.175)
• May 29, 2019—KB4497935 (OS Build 18362.145)
• Windows 10, version 1809, Windows Server, version 1809, and Windows Server 2019 update history

May 14, 2024—KB5037765 (OS Build 17763.5820)

• April 9, 2024—KB5036896 (OS Build 17763.5696)
• March 25, 2024—KB5037425 (OS Build 17763.5579) Out-of-band
• March 12, 2024—KB5035849 (OS Build 17763.5576)
• February 13, 2024—KB5034768 (OS Build 17763.5458)
• January 9, 2024—KB5034127 (OS Build 17763.5329)
• December 12, 2023—KB5033371 (OS Build 17763.5206)
• November 14, 2023—KB5032196 (OS Build 17763.5122)
• October 10, 2023—KB5031361 (OS Build 17763.4974)
• September 12, 2023—KB5030214 (OS Build 17763.4851)
• August 8, 2023—KB5029247 (OS Build 17763.4737)
• July 11, 2023—KB5028168 (OS Build 17763.4645)
• June 13, 2023—KB5027222 (OS Build 17763.4499)
• May 9, 2023—KB5026362 (OS Build 17763.4377)
• April 11, 2023—KB5025229 (OS Build 17763.4252)
• March 14, 2023—KB5023702 (OS Build 17763.4131)
• February 14, 2023—KB5022840 (OS Build 17763.4010)
• January 10, 2023—KB5022286 (OS Build 17763.3887)
• December 20, 2022—KB5022554 (OS Build 17763.3772) Out-of-band
• December 13, 2022—KB5021237 (OS Build 17763.3770)
• November 17, 2022—KB5021655 (OS Build 17763.3653) Out-of-band
• November 8, 2022—KB5019966 (OS Build 17763.3650)
• October 17, 2022—KB5020438 (OS Build 17763.3534) Out-of-band
• October 11, 2022—KB5018419 (OS Build 17763.3532)
• September 20, 2022—KB5017379 (OS Build 17763.3469) Preview
• September 13, 2022—KB5017315 (OS Build 17763.3406)
• August 23, 2022—KB5016690 (OS Build 17763.3346) Preview
• August 9, 2022—KB5016623 (OS Build 17763.3287)
• July 21, 2022—KB5015880 (OS Build 17763.3232) Preview
• July 12, 2022—KB5015811 (OS Build 17763.3165)
• June 23, 2022—KB5014669 (OS Build 17763.3113) Preview
• June 14, 2022—KB5014692 (OS Build 17763.3046)
• May 24, 2022—KB5014022 (OS Build 17763.2989) Preview
• May 19, 2022—KB5015018 (OS Build 17763.2931) Out-of-band
• May 10, 2022—KB5013941 (OS Build 17763.2928)
• April 21, 2022—KB5012636 (OS Build 17763.2867) Preview
• April 12, 2022—KB5012647 (OS Build 17763.2803)
• March 22, 2022—KB5011551 (OS Build 17763.2746) Preview
• March 8, 2022—KB5011503 (OS Build 17763.2686)
• February 15, 2022—KB5010427 (OS Build 17763.2628) Preview
• February 8, 2022—KB5010351 (OS Build 17763.2565)
• January 25, 2022—KB5009616 (OS Build 17763.2510) Preview
• January 18, 2022—KB5010791 (OS Build 17763.2458) Out-of-band
• January 11, 2022—KB5009557 (OS Build 17763.2452)
• January 4, 2022—KB5010196 (OS Build 17763.2369) Out-of-band
• December 14, 2021—KB5008218 (OS Build 17763.2366)
• November 22, 2021—KB5007266 (OS Build 17763.2330) Preview
• November 14, 2021—KB5008602 (OS Build 17763.2305) Out-of-band
• November 9, 2021—KB5007206 (OS Build 17763.2300)
• October 19, 2021—KB5006744 (OS Build 17763.2268) Preview
• October 12, 2021—KB5006672 (OS Build 17763.2237)
• September 21, 2021—KB5005625 (OS Build 17763.2210) Preview
• September 14, 2021—KB5005568 (OS Build 17763.2183)
• August 26, 2021—KB5005102 (OS Build 17763.2145) Preview
• August 10, 2021—KB5005030 (OS Build 17763.2114)
• July 27, 2021—KB5005394 (OS Build 17763.2091) Out-of-band
• July 20, 2021—KB5004308 (OS Build 17763.2090) Preview
• July 13, 2021—KB5004244 (OS Build 17763.2061)
• July 6, 2021—KB5004947 (OS Build 17763.2029) Out-of-band
• June 15, 2021—KB5003703 (OS Build 17763.2028) Preview
• June 8, 2021—KB5003646 (OS Build 17763.1999)
• May 20, 2021—KB5003217 (OS Build 17763.1971) Preview
• May 11, 2021—KB5003171 (OS Build 17763.1935)
• April 22, 2021—KB5001384 (OS Build 17763.1911) Preview
• April 13, 2021—KB5001342 (OS Build 17763.1879)
• March 25, 2021—KB5000854 (OS Build 17763.1852) Preview
• March 18, 2021—KB5001638 (OS Build 17763.1823) Out-of-band
• March 15, 2021—KB5001568 (OS Build 17763.1821) Out-of-band
• March 9, 2021—KB5000822 (OS Build 17763.1817)
• February 16, 2021—KB4601383 (OS Build 17763.1790) Preview
• February 9, 2021—KB4601345 (OS Build 17763.1757)
• January 21, 2021—KB4598296 (OS Build 17763.1728) Preview
• January 12, 2021—KB4598230 (OS Build 17763.1697)
• December 8, 2020—KB4592440 (OS Build 17763.1637)
• November 19, 2020—KB4586839 (OS Build 17763.1613) Preview
• November 17, 2020—KB4594442 (OS Build 17763.1579) Out-of-band
• November 10, 2020—KB4586793 (OS Build 17763.1577)
• October 20, 2020—KB4580390 (OS Build 17763.1554) Preview
• October 13, 2020—KB4577668 (OS Build 17763.1518)
• September 16, 2020—KB4577069 (OS Build 17763.1490) Preview
• September 8, 2020—KB4570333 (OS Build 17763.1457)
• August 20, 2020—KB4571748 (OS Build 17763.1432) Preview
• August 11, 2020—KB4565349 (OS Build 17763.1397)
• July 21, 2020—KB4559003 (OS Build 17763.1369)
• July 14, 2020—KB4558998 (OS Build 17763.1339)
• June 16, 2020—KB4567513 (OS Build 17763.1294)
• June 9, 2020—KB4561608 (OS Build 17763.1282)
• May 12, 2020—KB4551853 (OS Build 17763.1217)
• April 21, 2020—KB4550969 (OS Build 17763.1192)
• April 14, 2020—KB4549949 (OS Build 17763.1158)
• March 30, 2020—KB4554354 (OS Build 17763.1132)
• March 17, 2020—KB4541331 (OS Build 17763.1131)
• March 10, 2020—KB4538461 (OS Build 17763.1098)
• February 25, 2020—KB4537818 (OS Build 17763.1075)
• February 11, 2020—KB4532691 (OS Build 17763.1039)
• January 23, 2020—KB4534321 (OS Build 17763.1012)
• January 14, 2020—KB4534273 (OS Build 17763.973)
• December 10, 2019—KB4530715 (OS Build 17763.914)
• November 12, 2019—KB4523205 (OS Build 17763.864)
• October 15, 2019—KB4520062 (OS Build 17763.832)
• October 8, 2019—KB4519338 (OS Build 17763.805)
• October 3, 2019—KB4524148 (OS Build 17763.775)
• September 24, 2019—KB4516077 (OS Build 17763.774)
• September 23, 2019—KB4522015 (OS Build 17763.740)
• September 10, 2019—KB4512578 (OS Build 17763.737)
• August 17, 2019—KB4512534 (OS Build 17763.720)
• August 13, 2019—KB4511553 (OS Build 17763.678)
• July 22, 2019—KB4505658 (OS Build 17763.652)
• July 9, 2019—KB4507469 (OS Build 17763.615)
• June 26, 2019—KB4509479 (OS Build 17763.593)
• June 18, 2019—KB4501371 (OS Build 17763.592)
• June 11, 2019—KB4503327 (OS Build 17763.557)
• May 21, 2019—KB4497934 (OS Build OS 17763.529)
• May 19, 2019—KB4505056 (OS Build 17763.504)
• May 14, 2019—KB4494441 (OS Build 17763.503)
• May 3, 2019—KB4495667 (OS Build 17763.475)
• May 1, 2019—KB4501835 (OS Build 17763.439)
• April 9, 2019—KB4493509 (OS Build 17763.437)
• March 26, 2019—KB4490481 (OS Build 17763.402)
• March 12, 2019—KB4489899 (OS Build 17763.379)
• March 1, 2019—KB4482887 (OS Build 17763.348)
• February 12, 2019—KB4487044 (OS Build 17763.316)
• January 22, 2019—KB4476976 (OS Build 17763.292)
• January 8, 2019—KB4480116 (OS Build 17763.253)
• December 19, 2018—KB4483235 (OS Build 17763.195)
• December 11, 2018—KB4471332 (OS Build 17763.194)
• December 5, 2018—KB4469342 (OS Build 17763.168)
• November 13, 2018—KB4464455 (OS Build 17763.107)
• November 13, 2018—KB4467708 (OS Build 17763.134)
• October 9, 2018—KB4464330 (OS Build 17763.55)
• Windows 10, version 1803 update history
• May 11, 2021—KB5003174 (OS Build 17134.2208)
• April 13, 2021—KB5001339 (OS Build 17134.2145)
• March 18, 2021—KB5001634 (OS Build 17134.2090) Out-of-band
• March 15, 2021—KB5001565 (OS Build 17134.2088) Out-of-band
• March 9, 2021—KB5000809 (OS Build 17134.2087)
• February 9, 2021—KB4601354 (OS Build 17134.2026)
• January 12, 2021—KB4598245 (OS Build 17134.1967)
• December 8, 2020—KB4592446 (OS Build 17134.1902)
• November 10, 2020—KB4586785 (OS Build 17134.1845)
• October 13, 2020—KB4580330 (OS Build 17134.1792)
• September 8, 2020—KB4577032 (OS Build 17134.1726)
• August 11, 2020—KB4571709 (OS Build 17134.1667)
• July 14, 2020—KB4565489 (OS Build 17134.1610)
• June 16, 2020—KB4567514 (OS Build 17134.1553)
• June 9, 2020—KB4561621 (OS Build 17134.1550)
• May 12, 2020—KB4556807 (OS Build 17134.1488)
• April 21, 2020—KB4550944 (OS Build 17134.1456)
• April 14, 2020—KB4550922 (OS Build 17134.1425)
• March 30, 2020—KB4554349 (OS Build 17134.1401)
• March 17, 2020—KB4541333 (OS Build 17134.1399)
• March 10, 2020—KB4540689 (OS Build 17134.1365)
• February 25, 2020—KB4537795 (OS Build 17134.1345)
• February 11, 2020—KB4537762 (OS Build 17134.1304)
• January 23, 2020—KB4534308 (OS Build 17134.1276)
• January 14, 2020—KB4534293 (OS Build 17134.1246)
• December 10, 2019—KB4530717 (OS Build 17134.1184)
• November 12, 2019—KB4525237 (OS Build 17134.1130)
• October 15, 2019—KB4519978 (OS Build 17134.1099)
• October 8, 2019—KB4520008 (OS Build 17134.1069)
• October 3, 2019—KB4524149 (OS Build 17134.1040)
• September 24, 2019—KB4516045 (OS Build 17134.1039)
• September 23, 2019—KB4522014 (OS Build 17134.1009)
• September 10, 2019—KB4516058 (OS Build 17134.1006)
• August 19, 2019—KB4512509 (OS Build 17134.984)
• August 13, 2019—KB4512501 (OS Build 17134.950)
• July 16, 2019—KB4507466 (OS Build 17134.915)
• July 9, 2019—KB4507435 (OS Build 17134.885)
• June 26, 2019—KB4509478 (OS Build 17134.860)
• June 18, 2019—KB4503288 (OS Build 17134.858)
• June 11, 2019—KB4503286 (OS Build 17134.829)
• May 21, 2019—KB4499183 (OS Build 17134.799)
• May 19, 2019—KB4505064 (OS Build 17134.766)
• May 14, 2019—KB4499167 (OS Build 17134.765)
• April 25, 2019—KB4493437 (OS Build 17134.753)
• April 9, 2019—KB4493464 (OS Build 17134.706)
• March 19, 2019—KB4489894 (OS Build 17134.677)
• March 12, 2019—KB4489868 (OS Build 17134.648)
• February 19, 2019—KB4487029 (OS Build 17134.619)
• February 12, 2019—KB4487017 (OS Build 17134.590)
• January 15, 2019—KB4480976 (OS Build 17134.556)
• January 8, 2019—KB4480966 (OS Build 17134.523)
• December 19, 2018—KB4483234 (OS Build 17134.472)
• December 11, 2018—KB4471324 (OS Build 17134.471)
• November 27, 2018—KB4467682 (OS Build 17134.441)
• November 13, 2018—KB4467702 (OS Build 17134.407)
• October 24, 2018—KB4462933 (OS Build 17134.376)
• October 9, 2018—KB4462919 (OS Build 17134.345)
• September 26, 2018—KB4458469 (OS Build 17134.320)
• September 17, 2018—KB4464218 (OS Build 17134.286)
• September 11, 2018—KB4457128 (OS Build 17134.285)
• August 30, 2018—KB4346783 (OS Build 17134.254)
• August 14, 2018—KB4343909 (OS Build 17134.228)
• July 24, 2018—KB4340917 (OS Build 17134.191)
• July 16, 2018—KB4345421 (OS Build 17134.167)
• July 10, 2018—KB4338819 (OS Build 17134.165)
• June 26, 2018—KB4284848 (OS Build 17134.137)
• June 12, 2018—KB4284835 (OS Build 17134.112)
• June 5, 2018—KB4338548 (OS Build 17134.83)
• May 23, 2018—KB4100403 (OS Build 17134.81)
• May 8, 2018—KB4103721 (OS Build 17134.48)
• Windows 10, version 1709 update history
• October 13, 2020—KB4580328 (OS Build 16299.2166)
• September 8, 2020—KB4577041 (OS Build 16299.2107)
• August 11, 2020—KB4571741 (OS Build 16299.2045)
• July 14, 2020—KB4565508 (OS Build 16299.1992)
• June 18, 2020—KB4567515 (OS Build 16299.1937)
• June 9, 2020—KB4561602 (OS Build 16299.1932)
• May 12, 2020—KB4556812 (OS Build 16299.1868)
• April 14, 2020—KB4550927 (OS Build 16299.1806)
• March 30, 2020—KB4554342 (OS Build 16299.1776)
• March 17, 2020—KB4541330 (OS Build 16299.1775)
• March 10, 2020—KB4540681 (OS Build 16299.1747)
• February 25, 2020—KB4537816 (OS Build 16299.1717)
• February 11, 2020—KB4537789 (OS Build 16299.1686)
• January 23, 2020—KB4534318 (OS Build 16299.1654)
• January 14, 2020—KB4534276 (OS Build 16299.1625)
• January 14, 2020—KB4535289 Update for Windows 10 Mobile (OS Build 15254.603)
• December 10, 2019—KB4530714 (OS Build 16299.1565)
• December 10, 2019—KB4522812 Update for Windows 10 Mobile (OS Build 15254.600)
• November 12, 2019—KB4522811 Update for Windows 10 Mobile (OS Build 15254.597)
• November 12, 2019—KB4525241 (OS Build 16299.1508)
• October 15, 2019—KB4520006 (OS Build 16299.1481)
• October 8, 2019—KB4522809 Update for Windows 10 Mobile (OS Build 15254.590)
• October 8, 2019—KB4520004 (OS Build 16299.1451)
• October 3, 2019—KB4524150 (OS Build 16299.1421)
• September 24, 2019—KB4516071 (OS Build 16299.1420)
• September 23, 2019—KB4522012 (OS Build 16299.1392)
• September 10, 2019—KB4516066 (OS Build 16299.1387)
• September 10, 2019—KB4518514 Update for Windows 10 Mobile (OS Build 15254.587)
• August 16, 2019—KB4512494 (OS Build 16299.1365)
• August 13, 2019—KB4512516 (OS Build 16299.1331)
• August 13, 2019—KB4513172 Update for Windows 10 Mobile (OS Build 15254.582)
• July 16, 2019—KB4507465 (OS Build 16299.1296 )
• July 9, 2019—KB4507455 (OS Build 16299.1268)
• July 9, 2019—KB4509104 Update for Windows 10 Mobile (OS Build 15254.575)
• June 26, 2019—KB4509477 (OS Build 16299.1239)
• June 18, 2019—KB4503281 (OS Build 16299.1237)
• June 11, 2019—KB4503284 (OS Build 16299.1217)
• June 11, 2019—KB4505390 Update for Windows 10 Mobile (OS Build 15254.572)
• May 28, 2019—KB4499147 (OS Build 16299.1182)
• May 19, 2019—KB4505062 (OS Build 16299.1150)
• May 14, 2019—KB4500154 Update for Windows 10 Mobile (OS Build 15254.566)
• May 14, 2019—KB4499179 (OS Build 16299.1146)
• April 25, 2019—KB4493440 (OS Build 16299.1127)
• April 9, 2019—KB4495357 Update for Windows 10 Mobile (OS Build 15254.562)
• April 9, 2019—KB4493441 (OS Build 16299.1087)
• March 19, 2019—KB4489890 (OS Build 16299.1059)
• March 12, 2019—KB4489886 (OS Build 16299.1029)
• March 12, 2019—KB4491736 Update for Windows 10 Mobile (OS Build 15254.556)
• February 19, 2019—KB4487021 (OS Build 16299.1004)
• February 12, 2019—KB4487695 Update for Windows 10 Mobile (OS Build 15254.552)
• February 12, 2019—KB4486996 (OS Build 16299.967)
• January 15, 2019—KB4480967 (OS Build 16299.936)
• January 8, 2019—KB4480978 (OS Build 16299.904)
• January 8, 2019—KB4483203 Update for Windows 10 Mobile (OS Build 15254.547)
• December 19, 2018—KB4483232 (OS Build 16299.847)
• December 11, 2018—KB4478936 Update for Windows 10 Mobile (OS Build 15254.544)
• December 11, 2018—KB4471329 (OS Build 16299.846)
• November 27, 2018—KB4467681 (OS Build 16299.820)
• November 13, 2018—KB4469220 Update for Windows 10 Mobile (OS Build 15254.541)
• November 13, 2018—KB4467686 (OS Build 16299.785)
• October 18, 2018—KB4462932 (OS Build 16299.755)
• October 9, 2018—KB4464853 Update for Windows 10 Mobile (OS Build 15254.538)
• October 9, 2018—KB4462918 (OS Build 16299.726)
• September 26, 2018—KB4457136 (OS Build 16299.699)
• September 17, 2018—KB4464217 (OS Build 16299.666)
• September 11, 2018—KB4457142 (OS Build 16299.665)
• September 11, 2018—KB4459082 Update for Windows 10 Mobile (OS Build 15254.530)
• August 30, 2018—KB4343893 (OS Build 16299.637)
• August 14, 2018—KB4346644 Update for Windows 10 Mobile (OS Build 15254.527)
• August 14, 2018—KB4343897 (OS Build 16299.611)
• July 24, 2018—KB4338817 (OS Build 16299.579)
• July 16, 2018—KB4345420 (OS Build 16299.551)
• July 10, 2018—KB4338825 (OS Build 16299.547)
• June 21, 2018—KB4284822 (OS Build 16299.522)
• June 12, 2018—KB4316692 Update for Windows 10 Mobile (OS Build 15254.489)
• June 12, 2018—KB4284819 (OS Build 16299.492)
• May 21, 2018—KB4103714 (OS Build 16299.461)
• May 8, 2018—KB4134196 Update for Windows 10 Mobile (OS Build 15254.401)
• May 8, 2018—KB4103727 (OS Build 16299.431)
• April 23, 2018—KB4093105 (OS Build 16299.402)
• April 10, 2018—KB4099572 Update for Windows 10 Mobile (OS Build 15254.369)
• April 10, 2018—KB4093112 (OS Build 16299.371)
• March 22, 2018—KB4089848 (OS Build 16299.334)
• March 15, 2018—KB4090912 Update for Windows 10 Mobile (OS Build 15254.313)
• March 13, 2018—KB4088776 (OS Build 16299.309)
• March 5, 2018—KB4090913 (OS Build 16299.251)
• February 14, 2018—KB4077675 (OS Build 15254.248)
• February 13, 2018—KB4074588 (OS Build 16299.248)
• January 31, 2018—KB4058258 (OS Build 16299.214)
• January 18, 2018—KB4073291 (OS Build 16299.201)
• January 5, 2018—KB4073117 (OS Build 15254.158)
• January 3, 2018—KB4056892 (OS Build 16299.192)
• December 12, 2017—KB4054517 (OS Build 16299.125)
• December 12, 2017—KB4056342 Update for Windows 10 Mobile (OS Build 15254.124)
• November 30, 2017—KB4051963 (OS Build 16299.98)
• November 14, 2017—KB4048955 (OS Build 16299.64)
• November 14, 2017—KB4052314 (OS Build 15254.12)
• October 17, 2017—KB4043961 (OS Build 16299.19)
• Windows 10, version 1703 update history
• March 9, 2021—KB5000812 (OS Build 15063.2679)
• February 9, 2021—KB4601330 (OS Build 15063.2642)
• January 12, 2021—KB4599208 (OS Build 15063.2614)
• December 8, 2020—KB4592473 (OS Build 15063.2584)
• November 10, 2020—KB4586782 (OS Build 15063.2554)
• October 13, 2020—KB4580370 (OS Build 15063.2525)
• September 8, 2020—KB4577021 (OS Build 15063.2500)
• August 11, 2020—KB4571689 (OS Build 15063.2467)
• July 14, 2020—KB4565499 (OS Build 15063.2439)
• June 18, 2020—KB4567516 (OS Build 15063.2411)
• June 9, 2020—KB4561605 (OS Build 15063.2409)
• May 12, 2020—KB4556804 (OS Build 15063.2375)
• April 14, 2020—KB4550939 (OS Build 15063.2346)
• March 10, 2020—KB4540705 (OS Build 15063.2313)
• February 11, 2020—KB4537765 (OS Build 15063.2284)
• January 14, 2020—KB4534296 (OS Build 15063.2254)
• December 10, 2019—KB4530711 (OS Build 15063.2224)
• November 12, 2019—KB4525245 (OS Build 15063.2172)
• October 8, 2019—KB4520010 (OS Build 15063.2108)
• October 3, 2019—KB4524151 (OS Build 15063.2079)
• September 24, 2019—KB4516059 (OS Build 15063.2078)
• September 23, 2019—KB4522011 (OS Build 15063.2046)
• September 10, 2019—KB4516068 (OS Build 15063.2045)
• August 17, 2019—KB4512474 (OS Build 15063.2021)
• August 13, 2019—KB4512507 (OS Build 15063.1988)
• July 16, 2019—KB4507467 (OS Build 15063.1955)
• July 9, 2019—KB4507450 (OS Build 15063.1928)
• June 26, 2019—KB4509476 (OS Build 15063.1898)
• June 18, 2019—KB4503289 (OS Build 15063.1897)
• June 11, 2019—KB4503279 (OS Build 15063.1868)
• May 28, 2019—KB4499162 (OS Build 15063.1839)
• May 19, 2019—KB4505055 (OS Build 15063.1808)
• May 14, 2019—KB4499181 (OS Build 15063.1805)
• May 2, 2019—KB4502112 (OS Build 15063.1785)
• April 25, 2019—KB4493436 (OS Build 15063.1784)
• April 9, 2019—KB4493474 (OS Build 15063.1746)
• March 19, 2019—KB4489888 (OS Build 15063.1716)
• March 12, 2019—KB4489871 (OS Build 15063.1689)
• February 19, 2019—KB4487011 (OS Build 15063.1659)
• February 12, 2019—KB4487020 (OS Build 15063.1631)
• January 15, 2019—KB4480959 (OS Build 15063.1596)
• January 8, 2019—KB4480973 (OS Build 15063.1563)
• December 19, 2018—KB4483230 (OS Build 15063.1508)
• December 11, 2018—KB4471327 (OS Build 15063.1506)
• November 27, 2018—KB4467699 (OS Build 15063.1478)
• November 13, 2018—KB4467696 (OS Build 15063.1446)
• October 18, 2018—KB4462939 (OS Build 15063.1418)
• October 9, 2018—KB4462937 (OS Build 15063.1387)
• September 20, 2018—KB4457141 (OS Build 15063.1358)
• September 11, 2018—KB4457138 (OS Build 15063.1324)
• August 30, 2018—KB4343889 (OS Build 15063.1292)
• August 14, 2018—KB4343885 (OS Build 15063.1266)
• July 24, 2018—KB4338827 (OS Build 15063.1235)
• July 16, 2018—KB4345419 (OS Build 15063.1209)
• July 10, 2018—KB4338826 (OS Build 15063.1206)
• June 21, 2018—KB4284830 (OS Build 15063.1182)
• June 12, 2018—KB4284874 (OS Build 15063.1155)
• May 17, 2018—KB4103722 (OS Build 15063.1112)
• May 8, 2018—KB4103731 (OS Build 15063.1088)
• April 17, 2018—KB4093117 (OS Build 15063.1058)
• April 10, 2018—KB4093107 (OS Build 15063.1029)
• March 22, 2018—KB4088891 (OS Build 15063.994)
• March 13, 2018—KB4088782 (OS Build 15063.966 and 15063.968)
• March 8, 2018—KB4092077 (OS Build 15063.936)
• February 22, 2018—KB4077528 (OS Build 15063.936)
• February 13, 2018—KB4074592 (OS Build 15063.909)
• January 17, 2018—KB4057144 (OS Build 15063.877)
• January 3, 2018—KB4056891 (OS Build 15063.850)
• December 12, 2017—KB4053580 (OS Build 15063.786)
• November 22, 2017—KB4055254 (OS Build 15063.729)
• November 14, 2017—KB4048954 (OS Build 15063.726 and 15063.728)
• November 2, 2017—KB4049370 (OS Build 15063.675)
• October 10, 2017—KB4041676 (OS Build 15063.674)
• September 25, 2017—KB4040724 (OS Build 15063.632)
• September 12, 2017—KB4038788 (OS Build 15063.608)
• August 8, 2017—KB4034674 (OS Build 15063.540)
• July 31, 2017—KB4032188 (OS Build 15063.502)
• July 11, 2017—KB4025342 (OS Build 15063.483)
• June 27, 2017—KB4022716 (OS Build 15063.447)
• June 13, 2017—KB4022725 (OS Build 15063.413 and 15063.414)
• May 25, 2017—KB4020102 (OS Build 15063.332)
• May 9, 2017—KB4016871 (OS Build 15063.296 and 15063.297)
• April 25, 2017—KB4016240 (OS Build 15063.250)
• April 11, 2017—KB4015583 (OS Build 15063.138)
• April 5, 2017—KB4016251 (OS Build 15063.13)
• Windows 10, version 1607 and Windows Server 2016 update history
• May 14, 2024—KB5037763 (OS Build 14393.6981)
• April 9, 2024—KB5036899 (OS Build 14393.6897)
• March 22, 2024—KB5037423 (OS Build 14393.6799) Out-of-band
• March 12, 2024—KB5035855 (OS Build 14393.6796)
• February 13, 2024—KB5034767 (OS Build 14393.6709)
• January 9, 2024—KB5034119 (OS Build 14393.6614)
• December 12, 2023—KB5033373 (OS Build 14393.6529)
• November 14, 2023—KB5032197 (OS Build 14393.6452)
• October 10, 2023—KB5031362 (OS Build 14393.6351)
• September 12, 2023—KB5030213 (OS Build 14393.6252)
• August 8, 2023—KB5029242 (OS Build 14393.6167)
• July 11, 2023—KB5028169 (OS Build 14393.6085)
• June 23, 2023—KB5028623 (OS Build 14393.5996) Out-of-band
• June 13, 2023—KB5027219 (OS Build 14393.5989)
• May 9, 2023—KB5026363 (OS Build 14393.5921)
• April 11, 2023—KB5025228 (OS Build 14393.5850)
• March 14, 2023—KB5023697 (OS Build 14393.5786)
• February 14, 2023—KB5022838 (OS Build 14393.5717)
• January 10, 2023—KB5022289 (OS Build 14393.5648)
• December 13, 2022—KB5021235 (OS Build 14393.5582)
• November 17, 2022—KB5021654 (OS Build 14393.5502) Out-of-band
• November 8, 2022—KB5019964 (OS Build 14393.5501)
• October 18, 2022—KB5020439 (OS Build 14393.5429) Out-of-band
• October 11, 2022—KB5018411 (OS Build 14393.5427)
• September 13, 2022—KB5017305 (OS Build 14393.5356)
• August 9, 2022—KB5016622 (OS Build 14393.5291)
• July 12, 2022—KB5015808 (OS Build 14393.5246)
• June 14, 2022—KB5014702 (OS Build 14393.5192)
• May 19, 2022—KB5015019 (OS Build 14393.5127) Out-of-band
• May 10, 2022—KB5013952 (OS Build 14393.5125)
• April 12, 2022—KB5012596 (OS Build 14393.5066)
• March 8, 2022—KB5011495 (OS Build 14393.5006) - EXPIRED
• February 8, 2022—KB5010359 (OS Build 14393.4946) - EXPIRED
• January 17, 2022—KB5010790 (OS Build 14393.4889) Out-of-band
• January 11, 2022—KB5009546 (OS Build 14393.4886) - EXPIRED
• January 5, 2022—KB5010195 (OS Build 14393.4827) Out-of-band
• December 14, 2021—KB5008207 (OS Build 14393.4825) - EXPIRED
• November 14, 2021—KB5008601 (OS Build 14393.4771) Out-of-band
• November 9, 2021—KB5007192 (OS Build 14393.4770) - EXPIRED
• October 12, 2021—KB5006669 (OS Build 14393.4704) - EXPIRED
• September 14, 2021—KB5005573 (OS Build 14393.4651) - EXPIRED
• August 10, 2021—KB5005043 (OS Build 14393.4583) - EXPIRED
• July 29, 2021—KB5005393 (OS Build 14393.4532) Out-of-band
• July 13, 2021—KB5004238 (OS Build 14393.4530) - EXPIRED
• July 7, 2021—KB5004948 (OS Build 14393.4470) Out-of-band - EXPIRED
• June 8, 2021—KB5003638 (OS Build 14393.4467) - EXPIRED
• May 11, 2021—KB5003197 (OS Build 14393.4402) - EXPIRED
• April 13, 2021—KB5001347 (OS Build 14393.4350) - EXPIRED
• March 18, 2021—KB5001633 (OS Build 14393.4288) Out-of-band
• March 9, 2021—KB5000803 (OS Build 14393.4283) - EXPIRED
• February 9, 2021—KB4601318 (OS Build 14393.4225)
• January 12, 2021—KB4598243 (OS Build 14393.4169)
• December 8, 2020—KB4593226 (OS Build 14393.4104)
• November 19, 2020—KB4594441 (OS Build 14393.4048) Out-of-band
• November 10, 2020—KB4586830 (OS Build 14393.4046)
• October 13, 2020—KB4580346 (OS Build 14393.3986)
• September 8, 2020—KB4577015 (OS Build 14393.3930)
• August 11, 2020—KB4571694 (OS Build 14393.3866)
• July 14, 2020—KB4565511 (OS Build 14393.3808)
• June 18, 2020—KB4567517 (OS Build 14393.3755)
• June 9, 2020—KB4561616 (OS Build 14393.3750)
• May 12, 2020—KB4556813 (OS Build 14393.3686)
• April 21, 2020—KB4550947 (OS Build 14393.3659)
• April 14, 2020—KB4550929 (OS Build 14393.3630)
• March 17, 2020—KB4541329 (OS Build 14393.3595)
• March 10, 2020—KB4540670 (OS Build 14393.3564)
• February 25, 2020—KB4537806 (OS Build 14393.3542)
• February 11, 2020—KB4537764 (OS Build 14393.3504)
• January 23, 2020—KB4534307 (OS Build 14393.3474)
• January 14, 2020—KB4534271 (OS Build 14393.3443)
• December 10, 2019—KB4530689 (OS Build 14393.3384)
• November 12, 2019—KB4525236 (OS Build 14393.3326)
• October 15, 2019—KB4519979 (OS Build 14393.3300)
• October 8, 2019—KB4519998 (OS Build 14393.3274)
• October 3, 2019—KB4524152 (OS Build 14393.3243)
• September 24, 2019—KB4516061 (OS Build 14393.3242)
• September 23, 2019—KB4522010 (OS Build 14393.3206)
• September 10, 2019—KB4516044 (OS Build 14393.3204)
• August 17, 2019—KB4512495 (OS Build 14393.3181)
• August 13, 2019—KB4512517 (OS Build 14393.3144)
• July 16, 2019—KB4507459 (OS Build 14393.3115)
• July 9, 2019—KB4507460 (OS Build 14393.3085)
• June 27, 2019—KB4509475 (OS Build 14393.3056)
• June 18, 2019—KB4503294 (OS Build 14393.3053)
• June 11, 2019—KB4503267 (OS Build 14393.3025)
• May 23, 2019—KB4499177 (OS Build 14393.2999)
• May 19, 2019—KB4505052 (OS Build 14393.2972)
• May 14, 2019—KB4494440 (OS Build 14393.2969)
• April 25, 2019—KB4493473 (OS Build 14393.2941)
• April 9, 2019—KB4493470 (OS Build 14393.2906)
• March 19, 2019—KB4489889 (OS Build 14393.2879)
• March 12, 2019—KB4489882 (OS Build 14393.2848)
• February 19, 2019—KB4487006 (OS Build 14393.2828)
• February 12, 2019—KB4487026 (OS Build 14393.2791)
• January 17, 2019—KB4480977 (OS Build 14393.2759)
• January 8, 2019—KB4480961 (OS Build 14393.2724)
• December 19, 2018—KB4483229 (OS Build 14393.2670)
• December 11, 2018—KB4471321 (OS Build 14393.2665)
• December 3, 2018—KB4478877 (OS Build 14393.2641)
• November 27, 2018—KB4467684 (OS Build 14393.2639)
• November 13, 2018—KB4467691 (OS Build 14393.2608)
• October 18, 2018—KB4462928 (OS Build 14393.2580)
• October 9, 2018—KB4462917 (OS Build 14393.2551)
• September 20, 2018—KB4457127 (OS Build 14393.2515)
• September 11, 2018—KB4457131 (OS Build 14393.2485)
• August 30, 2018—KB4343884 (OS Build 14393.2457)
• August 14, 2018—KB4343887 (OS Build 14393.2430)
• July 30, 2018 - KB4346877 (OS Build 14393.2396)
• July 24, 2018—KB4338822 (OS Build 14393.2395)
• July 16, 2018—KB4345418 (OS Build 14393.2368)
• July 10, 2018—KB4338814 (OS Build 14393.2363)
• June 21, 2018—KB4284833 (OS Build 14393.2339)
• June 12, 2018—KB4284880 (OS Build 14393.2312)
• May 17, 2018—KB4103720 (OS Build 14393.2273)
• May 8, 2018—KB4103723 (OS Build 14393.2248)
• April 17, 2018—KB4093120 (OS Build 14393.2214)
• April 10, 2018—KB4093119 (OS Build 14393.2189)
• March 29, 2018—KB4096309 (OS Build 14393.2156)
• March 22, 2018—KB4088889 (OS Build 14393.2155)
• March 13, 2018—KB4088787 (OS Build 14393.2125 and 14393.2126)
• February 22, 2018—KB4077525 (OS Build 14393.2097)
• February 13, 2018—KB4074590 (OS Build 14393.2068)
• January 17, 2018—KB4057142 (OS Build 14393.2034)
• January 3, 2018—KB4056890 (OS Build 14393.2007)
• December 12, 2017—KB4053579 (OS Build 14393.1944)
• November 27, 2017—KB4051033 (OS Build 14393.1914)
• November 14, 2017—KB4048953 (OS Build 14393.1884)
• November 2, 2017—KB4052231 (OS Build 14393.1797)
• October 17, 2017—KB4041688 (OS Build 14393.1794)
• October 10, 2017—KB4041691 (OS Build 14393.1770)
• September 28, 2017—KB4038801 (OS Build 14393.1737)
• September 12, 2017—KB4038782 (OS Build 14393.1715)
• August 28, 2017—KB4039396 (OS Build 14393.1670)
• August 16, 2017—KB4034661 (OS Build 14393.1613)
• August 8, 2017—KB4034658 (OS Build 14393.1593)
• August 7, 2017—KB4038220 (OS Build 14393.1537)
• July 18, 2017—KB4025334 (OS Build 14393.1532)
• July 11, 2017—KB4025339 (OS Build 14393.1480)
• June 27, 2017—KB4022723 (OS Build 14393.1378)
• June 13, 2017—KB4022715 (OS Build 14393.1358)
• May 26, 2017—KB4023680 (OS Build 14393.1230)
• May 9, 2017—KB4019472 (OS Build 14393.1198)
• April 11, 2017—KB4015217 (OS Build 14393.1066 and 14393.1083)
• March 22, 2017—KB4016635 (OS Build 14393.970)
• March 20, 2017—KB4015438 (OS Build 14393.969)
• March 14, 2017—KB4013429 (OS Build 14393.953)
• January 30, 2017—KB4010672 (OS Build 14393.729)
• January 26, 2017—KB 3216755 (OS Build 14393.726)
• January 10, 2017—KB3213986 (OS Build 14393.693)
• December 13, 2016 — KB3206632 (OS Build 14393.571)
• December 9, 2016 — KB3201845 (OS Build 14393.479)
• November 9, 2016 — KB3200970 (OS Build 14393.448)
• November 8, 2016 — KB3200970 (OS Build 14393.447)
• October 27, 2016 — KB3197954 (OS Build 14393.351)
• October 11, 2016 — KB3194798 (OS Build 14393.321)
• September 29, 2016 — KB3194496 (OS Builds 14393.222)
• September 20, 2016 — KB3193494 (OS Builds 14393.187 and 14393.189)
• September 13, 2016 — KB3189866 (OS Builds 14393.187 and 14393.189)
• August 31, 2016 — KB3176938 (OS Build 14393.105)
• August 23, 2016 — KB3176934 (OS Build 14393.82)
• August 9, 2016 — KB3176495 (OS Build 14393.51)
• August 2, 2016 — KB3176929 (OS Build 14393.10)
• Windows 10, version 1511 update history
• April 10, 2018—KB4093109 (OS Build 10586.1540)
• March 13, 2018—KB4088779 (OS Build 10586.1478)
• February 13, 2018—KB4074591 (OS Build 10586.1417)
• January 18, 2018—KB4075200 (OS Build 10586.1358)
• January 3, 2018—KB4056888 (OS Build 10586.1356)
• December 12, 2017—KB4053578 (OS Build 10586.1295)
• November 14, 2017—KB4048952 (OS Build 10586.1232)
• November 2, 2017—KB4052232 (OS Build 10586.1177)
• October 10, 2017—KB4041689 (OS Build 10586.1176)
• September 12, 2017—KB4038783 (OS Build 10586.1106)
• August 8, 2017—KB4034660 (OS Build 10586.1045)
• July 11, 2017—KB4025344 (OS Build 10586.1007)
• June 27, 2017—KB4032693 (OS Build 10586.965)
• June 13, 2017—KB4022714 (OS Build 10586.962)
• May 9, 2017—KB4019473 (OS Build 10586.916)
• April 11, 2017—KB4015219 (OS Build 10586.873)
• March 22, 2017—KB4016636 (OS Build 10586.842)
• March 14, 2017—KB4013198 (OS Build 10586.839)
• January 10, 2017—KB3210721 (OS Build 10586.753)
• December 13, 2016 — KB3205386 (OS Build 10586.713)
• November 14, 2016 — KB3198586 (OS Build 10586.682)
• November 8, 2016 — KB3198586 (OS Build 10586.679)
• October 11, 2016 — KB3192441 (OS Build 10586.633)
• September 13, 2016 — KB3185614 (OS Build 10586.589)
• August 9, 2016 — KB3176493 (OS Build 10586.545)
• July 12, 2016 — KB3172985 (OS Build 10586.494)
• June 14, 2016 — KB3163018 (OS Build 10586.420)
• May 10, 2016 — KB3156421 (OS Build 10586.318)
• April 12, 2016 — KB3147458 (OS Build 10586.218)
• March 8, 2016 — KB3140768 (OS Build 10586.164)
• March 1, 2016 — KB3140743 (OS Build 10586.122)
• February 9, 2016 — KB3135173 (OS Build 10586.104)
• Windows 10 (initial version released July 2015) update history
• May 14, 2024-KB5037788 (OS Build 10240.20651)
• April 9, 2024-KB5036925 (OS Build 10240.20596)
• March 12, 2024-KB5035858 (OS Build 10240.20526)
• February 13, 2024-KB5034774 (OS Build 10240.20469)
• January 9, 2024-KB5034134 (OS Build 10240.20402)
• December 12, 2023-KB5033379 (OS Build 10240.20345)
• November 14, 2023-KB5032199 (OS Build 10240.20308)
• October 10, 2023-KB5031377 (OS Build 10240.20232)
• September 12, 2023-KB5030220 (OS Build 10240.20162)
• August 8, 2023-KB5029259 (OS Build 10240.20107)
• July 11, 2023-KB5028186 (OS Build 10240.20048)
• June 23, 2023-KB5028622 (OS Build 10240.19986) Out-of-band
• June 13, 2023-KB5027230 (OS Build 10240.19983)
• May 9, 2023-KB5026382 (OS Build 10240.19926)
• April 11, 2023-KB5025234 (OS Build 10240.19869)
• March 14, 2023-KB5023713 (OS Build 10240.19805)
• February 14, 2023-KB5022858 (OS Build 10240.19747)
• January 10, 2023-KB5022297 (OS Build 10240.19685)
• December 13, 2022-KB5021243 (OS Build 10240.19624)
• November 8, 2022-KB5019970 (OS Build 10240.19567)
• October 18, 2022-KB5020440 (OS Build 10240.19509) Out-of-band
• October 11, 2022-KB5018425 (OS Build 10240.19507)
• September 13, 2022-KB5017327 (OS Build 10240.19444)
• August 9, 2022-KB5016639 (OS Build 10240.19387) - EXPIRED
• July 12, 2022-KB5015832 (OS Build 10240.19360)
• June 14, 2022-KB5014710 (OS Build 10240.19325) - EXPIRED
• May 10, 2022-KB5013963 (OS Build 10240.19297) - EXPIRED
• April 12, 2022-KB5012653 (OS Build 10240.19265) - EXPIRED
• March 8, 2022-KB5011491 (OS Build 10240.19235) - EXPIRED
• February 8, 2022-KB5010358 (OS Build 10240.19204) - EXPIRED
• January 17, 2022-KB5010789 (OS Build 10240.19179) Out-of-band
• January 11, 2022-KB5009585 (OS Build 10240.19177) - EXPIRED
• December 14, 2021-KB5008230 (OS Build 10240.19145) - EXPIRED
• November 9, 2021-KB5007207 (OS Build 10240.19119) - EXPIRED
• October 12, 2021-KB5006675 (OS Build 10240.19086) - EXPIRED
• September 14, 2021-KB5005569 (OS Build 10240.19060) - EXPIRED
• August 10, 2021-KB5005040 (OS Build 10240.19022) - EXPIRED
• July 13, 2021-KB5004249 (OS Build 10240.19003) - EXPIRED
• July 6, 2021—KB5004950 (OS Build 10240.18969) Out-of-band - EXPIRED
• June 8, 2021-KB5003687 (OS Build 10240.18967) - EXPIRED
• May 11, 2021-KB5003172 (OS Build 10240.18932) - EXPIRED
• April 13, 2021-KB5001340 (OS Build 10240.18906)
• March 18, 2021-KB5001631 (OS Build 10240.18875) Out-of-band
• March 9, 2021-KB5000807 (OS Build 10240.18874)
• February 9, 2021-KB4601331 (OS Build 10240.18842)
• January 12, 2021-KB4598231 (OS Build 10240.18818)
• December 8, 2020-KB4592464 (OS Build 10240.18782)
• November 10, 2020-KB4586787 (OS Build 10240.18756)
• October 13, 2020-KB4580327 (OS Build 10240.18725)
• September 8, 2020-KB4577049 (OS Build 10240.18696)
• August 11, 2020-KB4571692 (OS Build 10240.18666)
• July 14, 2020-KB4565513 (OS Build 10240.18638)
• June 18, 2020-KB4567518 (OS Build 10240.18609)
• June 9, 2020-KB4561649 (OS Build 10240.18608)
• May 12, 2020-KB4556826 (OS Build 10240.18575)
• April 14, 2020-KB4550930 (OS Build 10240.18545)
• March 10, 2020-KB4540693 (OS Build 10240.18519)
• February 11, 2020-KB4537776 (OS Build 10240.18486)
• January 14, 2020-KB4534306 (OS Build 10240.18453)
• December 10, 2019-KB4530681 (OS Build 10240.18427)
• November 12, 2019-KB4525232 (OS Build 10240.18395)
• October 8, 2019-KB4520011 (OS Build 10240.18368)
• October 3, 2019-KB4524153 (OS Build 10240.18335)
• September 23, 2019-KB4522009 (OS Build 10240.18334)
• September 10, 2019-KB4516070 (OS Build 10240.18333)
• August 17, 2019-KB4517276 (OS Build 10240.18308)
• August 13, 2019-KB4512497 (OS Build 10240.18305)
• July 9, 2019-KB4507458 (OS Build 10240.18275)
• June 11, 2019-KB4503291 (OS Build 10240.18244)
• May 19, 2019-KB4505051 (OS Build 10240.18218)
• May 14, 2019-KB4499154 (OS Build 10240.18215)
• April 25, 2019-KB4498375 (OS Build 10240.18187)
• April 9, 2019-KB4493475 (OS Build 10240.18186)
• March 12, 2019-KB4489872 (OS Build 10240.18158)
• February 21, 2019-KB4491101 (OS Build 10240.18135)
• February 12, 2019-KB4487018 (OS Build 10240.18132)
• January 8, 2019-KB4480962 (OS Build 10240.18094)
• December 19, 2018-KB4483228 (OS Build 10240.18064)
• December 11, 2018-KB4471323 (OS Build 10240.18063)
• November 13, 2018-KB4467680 (OS Build 10240.18036)
• October 9, 2018-KB4462922 (OS Build 10240.18005)
• September 11, 2018-KB4457132 (OS Build 10240.17976)
• August 14, 2018—KB4343892 (OS Build 10240.17946)
• July 16, 2018—KB4345455 (OS Build 10240.17918)
• July 10, 2018—KB4338829 (OS Build 10240.17914)
• June 12, 2018—KB4284860 (OS Build 10240.17889)
• May 8, 2018—KB4103716 (OS Build 10240.17861)
• April 10, 2018—KB4093111 (OS Build 10240.17831)
• March 13, 2018—KB4088786 (OS Build 10240.17797)
• February 13, 2018—KB4074596 (OS Build 10240.17770)
• January 31, 2018—KB4077735 (OS Build 10240.17741)
• January 18, 2018—KB4075199 (OS Build 10240.17741)
• January 3, 2018—KB4056893 (OS Build 10240.17738)
• December 12, 2017—KB4053581 (OS Build 10240.17709)
• November 14, 2017—KB4048956 (OS Build 10240.17673)
• October 10, 2017—KB4042895 (OS Build 10240.17643)
• September 12, 2017—KB4038781 (OS Build 10240.17609)
• August 8, 2017—KB4034668 (OS Build 10240.17533)
• July 11, 2017—KB4025338 (OS Build 10240.17488)
• June 27, 2017—KB4032695 (OS Build 10240.17446)
• June 13, 2017—KB4022727 (OS Build 10240.17443)
• May 9, 2017—KB4019474 (OS Build 10240.17394)
• April 11, 2017—KB4015221 (OS Build 10240.17354)
• March 22, 2017—KB4016637 (OS Build 10240.17320)
• March 14, 2017—KB4012606 (OS Build 10240.17319)
• January 10, 2017—KB3210720 (OS Build 10240.17236)
• December 13, 2016 — KB3205383 (OS Build 10240.17202)
• November 8, 2016 — KB3198585 (OS Build 10240.17190)
• October 11, 2016 — KB3192440 (OS Build 10240.17146)
• September 20, 2016 — KB3193821 (OS Build 10240.17113)
• September 13, 2016 — KB3185611 (OS Build 10240.17113)
• August 9, 2016 — KB3176492 (OS Build 10240.17071)
• July 12, 2016 — KB3163912 (OS Build 10240.17024)
• June 14, 2016 — KB3163017 (OS Build 10240.16942)
• May 10, 2016 — KB3156387 (OS Build 10240.16854)
• April 12, 2016 — KB3147461 (OS Build 10240.16769)
• March 8, 2016 — KB3140745 (OS Build 10240.16725)
• February 9, 2016 — KB3135174 (OS Build 10240.16683)

Release Date:

OS Build 17763.5820

11/17/20 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 1809, see its  update history page .  

Highlights 

This update addresses an issue in that affects IE mode. It stops responding. This occurs if you press the left arrow key when an empty text box has focus and caret browsing is on.

This update addresses a known issue that might cause your VPN connection to fail. This occurs after you install the update dated April 9, 2024, or later.

Improvements

This security update includes improvements. When you install this KB: 

This update affects next secure record 3 (NSEC3) validation in a recursive resolver. Its limit is now 1,000 computations. One computation is equal to the validation of one label with one iteration. DNS Server Administrators can change the default number of computations. To do this, use the registry setting below.

Name: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\MaxComputationForNsec3Validation

Type: DWORD

Default: 1000

This update includes quarterly changes to the Windows Kernel Vulnerable Driver Blocklist file, DriverSiPolicy.p7b . It adds to the list of drivers that are at risk for Bring Your Own Vulnerable Driver (BYOVD) attacks.

This update addresses an issue that affects Active Directory. Bind requests to IPv6 addresses fail. This occurs when the requestor is not joined to a domain. 

This update addresses a known issue that might affect domain controllers (DC). NTLM authentication traffic might increase.

This update addresses an issue that might affect Virtual Secure Mode (VSM) scenarios. They might fail. These scenarios include VPN, Windows Hello, Credential Guard, and Key Guard.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

For more information about security vulnerabilities, please refer to the new Security Update Guide website and the May 2024 Security Updates .

Windows 10 servicing stack update - 17763.5695

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. 

Known issues in this update

How to get this update.

Before installing this update

Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For general information about SSUs, see Servicing stack updates  and  Servicing Stack Updates (SSU): Frequently Asked Questions . 

Prerequisite:

You  must  install the August 10, 2021 SSU ( KB5005112 ) before installing the LCU. 

Install this update

If you want to remove the LCU

To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages .

Running Windows Update Standalone Installer ( wusa.exe ) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File information

For a list of the files that are provided in this update, download the  file information for cumulative update 5037765 .

For a list of the files that are provided in the servicing stack update, download the  file information for the SSU - version 17763.5695.  

Need more help?

Want more options.

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders

Was this information helpful?

Thank you for your feedback.

litigation management services

Depositions, videography & video conferencing..

The reporters and staff at T&T Reporting are so excited to announce an expansion of our service area with the addition of a full-time reporter in Pocatello, Idaho, and the acquisition of Jackson Hole Court Reporting Services in Jackson, Wyoming. In doing so, allow us to (re)introduce ourselves:

With our reporters’ locations – and our ever-expanding network – we are happy to provide statewide in-person and/or remote coverage for the entire state of Idaho and Wyoming .  We are also pleased to be able to provide coverage for the states of Utah and Montana .

We work with YOUR timeline. Our standard transcript turnaround time is 8-10 business days. If you need a product sooner than that, let us know and we will make it happen.

We are proud to state that we are the most competitively-priced court reporting firm in the area.  With the increasing regularity of remote depositions, rest assured that we NEVER charge extra to host a remote meeting.

Reporter Services

Our team of certified court reporters are happy to provide services that include:

Same-day Drafts (Roughs)

Realtime services, hyperlinked exhibits, remote depositions, audio and video transcription, videography.

Our in-house videographers have the knowledge and experience to provide you with the best services including:

Remote Videography

Video synchronization, capture evidence.

Additional Services

In addition to our court reporting and videography services, our team also provides the following:

interpretation

Process serving, conference room rental, network companies.

Do you represent an insurance company or surety that requires scheduling through a national networking company?  No problem.  We are on all of the preferred lists.  Give us a call and let us know of your upcoming proceeding and we will communicate with the company to make sure you are covered.

Service Region

Service areas.

• Idaho Falls
• Soda Springs
• Green River
• Rock Springs

R&D Calculator

Calculate your benefit..

Fill out the Momentus R&D Tax Credit Calculator to find out how much your business could be eligible to receive in Tax Credits.

Tax Credit Calculator

• Global (EN)
• Albania (en)
• Algeria (fr)
• Argentina (es)
• Armenia (en)
• Australia (en)
• Austria (de)
• Austria (en)
• Azerbaijan (en)
• Bahamas (en)
• Bahrain (en)
• Bangladesh (en)
• Barbados (en)
• Belgium (en)
• Belgium (nl)
• Bermuda (en)
• Bosnia and Herzegovina (en)
• Brasil (pt)
• Brazil (en)
• British Virgin Islands (en)
• Bulgaria (en)
• Cambodia (en)
• Cameroon (fr)
• Canada (en)
• Canada (fr)
• Cayman Islands (en)
• Channel Islands (en)
• Colombia (es)
• Costa Rica (es)
• Croatia (en)
• Cyprus (en)
• Czech Republic (cs)
• Czech Republic (en)
• DR Congo (fr)
• Denmark (da)
• Denmark (en)
• Ecuador (es)
• Estonia (en)
• Estonia (et)
• Finland (fi)
• France (fr)
• Georgia (en)
• Germany (de)
• Germany (en)
• Gibraltar (en)
• Greece (el)
• Greece (en)
• Hong Kong SAR (en)
• Hungary (en)
• Hungary (hu)
• Iceland (is)
• Indonesia (en)
• Ireland (en)
• Isle of Man (en)
• Israel (en)
• Ivory Coast (fr)
• Jamaica (en)
• Jordan (en)
• Kazakhstan (en)
• Kazakhstan (kk)
• Kazakhstan (ru)
• Kuwait (en)
• Latvia (en)
• Latvia (lv)
• Lebanon (en)
• Lithuania (en)
• Lithuania (lt)
• Luxembourg (en)
• Macau SAR (en)
• Malaysia (en)
• Mauritius (en)
• Mexico (es)
• Moldova (en)
• Monaco (en)
• Monaco (fr)
• Mongolia (en)
• Montenegro (en)
• Mozambique (en)
• Myanmar (en)
• Namibia (en)
• Netherlands (en)
• Netherlands (nl)
• New Zealand (en)
• Nigeria (en)
• North Macedonia (en)
• Norway (nb)
• Pakistan (en)
• Panama (es)
• Philippines (en)
• Poland (en)
• Poland (pl)
• Portugal (en)
• Portugal (pt)
• Romania (en)
• Romania (ro)
• Saudi Arabia (en)
• Serbia (en)
• Singapore (en)
• Slovakia (en)
• Slovakia (sk)
• Slovenia (en)
• South Africa (en)
• Sri Lanka (en)
• Sweden (sv)
• Switzerland (de)
• Switzerland (en)
• Switzerland (fr)
• Taiwan (en)
• Taiwan (zh)
• Thailand (en)
• Trinidad and Tobago (en)
• Tunisia (en)
• Tunisia (fr)
• Turkey (en)
• Turkey (tr)
• Ukraine (en)
• Ukraine (ru)
• Ukraine (uk)
• United Arab Emirates (en)
• United Kingdom (en)
• United States (en)
• Uruguay (es)
• Uzbekistan (en)
• Uzbekistan (ru)
• Venezuela (es)
• Vietnam (en)
• Vietnam (vi)
• Zambia (en)
• Zimbabwe (en)
• Financial Reporting View
• Women's Leadership
• Corporate Finance
• Board Leadership
• Executive Education

Fresh thinking and actionable insights that address critical issues your organization faces.

• Insights by Industry
• Insights by Topic

KPMG's multi-disciplinary approach and deep, practical industry knowledge help clients meet challenges and respond to opportunities.

• Advisory Services
• Audit Services
• Tax Services

Services to meet your business goals

Technology Alliances

KPMG has market-leading alliances with many of the world's leading software and services vendors.

Helping clients meet their business challenges begins with an in-depth understanding of the industries in which they work. That’s why KPMG LLP established its industry-driven structure. In fact, KPMG LLP was the first of the Big Four firms to organize itself along the same industry lines as clients.

• Our Industries

How We Work

We bring together passionate problem-solvers, innovative technologies, and full-service capabilities to create opportunity with every insight.

• What sets us apart

Careers & Culture

What is culture? Culture is how we do things around here. It is the combination of a predominant mindset, actions (both big and small) that we all commit to every day, and the underlying processes, programs and systems supporting how work gets done.

Relevant Results

Sorry, there are no results matching your search..

• KPMG Corporate Communications
• Multimedia Resources
• News about KPMG

Navigating The AI Era In Financial Reporting

Opportunities, Risks, and Investments Trends to Enhance Trust through Technology 

• In the next three years, 100% of U.S. financial reporting leaders report they will be either piloting or using AI in financial reporting, up from 71% today.
• As for generative AI, 97% will be either piloting or using the technology in financial reporting in three years, up from 46% today. In fact, GenAI is the most prioritized technology among U.S. financial reporting leaders in the coming year.
• Survey finds the top five benefits of AI in financial reporting are real-time insights into risks, fraud, and control weaknesses (70%); lower costs (58%), ability to predict trends and impacts (57%), increased data accuracy and reliability (57%), and better data-enabled decisions (53%).
• In 2023, 61% of financial reporting leaders said that it was important for auditors to utilize AI in performing their analyses; today that number is 83%. Businesses expect their auditors to conduct a more detailed review of the control environment (66%) and assess their AI governance maturity (61%).

New York, May 8, 2024 – All U.S. financial reporting leaders surveyed report they expect to be piloting or using artificial intelligence (“AI”) in financial reporting within three years, and 97% expect to be doing the same with generative AI (“GenAI”), according to a new survey released today by KPMG LLP, the U.S. audit, tax, and advisory firm.

This new survey finds U.S. businesses will continue to invest more of their IT budget in AI-related activities, with GenAI being the top priority next year. Meanwhile, financial reporting leaders are focused on navigating risks by becoming AI ready and expect their external auditor to not only use AI and GenAI in the audit, but also use professional judgement to evaluate control environments. This includes conducting third-party attestation over companies' use of AI as well as providing insights on a company’s AI governance maturity.

“It’s clear that financial reporting leaders are rapidly accelerating investments to use AI and GenAI to not just gain efficiencies but create more value for their organizations by predicting trends and identifying emerging risks," said Scott Flynn, KPMG U.S. Vice Chair - Audit . “Understanding the range of complementary investments in cloud, data, and governance is critical for both financial reporting leaders and external auditors to mitigate risks from this rapid transformation.”

The findings come from KPMG’s latest survey, published in the report AI in Financial Reporting and Audit: Navigating the New Era . The survey was conducted among 1,800 companies across ten major markets. Key perspectives and findings from 300 U.S. respondents are highlighted below. They expand upon the findings from the October 2023 U.S. survey, AI’s Role in Enhancing Trust in Financial Reporting and the Capital Markets . 

Key takeaways from the survey are highlighted below.

The use of ai and genai in financial reporting will be ubiquitous in the coming years..

FLYNN : “The potential benefits of AI are driving every conversation with financial reporting leaders. In the next year or two, the fear of missing out on AI will be replaced with just missing out.”

• As for GenAI, 97% of financial reporting leaders will be either piloting or using GenAI in financial reporting in the next three years, up from 46% today.
• In the previous survey, 18% of leaders said they do not use AI in financial reporting with 10% specifying no specific time for rolling out AI solutions.
• Additionally, in the survey from last year, 10% said they were “not using or considering” GenAI in financial reporting.

GenAI is the #1 technology priority for financial reporting leaders in the coming years, with companies focusing on complementary technologies today.

FLYNN : “The depth of AI and GenAI’s capabilities certainly surprised many, and it’s clear companies are focusing on investing in the technologies that will better enable the use of AI, such as cloud, data, and ERP.”

• 19% of U.S. financial reporting leaders are going beyond planning and piloting, and using AI this year, behind cloud technology (77%), data and analytics (55%), and Enterprise Resource Planning (54%).
• Next year, however, U.S. financial reporting leaders will be prioritizing GenAI (58%) the most among all technologies, followed by process mining technology (45%).

U.S. companies are investing more of their IT budgets on AI-related activities than other countries, on average, and those investments are expected to rise in the coming years.

“The benefits of AI compound as companies organize their data, move to the cloud, and integrate AI across processes. In that context, how companies invest over the next few years will shape competitive positioning and the role of finance functions in business strategy,” said Thomas Mackenzie,   KPMG U.S. and Global Audit Chief Technology Officer .

• On average, U.S. companies are spending 10.1% of their IT budgets on AI-related activities today, compared with 9.9% across all countries studied. U.S. companies intend to boost their overall AI budgets by 16.9% next year, and by 24.6% over the next three years.
• Some are moving faster: 30% plan to ramp up their AI budgets by between 25% and 74% over the next three years. 

Relative to all companies, AI Leaders [1] are investing more in AI-enabling technologies and processes, taking more action to mitigate risk, and – most importantly – reporting more benefits.

FLYNN : “In the era of compound volatility , companies are navigating a multitude of risks, but the value that AI can deliver financial reporting teams demands prioritization.”

• AI Leaders in the U.S. spend nearly 12% of IT budgets on AI-related activities today and expect to increase that investment 25% next year and nearly 28% in the next three years.
• Boards of Directors for AI Leaders are more likely to have established mechanisms to monitor and/or measure AI impacts (71% of AI Leaders vs. 45% of other U.S. companies), met with management to understand AI activities and plans (61% vs. 48%), and set up policies and governance aligned with ESG (Environmental, Social, Governance) goals (79% vs. 69%).
• AI Leaders are also more likely to have developed principles for using AI, ensured tech leadership is involved in systems integration discussions, piloted AI initiatives to validate ROI (Return on Investment), and more.
• AI Leaders are more AI-ready from a technology perspective due to greater progress on implementing key enabling technologies and processes. These include cloud migration (94% of AI Leaders are at mid or full implementation vs. 72% of other U.S. companies), standardization of workflows (89% vs. 70%), establishment of common data basis or single source of truth (84% vs. 70%), and standardization of system landscape (60% vs. 48%).
• Most importantly, compared to those just beginning to use AI, Al Leaders are far more likely to report a host of benefits from AI-enabled reporting, including enhanced staff skills due to AI assistants (42% of Leaders vs. 30% of Beginners), ability to predict trends and impacts (62% vs. 51%), and greater ability to identify data outliers and anomalies (31% vs. 21%).

The landscape is evolving as companies seek to overcome barriers, mitigate risks, and realize benefits from an AI-enabled financial reporting process.

FLYNN: "As companies engage more with AI and GenAI in financial reporting processes, new barriers and challenges are driving critical thinking on risk mitigation strategies. Education is paramount, but a more holistic approach to responsible AI use is critical to building and preserving trust.”

• Across all U.S. companies, top benefits expected in three years include real-time insights into risks, fraud, control weaknesses (73%), increased data accuracy and reliability (67%), and lower costs (62%). In addition, 60% expect greater ability to predict trends and impacts.
• Despite industry concerns that AI will disrupt the workforce, some believe it will act as a magnet for talent and innovation. 34% expect AI to attract talent, while 26% believe AI will help fill staff shortages. 37% believe AI assistants will enhance staff skills.
• Thirty-one percent of financial reporting leaders indicated ethical concerns, such as bias or misinformation is a barrier to adoption, down from 48% last year.
• Keeping up with regulatory changes has also fallen to 41% from 49%.
• Risks from using algorithms without human oversight fell from nearly half to 35%.
• Meanwhile, 56% of respondents identified data security and privacy concerns as the biggest barriers to companies’ adoption of AI, compared to just 32% of respondents last year. Other barriers include limited skills and talent (46%), difficulty gathering relevant and consistent data (44%), and inadequate funding and investment levels (43%).
• U.S. financial reporting leaders noted the most effective practices for mitigating GenAI risks include regular audits and monitoring (50%), education and training (50%), ethical frameworks (47%), and human oversight (42%). Other important actions include collaboration and regulation adherence, third-party reviews, privacy measures, and disclosures. 

Today, financial reporting leaders expect auditors to use AI in their audit approach and evaluate companies’ use of AI within financial reporting.

FLYNN: “AI is fundamentally transforming the audit. We expect to deliver more real-time auditing with greater insights into anomalies and trends supported by deep evaluation of the control environment governing the use of AI in financial reporting.”

• In 2023, 61% of financial reporting leaders said that it was important for auditors to utilize AI in performing their analysis; today that number is 83%.
• Last year, 47% said they thought that GenAI would become a common practice among auditors in one to two years, and 46% foresaw it happening in three to five years. Now, 73% of financial reporting leaders expect the use of GenAI to become the norm over the next two years, and 23% believe it will happen in two to three years.
• Top areas that auditors should prioritize include risk/anomaly identification (65%), data analysis and quality management (65%), risk mitigation and internal controls (62%), and fraud detection (58%).
• Financial reporting leaders’ expectations of auditors in the future are highest in two areas: 66% expect their auditors will conduct a more detailed review of the control environment (slightly up from 64% last year), and 61% expect them to assess their AI governance maturity (considerably up from 53% last year).
• In addition, 33% expect their external auditor to provide third-party attestation over the use of AI technology. 

[1]  Leaders are defined as companies in the top 25 th percentile for AI readiness, based on responses to survey questions around AI adoption and governance in financial reporting. Beginners are in the bottom 25 th percentile.

About KPMG LLP

KPMG LLP is the U.S. firm of the KPMG global organization of independent professional services firms providing audit, tax and advisory services. The KPMG global organization operates in 143 countries and territories and has more than 273,000 people working in member firms around the world. Each KPMG firm is a legally distinct and separate entity and describes itself as such. KPMG International Limited is a private English company limited by guarantee. KPMG International Limited and its related entities do not provide services to clients.

KPMG is widely recognized for being a great place to work and build a career. Our people share a sense of purpose in the work we do, and a strong commitment to community service, inclusion and diversity and eradicating childhood illiteracy. Learn more at www.kpmg.com/us .

Additional Resources

Hannah Gould

Sr Assoc Corporate Communications

Explore more

AI's Role in Enhancing Trust in Financial Reporting & Capital Markets

AI is set to revolutionize financial reporting and audit, with many financial reporting functions adopting AI and generative AI.

The 2024 KPMG U.S. CEO Outlook Pulse Survey

CEOs are tackling risks to growth including geopolitics, cyber and structural changes such as tight labor market and new regulations, according to KPMG's latest survey.

KPMG Announces Google Cloud Center of Excellence to Advance Responsible Adoption of Generative AI

KPMG will bring Google Cloud technology to its workforce and build trusted GenAI solutions that accelerate business transformation for clients

Thank you for contacting KPMG. We will respond to you as soon as possible.

Contact KPMG

By submitting, you agree that KPMG LLP may process any personal information you provide pursuant to KPMG LLP's Privacy Statement .

Job seekers

Visit our careers section or search our jobs database.

Use the RFP submission form to detail the services KPMG can help assist you with.

Office locations

International hotline

You can confidentially report concerns to the KPMG International hotline

Press contacts

Do you need to speak with our Press Office? Here's how to get in touch.

International Students & Scholars

Apply for/renew your visa.

After receipt of your immigration documentation from UMD, and payment of the required SEVIS fee (F1/J1 only) , you can apply for your visa. An in-person interview is usually required. You should schedule your appointment as soon as possible. Some U.S. Embassies may have wait times for visa interviews and delays in visa processing.

To make your appointment and check wait times, visit the U.S. Visas - Department of State .

Note: You may not receive a U.S. visa more than 120 days before the reporting date on your I-20/DS-2019.

Attend the visa appointment and bring the application required documents listed below with you.

General Visa Application Required Documents

• U.S. Government Application form DS-160
• Payment of the U.S. Government Visa Application Fee
• U.S. passport-style photos for each visa applicant
• Passport(s) valid for at least 6 months into the future for each visa applicant 

Additional Requirements by Visa Category

• Dependent Visas
• Signed original I-20 or DS-2019 Form
• SEVIS Fee Receipt
• Proof of ties to your home country: F and J visas are non-immigrant visas. As such, you will need to show that you plan to return after your studies. You can do this by showing strong ties to your home country with evidence such as proof of property ownership, a job offer letter, or letters from family.
• Proof of financial support : You will need to present the financial documents you submitted for your I-20/DS-2019 checklist.
• Newly Admitted Student (F-1/J-1) – Admission Letter
• Any standardized test scores  you submitted to UMD
• Current Student (F-1/J-1) – Official Transcript and the Confirmation of visa status letter from iTerp
• Professors, research scholars, short-term scholars and interns (J-1) - Invitation letter from your sponsoring department
• OPT/STEM OPT (F-1) – Current OPT EAD Card and offer letter or proof of employment. If your STEM OPT application is still pending, ISSS does not recommend traveling abroad.
• Post-Completion Academic Training (J-1) – Offer letter or proof of employment

Note: Citizens of Canada and Bermuda do not require visas to enter the United States as students. However, you must pay the SEVIS fee and present a valid Form I-20 at the time of admission. For more information see U.S. Department of State information for Citizens of Canada and Bermuda

Original bottom portion and a copy of the original I-797 H-1B Approval Notice and travel packet.   Appointment letter or job offer letter on university letterhead stating:

• Your position title and salary
• Academic Department
• Dates of Employment
• Brief job description  

Note: individuals in H-1B status are viewed as having a dual intent when entering the U.S. Dual intent means that the H-1B holder may intend either to return home at the end of the H-1B program or to apply for immigrant status.

• Original certified and signed Labor Condition Application
• Proof of payment of the visa fee.

Important: A person in initial E-3 status can enter the U.S. up to 10 days before the E-3 start date

Mexican Citizens do need to apply for a visa using their original and signed TN letter provided by the department, or they may present the original bottom portion and a copy of the original I-797 TN Approval Notice.

Canadian Citizens do not need to apply for a visa. You can enter the U.S. using your original and signed TN letter provided by the department.  

Important: A person in initial TN status can enter the U.S. up to 10 days before the TN start date.

Immediate family members (spouse and unmarried children under the age of 21) who will come with you to the U.S. may apply for dependent visas. You need to bring documents that prove your relationship. These can include a marriage certificate, birth certificate, or official family registry.

If your dependents go to the visa interview alone, they will need to bring copies of all the documents listed above for your visa category.  

If all goes according to plan, you will receive a visa stamp in your passport. Congratulations! Check your visa for errors before you leave the U.S. Embassy or Consulate.

You may not enter the U.S. on your F-1 or J-1 visa more than 30 days prior to the report date on your I-20/DS-2019. Keep in mind the visa itself does not guarantee admission into the U.S.; all other documents must be in order as well . 

Individuals entering the U.S. in H-1B/O-1/E-3/TN status may enter the U.S. no more than 10 days before their start date.

Please contact ISSS if you received a late visa appointment and will not be able to enter the U.S. by the report date on your I-20/DS-2019, or if your visa application has been denied.

Note: For J-1 visa holders, the U.S. Embassies may put your DS-2019 in a sealed envelope and staple it to your passport. We recommended that you do not open this envelope. The Immigration officer at the U.S. port-of-entry will open it and check your documents when you arrive.   

If you have difficulty scheduling your visa appointment due to an unforeseen situation, such as a funeral or medical emergency, you may request an Expedited Visa Interview . Check the instructions posted on your U.S. Embassy website to schedule visa interviews. You will have to provide proof of your need for an early appointment.

Your I-20/DS2019 start date provides the necessary information you need to demonstrate your start date at UMD. Feel free to use our visa expedition letter if you feel it will assist your immigration case.

• Administrative Processing    The U.S. Embassy may inform you your visa requires Administrative Processing. This means the consular officer needs more information before deciding to issue you a visa. Administrative processing can result in significant delays in visa issuance. Contact us and your UMD department if you will be unable to arrive for the start of your program.    
• Visa Denial    Contact us if your visa application has been denied

You only need the visa stamp in your passport to enter into the United States. Once you are in the U.S. the visa stamp may expire as long as you have:

• A passport that is valid for at least six months into the future
• An unexpired I-20 (for F-1s) or DS-2019 (for J-1s)
• An I-94 that indicates D/S (F-1 and J-1 only) or a date into the future
• A valid I-797 Approval Notice or valid I-94 for H-1B, O-1, E-3 or TN

If you leave the country, you will need to apply for a new visa before returning to the United States.

Arrival to U.S. - U.S. Customs and I-94

Arriving on Campus

This website uses cookies to measure traffic and improve your experience. View our Privacy Policy to learn more.

Content Search

Mali + 2 more

UNICEF Mali Humanitarian Situation Report No. 03: Reporting Period March 2024

Attachments.

• During the reporting period, the humanitarian and security situation continues to deteriorate in the northern regions of Mali, with a sharp rise in violence against civilians across the country and increasing difficulties to access basic social services.
• According to the recently published March 2024 Cadre Harmonise, the below average food availability among the worst affected population is expected to push some areas into catastrophe (IPC Phase 5) during the upcoming lean season. The Menaka region is already in a state of severe food insecurity, from March to May 2024, 850 people will be in famine-like conditions, while 2,575 people are expected to be in such a situation during the 2024 lean season.
• UNICEF is appealing for US$133.5 million in 2024 to sustain and scale lifesaving and resilience services for 3.8 million of the most vulnerable children. As of the end of March, the UNICEF HAC is 7 per cent funded.

Related Content

Unicef mali humanitarian situation report no. 02: reporting period february 2024.

Mali + 4 more

UNICEF Mali Humanitarian Situation Report No. 01: Reporting Period January 2024

Unicef mali humanitarian situation report no. 12 -- end-of-year 2023, unicef mali humanitarian situation report, 31 december 2019.

Microsoft SQL Server 2022 Reporting Services

SQL Server Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality.

Important! Selecting a language below will dynamically change the complete page content to that language.

16.0.1115.92

Date Published:

SQLServerReportingServices.exe

• Paginated reports optimized for document generation and printing.
• A modern web portal you can view in any modern web browser.

System Requirements

Supported Operating Systems

Windows Server 2019, Windows Server 2016, Windows 10, Windows 11, Windows Server 2022

• .NET Framework 4.8 or later
• SQL Server Database Engine (2014 SP3 or later), to store the report server database
• Download the Evaluation Edition of Microsoft SQL Server

Install Instructions

• Install SQL Server Reporting Services (SQLServerReportingServices.exe)
• Configure your report server using Report Server Configuration Manager

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Upgrade and Migrate Reporting Services

• 11 contributors

This topic is an overview of the upgrade and migration options for SQL Server Reporting Services. Here are the general approaches to upgrading a SQL Server Reporting Services deployment:

Upgrade to Reporting Services 2016 and older from Reporting Services 2016 and older: You upgrade the Reporting Services components on the servers and instances where they are currently installed. This is commonly called an "in place" upgrade. In-place upgrade is not supported from one mode of Reporting Services server to another. For example, you cannot upgrade a Native Mode report server to a SharePoint mode report server. You can migrate your report items from one mode to another. For more information, see the SharePoint mode upgrade and migration scenarios section later in this document.

Upgrade to Reporting Services 2017 and later from Reporting Services 2016 and older isn't the same upgrade scenario as in previous versions. When upgrading to Reporting Services 2016 and older versions, you could following an in-place upgrade process using SQL Server installation media. When upgrading to Reporting Services 2017 and later from Reporting Services 2016 and older, you can't follow the same steps because the new Reporting Services installation is a standalone product. It's no longer part of the SQL Server installation media.

To upgrade from Reporting Services 2016 and older versions to Reporting Services 2017 and later, follow the Migrate a Reporting Services Installation (Native Mode) article, with Reporting Services 2017 or later as your destination instance.

Upgrade from Reporting Services 2017 to future versions is again an in-place upgrade scenario, because the product installation GUIDs are the same. Run the SQLServerReportingServices.exe installation file to begin the in-place upgrade on the server where Reporting Services is currently installed.

Migrate : You install and configure a new SharePoint environment, copy your report items and resources to the new environment, and configure the new environment to use existing content. A lower level form of migration is to copy the Reporting Services databases, configuration files, and if you are using SharePoint mode, the SharePoint content databases.

Reporting Services integration with SharePoint isn't available after SQL Server 2016.

Known Upgrade Issues and Best Practices

For a detailed list of the supported editions and versions you can upgrade, see Supported Version and Edition Upgrades .

For the latest information regarding issues with SQL Server, see SQL Server 2016 Release Notes .

Side By Side Installations

SQL Server Reporting Services Native mode can be installed side-by-side with a SQL Server 2012 (11.x) or SQL Server 2014 (12.x) Native mode deployment.

There is no support for side-by-side deployments of SQL Server Reporting Services in SharePoint mode and any previous versions of Reporting Services SharePoint mode components.

In-place Upgrade

Upgrade is completed by SQL Server Setup. SQL Server Setup can be used to upgrade any or all SQL Server components, including Reporting Services. Setup detects the existing instances and prompts you to upgrade. SQL Server Setup provides upgrade options that you can specify as a command-line argument or in the Setup wizard.

When you run SQL Server Setup, you can select the option to upgrade from one of the following versions or you can install a new instance of SQL Server Reporting Services that runs side-by-side existing installations:

SQL Server 2014 (12.x)

SQL Server 2012 (11.x)

SQL Server 2008 R2 (10.50.x)

SQL Server 2008 (10.0.x)

For more information on SQL Server, see the following:

• Upgrade to SQL Server 2016
• Upgrade to SQL Server 2016 Using the Installation Wizard (Setup)
• Install SQL Server 2016 from the Command Prompt

Pre-Upgrade Checklist

Before upgrading to SQL Server Reporting Services, review the following:

Review requirements to determine whether your hardware and software can support SQL Server 2016 (13.x) Reporting Services or later (SSRS). For more information, see Hardware and Software Requirements for Installing SQL Server 2016 .

Use System Configuration Checker (SCC) to scan the report server computer for any conditions that might prevent a successful installation of SQL Server Reporting Services. For more information, see Check Parameters for the System Configuration Checker .

Review security best practices and guidance for SQL Server. For more information, see Security Considerations for a SQL Server Installation .

Back up your symmetric key. For more information, see Back Up and Restore Reporting Services Encryption Keys .

Back up your report server databases and configuration files. For more information, see Backup and Restore Operations for Reporting Services .

Back up any customizations to existing Reporting Services virtual directories in IIS.

Remove invalid TLS/SSL certificates. This includes certificates that are expired and you do not plan to update prior to upgrading Reporting Services. Invalid certificates will cause upgrade to fail and an error message similar to the following will be written to the Reporting Services Log file: Microsoft.ReportingServices.WmiProvider.WMIProviderException: A Secure Sockets Layer (SSL) certificate is not configured on the Web site. .

Before you upgrade a production environment, always run a test upgrade in a pre-production environment that has the same configuration as your production environment.

These steps must be completed in full for a later rollback to be possible. Microsoft Support cannot recover backups, encryption keys, or configuration files that were not backed up.

Overview of Migration Scenarios

If you are upgrading from a supported version of Reporting Services to SQL Server, you can usually run the SQL Server Setup Wizard to upgrade the report server program files, database, and all application data.

However, migrating a report server installation manually is required if you encounter any of the following conditions:

You want to change the type of report server used in your deployment. For example, you cannot upgrade or convert a native mode report server to SharePoint mode. For more information, see Native to SharePoint Migration (SSRS) .

You want to minimize the amount of time the report server is taken offline during the upgrade process. Your current installation remains online while you copy content data to a new report server instance and test the installation without changing the state of your existing report server installation.

You want to migrate a SharePoint 2010 deployment of Reporting Services to SharePoint 2013/2016. SharePoint 2013/2016 does not support in-place upgrade from SharePoint 2010. For more information, see Migrate a Reporting Services Installation (SharePoint Mode) .

Native Mode Upgrade and Migration Scenarios

Upgrade: In-place upgrade for native mode is the same process for each of the supported versions that are listed earlier in this topic. Run the SQL Server installation wizard or a command line installation. Following installation the report server database will automatically upgrade to the new report server database schema. For more information, see the In-place Upgrade section in this topic.

The upgrade process begins when you select an existing report server instance to upgrade.

If the report server database is on a remote computer and you do not have permission to update that database, Setup prompts you to provide credentials to update to a remote report server database. Be sure to provide credentials that have sysadmin or database update permissions.

Setup checks for conditions or settings that prevent upgrade and reads configuration settings. Examples include custom extensions deployed on the report server. If upgrade is blocked, you must either modify your installation so that upgrade is no longer blocked, or migrate to a new SQL Server Reporting Services instance. For more information, see the Upgrade Advisor documentation.

If upgrade can proceed, Setup prompts you to continue with the upgrade process.

Setup creates new folders for SQL Server Reporting Services program files. The program folders for a Reporting Services installation include MSRS13.< instance name >.

Setup adds the SQL Server Reporting Services report server program files, configuration tools, and command line utilities that are part of the report server feature.

Program files from the previous version are removed.

Report server configuration tools and utilities that are upgraded to the new version include the Native Mode Reporting Services Configuration tool, command line utilities such as RS.exe, and Report Builder.

Other client tools such as SQL Server Management Studio are a separate download and need to be upgraded separately. For more information, see Download SQL Server Management Studio (SSMS) .

SQL Server Data Tools (SSDT) is a separate download. For more information, see SQL Server Data Tools in Visual Studio 2015 .

Setup reuses the service entry in Service Control Manager for the SQL Server Reporting Services Report Server service. This service entry includes the Report Server Windows service account.

Setup reserves new URLs based on existing virtual directory settings in IIS. Setup might not remove virtual directories in IIS, so be sure to remove those manually after upgrade is finished.

Setup merges settings in the configuration files. Using the configuration files from the current installation as the basis, new entries are added. Obsolete entries are not removed, but they will no longer be read by the report server after upgrade is finished. Upgrade will not delete old log files, the obsolete RSWebApplication.config file, or virtual directory settings in IIS. Upgrade will not remove older versions of Report Designer, Management Studio, or other client tools. If you no longer require them, be sure to remove these files and tools after upgrade is finished.

Migration: Migrating a previous version of a native mode installation to SQL Server Reporting Services is the same steps for all of the supported versions that are listed earlier in this topic. For more information, see Migrate a Reporting Services Installation (Native Mode)

Upgrade a Reporting Services Native Mode Scale-out Deployment

The following is a summary of how to upgrade a Reporting Services Native mode deployment that is scaled-out to more than one report server. This process requires downtime of the Reporting Services deployment:

Backup the report server databases and encryption keys. For more information, see Backup and Restore Operations for Reporting Services and Add and Remove Encryption Keys for Scale-Out Deployment (Report Server Configuration Manager) .

Use the Reporting Services Configuration Manager and remove all of the report servers from the scaled-out deployment. For more information, see Configure a Native Mode Report Server Scale-Out Deployment (Report Server Configuration Manager) .

Upgrade one of the report servers to SQL Server Reporting Services.

Use the Reporting Services Configuration Manager to add the report servers back to the scale-out deployment. For more information, see Configure a Native Mode Report Server Scale-Out Deployment (Report Server Configuration Manager) .

For each server, repeat the upgrade and Scale-out steps.

Roll back a Reporting Services Cumulative Update

Cumulative Updates in Reporting Services versions 2017 and later support in-place upgrade but cannot be selectively uninstalled. To roll back an upgrade, you must uninstall the entire service and reinstall the prior version following the directions below:

These steps require that the pre-upgrade checklist has been followed completely. Step 2 will render existing configuration files, service configurations, and encryption keys irrecoverable. Microsoft Support cannot recover these configuration files or decrypt these encryption keys to assist in rollback.

Take note of any custom configurations including service credentials, email or file share settings, or report server URLs.

Uninstall SQL Server Reporting Services. In a scale-out deployment, repeat for all nodes in the scale-out. For more information, see Uninstall Native Mode

Restore backups of ReportServer database. For more information, see Backup and Restore Operations for Reporting Services

Reinstall the prior update of SQL Server Reporting Services.

Restore pre-upgrade configuration files.

Restore the encryption key backup. For more information, see Back Up and Restore Encryption Keys

Recreate all of the custom configurations noted in step 1.

In a scale-out deployment, repeat steps 4 through 7 for all other nodes in the scale-out deployment.

SharePoint Mode Upgrade and Migration Scenarios

The following sections describe the issues and basic steps needed to upgrade or migrate from specified versions of Reporting Services SharePoint mode to SQL Server Reporting Services Reporting Services SharePoint mode.

There are two installation components to upgrade a Reporting Services SharePoint Mode deployment.

Reporting Services SharePoint Shared Service.

Use the Reporting Services SharePoint cmdlet Get-SPRSServiceApplicationServers to determine servers in the SharePoint farm that are currently running the Reporting Services SharePoint Shared Service and therefore require an upgrade.

Reporting Services Add-in for SharePoint products. For more information, see Install or Uninstall the Reporting Services Add-in for SharePoint .

For detailed steps on Migrating a SharePoint mode installation, see Migrate a Reporting Services Installation (SharePoint Mode) .

Some of the following scenarios require down time of the SharePoint environment due to the different technologies that need to be upgraded. If your situation does not allow for down time, you will need to complete a migration instead of an in-place upgrade.

SQL Server 2014 (12.x) to SQL Server Reporting Services

Starting environment: SQL Server 2014 (12.x) or SQL Server 2014 (12.x) SP1, SharePoint 2010 or SharePoint 2013.

Ending environment: SQL Server Reporting Services, SharePoint 2013 or SharePoint 2016.

SharePoint 2013/2016: SharePoint 2013/2016 does not support in-place upgrade from SharePoint 2010. However the procedure of database-attach upgrade is supported.

If you have a Reporting Services installation integrated with SharePoint 2010, you cannot upgrade in-place the SharePoint server. However you can migrate content databases and service application databases from the SharePoint 2010 farm to a SharePoint 2013/2016 farm.

SQL Server 2012 (11.x) to SQL Server Reporting Services

Starting environment: SQL Server 2012 (11.x) or SQL Server 2012 SP1 (11.0.3x), SharePoint 2010.

SQL Server 2008 R2 (10.50.x) to SQL Server Reporting Services

Starting environment: SQL Server 2008 R2 (10.50.x), SharePoint 2010.

SharePoint must be migrated first before you can upgrade Reporting Services.

Install the SQL Server Reporting Services version of the Reporting Services add-in for SharePoint on each web front-end in the farm. You can install the add-in by using the SQL Server Reporting Services installation wizard or by downloading the add-in.

Run SQL Server Reporting Services installation to upgrade SharePoint mode for each 'report server'. The SQL Server installation wizard will install the Reporting Services Service and create a new Service application.

Considerations for a Migration

When moving application data, you should be aware of the following concerns and restrictions:

Protection of encryption key includes a hash that incorporates machine identity.

Report server database names are fixed and cannot be renamed on new computer.

Encryption Key Considerations

Always back up the encryption keys before moving a report server database to a new computer.

Moving a report server installation to another computer will invalidate the hash that protects the encryption keys used to help secure sensitive data stored in the report server database. Each report server instance that uses the database has its copy of the encryption key, which is encrypted with the identity of the service account as it is defined on the current computer. If you change computers, the service will no longer have access to its key, even if you use the same account name on the new computer.

To re-establish reversible encryption on the new report server computer, you must restore the key that you previously backed up. The complete key set that is stored in the report server database consists of a symmetric key value, plus service identity information used to restrict access to the key so that it can be used only by the report server instance that stored it. During key restoration, the report server replaces existing copies of the key with new versions. The new version includes machine and service identity values as defined on the current computer. For more information, see the following topics:

SharePoint mode: See the "Key Management" section of Manage a Reporting Services SharePoint Service Application

Native Mode: See Back Up and Restore Reporting Services Encryption Keys

Fixed Database Name

You cannot rename the report server database. The identity of the database is recorded in report server stored procedures when the database is created. Renaming either the report server primary or temporary databases will cause errors to occur when the procedures run, invalidating your report server installation.

If the database name from the existing installation is not suited for the new installation, you should consider creating a new database that has the name that you prefer, and then load existing application data using the techniques in the following list:

Write a Visual Basic script that calls Report Server Web service SOAP methods to copy data between databases. You can use the RS.exe utility to run the script. For more information about this approach, see Scripting and PowerShell with Reporting Services .

Write code that calls the WMI provider to copy data between databases. For more information about this approach, see Access the Reporting Services WMI Provider .

If you have just a few items, you can republish reports, and shared data sources from Report Designer, Model Designer, and Report Builder to the new report server. You must re-create role assignments, subscriptions, shared schedules, report snapshot schedules, custom properties that you set on reports or other items, model item security, and properties that you set on the report server. You will lose report history and report execution log data.

Additional Resources

For more information on SharePoint database-attach upgrade, see the following:

Overview of the upgrade process to SharePoint 2016 .

Overview of the upgrade process to SharePoint 2013 .

Clean up preparations before an upgrade to SharePoint 2013 .

Upgrade databases from SharePoint 2013 to SharePoint 2016 .

Upgrade databases from SharePoint 2010 to SharePoint 2013 .

Upgrade Reports Upgrade to SQL Server 2016 Using the Installation Wizard (Setup)

More questions? Try asking the Reporting Services forum

Was this page helpful?

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources

United States Provider Experiences with Telemedicine for Hepatitis C Treatment: A Nationwide Survey

• Find this author on Google Scholar
• Find this author on PubMed
• Search for this author on this site
• ORCID record for Shashi N Kapadia
• For correspondence: [email protected]
• Info/History
• Supplementary material
• Preview PDF

Background Hepatitis C virus (HCV) elimination requires treatment access expansion, especially for underserved populations. Telehealth has the potential to improve HCV treatment access, although data are limited on its incorporation into standard clinical practice.

Methods We conducted a cross-sectional, e-mail survey of 598 US HCV treatment providers who had valid email addresses and 1) were located in urban areas and had written ≥20 prescriptions for HCV treatment to US Medicare beneficiaries in 2019-20 or 2) were located in non-urban areas and wrote any HCV prescriptions in 2019-20. Through email, we notified providers of a self-administered electronic 28-item survey of clinical strategies and attitudes about telemedicine for HCV.

Results We received 86 responses (14% response rate), of which 75 used telemedicine for HCV in 2022. Of those 75, 24% were gastroenterologists/hepatologists, 23% general medicine, 17% infectious diseases, and 32% non-physicians. Most (82%) referred patients to commercial laboratories, and 85% had medications delivered directly to patients. Overwhelmingly, respondents (92%) felt that telehealth increases healthcare access, and 76% reported that it promotes or is neutral for treatment completion. Factors believed to be “extremely” or “very” important for telehealth use included patient access to technology (86%); patients’ internet access (74%); laboratory access (76%); reimbursement for video visits (74%) and audio-only visits (66%). Non-physician licensing and liability statutes were rated “extremely” or “very” important by 43% and 44%, respectively.

Conclusions Providers felt that telehealth increases HCV treatment access. Major limitations were technological requirements, reimbursement, and access to ancillary services. These findings support the importance of digital equity and literacy to achieve HCV elimination goals.

Competing Interest Statement

Dr Kapadia reports grants to his institution from Gilead Sciences Inc unrelated to the current study. Dr. Patel is part of the Speakers Bureau for Gilead Sciences. Dr. Talal reports grants to his institution from Gilead Sciences, Merck, and Abbott Laboratories. He has also served on advisory committees and as an advisor to Gilead Sciences, Novo Nordisk, and AbbVie. All other authors report no conflicts of interest.

Funding Statement

This work was supported in part by R01 DK123205 (to MS, MTW, EW, AHT), K01 DA048172 (to SNK), a Patient-Centered Outcomes Research Institute (PCORI) Award (IHS-1507-31640) (to AHT) and the Troup Fund of the Kaleida Health Foundation (to AHT). The opinions expressed in this work are those of the authors, and do not necessarily reflect the views of the funding agencies or the US Government.

Author Declarations

I confirm all relevant ethical guidelines have been followed, and any necessary IRB and/or ethics committee approvals have been obtained.

The details of the IRB/oversight body that provided approval or exemption for the research described are given below:

The IRB of the Biomedical Research Alliance of New York (BRANY) gave ethical approval for this work.

I confirm that all necessary patient/participant consent has been obtained and the appropriate institutional forms have been archived, and that any patient/participant/sample identifiers included were not known to anyone (e.g., hospital staff, patients or participants themselves) outside the research group so cannot be used to identify individuals.

I understand that all clinical trials and any other prospective interventional studies must be registered with an ICMJE-approved registry, such as ClinicalTrials.gov. I confirm that any such study reported in the manuscript has been registered and the trial registration ID is provided (note: if posting a prospective study registered retrospectively, please provide a statement in the trial ID field explaining why the study was not registered in advance).

I have followed all appropriate research reporting guidelines, such as any relevant EQUATOR Network research reporting checklist(s) and other pertinent material, if applicable.

Disclosures: Dr Kapadia reports grants to his institution from Gilead Sciences Inc unrelated to the current study. Dr. Patel is part of the Speakers Bureau for Gilead Sciences. Dr. Talal reports grants to his institution from Gilead Sciences, Merck, and Abbott Laboratories. He has also served on advisory committees and as an advisor to Gilead Sciences, Novo Nordisk, and AbbVie. All other authors report no conflicts of interest.

Funding: This work was supported in part by R01 DK123205 (to MS, MTW, EW, AHT), K01 DA048172 (to SNK), a Patient-Centered Outcomes Research Institute (PCORI) Award (IHS-1507-31640) (to AHT) and the Troup Fund of the Kaleida Health Foundation (to AHT). The statements in this work solely the responsibility of the authors, and do not necessarily represent the views of PCORI, its Board of Governors or Methodology Committee, or the US Government.

Data Availability

All data produced in the present study are available upon reasonable request to the authors

View the discussion thread.

Supplementary Material

Thank you for your interest in spreading the word about medRxiv.

NOTE: Your email address is requested solely to identify you as the sender of this article.

Citation Manager Formats

• EndNote (tagged)
• EndNote 8 (xml)
• RefWorks Tagged
• Ref Manager
• Tweet Widget
• Facebook Like
• Google Plus One

Subject Area

• Gastroenterology
• Addiction Medicine (324)
• Allergy and Immunology (628)
• Anesthesia (165)
• Cardiovascular Medicine (2377)
• Dentistry and Oral Medicine (289)
• Dermatology (207)
• Emergency Medicine (379)
• Endocrinology (including Diabetes Mellitus and Metabolic Disease) (837)
• Epidemiology (11775)
• Forensic Medicine (10)
• Gastroenterology (703)
• Genetic and Genomic Medicine (3744)
• Geriatric Medicine (350)
• Health Economics (634)
• Health Informatics (2399)
• Health Policy (933)
• Health Systems and Quality Improvement (898)
• Hematology (341)
• HIV/AIDS (782)
• Infectious Diseases (except HIV/AIDS) (13318)
• Intensive Care and Critical Care Medicine (767)
• Medical Education (365)
• Medical Ethics (105)
• Nephrology (398)
• Neurology (3507)
• Nursing (198)
• Nutrition (526)
• Obstetrics and Gynecology (674)
• Occupational and Environmental Health (664)
• Oncology (1824)
• Ophthalmology (538)
• Orthopedics (219)
• Otolaryngology (287)
• Pain Medicine (233)
• Palliative Medicine (66)
• Pathology (446)
• Pediatrics (1035)
• Pharmacology and Therapeutics (426)
• Primary Care Research (420)
• Psychiatry and Clinical Psychology (3178)
• Public and Global Health (6145)
• Radiology and Imaging (1280)
• Rehabilitation Medicine and Physical Therapy (747)
• Respiratory Medicine (828)
• Rheumatology (379)
• Sexual and Reproductive Health (372)
• Sports Medicine (323)
• Surgery (402)
• Toxicology (50)
• Transplantation (172)
• Urology (146)