Whats the most simple way to detect if the Current OSBuild still gets security updates?

[schittli]

Hello

Thanks a lot for sharing your great work!

Customers pay billions to Microsoft and in 2023, it's a shame that they do not offer a REST Service that offers this information.

I probably have a question about the most common use case:

How can we tell until which date the current OS Build receives security updates?

In our days this information is very important and I suppose your WindowsOSBuild Module is a very good source of information for this question. But I don't know what information I have to interpret for this question to get a 100% sure answer.

Thanks a lot, kind regards, Thomas

[schittli]

Good evening

It looks like there is a bug...

1: Microsoft tells that Win10, 20H2 does no longer get updates:

https://learn.microsoft.com/en-us/windows/release-health/release-information

2: But WindowsOSBuild explains, that Win10, 20H2 still gets updates:

Get-LatestOSBuild -OSName Win10 -OSVersion 20H2

Version           : Version 20H2 (OS build 19042)
Build             : 19042.2965
Availability date : 2023-05-09
Preview           : False
Out-of-band       : False
Servicing option  : Semi-Annual Channel
KB article        : KB5026361
KB URL            : https://support.microsoft.com/help/5026361
Catalog URL       : https://www.catalog.update.microsoft.com/Search.aspx?q=KB5026361

WindowsOSBuild should report for Servicing option something like End of servicing and not Semi-Annual Channel

Thanks a lot, kind regards, Thomas

[AshleyHow]

Hi Tom,

I think you are confusing the servicing option with end of servicing columns. I dont not consider this to be a bug. It is currently pulling the 'servicing option' as per table along with the latest Available update correctly provided by Microsoft. I think that column didn't exist when I was creating this module years ago.

This module does not have the capability yet to state about end of servicing, although it is something I would like to add. I'll see what I can do.

On Fri, 2 Jun 2023, 23:29 Tom--, @.***> wrote:

Good evening It looks like there is a bug... 1: Microsoft tells that Win10, 20H2 does no longer get updates:

https://learn.microsoft.com/en-us/windows/release-health/release-information [image: image] https://user-images.githubusercontent.com/8282673/243001805-8450532b-2dc5-4703-9d35-967e12b714e5.png 2: But WindowsOSBuild explains, that Win10, 20H2 still gets updates:

Get-LatestOSBuild -OSName Win10 -OSVersion 20H2

Version : Version 20H2 (OS build 19042) Build : 19042.2965 Availability date : 2023-05-09 Preview : False Out-of-band : False Servicing option : Semi-Annual Channel KB article : KB5026361 KB URL : https://support.microsoft.com/help/5026361 Catalog URL : https://www.catalog.update.microsoft.com/Search.aspx?q=KB5026361

WindowsOSBuild should report for Servicing option something like End of servicing and not Semi-Annual Channel

Thanks a lot, kind regards, Thomas

— Reply to this email directly, view it on GitHub https://github.com/AshleyHow/WindowsOSBuild/issues/30#issuecomment-1574387837, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGXYCG7TVEXJEUP4GOHY37DXJJSNHANCNFSM6AAAAAAYYPMFSU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[schittli]

Good morning @AshleyHow ,

thank you very much for your answer!, yes, the 'servicing option' column seems new to me (us) and we liked the old rules much more because it was clear at a glance what stage the OS is in: 1) It has normal maintenance with features and security updates. 2) It has extended maintenance with only security updates. 3) It has no more maintenance

It makes no sense to the end user and is dangerous if the maintenance status does not explicitly state that the currently installed Windows version has no more maintenance.

This means: If installed Windows has no more maintenance, the 'servicing option' must display "None" so that the end user knows: I no longer have a 'servicing option' for my installed Windows and must upgrade it.

If I understand it correctly, the new 'servicing option' says: "Your Windows is no longer serviced, but if you install the Windows upgrade, everything will be fine again". The end-user only sees that there is a 'servicing option' and therefore he thinks that everything is fine.

I suspect that's why many friends and co-workers are still running a Windows 10 version that doesn't even get security updates anymore.

Therefore, it would actually be ingenious if WindowsOSBuild could somehow represent that a Windows version no longer has maintenance and one must necessarily install an upgrade. 😄

Thanks a lot, kind regards, Thomas

[AshleyHow]

[schittli]

Good evening @AshleyHow,

thanks a lot for your support!, I just saw your screenshot....

If users can use WindowsOSBuild to answer this not-so-simple question after calling the command with a clear True / False, I think that's really great and could help to protect users if the Windows Update once more fails.

Thanks a lot, kind regards, Thomas

[AshleyHow]

In the end I decided to split this out to a different module.

Please see https://github.com/AshleyHow/WindowsOSServicing

Closing.