Skip to content

Windows.System.Profile: add Remarks to HardwareToken, SystemIdentification, AnalyticsVersionInfo, HardwareIdentification#2524

Open
GrantMeStrength wants to merge 5 commits intodocsfrom
jken/311114-windows-system-profile-remarks
Open

Windows.System.Profile: add Remarks to HardwareToken, SystemIdentification, AnalyticsVersionInfo, HardwareIdentification#2524
GrantMeStrength wants to merge 5 commits intodocsfrom
jken/311114-windows-system-profile-remarks

Conversation

@GrantMeStrength
Copy link
Contributor

Addresses ADO work item #311114 (GitHub issues #1700, #1701, #1743, #1747, #1783).

All additions are sourced from existing official documentation — no engineering SME was required.

Changes

HardwareToken.Signature (#1700)

Added Remarks explaining that the signature verifies the Id was generated by Windows, that verification uses the public key from the Certificate property, and that a nonce (if provided) protects against replay attacks. Links to the ASHWID guidance for the full cloud-side verification workflow.

HardwareToken.Certificate (#1701)

Added Remarks documenting that the buffer is a PKCS#7 formatted certificate chain (not a single certificate), rooted at Microsoft Assurance Designation Root 2011, with leaf EKU OID 1.3.6.1.4.1.311.10.5.40. Notes that revocation checking should be enabled on the cloud service. Source: ASHWID guidance page.

SystemIdentification.GetSystemIdForUser (#1743)

Added a note to the existing Remarks clarifying that this method returns a hardware-based identifier for correlation purposes. For accessing current-user properties (display name, account name, etc.), use Windows.System.User.GetDefault (available from Windows 10, version 2104) instead.

AnalyticsVersionInfo.DeviceFamily (#1747)

Added a table of currently defined device family values (Windows.Desktop, Windows.Holographic, Windows.IoT, Windows.Mobile, Windows.Team, Windows.Universal, Windows.Xbox) with a link to the device families overview. Retained the existing caveat that this property is for analytics only and values may change. Source: Device families overview.

HardwareIdentification (#1783)

Added Remarks clarifying that an ASHWID can contain multiple records of the same component type (e.g., three disks produce three disk records; a docked tablet adds extra network and audio records), and describing the 4-byte group format. Source: ASHWID guidance page.

@prmerger-automator prmerger-automator bot added do-not-merge PR is being processed and awaiting review/approval. docs-editor-pilot review-team-triage labels Mar 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge PR is being processed and awaiting review/approval. docs-editor-pilot review-team-triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant