Windows 10 version is no longer supported after today – Microsoft Community Hub – Windows 10 current versions by servicing option

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Addresses an issue that may prevent access to some gov. Note: After installation, the OS build will be Use the credentials of a local admin to create and set the following registry keys on the Host OS then restart the Host:. This issue is resolved in KB Microsoft strongly recommends you install the latest servicing stack update SSU for your operating system before installing the latest cumulative update LCU. SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes.

For more information, see Servicing stack updates. This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website. For a list of the files that are provided in this update, download the file information for cumulative update This update replaces the previously released update Learn about the terminology that Microsoft uses to describe software updates.

Windows 10, version , all editions More Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn’t match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback?

Submit feedback. Thank you for your feedback!

 
 

 

Windows 10 version history – Wikipedia.Windows 10 update | Download Windows 10 version Update

 

Microsoft strongly recommends you install the latest servicing stack update SSU for your operating system before installing the latest cumulative update LCU. SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes. For more information, see Servicing stack updates. This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.

For a list of the files that are provided in this update, download the file information for cumulative update This update replaces the previously released update Learn about the terminology that Microsoft uses to describe software updates. Windows 10, version , all editions More Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you!

Any more feedback? The more you tell us the more we can help. This event indicates that the First Accept dialog has been shown. This critical event sends information about the driver installation that took place. This event sends data about the driver installation once it is completed. This event sends data about the driver that the new driver installation is replacing.

This event sends basic GPU and display driver information to keep Windows and display drivers up-to-date. This event returns information about how many resources and of what type are in the server cluster. This data is collected to keep Windows Server safe, secure, and up to date. The data includes information about whether hardware is configured correctly, if the software is patched correctly, and assists in preventing crashes by attributing issues like fatal errors to workloads and system configurations.

This event sends data about crashes for both native and managed applications, to help keep Windows up to date. The data includes information about the crashing process and a summary of its exception record. It does not contain any Watson bucketing information. AppCrash is emitted once for each crash handled by WER e.

Note that Generic Watson event types e. This event sends diagnostic data about failures when uninstalling a feature update, to help resolve any issues preventing customers from reverting to a known state. This event indicates that the uninstall was properly configured and that a system reboot was initiated.

This event sends data about hangs for both native and managed applications, to help keep Windows up to date. AppHang is reported only on PC devices. It handles classic Win32 hangs and is emitted only once per report. Some behaviors that may be perceived by a user as a hang are reported by app managers e. This event is also used to count WMR device. This event indicates Windows Mixed Reality Portal app activation state.

This event also used to count WMR device. This event indicates Windows Mixed Reality Portal app resuming. This event provides Windows Mixed Reality device information. This event is also used to count WMR device and device type. This event captures basic checksum data about the device inventory items stored in the cache for use in validating data completeness for Microsoft.

Core events. The fields in this event may change over time, but they will always represent a count of a given object. This event sends inventory component versions for the Device Inventory data. This event enumerates the signatures of files, either driver packages or application executables. For driver packages, this data is collected on demand via Telecommand to limit it only to unrecognized driver packages, saving time for the client and space on the server. For applications, this data is collected for up to 10 random executables on a system.

This event sends basic metadata about an application on the system. The data collected with this event is used to keep Windows performing properly and up to date. This event represents what drivers an application installs. This event provides file-level information about the applications that exist on the system.

This event is used to understand the applications on a device to determine if those applications will experience compatibility issues when upgrading Windows. This event provides the basic metadata about the frameworks an application may depend on. This event indicates that a new set of InventoryApplicationFrameworkAdd events will be sent. This event indicates that a new set of InventoryDevicePnpAdd events will be sent. This event indicates that a new set of InventoryApplicationAdd events will be sent.

This event sends basic metadata about a device container such as a monitor or printer as opposed to a Plug and Play device. The data collected with this event is used to help keep Windows up to date and to keep Windows performing properly. This event indicates that the InventoryDeviceContainer object is no longer present. This event indicates that a new set of InventoryDeviceContainerAdd events will be sent. This event retrieves information about what sensor interfaces are available on the device.

This event indicates that a new set of InventoryDeviceInterfaceAdd events will be sent. This event sends additional metadata about a Plug and Play device that is specific to a particular class of devices. The data collected with this event is used to help keep Windows up to date and performing properly while reducing overall size of data payload. This event indicates that the InventoryDeviceMediaClass object represented by the objectInstanceId is no longer present.

This event is used to understand a PNP device that is specific to a particular class of devices. This event sends basic metadata about a PNP device and its associated driver to help keep Windows up to date. This information is used to assess if the PNP device and driver will remain compatible when upgrading Windows. This event indicates that the InventoryDevicePnpRemove object is no longer present.

This event sends basic metadata about sensor devices on a machine. This event indicates that a new set of InventoryDeviceSensor events will be sent. This event sends basic metadata about the USB hubs on the device.

This event sends basic metadata about driver binaries running on the system. This event indicates that the InventoryDriverBinary object is no longer present. This event indicates that a new set of InventoryDriverBinaryAdd events will be sent. This event sends basic metadata about drive packages installed on the system. This event indicates that the InventoryDriverPackageRemove object is no longer present.

This event indicates that a new set of InventoryDriverPackageAdd events will be sent. This event collects traces of all other Core events, not used in typical customer scenarios. This event signals the beginning of the event download, and that tracing should begin. This event signals the end of the event download, and that tracing should end.

This event sends details collected for a specific application on the source device. This event indicates the beginning of a series of AppHealthStaticAdd events. This event indicates that this particular data object represented by the objectInstanceId is no longer present. This is a diagnostic event that indicates a new sync is being generated for this object type. This event represents the basic metadata about the OS indicators installed on the system. The data collected with this event helps ensure the device is up to date and keeps Windows performing properly.

This event is used to understand the OS indicators installed on the system. The data collected with this event helps ensure the device is current and Windows is up to date and performing properly. This event indicates the number of bytes read from or read by the OS and written to or written by the OS upon system startup. This event includes basic data about the Operating System, collected during Boot and used to evaluate the success of the upgrade process.

This critical device configuration event provides information about drivers for a driver installation that took place within the kernel. This event is sent when a problem code is cleared from a device.

This event is sent when a new problem code is assigned to a device. This event sends Product and Service Performance data on which area of the device exceeded safe temperature limits and caused the device to shutdown. This information is used to ensure devices are behaving as they are expected to. This config event sends basic device connectivity and configuration information from Microsoft Edge about the current data collection consent, app version, and installation state to keep Microsoft Edge up to date and secure.

This Ping event sends a detailed inventory of software and hardware information about the EdgeUpdate service, Edge applications, and the current system environment including app configuration, update configuration, and hardware capabilities. One or more events is sent each time any installation, update, or uninstallation occurs with the EdgeUpdate service or with Edge applications.

This event is used to measure the reliability and performance of the EdgeUpdate service and if Edge applications are up to date. This is an indication that the event is designed to keep Windows secure and up to date.

This event sends simple Product and Service Performance data on a crashing Microsoft Edge browser process to help mitigate future instances of the crash. This event sends hardware and software inventory information about the Microsoft Edge Update service, Microsoft Edge applications, and the current system environment, including app configuration, update configuration, and hardware capabilities.

It’s used to measure the reliability and performance of the EdgeUpdate service and if Microsoft Edge applications are up to date.

This event returns data to track the count of the migration objects across various phases during feature update. The data collected with this event is used to help keep Windows secure and to track data loss scenarios. This event returns data about the count of the migration objects across various phases during feature update.

This event sends data at the end of a Miracast session that helps determine RTSP related Miracast failures along with some statistics about the session. The data collected with this event is used to keep Windows product and service performing properly. This event indicates Windows Mixed Reality device state.

This is an internal-only test event used to validate the utc. The provider of this event is assigned to the Windows Core Telemetry group provider in order to test. This event is used to determine whether the user successfully completed the privacy consent experience.

This event provides the effectiveness of new privacy experience. This event is sent when detailed state information is needed from an update trial run. The event indicates progress made by the updater. This information assists in keeping Windows up to date. This event sends basic metadata about the SetupPlatform update installation process, to help keep Windows up to date. This event sends basic metadata about the update installation process generated by SetupPlatform to help keep Windows up to date.

This service retrieves events generated by SetupPlatform, the engine that drives the various deployment scenarios, to help keep Windows up to date. This event is sent when targeting logic is evaluated to determine if a device is eligible for a given action. This event sends tracking data about the software distribution client check for content that is applicable to a device, to help keep Windows up to date.

This event sends data on whether the Update Service has been called to execute an upgrade, to help keep Windows up to date. This event sends tracking data about the software distribution client download of the content for that update, to help keep Windows up to date. This event allows tracking of ongoing downloads and contains data to explain the current state of the download. This event sends tracking data about the software distribution client installation of the content for that update, to help keep Windows up to date.

This is a revert event for target update on Windows Update Client. This is a start event for Server Initiated Healing client. This is an uninstall event for target update on Windows Update Client. This event helps to identify whether update content has been tampered with and protects against man-in-the-middle attack.

This event includes the hardware level data about battery performance. The data collected with this event is used to help keep Windows products and services performing properly. This event collects information to keep track of health indicator of the built-in micro controller. For example, the number of abnormal shutdowns due to power issues during boot sequence, type of display panel attached to base, thermal indicator, throttling data in hardware etc. The data collected with this event is used to help keep Windows secure and performing properly.

This event indicates the customer has cancelled uninstallation of Windows. The data collected with this event is used to keep Windows performing properly and helps with tracking the health of recovery and OSUninstall scenarios. This event sends an error code when the Windows uninstallation fails. This event is sent to signal an upcoming reboot during uninstallation of Windows. This event indicates that the Windows uninstallation has started.

This event sends diagnostic data when the Windows uninstallation is not available. This event is sent when users have actions that will block the uninstall of the latest quality update. This event is sent when the registry indicates that the latest cumulative Windows update package has finished uninstalling. This event is sent when the latest cumulative Windows update was uninstalled on a device. This event is sent when a push-button reset operation is blocked by the System Administrator.

This event signals a failed handoff between two recovery binaries. This event signals successful handoff between two recovery binaries. This event reports the error code when recovery fails. This event provides information about whether a system reset needs repair. This event sends basic data during boot about the firmware loaded or recently installed on the machine. This event sends basic info on whether the device should be updated to the latest cumulative update.

The data collected with this event is used to help keep Windows up to date and secure. This event sends basic info on whether the device is ready to download the latest cumulative update. This event sends basic info when download of the latest cumulative update begins. This event sends basic info on the result of the installation of the latest cumulative update. Event that tracks the effectiveness of an operation to mitigate an issue on devices that meet certain requirements.

This event provides the result of running the compatibility check for update assistant. This event provides basic information about the device where update assistant was run. This event provides details about user action. This event indicates that an update detection has occurred and the targeted install has been blocked. This event indicates that the update has been completed. This event indicates that the detection phase of USO has started. This event indicates that the download phase of USO has started.

This event indicates that the install phase of USO has started. This event indicates that the device is already on the expected UBR. This event indicates the expected UBR of the device. This event indicates that the expedite update is completed with reboot. This event indicates that the device has finished servicing and a reboot is required. This event sends results of the expedite USO scan.

This event indicates that the unified installer has completed. This event indicates that the installation has started for the unified installer. This event is sent when a blob notification is received. This event is sent when a notification is received. This event is received when the UpdateHealthTools service uploads device information. This event provides information for device which failed to upload the details.

This event is received when a push notification has been completed by the UpdateHealthTools service. This event is received when the UpdateHealthTools service receives a push notification. This event is received when there is status on a push notification.

The event indicates the details about the blob used for update health tools. The event is sent when the device is not joined to AAD. This event is sent when a device has been detected as DSS device. This event is sent when the service first starts. It is a heartbeat indicating that the service is available on the device. This event sends data relating to the Revert phase of updating Windows. This event collects information regarding the commit phase of the new Unified Update Platform UUP update scenario, which is leveraged by both Mobile and Desktop.

Applicable to PC and Mobile. This event collects information regarding the expansion phase of the new Unified Update Platform UUP update scenario, which is leveraged by both Mobile and Desktop.

This event sends data for the install phase of updating Windows. The UpdateAgentMerge event sends data on the merge phase when updating Windows. This event sends data indicating the result of each update agent mitigation.

This event sends a summary of all the update agent mitigations available for an this update. This event sends data for the start of each mode during the process of updating Windows via the new Unified Update Platform UUP scenario.

Applicable to both PCs and Mobile. This event collects information regarding the post reboot phase of the new UUP Unified Update Platform update scenario, which is leveraged by both Mobile and Desktop.

This event sends information indicating that a request has been sent to suspend an update. This event is only applicable to PCs. This event is sent at the start of the CampaignManager event and is intended to be used as a heartbeat. This event indicates whether devices received additional or critical supplemental content during an OS Upgrade, to help keep Windows up to date and secure.

This event returns data about the download of supplemental packages critical to upgrading a device to the next version of Windows. This event determines whether devices received additional or critical supplemental content during an OS upgrade. This event sends data indicating that the device has started the downlevel phase of the upgrade, to help keep Windows up to date and secure. This event sends data indicating that the device has started the phase of finalizing the upgrade, to help keep Windows up-to-date and secure.

Specifically, it indicates the outcome of an OS uninstall. This event sends data indicating that the device has invoked the post reboot install phase of the upgrade, to help keep Windows up-to-date.

This event sends data indicating that the device has invoked the predownload quiet phase of the upgrade, to help keep Windows up to date.

X, Windows 8. X, Windows 10 and RS, to help keep Windows up-to-date and secure. Specifically, it indicates the outcome of the PredownloadUX portion of the update process. This event sends data indicating that the device has invoked the preinstall quiet phase of the upgrade, to help keep Windows up-to-date. This event sends data regarding OS updates and upgrades from Windows 7, Windows 8, and Windows 10, to help keep Windows up-to-date.

Specifically, it indicates the outcome of the PreinstallUX portion of the update process. This event helps determine whether the device received supplemental content during an operating system upgrade, to help keep Windows up-to-date. This event sends data indicating the result of each setup mitigation. This event sends a summary of all the setup mitigations available for this update. This event sends data indicating that the device has invoked the unexpected event phase of the upgrade, to help keep Windows up to date.

This event is sent when WaaSMedic fails to apply the named diagnostic. This event is sent when the WaaS Medic update stack remediation tool fails to apply a described resolution to a problem that is blocking Windows Update from operating correctly on a target device. This event provides the result of the WaaSMedic operation. This event sends binary data from the collected dump file wheneveer a bug check occurs, to help keep Windows up to date. The is the OneCore version of this event.

It is the primary means of estimating reliability problems in Basic Diagnostic reporting with very strong privacy guarantees. This event provides a denominator to calculate MTTF mean-time-to-failure for crashes and other errors, to help keep Windows up to date. This event provides information about the datastore migration and whether it was successful.

This event is sent when an installation or update is canceled by a user or the system and is used to help keep Windows Apps up to date and secure. This event is sent when an inventory of the apps installed is started to determine whether updates for those apps are available. It’s used to help keep Windows up-to-date and secure. This event is sent when the Store Agent cache is refreshed with any available package updates.

This event is sent when an app update or installation is canceled while in interactive mode. This can be canceled by the user or the system. This event is sent at the end of app installations or updates to help keep Windows up-to-date and secure. This event is sent after the license is acquired when a product is being installed.

This event is sent when an app update requires an updated Framework package and the process starts to download it. It is used to help keep Windows up-to-date and secure. This event is sent after sending the inventory of the products installed to determine whether updates for those products are available.

This event is sent after a product has been installed to help keep Windows up-to-date and secure. This event is sent after a scan for product updates to determine if there are packages to install.

This event is sent after searching for update packages to install. This event is sent after restoring user data if any that needs to be restored following a product install. It is used to keep Windows up-to-date and secure. This event is sent after a scan for available app updates to help keep Windows up-to-date and secure. This event is sent at the end of an app install or update to help keep Windows up-to-date and secure.

This event is sent at the beginning of an app install or update to help keep Windows up-to-date and secure. This event is sent when a product install or update is initiated, to help keep Windows up-to-date and secure. This event is sent when a product install or update is paused either by a user or the system , to help keep Windows up-to-date and secure. This event is sent when a product install or update is resumed either by a user or the system , to help keep Windows up-to-date and secure.

This event is sent when a product install or update is resumed by a user or on installation retries, to help keep Windows up-to-date and secure.

This event is sent when searching for update packages to install, to help keep Windows up-to-date and secure. Products in the process of being fulfilled installed or updated are maintained in a list. This event is sent any time there is a change in a product’s fulfillment status pending, working, paused, cancelled, or complete , to help keep Windows up to date and secure.

This event occurs when an update is requested for an app, to help keep Windows up-to-date and secure. This event sends basic telemetry on the failure of the Feature Rollback. This event sends basic telemetry on whether Feature Rollback rolling back features updates is applicable to a device. This event sends basic information indicating that Feature Rollback has started. This event informs you whether a rollback of Quality updates is applicable to the devices that you are attempting to rollback.

This event indicates that the Quality Rollback process has started. This event describes when a download was canceled with Delivery Optimization. It’s used to understand and address problems regarding downloads.

This event describes when a download has completed with Delivery Optimization. This event represents a temporary suspension of a download with Delivery Optimization. This event sends data describing the start of a new download to enable Delivery Optimization. This event represents a Windows Update job error. It allows for investigation of top errors.

This event collects information regarding the state of devices and drivers on the system following a reboot after the install phase of the new device manifest UUP Unified Update Platform update scenario which is used to install a device manifest describing a set of driver packages. This event collects information regarding the final commit phase of the new device manifest UUP Unified Update Platform update scenario, which is used to install a device manifest describing a set of driver packages.

This event collects information regarding the download request phase of the new device manifest UUP Unified Update Platform update scenario, which is used to install a device manifest describing a set of driver packages.

This event sends data for initializing a new update session for the new device manifest UUP Unified Update Platform update scenario, which is used to install a device manifest describing a set of driver packages. This event collects information regarding the install phase of the new device manifest UUP Unified Update Platform update scenario, which is used to install a device manifest describing a set of driver packages. This event sends data for the start of each mode during the process of updating device manifest assets via the UUP Unified Update Platform update scenario, which is used to install a device manifest describing a set of driver packages.

This event indicates that a notification dialog box is about to be displayed to user. This event indicates that the Enhanced Engaged restart “accept automatically” dialog box was displayed. This event indicates that the Enhanced Engaged restart “restart failed” dialog box was displayed. This event indicates that the Enhanced Engaged restart “restart imminent” dialog box was displayed.

This event returns information relating to the Enhanced Engaged reboot reminder dialog that was displayed. This event sends basic information for scheduling a device restart to install security updates. It’s used to help keep Windows secure and up-to-date by indicating when a reboot is scheduled by the system or a user for a security, quality, or feature update.

This event measures overall health of UpdateOrchestrator. This event indicates a policy is present that may restrict update activity to outside of active hours. This event indicates that update activity was blocked because it is within the active hours window. This event indicates that Windows Update activity was blocked due to low battery level. This event indicates that a restart required for installing updates was postponed. This event sends launch data for a Windows Update scan to help keep Windows secure and up to date.

This event returns data about detected updates, as well as the types of update optional or recommended. This data helps keep Windows up to date. This event indicates the reboot was postponed due to needing a display.