This commit is contained in:
Meghan Stewart 2022-05-06 15:15:54 -07:00
parent f7ef6583d7
commit 29bf0412ff

View File

@ -56,56 +56,55 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
|Error |Description | |Error |Description |
|---------|---------| |---------|---------|
| 1 | General unexpected error|
| 6 | Invalid CommercialID|
| 8 | Couldn't create registry key path to setup CommercialID|
| 9 | Couldn't write CommercialID at registry key path|
| 11 | Unexpected result when setting up CommercialID.|
| 12 | CheckVortexConnectivity failed, check Log output for more information.|
| 12 | Unexpected failure when running CheckVortexConnectivity.|
| 16 | Reboot is pending on device, restart device and restart script.|
| 17 | Unexpected exception in CheckRebootRequired.|
| 27 | Not system account. | | 27 | Not system account. |
| 37 | Unexpected exception when collecting logs| | 30 | Unable to disable Enterprise Auth Proxy. This registry value must be 0 for UTC to operate in an authenticated proxy environment.|
| 1 | General unexpected error| | 34 | Unexpected exception when attempting to check Proxy settings.|
| 6 | Invalid CommercialID| | 35 | Unexpected exception when checking User Proxy.|
| 48 | CommercialID is not a GUID| | 37 | Unexpected exception when collecting logs|
| 8 | Couldn't create registry key path to setup CommercialID| | 40 | Unexpected exception when checking and setting telemetry.|
| 9 | Couldn't write CommercialID at registry key path| | 41 | Unable to impersonate logged-on user.|
| 53 | There are conflicting CommercialID values.| | 42 | Unexpected exception when attempting to impersonate logged-on user.|
| 11 | Unexpected result when setting up CommercialID.| | 43 | Unexpected exception when attempting to impersonate logged-on user.|
| 62 | AllowTelemetry registry key is not of the correct type REG_DWORD| | 44 | Error when running CheckDiagTrack service.|
| 63 | AllowTelemetry is not set to the appropriate value and it could not be set by the script.| | 45 | DiagTrack.dll not found.|
| 64 | AllowTelemetry is not of the correct type REG_DWORD.| | 48 | CommercialID is not a GUID|
| 99 | Device is not Windows 10.| | 50 | DiagTrack service not running.|
| 40 | Unexpected exception when checking and setting telemetry.| | 51 | Unexpected exception when attempting to run Census.exe|
| 12 | CheckVortexConnectivity failed, check Log output for more information.| | 52 | Could not find Census.exe|
| 12 | Unexpected failure when running CheckVortexConnectivity.| | 53 | There are conflicting CommercialID values.|
| 54 | Microsoft Account Sign In Assistant (MSA) Service disabled.|
| 55 | Failed to create new registry path for SetDeviceNameOptIn|
| 56 | Failed to create property for SetDeviceNameOptIn at registry path|
| 57 | Failed to update value for SetDeviceNameOptIn|
| 58 | Unexpected exception in SetrDeviceNameOptIn|
| 59 | Failed to delete LastPersistedEventTimeOrFirstBoot property at registry path when attempting to clean up OneSettings.|
| 60 | Failed to delete registry key when attempting to clean up OneSettings.|
| 61 | Unexpected exception when attempting to clean up OneSettings.|
| 62 | AllowTelemetry registry key is not of the correct type REG_DWORD|
| 63 | AllowTelemetry is not set to the appropriate value and it could not be set by the script.|
| 64 | AllowTelemetry is not of the correct type REG_DWORD.|
| 66 | Failed to verify UTC connectivity and recent uploads.| | 66 | Failed to verify UTC connectivity and recent uploads.|
| 67 | Unexpected failure when verifying UTC CSP.| | 67 | Unexpected failure when verifying UTC CSP.|
| 41 | Unable to impersonate logged-on user.| | 91 | Failed to create new registry path for EnableAllowUCProcessing|
| 42 | Unexpected exception when attempting to impersonate logged-on user.| | 92 | Failed to create property for EnableAllowUCProcessing at registry path|
| 43 | Unexpected exception when attempting to impersonate logged-on user.| | 93 | Failed to update value for EnableAllowUCProcessing|
| 16 | Reboot is pending on device, restart device and restart script.| | 94 | Unexpected exception in EnableAllowUCProcessing|
| 17 | Unexpected exception in CheckRebootRequired.| | 99 | Device is not Windows 10.|
| 44 | Error when running CheckDiagTrack service.|
| 45 | DiagTrack.dll not found.|
| 50 | DiagTrack service not running.|
| 54 | Microsoft Account Sign In Assistant (MSA) Service disabled.|
| 55 | Failed to create new registry path for SetDeviceNameOptIn|
| 56 | Failed to create property for SetDeviceNameOptIn at registry path|
| 57 | Failed to update value for SetDeviceNameOptIn|
| 58 | Unexpected exception in SetrDeviceNameOptIn|
| 59 | Failed to delete LastPersistedEventTimeOrFirstBoot property at registry path when attempting to clean up OneSettings.|
| 60 | Failed to delete registry key when attempting to clean up OneSettings.|
| 61 | Unexpected exception when attempting to clean up OneSettings.|
| 52 | Could not find Census.exe|
| 51 | Unexpected exception when attempting to run Census.exe|
| 34 | Unexpected exception when attempting to check Proxy settings.|
| 30 | Unable to disable Enterprise Auth Proxy. This registry value must be 0 for UTC to operate in an authenticated proxy environment.|
| 35 | Unexpected exception when checking User Proxy.|
| 91 | Failed to create new registry path for EnableAllowUCProcessing|
| 92 | Failed to create property for EnableAllowUCProcessing at registry path|
| 93 | Failed to update value for EnableAllowUCProcessing|
| 94 | Unexpected exception in EnableAllowUCProcessing|
## Verify device configuration ## Verify device configuration
In some cases, you may need to manually verify the device configuration has the `AllowUpdateComplianceProcessing` policy enabled. To verify the setting, use the following steps: In some cases, you may need to manually verify the device configuration has the `AllowUpdateComplianceProcessing` policy enabled. To verify the setting, use the following steps:
1. Download and enable the **Diagnostic Data Viewer**. For more information, see [Diagnostic Data Viewer overview](/windows/privacy/diagnostic-data-viewer-overview#install-and-use-the-diagnostic-data-viewer). 1. Download and enable the **Diagnostic Data Viewer**. For more information, see [Diagnostic Data Viewer overview](/windows/privacy/diagnostic-data-viewer-overview#install-and-use-the-diagnostic-data-viewer).
1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**. 1. Go to **Start**, select **Settings** > **Privacy** > **Diagnostics & feedback**.
1. Under **View diagnostic data**, select **On** for the following option: 1. Under **View diagnostic data**, select **On** for the following option:
@ -132,4 +131,4 @@ In some cases, you may need to manually verify the device configuration has the
- The **MSP** field value under **protocol** should be either `16` or `18`. - The **MSP** field value under **protocol** should be either `16` or `18`.
- If you need to send this data to Microsoft Support, select **Export data**. - If you need to send this data to Microsoft Support, select **Export data**.
:::image type="content" alt-text="Screenshot of the Diagnostic Data Viewer displaying the data from SoftwareUpdateClientTelemetry. The export data option and the fields for MSP and EnrolledTenantID are outlined in red." source="./media/update-compliance-diagnostic-data-viewer.png" lightbox="./media/update-compliance-diagnostic-data-viewer.png"::: :::image type="content" alt-text="Screenshot of the Diagnostic Data Viewer displaying the data from SoftwareUpdateClientTelemetry. The export data option and the fields for MSP and EnrolledTenantID are outlined in red." source="./media/update-compliance-diagnostic-data-viewer.png" lightbox="./media/update-compliance-diagnostic-data-viewer.png":::