diff --git a/.github/workflows/AutoPublish.yml b/.github/workflows/AutoPublish.yml
index a7e46e4f16..c067d8f47b 100644
--- a/.github/workflows/AutoPublish.yml
+++ b/.github/workflows/AutoPublish.yml
@@ -3,10 +3,11 @@ name: (Scheduled) Publish to live
permissions:
contents: write
pull-requests: write
+ checks: read
on:
schedule:
- - cron: "25 5,11,17,22 * * *" # Times are UTC based on Daylight Saving Time. Need to be adjusted for Standard Time. Scheduling at :25 to account for queuing lag.
+ - cron: "25 2,5,8,11,14,17,20,22 * * *" # Times are UTC based on Daylight Saving Time. Need to be adjusted for Standard Time. Scheduling at :25 to account for queuing lag.
workflow_dispatch:
@@ -14,10 +15,11 @@ jobs:
auto-publish:
if: github.repository_owner == 'MicrosoftDocs' && contains(github.event.repository.topics, 'build')
- uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoPublish.yml@workflows-prod
+ uses: MicrosoftDocs/microsoft-365-docs/.github/workflows/Shared-AutoPublishV2.yml@workflows-prod
with:
PayloadJson: ${{ toJSON(github) }}
EnableAutoPublish: true
+ EnableAutoMerge: true
secrets:
AccessToken: ${{ secrets.GITHUB_TOKEN }}
diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-edge.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-edge.md
index 409b518326..ad4f28e24c 100644
--- a/windows/deployment/windows-autopatch/manage/windows-autopatch-edge.md
+++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-edge.md
@@ -77,8 +77,8 @@ If you [created an Autopatch group](../manage/windows-autopatch-manage-autopatch
1. The following new policies should be discoverable from the list of profiles:
1. `"Windows Autopatch Microsoft Edge Update Policy - Microsoft uses diagnostic data to keep Windows secure, up to date, troubleshoot problems, and make product improvements. Regardless of what choices you make for diagnostic data collection, the device will be just as secure and will operate normally. This data is collected by Microsoft to quickly identify and address issues affecting its customers. Diagnostic data is categorized into the following:
v10c.events.data.microsoft.com
v10.vortex-win.data.microsoft.com |
| [Windows Error Reporting](/windows/win32/wer/windows-error-reporting) | watson.telemetry.microsoft.com
umwatsonc.events.data.microsoft.com
*-umwatsonc.events.data.microsoft.com
ceuswatcab01.blob.core.windows.net
ceuswatcab02.blob.core.windows.net
eaus2watcab01.blob.core.windows.net
eaus2watcab02.blob.core.windows.net
weus2watcab01.blob.core.windows.net
weus2watcab02.blob.core.windows.net |
-|Authentication | login.live.com
IMPORTANT: This endpoint is used for device authentication. We do not recommend disabling this endpoint.|
+|Authentication | login.live.com
IMPORTANT: This endpoint is used for device authentication. We don't recommend disabling this endpoint.|
| [Online Crash Analysis](/windows/win32/dxtecharts/crash-dump-analysis) | oca.telemetry.microsoft.com
oca.microsoft.com
kmwatsonc.events.data.microsoft.com
*-kmwatsonc.events.data.microsoft.com |
-|Settings | settings-win.data.microsoft.com
IMPORTANT: This endpoint is required to remotely configure diagnostics-related settings and data collection. For example, we use the settings endpoint to remotely block an event from being sent back to Microsoft, or to enroll a device in the Windows diagnostic data processor configuration. Do not block access to this endpoint. This endpoint does not upload Windows diagnostic data. |
+|Settings | settings-win.data.microsoft.com
IMPORTANT: This endpoint is required to remotely configure diagnostics-related settings and data collection. For example, we use the settings endpoint to remotely block an event from being sent back to Microsoft, or to enroll a device in the Windows diagnostic data processor configuration. Don't block access to this endpoint. This endpoint doesn't upload Windows diagnostic data. |
### Proxy server authentication
@@ -109,7 +110,7 @@ Configure devices to use the signed-in user's context for proxy authentication.
- Make sure that the users have proxy permission to reach the diagnostic data endpoints. This option requires that the devices have console users with proxy permissions, so you can't use this method with headless devices.
> [!IMPORTANT]
-> The user proxy authentication approach is incompatible with the use of Microsoft Defender for Endpoint. This behavior is because this authentication relies on the **DisableEnterpriseAuthProxy** registry key set to `0`, while Microsoft Defender for Endpoint requires it to be set to `1`. For more information, see [Configure machine proxy and internet connectivity settings in Microsoft Defender for Endpoint](/windows/security/threat-protection/windows-defender-atp/configure-proxy-internet-windows-defender-advanced-threat-protection).
+> The user proxy authentication approach is incompatible with the use of Microsoft Defender for Endpoint. This behavior is because this authentication relies on the **DisableEnterpriseAuthProxy** registry key set to `0`, while Microsoft Defender for Endpoint requires it to be set to `1`. For more information, see [Configure your devices to connect to the Defender for Endpoint service using a proxy](/defender-endpoint/configure-proxy-internet).
#### Device proxy authentication
@@ -139,11 +140,11 @@ This approach is the most complex because it requires the following configuratio
### Data access
-The principle of least privileged access guides access to Windows diagnostic data. Microsoft does not share personal data of our customers with third parties, except at the customer’s discretion or for the limited purposes described in the [Privacy Statement](https://www.microsoft.com/privacy/privacystatement). Microsoft may share business reports with hardware manufacturers and third-party partners that include aggregated and deidentified diagnostic data information. Data-sharing decisions are made by an internal team including privacy, legal, and data management.
+The principle of least privileged access guides access to Windows diagnostic data. Microsoft doesn't share personal data of our customers with third parties, except at the customer’s discretion or for the limited purposes described in the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement). Microsoft may share business reports with hardware manufacturers and third-party partners that include aggregated and deidentified diagnostic data information. Data-sharing decisions are made by an internal team including privacy, legal, and data management.
### Retention
-Microsoft believes in and practices data minimization. We strive to gather only the info we need and to store it only for as long as it’s needed to provide a service or for analysis. For more information on how long data is retained, see the section named **Our retention of personal data** in the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement).
+Microsoft believes in and practices data minimization. We strive to gather only the info we need and to store it only for as long as it’s needed to provide a service or for analysis. For more information on how long data is retained, see the section named **Our retention of personal data** in the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement#mainOurretentionofpersonaldatamodule).
## Diagnostic data settings
@@ -151,7 +152,7 @@ There are four diagnostic data collection settings. Each setting is described in
- Diagnostic data off (Security)
- Required diagnostic data (Basic)
-- Enhanced (This setting is only available on devices running Windows 10, Windows Server 2016, and Windows Server 2019.)
+- Enhanced (This setting is only available on devices running Windows 10 version 1809 and earlier, Windows Server 2016, and Windows Server 2019.)
- Optional diagnostic data (Full)
Here’s a summary of the types of data that is included with each setting:
@@ -172,13 +173,13 @@ This setting was previously labeled as **Security**. When you configure this set
This was the default setting for Windows Server 2022 Datacenter: Azure Edition prior to December 13, 2022.
>[!NOTE]
-> If your organization relies on Windows Update, the minimum recommended setting is **Required diagnostic data**. Because no Windows Update information is collected when diagnostic data is off, important information about update failures is not sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates.
+> If your organization relies on Windows Update, the minimum recommended setting is **Required diagnostic data**. Because no Windows Update information is collected when diagnostic data is off, important information about update failures isn't sent. Microsoft uses this information to fix the causes of those failures and improve the quality of our updates.
### Required diagnostic data
Required diagnostic data, previously labeled as **Basic**, gathers a limited set of data that’s critical for understanding the device and its configuration. This data helps to identify problems that can occur on a specific hardware or software configuration. For example, it can help determine if crashes are more frequent on devices with a specific amount of memory or that are running a specific driver version.
-This is the default setting for current releases of Windows, Windows 10, version 1903. Beginning December 13, 2022, it is also the default setting for Windows Server 2022 Datacenter: Azure Edition.
+This is the default setting for Windows 10, version 1903 and later. Beginning December 13, 2022, it's also the default setting for Windows Server 2022 Datacenter: Azure Edition.
Required diagnostic data includes:
@@ -208,10 +209,10 @@ Required diagnostic data includes:
### Enhanced diagnostic data
-In Windows 10 and Windows Server 2019, enhanced diagnostic data includes data about the websites you browse, how Windows and apps are used and how they perform, and device activity. The additional data helps Microsoft to fix and improve products and services for all users.
+In Windows 10 (version 1809 and earlier) and Windows Server 2019, enhanced diagnostic data includes data about the websites you browse, how Windows and apps are used and how they perform, and device activity. The additional data helps Microsoft to fix and improve products and services for all users.
>[!Important]
->This diagnostic data setting is not available on Windows 11 and Windows Server 2022 and has been replaced with policies that can control the amount of optional diagnostic data that is sent. More information on these settings are available in the **Manage diagnostic data using Group Policy and MDM** section of this topic.
+>This diagnostic data setting is not available on Windows 11 and Windows Server 2022 and has been replaced with policies that can control the amount of optional diagnostic data that is sent. More information on these settings are available in the [Manage diagnostic data using Group Policy and MDM](#manage-diagnostic-data-using-group-policy-and-mdm) section of this article.
When you choose to send enhanced diagnostic data, required diagnostic data will always be included, and we collect the following additional information:
@@ -245,7 +246,11 @@ Optional diagnostic data, previously labeled as **Full**, includes more detailed
Use the steps in this section to configure the diagnostic data settings for Windows and Windows Server in your organization.
>[!IMPORTANT]
->These diagnostic data settings only apply to components, features, and apps that are considered a part of the Windows operating system. Third-party apps and other Microsoft apps, such as Microsoft Office, that customers install may also collect and send diagnostic data using their own controls. You should work with your app vendors to understand their diagnostic data policy, and how you can opt in or opt out. For more information on how Microsoft Office uses diagnostic data, see [Overview of privacy controls for Microsoft 365 Apps for enterprise](/deployoffice/privacy/overview-privacy-controls). If you would like to control Windows data collection that is not Windows diagnostic data, see [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md).
+>- These diagnostic data settings only apply to components, features, and apps that are considered a part of the Windows operating system.
+>- Third-party apps and other Microsoft apps, such as Microsoft 365 Apps, that customers install may also collect and send diagnostic data using their own controls.
+>- You should work with your app vendors to understand their diagnostic data policy, and how you can opt in or opt out.
+>- For more information on how Microsoft 365 Apps uses diagnostic data, see [Overview of privacy controls for Microsoft 365 Apps for enterprise](/microsoft-365-apps/privacy/overview-privacy-controls).
+>- If you would like to control Windows data collection that isn't Windows diagnostic data, see [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md).
You can configure your device's diagnostic data settings using the management tools you’re already using, such as Group Policy or MDM.
@@ -267,12 +272,12 @@ You can use Group Policy to set your organization’s diagnostic data setting:
1. From the Group Policy Management Console, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Data Collection and Preview Builds**.
-2. Double-click **Allow Telemetry** (or **Allow diagnostic data** on Windows 11 and Windows Server 2022).
+2. Double-click **Allow diagnostic data** (or **Allow telemetry** on Windows 10 version 1809 and earlier, and on Windows Server 2019).
> [!NOTE]
> If devices in your organization are running Windows 10, 1803 and later, the user can still use Settings to set the diagnostic data setting to a more restrictive value, unless the **Configure diagnostic data opt-in settings user interface** policy is set.
-3. In the **Options** box, choose the setting that you want to configure, and then click **OK**.
+3. In the **Options** box, choose the setting that you want to configure, and then select **OK**.
### Use Group Policy to manage optional diagnostic data collection
@@ -283,15 +288,15 @@ The following policy lets you limit the types of [crash dumps](/windows/win32/dx
2. Double-click **Limit dump collection**.
-3. In the **Options** box, choose the setting that you want to configure, and then click **OK**.
+3. In the **Options** box, choose the setting that you want to configure, and then select **OK**.
-You can also limit the number of diagnostic logs that are sent back to Microsoft. If this policy is enabled, diagnostic logs are not sent back to Microsoft.
+You can also limit the number of diagnostic logs that are sent back to Microsoft. If this policy is enabled, diagnostic logs aren't sent back to Microsoft.
1. From the Group Policy Management Console, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Data Collection and Preview Builds**.
2. Double-click **Limit diagnostic log collection**.
-3. In the **Options** box, choose the setting that you want to configure, and then click **OK**.
+3. In the **Options** box, choose the setting that you want to configure, and then select **OK**.
### Use MDM to manage diagnostic data collection
@@ -315,10 +320,10 @@ The Windows diagnostic data processor configuration enables you to be the contro
- Enterprise
- Professional
- Education
-- The device must be joined to Azure Active Directory (can be a hybrid Azure AD join).
+- The device must be joined to Microsoft Entra (can be a Microsoft Entra hybrid join).
> [!NOTE]
-> In all cases, enrollment in the Windows diagnostic data processor configuration requires a device to be joined to an Azure AD tenant. If a device isn't properly enrolled, Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
+> In all cases, enrollment in the Windows diagnostic data processor configuration requires a device to be joined to a Microsoft Entra tenant. If a device isn't properly enrolled, Microsoft will act as the controller for Windows diagnostic data in accordance with the [Microsoft Privacy Statement](https://www.microsoft.com/privacy/privacystatement) and the [Data Protection Addendum](https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA) terms won't apply.
For the best experience, use the most current build of any operating system specified above. Configuration functionality and availability may vary on older systems. For release information, see [Windows 10 Enterprise and Education](/lifecycle/products/windows-10-enterprise-and-education) and [Windows 11 Enterprise and Education](/lifecycle/products/windows-11-enterprise-and-education) on the Microsoft Lifecycle Policy site.
@@ -339,24 +344,24 @@ Tenants with billing addresses in countries or regions in the Middle East and Af
> [!NOTE]
> The information in this section applies to the following versions of Windows:
-> - Windows 10, versions 20H2, 21H2, 22H2, and newer
-> - Windows 11, versions 21H2, 22H2, 23H2, and newer
+> - Windows 10, versions 20H2 and newer
+> - Windows 11, versions 21H2 and newer
-Starting with the January 2023 preview cumulative update, how you enable the processor configuration option depends on the billing address of the Azure AD tenant to which your devices are joined.
+Starting with the January 2023 preview cumulative update, how you enable the processor configuration option depends on the billing address of the Microsoft Entra tenant to which your devices are joined.
-#### Devices in Azure AD tenants with a billing address in the European Union (EU) or European Free Trade Association (EFTA)
+#### Devices in Microsoft Entra tenants with a billing address in the European Union (EU) or European Free Trade Association (EFTA)
-For Windows devices with diagnostic data turned on and that are joined to an [Azure AD tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) in the EU or EFTA, the Windows diagnostic data for that device will be automatically configured for the processor option. The Windows diagnostic data for those devices will be processed in Europe.
+For Windows devices with diagnostic data turned on and that are joined to an [Microsoft Entra tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) in the EU or EFTA, the Windows diagnostic data for that device will be automatically configured for the processor option. The Windows diagnostic data for those devices will be processed in Europe.
From a compliance standpoint, this change means that Microsoft will be the processor and the organization will be the controller of the Windows diagnostic data. IT admins for those organizations will become responsible for responding to their users’ [data subject requests](/compliance/regulatory/gdpr-dsr-windows).
-#### Devices in Azure AD tenants with a billing address outside of the EU and EFTA
+#### Devices in Microsoft Entra tenants with a billing address outside of the EU and EFTA
-For Windows devices with diagnostic data turned on and that are joined to an [Azure AD tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) outside of the EU and EFTA, to enable the processor configuration option, the organization must sign up for any of the following enterprise services, which rely on diagnostic data:
+For Windows devices with diagnostic data turned on and that are joined to an [Microsoft Entra tenant with billing address](/azure/cost-management-billing/manage/change-azure-account-profile) outside of the EU and EFTA, to enable the processor configuration option, the organization must sign up for any of the following enterprise services, which rely on diagnostic data:
- [Windows Update for Business reports](/windows/deployment/update/wufb-reports-overview)
- [Windows Autopatch](/windows/deployment/windows-autopatch/overview/windows-autopatch-overview)
-- [Windows updates reports (in Microsoft Intune)](/mem/intune/protect/data-enable-windows-data#windows-data)
+- [Windows updates reports (in Microsoft Intune)](/intune/intune-service/protect/data-enable-windows-data#windows-data)
*(Additional licensing requirements may apply to use these services.)*
@@ -367,15 +372,15 @@ If you don’t sign up for any of these enterprise services, Microsoft will act
> [!NOTE]
> The information in this section applies to the following versions of Windows:
> - Windows 10, versions 1809, 1903, 1909, and 2004.
-> - Newer versions of Windows 10 and Windows 11 that have not updated yet to at least the January 2023 preview cumulative update.
+> - Newer versions of Windows 10 and Windows 11 that haven't updated yet to at least the January 2023 preview cumulative update.
To enable Windows diagnostic data processor configuration, you can use Group Policy or a custom setting in an MDM solution, such as Microsoft Intune.
-- For Group Policy, you can use the “Allow commercial data pipeline” policy, which is also available in the Intune [settings catalog](/mem/intune/configuration/settings-catalog).
+- For Group Policy, you can use the "Allow commercial data pipeline" policy, which is also available in the Intune [settings catalog](/intune/intune-service/configuration/settings-catalog).
- For an MDM solution, you can use the AllowCommercialDataPipeline setting in the System Policy configuration service provider (CSP).
-For more information about AllowCommercialDataPipeline and the “Allow commercial data pipeline” policy, [review this information](/windows/client-management/mdm/policy-csp-system#allowcommercialdatapipeline).
+For more information about AllowCommercialDataPipeline and the "Allow commercial data pipeline" policy, [review this information](/windows/client-management/mdm/policy-csp-system#allowcommercialdatapipeline).
## Change privacy settings on a single server
-You can also change the privacy settings on a server running either the Azure Stack HCI operating system or Windows Server. For more information, see [Change privacy settings on individual servers](/azure-stack/hci/manage/change-privacy-settings).
+You can also change the privacy settings on a server running either the Azure Stack HCI operating system or Windows Server. For more information, see [Change privacy settings on individual servers](/azure/azure-local/manage/change-privacy-settings).
diff --git a/windows/privacy/diagnostic-data-viewer-overview.md b/windows/privacy/diagnostic-data-viewer-overview.md
index a794a57c74..2ef8b38b94 100644
--- a/windows/privacy/diagnostic-data-viewer-overview.md
+++ b/windows/privacy/diagnostic-data-viewer-overview.md
@@ -1,5 +1,5 @@
---
-title: Diagnostic Data Viewer Overview (Windows 10 and Windows 11)
+title: Diagnostic Data Viewer overview
description: Use this article to use the Diagnostic Data Viewer application to review the diagnostic data sent to Microsoft by your device.
ms.service: windows-client
ms.subservice: itpro-privacy
@@ -7,175 +7,158 @@ ms.localizationpriority: high
author: DHB-MSFT
ms.author: danbrown
manager: dansimp
-ms.date: 01/09/2018
+ms.date: 05/30/2025
ms.topic: how-to
+hideEdit: true
ms.collection:
- privacy-windows
- must-keep
---
-# Diagnostic Data Viewer Overview
+# Diagnostic Data Viewer overview
**Applies to**
- Windows 11, version 21H2 and later
- Windows 10, version 1803 and later
-## Introduction
-
The Diagnostic Data Viewer is a Windows app that lets you review the Windows diagnostic data your device is sending to Microsoft, grouping the info into simple categories based on how it's used by Microsoft.
-## Install and Use the Diagnostic Data Viewer
+## Install the Diagnostic Data Viewer
-You must download the app before you can use the Diagnostic Data Viewer to review your device's diagnostic data.
+You must download the app before you can use the Diagnostic Data Viewer to review your device's diagnostic data. You can download the app from the [Microsoft Store Diagnostic Data Viewer](https://apps.microsoft.com/detail/9n8wtrrsq8f7) page.
-### Turn on data viewing
+> [!NOTE]
+> It's possible that your Windows device doesn't have the Microsoft Store available (for example, Windows Server). If this is the case, see [Diagnostic Data Viewer for PowerShell overview](diagnostic-data-viewer-powershell.md).
-Before you can use this tool for viewing Windows diagnostic data, you must turn on data viewing in the **Settings** panel. Turning on data viewing lets Windows store your device's diagnostic data until you turn it off. Turning off data viewing stops Windows from collecting your diagnostic data and clears the existing diagnostic data from your device. Note that this setting does not affect your Office data viewing or history.
+## Turn on data viewing
-**To turn on data viewing**
+Before you can use the app for viewing Windows diagnostic data, you must turn on data viewing in the **Settings** panel. Turning on data viewing lets Windows store your device's diagnostic data until you turn it off. Turning off data viewing stops Windows from collecting your diagnostic data and clears the existing diagnostic data from your device. This setting doesn't affect your data viewing or history for Microsoft 365 Apps or Microsoft Office.
-1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
+>[!Important]
+>Turning on data viewing can use up to 1 GB (by default) of disk space on your system drive. We strongly recommend that you turn off data viewing when you're done using the Diagnostic Data Viewer. For info about turning off data viewing, see the [Turn off data viewing](#turn-off-data-viewing) section later in this article.
-2. Under **Diagnostic data**, turn on the **If data viewing is enabled, you can see your diagnostics data** option.
+To turn on data viewing, do the following steps:
- 
+1. Go to **Start**, select **Settings** > **Privacy & security** > **Diagnostics & feedback**.
-### Download the Diagnostic Data Viewer
+2. Under **View diagnostic data**, turn on the **Turn on the Diagnostic Data Viewer** option.
-Download the app from the [Microsoft Store Diagnostic Data Viewer](https://www.microsoft.com/store/p/diagnostic-data-viewer/9n8wtrrsq8f7?rtc=1) page.
+## Start the Diagnostic Data Viewer
-> [!Important]
-> It's possible that your Windows device doesn't have the Microsoft Store available (for example, Windows Server). If this is the case, see [Diagnostic Data Viewer for PowerShell](./diagnostic-data-viewer-powershell.md).
+To start the Diagnostic Data Viewer, do the following steps:
-### Start the Diagnostic Data Viewer
+1. Go to **Start**, select **Settings** > **Privacy & security** > **Diagnostics & feedback**.
-You can start this app from the **Settings** panel.
+ (You can also go to **Start** and search for *Diagnostic Data Viewer*.)
-**To start the Diagnostic Data Viewer**
+2. Under **View diagnostic data**, select the **Open Diagnostic Data Viewer** button.
-1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
+3. Close the Diagnostic Data Viewer. Use your device as you normally would for a few days. Then open the Diagnostic Data Viewer again to review the updated list of diagnostic data.
-2. Under **Diagnostic data**, select the **Diagnostic Data Viewer** button.
-
- 
-OR-
-
- Go to **Start** and search for _Diagnostic Data Viewer_.
-
-3. Close the Diagnostic Data Viewer app, use your device as you normally would for a few days, and then open Diagnostic Data Viewer again to review the updated list of diagnostic data.
-
- >[!Important]
- >Turning on data viewing can use up to 1GB (by default) of disk space on your system drive. We strongly recommend that you turn off data viewing when you're done using the Diagnostic Data Viewer. For info about turning off data viewing, see the [Turn off data viewing](#turn-off-data-viewing) section in this article.
-
-### Use the Diagnostic Data Viewer
+## Use the Diagnostic Data Viewer
The Diagnostic Data Viewer provides you with the following features to view and filter your device's diagnostic data.
-- **View your Windows diagnostic events.** In the left column, you can review your diagnostic events. These events reflect activities that occurred and were sent to Microsoft.
+### View your Windows diagnostic events
- Selecting an event opens the detailed JSON view, which provides the exact details uploaded to Microsoft. Microsoft uses this info to continually improve the Windows operating system.
+In the left column, you can review your diagnostic events. These events reflect activities that occurred and were sent to Microsoft.
- >[!Important]
- >Seeing an event does not necessarily mean it has been uploaded yet. It’s possible that some events are still queued and will be uploaded at a later time.
+Selecting an event opens the detailed JSON view, which provides the exact details uploaded to Microsoft. Microsoft uses this info to continually improve the Windows operating system.
- 
+>[!NOTE]
+>Seeing an event doesn't necessarily mean it has been uploaded yet. It’s possible that some events are still queued and will be uploaded at a later time.
-- **Search your diagnostic events.** The **Search** box at the top of the screen lets you search amongst all of the diagnostic event details. The returned search results include any diagnostic event that contains the matching text.
+
- Selecting an event opens the detailed JSON view, with the matching text highlighted.
+### Search your diagnostic events
-- **Filter your diagnostic event categories.** The app's **Menu** button opens the detailed menu. In here, you'll find a list of diagnostic event categories, which define how the events are used by Microsoft. Selecting a check box lets you filter between the diagnostic event categories.
+The **Search** box at the top of the screen lets you search among all of the diagnostic event details. The returned search results include any diagnostic event that contains the matching text.
-- **Help to make your Windows experience better.** Microsoft only needs diagnostic data from a small amount of devices to make big improvements to the Windows operating system and ultimately, your experience. If you’re a part of this small device group and you experience issues, Microsoft will collect the associated event diagnostic data, allowing your info to potentially help fix the issue for others.
+Selecting an event opens the detailed JSON view, with the matching text highlighted.
- To signify your contribution, you’ll see this icon () if your device is part of the group. In addition, if any of your diagnostic data events are sent from your device to Microsoft to help make improvements, you’ll see this icon ().
+### Filter your diagnostic event categories
-- **Provide diagnostic event feedback.** The **Feedback** icon in the upper right corner of the window opens the Feedback Hub app, letting you provide feedback about the Diagnostic Data Viewer and the diagnostic events.
+The app's **Menu** button opens the detailed menu. In here, you can find a list of diagnostic event categories, which define how the events are used by Microsoft. Selecting a check box lets you filter between the diagnostic event categories.
- Selecting a specific event in the Diagnostic Data Viewer automatically fills in the field in the Feedback Hub. You can add your comments to the box labeled, **Give us more detail (optional)**.
+### Help to make your Windows experience better
- >[!Important]
- >All content in the Feedback Hub is publicly viewable. Therefore, make sure you don't put any personal info into your feedback comments.
+Microsoft only needs diagnostic data from a small number of devices to make big improvements to the Windows operating system and ultimately, your experience. If you’re a part of this small device group and you experience issues, Microsoft collects the associated event diagnostic data, allowing your info to potentially help fix the issue for others.
-- **View a summary of the data you've shared with us over time.** Available for users on build 19H1+, 'About my data' in Diagnostic Data Viewer lets you see an overview of the Windows data you've shared with Microsoft.
+To signify your contribution, you’ll see this icon () if your device is part of the group. In addition, if any of your diagnostic data events are sent from your device to Microsoft to help make improvements, you’ll see this icon ().
- Through this feature, you can checkout how much data you send on average each day, the breakdown of your data by category, the top components and services that have sent data, and more.
+### Provide event feedback
- >[!Important]
- >This content is a reflection of the history of Windows data the app has stored. If you'd like to have extended analyses, please modify the storage capacity of Diagnostic Data Viewer.
+The **Feedback** icon in the upper right corner of the window opens the Feedback Hub app, letting you provide feedback about the Diagnostic Data Viewer and the diagnostic events.
- 
+Selecting a specific event in the Diagnostic Data Viewer automatically fills in the field in the Feedback Hub. You can add your comments to the box labeled, **Give us more detail (optional)**.
-## View Office Diagnostic Data
+>[!IMPORTANT]
+>All content in the Feedback Hub is publicly viewable. Therefore, make sure you don't put any personal info into your feedback comments.
-By default, Diagnostic Data Viewer shows you Windows data. You can also view Office diagnostic data by enabling the feature in the app settings page. To learn more about how to view Office diagnostic data, please visit this [page](https://go.microsoft.com/fwlink/?linkid=2023830).
+### View a summary of the data you've shared with us over time
+
+The **About your data** in the Diagnostic Data Viewer lets you see an overview of the Windows data you've shared with Microsoft.
+
+Through this feature, you can see how much data you send on average each day, the breakdown of your data by category, the top components and services that have sent data, and more.
+
+>[!NOTE]
+>This content is a reflection of the history of Windows data that the app has stored. If you'd like to have extended analyses, modify the storage capacity of the Diagnostic Data Viewer.
+
+
+
+## View Microsoft 365 Apps or Microsoft Office diagnostic data
+
+By default, the Diagnostic Data Viewer shows you Windows data. You can also view Microsoft 365 Apps or Microsoft Office diagnostic data by enabling the feature in the app settings page. To learn more about how to view Microsoft 365 Apps or Microsoft Office diagnostic data, see [Using the Diagnostic Data Viewer with Office](https://support.microsoft.com/office/cf761ce9-d805-4c60-a339-4e07f3182855).
## Turn off data viewing
-When you're done reviewing your diagnostic data, you should turn of data viewing. This will also remove your Windows data history. Note that this setting does not affect your Office data viewing or history.
+When you're done reviewing your diagnostic data, you should turn off data viewing. This also removes your Windows data history. This setting doesn't affect your data viewing or history for Microsoft 365 Apps or Microsoft Office.
-**To turn off data viewing**
+To turn off data viewing, do the following steps:
-1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
+1. Go to **Start**, select **Settings** > **Privacy & security** > **Diagnostics & feedback**.
-2. Under **Diagnostic data**, turn off the **If data viewing is enabled, you can see your diagnostics data** option.
-
- 
+2. Under **View diagnostic data**, turn off the **Turn on the Diagnostic Data Viewer** option.
## Modifying the size of your data history
-By default, Diagnostic Data Viewer shows you up to 1GB or 30 days of data (whichever comes first) for Windows diagnostic data. Once either the time or space limit is reached, the data is incrementally dropped with the oldest data points dropped first.
+By default, the Diagnostic Data Viewer shows you up to 1 GB or 30 days of data (whichever comes first) for Windows diagnostic data. Once either the time or space limit is reached, the data is incrementally dropped with the oldest data points dropped first.
> [!Important]
-> Note that if you have [Office diagnostic data viewing enabled](#view-office-diagnostic-data), the Office data history is fixed at 1 GB and cannot be modified.
+> If you have [diagnostic data viewing enabled](#view-microsoft-365-apps-or-microsoft-office-diagnostic-data) for Microsoft 365 Apps or Microsoft Office, their data history is fixed at 1 GB and cannot be modified.
**Modify the size of your data history**
-To make changes to the size of your Windows diagnostic data history, visit the **app settings**, located at the bottom of the navigation menu. Data will be incrementally dropped with the oldest data points first once your chosen size or time limit is reached.
+To make changes to the size of your Windows diagnostic data history, visit the **app settings**, located at the bottom of the navigation menu. Data is incrementally dropped with the oldest data points first once your chosen size or time limit is reached.
> [!Important]
> Decreasing the maximum amount of diagnostic data viewable through the tool will remove all data history and requires a reboot of your device. Additionally, increasing the maximum amount of diagnostic data viewable by the tool may come with performance impacts to your machine.
-## View additional diagnostic data in the View problem reports tool
+## View additional diagnostic data in the "View problem reports" tool
-Available on Windows 10 1809 and higher and Windows 11, you can review additional Windows Error Reporting diagnostic data in the **View problem reports** page within the Diagnostic Data Viewer.
+Available on Windows 10 (version 1809 and higher) and on Windows 11, you can review additional Windows Error Reporting diagnostic data in the **View problem reports** page within the Diagnostic Data Viewer.
-This page provides you with a summary of various crash reports that are sent to Microsoft as part of Windows Error Reporting.
-We use this data to find and fix specific issues that are hard to replicate and to improve the Windows operating system.
+This page provides you with a summary of various crash reports that are sent to Microsoft as part of Windows Error Reporting. We use this data to find and fix specific issues that are hard to replicate and to improve the Windows operating system.
-You can also use the Windows Error Reporting tool available in the Control Panel.
+You can also use the Windows Error Reporting tool available in the Control Panel.
-**To view your Windows Error Reporting diagnostic data using the Diagnostic Data Viewer**
+### To view your Windows Error Reporting diagnostic data using the Diagnostic Data Viewer
-Starting with Windows 1809 and higher, you can review Windows Error Reporting diagnostic data in the Diagnostic Data Viewer.
+On Windows 10 (version 1809 and higher) and on Windows 11, you can review Windows Error Reporting diagnostic data in the Diagnostic Data Viewer.
-
+
-**To view your Windows Error Reporting diagnostic data using the Control Panel**
+### To view your Windows Error Reporting diagnostic data using the Control Panel
+
+To use the Windows Error Reporting tool in the Control Panel, you can do either of the following steps:
+
+- Go to **Start**, select **Control Panel** > **All Control Panel Items** > **Security and Maintenance** > **Problem Reports**.
+- Go to **Start** and search for *Problem Reports*.
-Go to **Start**, select **Control Panel** > **All Control Panel Items** > **Security and Maintenance** > **Problem Reports**.
-OR-
-Go to **Start** and search for _Problem Reports_.
The **Review problem reports** tool opens, showing you your Windows Error Reporting reports, along with a status about whether it was sent to Microsoft.
-
-
-## Known Issues with Diagnostic Data Viewer
-
-### Microsoft Edge diagnostic data appearing as a blob of text
-
-**Applicable to:** The new Microsoft Edge (v. 79.x.x.x or higher)
-
-**Issue:** In some cases, diagnostic data collected and sent from the New Microsoft Edge fails to be translated by the decoder. When decoding fails, the data appears as a blob of text in the Diagnostic Data Viewer. We are working on a fix for this issue.
-
-**Workaround:**
-
-- Restart your computer and open Diagnostic Data Viewer.
-
-*OR*
-
-- Restart the *DiagTrack* service, through the Services tab in task manager, and open Diagnostic Data Viewer.
-
-**Background:** Some of the diagnostic data collected from the new Microsoft Edge is sent using a Protocol Buffers (protobuf) to reduce network bandwidth and to improve data transfer efficiency. Diagnostic Data Viewer has a decoding capability to translate this protobuf format into human readable text. Due to a bug, sometimes the decoder fails to translate these protobuf messages and hence some of the New Microsoft Edge diagnostic data will appear as a blob of encoded text.
+
> [!IMPORTANT]
> To inquire about Windows data access or interoperability related to the Digital Markets Act (DMA), [submit this form](https://go.microsoft.com/fwlink/p/?linkid=2271128).
diff --git a/windows/privacy/diagnostic-data-viewer-powershell.md b/windows/privacy/diagnostic-data-viewer-powershell.md
index 54ed628d22..e108be2379 100644
--- a/windows/privacy/diagnostic-data-viewer-powershell.md
+++ b/windows/privacy/diagnostic-data-viewer-powershell.md
@@ -1,5 +1,5 @@
---
-title: Diagnostic Data Viewer for PowerShell Overview (Windows 10)
+title: Diagnostic Data Viewer for PowerShell overview
description: Use this article to use the Diagnostic Data Viewer for PowerShell to review the diagnostic data sent to Microsoft by your device.
ms.service: windows-client
ms.subservice: itpro-privacy
@@ -7,64 +7,68 @@ ms.localizationpriority: high
author: DHB-MSFT
ms.author: danbrown
manager: dansimp
-ms.date: 12/13/2018
+ms.date: 05/30/2025
ms.topic: how-to
+hideEdit: true
ms.collection:
- privacy-windows
- must-keep
---
-# Diagnostic Data Viewer for PowerShell Overview
+# Diagnostic Data Viewer for PowerShell overview
**Applies to**
-- Windows 11, version 21H2 and later
-- Windows 10, version 1803 and later
-- Windows Server, version 1803
-- Windows Server 2019
+- Windows 11, version 21H2 and later
+- Windows 10, version 1803 and later
+- Windows Server, version 1803
+- Windows Server 2019
-## Introduction
The Diagnostic Data Viewer for PowerShell is a PowerShell module that lets you review the diagnostic data your device is sending to Microsoft, grouping the info into simple categories based on how it's used by Microsoft.
-## Requirements
+> [!NOTE]
+> You must have administrative privilege on the device in order to use this PowerShell module.
-You must have administrative privilege on the device in order to use this PowerShell module. This module requires OS version 1803 and higher.
+## Install the Diagnostic Data Viewer for PowerShell
-## Install and Use the Diagnostic Data Viewer for PowerShell
+You must install the module before you can use the Diagnostic Data Viewer for PowerShell.
-You must install the module before you can use the Diagnostic Data Viewer for PowerShell.
+### Open an elevated PowerShell session
-### Opening an Elevated PowerShell session
-
-Using the Diagnostic Data Viewer for PowerShell requires administrative (elevated) privilege. There are two ways to open an elevated PowerShell prompt. You can use either method.
+Using the Diagnostic Data Viewer for PowerShell requires administrative (elevated) privilege. There are two ways to open an elevated PowerShell prompt. You can use either method.
- Go to **Start** > **Windows PowerShell** > **Run as administrator**
- Go to **Start** > **Command prompt** > **Run as administrator**, and run the command `C:\> powershell.exe`
### Install the Diagnostic Data Viewer for PowerShell
- >[!IMPORTANT]
- >It is recommended to visit the documentation on [Getting Started](/powershell/gallery/getting-started) with PowerShell Gallery. This page provides more specific details on installing a PowerShell module.
+>[!TIP]
+>For more information on installing a PowerShell module, see [Getting Started with the PowerShell Galley](/powershell/gallery/getting-started).
-To install the newest version of the Diagnostic Data Viewer PowerShell module, run the following command within an elevated PowerShell session:
+To install the newest version of the Diagnostic Data Viewer PowerShell module, run the following command within an elevated PowerShell session:
```powershell
PS C:\> Install-Module -Name Microsoft.DiagnosticDataViewer
```
-To see more information about the module, visit [PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer).
+For more information about the module, go to the [Microsoft.DiagnosticDataViewer](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer) page in the PowerShell Gallery.
### Turn on data viewing
-Before you can use this tool, you must turn on data viewing. Turning on data viewing enables Windows to store a local history of your device's diagnostic data for you to view until you turn it off.
-Note that this setting does not control whether your device sends diagnostic data. Instead, it controls whether your Windows device saves a local copy of the diagnostic data sent for your viewing.
+Before you can use this tool, you must turn on data viewing. Turning on data viewing enables Windows to store a local history of your device's diagnostic data for you to view until you turn it off.
-**To turn on data viewing through the Settings page**
-1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
+This setting doesn't control whether your device sends diagnostic data. Instead, it controls whether your Windows device saves a local copy of the diagnostic data sent for your viewing.
-2. Under **Diagnostic data**, turn on the **If data viewing is enabled, you can see your diagnostics data** option.
+Once data viewing is enabled, your device begins saving a history of diagnostic data that is sent to Microsoft from this point on.
- 
+>[!IMPORTANT]
+>Turning on data viewing can use up to 1 GB (default setting) of disk space on your system drive. We recommend that you turn off data viewing when you're done using the Diagnostic Data Viewer. For info about turning off data viewing, see the [Turn off data viewing](#turn-off-data-viewing) section later in this article.
-**To turn on data viewing through PowerShell**
+#### To turn on data viewing through the Settings page
+
+1. Go to **Start**, select **Settings** > **Privacy & security** > **Diagnostics & feedback**.
+
+2. Under **View diagnostic data**, turn on the **Turn on the Diagnostic Data Viewer** option.
+
+#### To turn on data viewing through PowerShell
Run the following command within an elevated PowerShell session:
@@ -72,69 +76,76 @@ Run the following command within an elevated PowerShell session:
PS C:\> Enable-DiagnosticDataViewing
```
-Once data viewing is enabled, your Windows machine will begin saving a history of diagnostic data that is sent to Microsoft from this point on.
+## Get started with using the Diagnostic Data Viewer for PowerShell
- >[!IMPORTANT]
- >Turning on data viewing can use up to 1GB (default setting) of disk space on your system drive. We recommend that you turn off data viewing when you're done using the Diagnostic Data Viewer. For info about turning off data viewing, see the [Turn off data viewing](#turn-off-data-viewing) section in this article.
-
-
-### Getting Started with Diagnostic Data Viewer for PowerShell
-To see how to use the cmdlet, the parameters it accepts, and examples, run the following command from an elevated PowerShell session:
+To see how to use the cmdlet, the parameters it accepts, and examples, run the following command from an elevated PowerShell session:
```powershell
PS C:\> Get-Help Get-DiagnosticData
```
-**To Start Viewing Diagnostic Data**
-
-From an elevated PowerShell session, run the following command:
+To start viewing Diagnostic Data, from an elevated PowerShell session, run the following command:
```powershell
PS C:\> Get-DiagnosticData
```
-If the number of events is large, and you'd like to stop the command, enter `Ctrl+C`.
+If the number of events is large, and you'd like to stop the command, enter `Ctrl+C`.
- >[!IMPORTANT]
- >The above command may produce little to no results if you enabled data viewing recently. It can take several minutes before your Windows device can show diagnostic data it has sent. Use your device as you normally would in the mean time and try again.
+>[!NOTE]
+>The preceding command might produce little to no results if you enabled data viewing recently. It can take several minutes before your Windows device can show diagnostic data it sent.
-### Doing more with the Diagnostic Data Viewer for PowerShell
-The Diagnostic Data Viewer for PowerShell provides you with the following features to view and filter your device's diagnostic data. You can also use the extensive suite of other PowerShell tools with this module.
+## Working with the Diagnostic Data Viewer for PowerShell
-- **View your diagnostic events.** Running `PS C:\> Get-DiagnosticData`, you can review your diagnostic events. These events reflect activities that occurred and were sent to Microsoft.
+The Diagnostic Data Viewer for PowerShell provides you with the following features to view and filter your device's diagnostic data. You can also use the extensive suite of other PowerShell tools with this module.
- Each event is displayed as a PowerShell Object. By default each event shows the event name, the time when it was seen by your Windows device, whether the event is [Basic](./configure-windows-diagnostic-data-in-your-organization.md), its [diagnostic event category](#view-diagnostic-event-categories), and a detailed JSON view of the information it contains, which shows the event exactly as it was when sent to Microsoft. Microsoft uses this info to continually improve the Windows operating system.
+> [!TIP]
+> For more information about the PowerShell commands available, see the [Microsoft.DiagnosticDataViewer module documentation](/powershell/module/microsoft.diagnosticdataviewer).
-- **View diagnostic event categories.** Each event shows the diagnostic event categories that it belongs to. These categories define how events are used by Microsoft. The categories are shown as numeric identifiers. For more information about these categories, see [Windows Diagnostic Data](./windows-diagnostic-data.md).
-
- To view the diagnostic category represented by each numeric identifier and what the category means, you can run the command:
+### View your diagnostic events
- ```powershell
- PS C:\> Get-DiagnosticDataTypes
- ```
+Running `PS C:\> Get-DiagnosticData`, you can review your diagnostic events. These events reflect activities that occurred and were sent to Microsoft.
-- **Filter events by when they were sent.** You can view events within specified time ranges by specifying a start time and end time of each command. For example, to see all diagnostic data sent between 12 and 6 hours ago, run the following command. Note that data is shown in order of oldest first.
- ```powershell
- PS C:\> Get-DiagnosticData -StartTime (Get-Date).AddHours(-12) -EndTime (Get-Date).AddHours(-6)
- ```
+Each event is displayed as a PowerShell Object. By default each event shows the event name, the time when it was seen by your Windows device, whether the event is [Required](configure-windows-diagnostic-data-in-your-organization.md#required-diagnostic-data), its diagnostic event category, and a detailed JSON view of the information it contains, which shows the event exactly as it was when sent to Microsoft. Microsoft uses this info to continually improve the Windows operating system.
-- **Export the results of each command.** You can export the results of each command to a separate file such as a csv by using pipe `|`. For example,
+### View diagnostic event categories
- ```powershell
- PS C:\> Get-DiagnosticData | Export-Csv 'mydata.csv'
- ```
+Each event shows the diagnostic event categories that it belongs to. These categories define how events are used by Microsoft. The categories are shown as numeric identifiers.
+
+To view the diagnostic category represented by each numeric identifier and what the category means, you can run the following command:
+
+```powershell
+PS C:\> Get-DiagnosticDataTypes
+```
+
+### Filter events by when they were sent
+
+You can view events within specified time ranges by specifying a start time and end time of each command. For example, to see all diagnostic data sent between 12 and 6 hours ago, run the following command. Data is shown in order of oldest first.
+
+```powershell
+PS C:\> Get-DiagnosticData -StartTime (Get-Date).AddHours(-12) -EndTime (Get-Date).AddHours(-6)
+```
+
+### Export the results of each command
+
+You can export the results of each command to a separate file such as a csv by using pipe `|`. For example:
+
+```powershell
+PS C:\> Get-DiagnosticData | Export-Csv 'mydata.csv'
+```
## Turn off data viewing
-When you're done reviewing your diagnostic data, we recommend turning off data viewing to prevent using up more memory. Turning off data viewing stops Windows from saving a history of your diagnostic data and clears the existing history of diagnostic data from your device.
-**To turn off data viewing through the Settings page**
-1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
+When you're done reviewing your diagnostic data, we recommend turning off data viewing to prevent using up more memory. Turning off data viewing stops Windows from saving a history of your diagnostic data and clears the existing history of diagnostic data from your device.
-2. Under **Diagnostic data**, turn off the **If data viewing is enabled, you can see your diagnostics data** option.
+### To turn off data viewing through the Settings page
- 
+1. Go to **Start**, select **Settings** > **Privacy & security** > **Diagnostics & feedback**.
-**To turn off data viewing through PowerShell**
+2. Under **View diagnostic data**, turn off the **If data viewing is enabled, you can see your diagnostics data** option.
+
+
+### To turn off data viewing through PowerShell
Within an elevated PowerShell session, run the following command:
@@ -143,44 +154,37 @@ PS C:\> Disable-DiagnosticDataViewing
```
## Modifying the size of your data history
-By default, the tool will show you up to 1GB or 30 days of data (whichever comes first). Once either the time or space limit is reached, the data is incrementally dropped with the oldest data points dropped first.
-**Modify the size of your data history**
+By default, the tool shows you up to 1 GB or 30 days of data (whichever comes first). Once either the time or space limit is reached, the data is incrementally dropped with the oldest data points dropped first.
- >[!IMPORTANT]
- >Modifying the maximum amount of diagnostic data viewable by the tool may come with performance impacts to your machine.
+### Modify the size of your data history
- >[!IMPORTANT]
- >If you modify the maximum data history size from a larger value to a lower value, you must turn off data viewing and turn it back on in order to reclaim disk space.
+>[!IMPORTANT]
+>- Modifying the maximum amount of diagnostic data viewable by the tool might come with performance impacts to your machine.
+>- If you modify the maximum data history size from a larger value to a lower value, you must turn off data viewing and turn it back on in order to reclaim disk space.
-You can change the maximum data history size (in megabytes) that you can view. For example, to set the maximum data history size to 2048MB (2GB), you can run the following command.
+You can change the maximum data history size (in megabytes) that you can view. For example, to set the maximum data history size to 2,048 MB (2 GB), you can run the following command.
```powershell
PS C:\> Set-DiagnosticStoreCapacity -Size 2048
```
-You can change the maximum data history time (in hours) that you can view. For example, to set the maximum data history time to 24 hours, you can run the following command.
+You can change the maximum data history time (in hours) that you can view. For example, to set the maximum data history time to 24 hours, you can run the following command.
```powershell
PS C:\> Set-DiagnosticStoreCapacity -Time 24
```
- >[!IMPORTANT]
- >You may need to restart your machine for the new settings to take effect.
+>[!NOTE]
+>- You might need to restart your machine for the new settings to take effect.
+>- If you have the [Diagnostic Data Viewer](diagnostic-data-viewer-overview.md) store app installed on the same device, modifications to the size of your data history through the PowerShell module will also be reflected in the app.
- >[!IMPORTANT]
- >If you have the [Diagnostic Data Viewer](diagnostic-data-viewer-overview.md) store app installed on the same device, modifications to the size of your data history through the PowerShell module will also be reflected in the app.
+### Reset the size of your data history
-**Reset the size of your data history**
-
-To reset the maximum data history size back to its original 1GB default value, run the following command in an elevated PowerShell session:
+To reset the maximum data history size back to its original 1 GB default value, run the following command in an elevated PowerShell session:
```powershell
PS C:\> Set-DiagnosticStoreCapacity -Size 1024 -Time 720
```
When resetting the size of your data history to a lower value, be sure to turn off data viewing and turn it back on in order to reclaim disk space.
-
-## Related Links
-- [Module in PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.DiagnosticDataViewer)
-- [Documentation for Diagnostic Data Viewer for PowerShell](/powershell/module/microsoft.diagnosticdataviewer)
diff --git a/windows/privacy/images/ddv-data-viewing.png b/windows/privacy/images/ddv-data-viewing.png
deleted file mode 100644
index b2f72cfc85..0000000000
Binary files a/windows/privacy/images/ddv-data-viewing.png and /dev/null differ
diff --git a/windows/privacy/images/ddv-settings-launch.png b/windows/privacy/images/ddv-settings-launch.png
deleted file mode 100644
index dc105bfde3..0000000000
Binary files a/windows/privacy/images/ddv-settings-launch.png and /dev/null differ
diff --git a/windows/privacy/images/ddv-settings-off.png b/windows/privacy/images/ddv-settings-off.png
deleted file mode 100644
index 9c1e292e89..0000000000
Binary files a/windows/privacy/images/ddv-settings-off.png and /dev/null differ
diff --git a/windows/privacy/toc.yml b/windows/privacy/toc.yml
index cd66cb48a1..13ade8af19 100644
--- a/windows/privacy/toc.yml
+++ b/windows/privacy/toc.yml
@@ -7,9 +7,9 @@
href: configure-windows-diagnostic-data-in-your-organization.md
- name: Diagnostic Data Viewer
items:
- - name: Diagnostic Data Viewer Overview
+ - name: Diagnostic Data Viewer overview
href: diagnostic-data-viewer-overview.md
- - name: Diagnostic Data Viewer for PowerShell Overview
+ - name: Diagnostic Data Viewer for PowerShell overview
href: diagnostic-data-viewer-powershell.md
- name: Required Windows diagnostic data events and fields
items:
diff --git a/windows/privacy/windows-privacy-compliance-guide.md b/windows/privacy/windows-privacy-compliance-guide.md
index 155caa56e4..4b10abed89 100644
--- a/windows/privacy/windows-privacy-compliance-guide.md
+++ b/windows/privacy/windows-privacy-compliance-guide.md
@@ -7,15 +7,16 @@ ms.localizationpriority: high
author: DHB-MSFT
ms.author: danbrown
manager: dansimp
-ms.date: 05/20/2019
-ms.topic: article
+ms.date: 05/30/2025
+ms.topic: concept-article
+hideEdit: true
ms.collection:
- essentials-compliance
- privacy-windows
- must-keep
---
-# Windows Privacy Compliance:
A Guide for IT and Compliance Professionals
+# Windows Privacy Compliance:
A Guide for IT and Compliance Professionals
Applies to:
@@ -26,7 +27,7 @@ Applies to:
## Overview
-At Microsoft, we are committed to data privacy across all our products and services. With this guide, we provide administrators and compliance professionals with data privacy considerations for Windows.
+At Microsoft, we're committed to data privacy across all our products and services. With this guide, we provide administrators and compliance professionals with data privacy considerations for Windows.
Microsoft collects data through multiple interactions with users of Windows devices. This information can contain personal data that may be used to provide, secure and improve Windows, and to provide connected experiences. To help users and organizations control the collection of personal data, Windows provides comprehensive transparency features, settings choices, controls, and support for data subject requests, all of which are detailed in this article.
@@ -45,24 +46,24 @@ The following table provides an overview of the Windows 10 and Windows 11 privac
> [!NOTE]
> This table is limited to the privacy settings that are most commonly available when setting up a current version of Windows 10 or newer. For the full list of settings that involve data collection, see [Manage connections from Windows operating system components to Microsoft services](manage-connections-from-windows-operating-system-components-to-microsoft-services.md).
-| Feature/Setting | Description | Supporting content | Privacy statement |
+| Feature/Setting | Description | Supporting content | Section of the Microsoft Privacy Statement |
| --- | --- | --- | --- |
-| Diagnostic Data |
Required diagnostic data includes information about your device, its settings, capabilities, and whether it is performing properly, whether a device is ready for an update, and whether there are factors that may impede the ability to receive updates, such as low battery, limited disk space, or connectivity through a paid network. You can find out what is collected with required diagnostic data [here](./required-windows-diagnostic-data-events-and-fields-2004.md).
Optional diagnostic data includes more detailed information about your device and its settings, capabilities, and device health. When you choose to send optional diagnostic data, required diagnostic data will always be included. You can find out the types of optional diagnostic data collected [here](./optional-diagnostic-data.md).
Microsoft uses diagnostic data to keep Windows secure, up to date, troubleshoot problems, and make product improvements. Regardless of what choices you make for diagnostic data collection, the device will be just as secure and will operate normally. This data is collected by Microsoft to quickly identify and address issues affecting its customers.
Diagnostic data is categorized into the following: