Anyone know why Lifecycle product never received the content for KB5034683? I do not see it.
We did publish those in âPatches for Windowsâ -
You may need to check whether you have âShow Non-Relevant Contentâ selected, and also whether your license has expired (Iâve seen at least one or two others whose licenses expired at end of 2023 that did not gather February updates).
Check your Site Version for âPatches for Windowsâ as well to see if your root is gathering it. Currently version 4334âŚ
Unfortunately, we are on 4334 and still does not exist and I have show non-relevant (been burned here more times than I care to admit) and still donât have that fix.
Is it hidden?
Some of my team have been burned by that.
Looked for it in WebUI too under Apps > Patch and Apps > Content > Patching Support and itâs not there either.
Turned on show hidden and still no joy.
Nevermind, I was searching for KB + 5034683 and not just 5034683. Ugh
1 Like
It may be time to open a support ticket.
Ah, ok, in my case âKB5034683â did find the results, but thatâs because I have the âSource IDâ column displayed in the Fixlet List of my console
Funny, how MS refers to it with KB on the front.
Worked for me, not sure what is different.
I am assuming you have Source ID visible.
Ah, it looks like once again KB5034683 is some kind of âwrapperâ article and the individual products may have different KBs beneath that article for different OS / .NET versions.
Checking KB5034619 at https://support.microsoft.com/en-us/topic/february-13-2024-kb5034619-cumulative-update-for-net-framework-3-5-and-4-7-2-for-windows-10-version-1809-and-windows-server-2019-826a3447-6c71-4daf-9848-c26d05cb9b30 it does have a reference to KB5034683 as well.
Oh the fun of wrappers. Thanks for the insights.