Skip to content

Commit 6642930

Browse files
Cabbie Teamcopybara-github
authored andcommitted
Some clarifications about UpdateIDs
PiperOrigin-RevId: 983578133
1 parent 1403fb8 commit 6642930

1 file changed

Lines changed: 12 additions & 3 deletions

File tree

‎README.md‎

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -187,12 +187,21 @@ ProgramData directory (C:\ProgramData\Cabbie).
187187

188188
Required updates can be designated as a list of zero or more KB article strings
189189
under the `required` key. To hide an update from cabbie, place the KB article
190-
string under the `hidden` key or use the Update ID under the `hidden-UpdateID`
191-
key.
190+
string under the `hidden` key or use the client-side Windows Update Agent (WUA)
191+
`UpdateID` GUID under the `hidden-UpdateID` key.
192+
193+
> **Note:** The `UpdateID` used in `hidden-UpdateID` must be the client-side WUA
194+
> `IUpdateIdentity.UpdateID` evaluated on the host (which can be found via
195+
> `cabbie list --ids`, `cabbie history`, or Windows Event ID 41 `updateGuid` in
196+
> `Microsoft-Windows-WindowsUpdateClient/Operational`). Do **not** use the
197+
> `updateid` GUID parameter from Microsoft Update Catalog URLs
198+
> (`catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=...`), as that
199+
> represents a server-side package container GUID that does not match the
200+
> client-side `UpdateID`.
192201
193202
Example:
194203

195-
```
204+
```json
196205
{
197206
"required": [
198207
"123456"

0 commit comments

Comments
 (0)