Continue to see commas added by HCL

Usage and Config Patch
1

MS catalog
2024-02 Cumulative Update for Microsoft server operating system version 23H2 for x64-based Systems (KB5034769)

HCL version
MS24-FEB: Cumulative Update for Windows Server, version 23H2 - Windows Server version 23H2 - KB5034769 (x64)

This keeps happening over and over throughout the years. Can we stop adding commas to the descriptions of fixlets? It tends to raise heck for any processes customers put together for whatever reason and they incorporate comma separated values logic.

Can we get someone to fix KB5034769 please?

2

Four more for January.

MS24-JAN: Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows Server, version 23H2 - Windows Server version 23H2 - .NET Framework 3.5/4.8.1 - KB5033917 (x64)
MS24-JAN: Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 - Windows 11 Version 22H2 - .NET Framework 3.5/4.8.1 - KB5033920 (x64)
MS24-JAN: Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 23H2 - Windows 11 Version 23H2 - .NET Framework 3.5/4.8.1 - KB5033920 (x64)
MS24-JAN: Cumulative Update for Windows Server, version 23H2 - Windows Server version 23H2 - KB5034130 (x64) (Superseded)

3

I don’t believe anyone here will be able to help you. Have you opened a support ticket?

I recently opened tickets for a couple of issues related to the description and name and had a response and fix within a few days.

4

I couldn’t speak for Path here, but it’s likely we reuse some template based on how Microsoft “used to” name their patches, and now we’d probably get different complaints if we changed our own templates.
Any time you’re trying to match data based on titles or descriptions it’s going to be a bad time though. If you’re doing some kind of integration or correlation between systems, I’d suggest either using the ‘Source ID’ field, or look into the MIME fields that are present on those Patch fixlets for selection/filtering. Internally, the MIME fields are what drives their placements in the Patch Management Domain and in WebUI Patch Policy.

5

Why the randomness of these description changes? Can’t we be consistent with description from MS? I would find it hard to believe that humans are creating this content and not some unattended code you are running.