mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-11 12:57:23 +00:00
Merge pull request #10831 from MicrosoftDocs/main
[Publish, Tuesday 29 April 2025, 5:10 PM PDT] Move "Windows 11 version 21H2 required diagnostic data" article to ARCHIVE repo
This commit is contained in:
Dan Brown
GitHub
commit
8af05b35a1
@ -164,6 +164,11 @@
|
||||
"source_path": "windows/privacy/copilot-supplemental-terms.md",
|
||||
"redirect_url": "https://www.microsoft.com/privacy/privacystatement?form=MG0AV3#mainartificialintelligenceandmicrosoftcopilotmodule",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
},
|
||||
{
|
||||
"source_path": "windows/privacy/required-windows-11-diagnostic-events-and-fields.md",
|
||||
"redirect_url": "/previous-versions/windows/it-pro/privacy/required-windows-11-diagnostic-events-and-fields",
|
||||
"redirect_document_id": false
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@ -29,7 +29,6 @@ You can learn more about Windows functional and diagnostic data through these ar
|
||||
|
||||
- [Required diagnostic events and fields for Windows 11, version 24H2](required-diagnostic-events-fields-windows-11-24H2.md)
|
||||
- [Required diagnostic events and fields for Windows 11, versions 23H2 and 22H2](required-diagnostic-events-fields-windows-11-22H2.md)
|
||||
- [Required diagnostic events and fields for Windows 11, version 21H2](required-windows-11-diagnostic-events-and-fields.md)
|
||||
- [Required diagnostic events and fields for Windows 10, versions 22H2 and 21H2](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||
- [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md)
|
||||
|
||||
@ -15,17 +15,17 @@ ms.topic: reference
|
||||
# Optional diagnostic data for Windows 11 and Windows 10
|
||||
|
||||
Applies to:
|
||||
- Windows 11, version 24H2
|
||||
- Windows 11, version 23H2
|
||||
- Windows 11, version 22H2
|
||||
- Windows 11, version 21H2
|
||||
- Windows 10, version 22H2
|
||||
- Windows 10, version 21H2
|
||||
- Windows 10, version 1809
|
||||
|
||||
> [!NOTE]
|
||||
> The information in this article also applies to these versions of Windows 10: 21H1, 20H2, 2004, 1909, 1903, 1803, and 1709. But those versions have reached their end of servicing date. For more information, see [Microsoft Product Lifecycle](/lifecycle/products).
|
||||
> The information in this article also applies to Windows 11 (version 21H2) and these versions of Windows 10: 21H1, 20H2, 2004, 1909, 1903, 1803, and 1709. But those versions have reached their end of servicing date. For more information, see [Microsoft Product Lifecycle](/lifecycle/products).
|
||||
|
||||
Microsoft uses Windows diagnostic data to keep Windows secure and up-to-date, troubleshoot problems, and make product improvements. For users who have turned on "Tailored experiences", it can also be used to offer you personalized tips, ads, and recommendations to enhance Microsoft products and services for your needs. This article describes all types of optional diagnostic data collected by Windows, with comprehensive examples of data we collect per each type. For additional, detailed technical descriptions of Basic data items, see [Windows 11 required diagnostic events and fields](/windows/privacy/required-windows-11-diagnostic-events-and-fields).
|
||||
Microsoft uses Windows diagnostic data to keep Windows secure and up-to-date, troubleshoot problems, and make product improvements. For users who have turned on "Tailored experiences", it can also be used to offer you personalized tips, ads, and recommendations to enhance Microsoft products and services for your needs. This article describes all types of optional diagnostic data collected by Windows, with comprehensive examples of data we collect per each type.
|
||||
|
||||
In addition, this article provides references to equivalent definitions for the data types and examples from [ISO/IEC 19944-1:2020 Information technology - Cloud computing - Cloud services and devices: Data flow, data categories, and data use](https://www.iso.org/standard/79573.html). Each data type also has a Data Use statement, for diagnostics and for Tailored experiences on the device, using the terms as defined by the standard. These Data Use statements define the purposes for which Microsoft processes each type of Windows diagnostic data, using a uniform set of definitions referenced at the end of this document and based on the ISO standard. Reference to the ISO standard provides additional clarity about the information collected, and allows easy comparison with other services or guidance that also references the standard.
|
||||
|
||||
@ -54,9 +54,9 @@ Information that is added to most diagnostic events, if relevant and available:
|
||||
- Diagnostic level - Required or Optional, Sample level - for sampled data, what sample level is this device opted into (8.2.3.2.4 Observed Usage of the Service Capability)
|
||||
- Operating system name, version, build, and locale (8.2.3.2.2 Telemetry data)
|
||||
- Event collection time (8.2.3.2.2 Telemetry data)
|
||||
- User ID - a unique identifier associated with the user's Microsoft Account (if one is used) or local account. The user's Microsoft Account identifier is not collected from devices configured to send Basic - diagnostic data (8.2.5 Account data)
|
||||
- User ID - a unique identifier associated with the user's Microsoft Account (if one is used) or local account. The user's Microsoft Account identifier isn't collected from devices configured to send Basic - diagnostic data (8.2.5 Account data)
|
||||
- Xbox UserID (8.2.5 Account data)
|
||||
- Device ID - This ID is not the user provided device name, but an ID that is unique for that device. (8.2.3.2.3 Connectivity data)
|
||||
- Device ID - This ID isn't the user provided device name, but an ID that is unique for that device. (8.2.3.2.3 Connectivity data)
|
||||
- Device class - Desktop, Server, or Mobile (8.2.3.2.3 Connectivity data)
|
||||
- Environment from which the event was logged - Application ID of app or component that logged the event, Session GUID. Used to track events over a given period of time, such as the amount of time an app is running or between boots of the operating system (8.2.4 Cloud service provider data)
|
||||
- Diagnostic event name, Event ID, ETW opcode, version, schema signature, keywords, and flags (8.2.4 Cloud service provider data)
|
||||
@ -194,7 +194,7 @@ This type of data includes details about the usage of the device, operating syst
|
||||
**With (optional) Tailored experiences:**<br>
|
||||
If a user has enabled Tailored experiences on the device, [pseudonymized](#pseudo) Product and Service Usage data from Windows 10 and Windows 11 is used by Microsoft to [personalize](#personalize), [recommend](#recommend), and [offer](#offer) Microsoft products and services to Windows 10 and Windows 11 users. Also, if a user has enabled Tailored experiences on the device, [pseudonymized](#pseudo) Product and Service Usage data from Windows 10 and Windows 11 is used by Microsoft to [promote](#promote) third-party Windows apps, services, hardware, and peripherals to Windows 10 and Windows 11 users. For example:
|
||||
|
||||
- If data shows that a user has not used a particular feature of Windows, we might recommend that the user try that feature.
|
||||
- If data shows that a user hasn't used a particular feature of Windows, we might recommend that the user try that feature.
|
||||
- Data about which apps are most-used on a device is used to provide recommendations for similar or complementary (Microsoft or third-party) apps. These apps might be free or paid.
|
||||
|
||||
|
||||
@ -303,7 +303,7 @@ If a user has enabled Tailored experiences on the device, [pseudonymized](#pseud
|
||||
|
||||
- Video Width, height, color palette, encoding (compression) type, and encryption type
|
||||
- Instructions about how to stream content for the user - the smooth streaming manifest of content file chunks that must be pieced together to stream the content based on screen resolution and bandwidth
|
||||
- URL for a specific two-second chunk of content if there is an error
|
||||
- URL for a specific two-second chunk of content if there's an error
|
||||
- Full-screen viewing mode details
|
||||
|
||||
**Music & TV subtype:** Information about music and TV consumption on the device
|
||||
|
||||
@ -29,7 +29,6 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
||||
You can learn more about Windows functional and diagnostic data through these articles:
|
||||
|
||||
- [Required diagnostic events and fields for Windows 11, version 24H2](required-diagnostic-events-fields-windows-11-24H2.md)
|
||||
- [Required diagnostic events and fields for Windows 11, version 21H2](required-windows-11-diagnostic-events-and-fields.md)
|
||||
- [Required diagnostic events and fields for Windows 10, versions 22H2 and 21H2](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||
@ -488,7 +487,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.Appraiser.General.InventoryApplicationFileAdd
|
||||
|
||||
This event represents the basic metadata about a file on the system. The file must be part of an app and either have a block in the compatibility database or be part of an antivirus program. The data collected with this event is used to help keep Windows up to date.
|
||||
This event represents the basic metadata about a file on the system. The file must be part of an app and either have a block in the compatibility database or be part of an antivirus program. The data collected with this event is used to help keep Windows up to date.
|
||||
|
||||
This event includes fields from [Ms.Device.DeviceInventoryChange](#msdevicedeviceinventorychange).
|
||||
|
||||
@ -497,7 +496,7 @@ The following fields are available:
|
||||
- **AppraiserVersion** The version of the Appraiser file generating the events.
|
||||
- **AvDisplayName** If the app is an antivirus app, this is its display name.
|
||||
- **AvProductState** Indicates whether the antivirus program is turned on and the signatures are up to date.
|
||||
- **BinaryType** A binary type. Example: UNINITIALIZED, ZERO_BYTE, DATA_ONLY, DOS_MODULE, NE16_MODULE, PE32_UNKNOWN, PE32_I386, PE32_ARM, PE64_UNKNOWN, PE64_AMD64, PE64_ARM64, PE64_IA64, PE32_CLR_32, PE32_CLR_IL, PE32_CLR_IL_PREFER32, PE64_CLR_64.
|
||||
- **BinaryType** A binary type. Example: UNINITIALIZED, ZERO_BYTE, DATA_ONLY, DOS_MODULE, NE16_MODULE, PE32_UNKNOWN, PE32_I386, PE32_ARM, PE64_UNKNOWN, PE64_AMD64, PE64_ARM64, PE64_IA64, PE32_CLR_32, PE32_CLR_IL, PE32_CLR_IL_PREFER32, PE64_CLR_64.
|
||||
- **BinFileVersion** An attempt to clean up FileVersion at the client that tries to place the version into 4 octets.
|
||||
- **BinProductVersion** An attempt to clean up ProductVersion at the client that tries to place the version into 4 octets.
|
||||
- **BoeProgramId** If there's no entry in Add/Remove Programs, this is the ProgramID that is generated from the file metadata.
|
||||
@ -997,7 +996,7 @@ The following fields are available:
|
||||
- **AzureOSIDPresent** Represents the field used to identify an Azure machine.
|
||||
- **AzureVMType** Represents whether the instance is Azure VM PAAS, Azure VM IAAS or any other VMs.
|
||||
- **CDJType** Represents the type of cloud domain joined for the machine.
|
||||
- **CommercialId** Represents the GUID for the commercial entity that the device is a member of. Will be used to reflect insights back to customers.
|
||||
- **CommercialId** Represents the GUID for the commercial entity that the device is a member of. Will be used to reflect insights back to customers.
|
||||
- **ContainerType** The type of container, such as process or virtual machine hosted.
|
||||
- **EnrollmentType** Defines the type of MDM enrollment on the device.
|
||||
- **HashedDomain** The hashed representation of the user domain used for login.
|
||||
@ -1065,7 +1064,7 @@ The following fields are available:
|
||||
- **IsPortableOperatingSystem** Retrieves whether OS is running Windows-To-Go
|
||||
- **IsSecureBootEnabled** Retrieves whether Boot chain is signed under UEFI.
|
||||
- **LanguagePacks** The list of language packages installed on the device.
|
||||
- **LicenseStateReason** Retrieves why (or how) a system is licensed or unlicensed. The HRESULT may indicate an error code that indicates a key blocked error, or it may indicate that we're running an OS License granted by the MS store.
|
||||
- **LicenseStateReason** Retrieves why (or how) a system is licensed or unlicensed. The HRESULT may indicate an error code that indicates a key blocked error, or it may indicate that we're running an OS License granted by the MS store.
|
||||
- **OA3xOriginalProductKey** Retrieves the License key stamped by the OEM to the machine.
|
||||
- **OSEdition** Retrieves the version of the current OS.
|
||||
- **OSInstallType** Retrieves a numeric description of what install was used on the device i.e. clean, upgrade, refresh, reset, etc
|
||||
@ -1118,7 +1117,7 @@ The following fields are available:
|
||||
- **InternalPrimaryDisplayPhysicalDPIY** Retrieves the physical DPI in the y-direction of the internal display.
|
||||
- **InternalPrimaryDisplayResolutionHorizontal** Retrieves the number of pixels in the horizontal direction of the internal display.
|
||||
- **InternalPrimaryDisplayResolutionVertical** Retrieves the number of pixels in the vertical direction of the internal display.
|
||||
- **InternalPrimaryDisplaySizePhysicalH** Retrieves the physical horizontal length of the display in mm. Used for calculating the diagonal length in inches .
|
||||
- **InternalPrimaryDisplaySizePhysicalH** Retrieves the physical horizontal length of the display in mm. Used for calculating the diagonal length in inches.
|
||||
- **InternalPrimaryDisplaySizePhysicalY** Retrieves the physical vertical length of the display in mm. Used for calculating the diagonal length in inches
|
||||
- **NumberofExternalDisplays** Retrieves the number of external displays connected to the machine
|
||||
- **NumberofInternalDisplays** Retrieves the number of internal displays in a machine.
|
||||
@ -1281,7 +1280,7 @@ The following fields are available:
|
||||
- **popSample** Represents the effective sample rate for this event at the time it was generated by a client.
|
||||
- **providerGuid** The ETW provider ID associated with the provider name.
|
||||
- **raId** Represents the ETW Related ActivityId. Logged via TraceLogging or directly via ETW.
|
||||
- **seq** Represents the sequence field used to track absolute order of uploaded events. It's an incrementing identifier for each event added to the upload queue. The Sequence helps track how many events were fired and how many events were uploaded and enables identification of data lost during upload and de-duplication of events on the ingress server.
|
||||
- **seq** Represents the sequence field used to track absolute order of uploaded events. It's an incrementing identifier for each event added to the upload queue. The Sequence helps track how many events were fired and how many events were uploaded and enables identification of data lost during upload and de-duplication of events on the ingress server.
|
||||
- **sqmId** The Windows SQM (Software Quality Metrics—a precursor of Windows 10 Diagnostic Data collection) device identifier.
|
||||
- **stId** Represents the Scenario Entry Point ID. This is a unique GUID for each event in a diagnostic scenario. This used to be Scenario Trigger ID.
|
||||
- **wcmp** The Windows Shell Composer ID.
|
||||
@ -2932,7 +2931,7 @@ The following fields are available:
|
||||
|
||||
### Setup360Telemetry.PreInstallUX
|
||||
|
||||
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 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.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -3167,7 +3166,7 @@ The following fields are available:
|
||||
|
||||
### Microsoft.Windows.StoreAgent.Telemetry.EndGetInstalledContentIds
|
||||
|
||||
This event is sent after sending the inventory of the products installed to determine whether updates for those products are available. It's 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. It's used to help keep Windows up-to-date and secure.
|
||||
|
||||
The following fields are available:
|
||||
|
||||
@ -3561,7 +3560,7 @@ This event sends data on whether Update Management Policies were enabled on a de
|
||||
The following fields are available:
|
||||
|
||||
- **configuredPoliciescount** Number of policies on the device.
|
||||
- **policiesNamevaluesource** Policy name and source of policy (group policy, MDM or flight).
|
||||
- **policiesNamevaluesource** Policy name and source of policy (group policy, MDM, or flight).
|
||||
- **updateInstalluxsetting** Indicates whether a user has set policies via a user experience option.
|
||||
|
||||
|
||||
|
||||
@ -28,7 +28,6 @@ Use this article to learn about diagnostic events, grouped by event area, and th
|
||||
You can learn more about Windows functional and diagnostic data through these articles:
|
||||
|
||||
- [Required diagnostic events and fields for Windows 11, versions 23H2 and 22H2](required-diagnostic-events-fields-windows-11-22H2.md)
|
||||
- [Required diagnostic events and fields for Windows 11, version 21H2](required-windows-11-diagnostic-events-and-fields.md)
|
||||
- [Required diagnostic events and fields for Windows 10, versions 22H2 and 21H2](required-windows-diagnostic-data-events-and-fields-2004.md)
|
||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -33,7 +33,6 @@ You can learn more about Windows functional and diagnostic data through these ar
|
||||
|
||||
- [Required diagnostic events and fields for Windows 11, version 24H2](required-diagnostic-events-fields-windows-11-24H2.md)
|
||||
- [Required diagnostic events and fields for Windows 11, versions 23H2 and 22H2](required-diagnostic-events-fields-windows-11-22H2.md)
|
||||
- [Required diagnostic events and fields for Windows 11, version 21H2](required-windows-11-diagnostic-events-and-fields.md)
|
||||
- [Windows 10, version 1809 basic diagnostic events and fields](basic-level-windows-diagnostic-events-and-fields-1809.md)
|
||||
- [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md)
|
||||
- [Configure Windows diagnostic data in your organization](configure-windows-diagnostic-data-in-your-organization.md)
|
||||
|
||||
@ -17,8 +17,6 @@
|
||||
href: required-diagnostic-events-fields-windows-11-24H2.md
|
||||
- name: Windows 11, versions 23H2 and 22H2
|
||||
href: required-diagnostic-events-fields-windows-11-22H2.md
|
||||
- name: Windows 11, version 21H2
|
||||
href: required-windows-11-diagnostic-events-and-fields.md
|
||||
- name: Windows 10, versions 22H2 and 21H2
|
||||
href: required-windows-diagnostic-data-events-and-fields-2004.md
|
||||
- name: Windows 10, version 1809
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user