Messages

It would appear that .NET Core Runtime 2.2.6 (the newly released one) is being detected as applicable on machines that have the Hosting bundle installed, which previously you all had prevented.  Is this intentional or should it be fixed again?  I've attached an image from a report showing what I mean.

Support request sent.

Its full name is the ".NET Core Runtime and Hosting Bundle", but if it's easier, we can just call it the Hosting Bundle, for clarity    This is not about the Runtime standalone

What about reorganizing them just a bit? This should detect better but should still provide exclusivity (using a shorthand to refer to previous posts set, please let me know if this isn't clear):
AND group
    OR group
        AND Group
            Set 1 a
            Set 1 b
        AND Group
            Set 2 a
            Set 2 b
        AND Group
            Set 3 a
            Set 3 b
        AND Group
            Set 4 a
            Set 4 b
    OR group
        Set 1 c
        Set 2 c

Microsoft isn't making these updates available in catalog or WSUS, so I'm hoping you all can help.
Here's a recent post that gives links to the update as well as some initial detection info: https://devblogs.microsoft.com/devops/may-security-release-patches-available-for-azure-devops-server-2019-tfs-2018-3-2-tfs-2018-1-2-tfs-2017-3-1-and-tfs-2015-4-2/

Please let me know if I can help further.

The .NET Core Runtime and Hosting Bundle Detection methods need updating I think.  After an update, many machines don't detect unless I run a repair install after and then rescan again, though they in fact installed fine the first time.

Here's what I can tell based on the detection methods in SCUP and what's present on the machine:
There are 4 sets of detections in an OR statement, each of which contains 3 detections in an AND group
Set 1 Detection Method:
a) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\sharedhost\Version exists
b) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\Microsoft\Updates\.NET Core exists

Set 2 Detection Method:
a) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x86\sharedhost\Version exists
b) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x86\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\WOW6432Node\Microsoft\Updates\.NET Core exists

Set 3 Detection Method:
a) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost\Version exists
b) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\Microsoft\Updates\.NET Core exists

Set 4 Detection Method:
a) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x64\sharedhost\Version exists
b) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x64\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\WOW6432Node\Microsoft\Updates\.NET Core exists

Results on machine not detecting (update is installed, but repair not done):
Set 1:
a) Does not exist
b) Does not exist, so comparison no good
c) Does not exist

Set 2:
a) Exists
b) 2.1.5
c) Exists

Set 3:
a) Exists
b) 2.2.4
c) Does not exist

Set 4:
a) Does not exist
b) Does not exist, so comparison no good
c) Exists

Same box after repair install performed:
Set 1:
a) Does not exist
b) Does not exist, so comparison no good
c) Does not exist

Set 2:
a) Exists
b) 2.2.4
c) Exists
Detection occurs because of this set

Set 3:
a) Exists
b) 2.2.4
c) Does not exist

Set 4:
a) Does not exist
b) Does not exist, so comparison no good
c) Exists

These detections seem to work about 85-90% of the time, but not always.  The example machine for this is an x64 Server Core 2016 system.  Please let me know if I can help provide more information.

Sorry, I didn't see this, no email on the reply.  I don't have any older version to provide, sorry, only the most recent version that came out in February.

Sorry to bother you guys, was just checking in to see if there was any information on this as this would be very helpful to my company?

Sorry to bother you guys, was just checking in to see if there was any information on this?

I'd like to second this for SharePoint 2010, 2013, 2016 Security Updates.  If you do the security updates (as opposed to the CU's) it should be pretty safe to include them.  This site can help you search for the updates each month: https://portal.msrc.microsoft.com/en-us/security-guidance.  And this site lists them for each month as well: https://docs.microsoft.com/en-us/officeupdates/sharepoint-updates.

So far it seems to be better, yes, thank you.

Yep, I've got multiple machines indicating they need the following:
Microsoft .NET Core SDK 2.1.402 (x64)
Microsoft .NET Core Runtime and Hosting Bundle 2.1.4
Microsoft .NET Core Runtime 2.1.4 (x64)

First, thanks for all your hard work.  It helps having the hosting bundle added. However, I did notice that the .NET Core Runtime still gets detected as needed on a machine with the runtime and hosting bundle installed.

Totally understandable.  If it helps, I would note that Microsoft specifically separated the components largely to help ease updating of the SSRS component more regularly and in a way that doesn't interrupt SQL Server itself.  For reference, here's the release article: https://blogs.msdn.microsoft.com/sqlrsteamblog/2017/10/02/sql-server-2017-reporting-services-now-generally-available/


Edited: Typo

Microsoft separated SQL Server and its Reporting Services component, but now there's no automatic update or WSUS product to update it with.  It's freely available to get the installer (though you need a product key for new installs - there is an evaluation period though -, no product key is required for updates) from here: https://www.microsoft.com/en-us/download/details.aspx?id=55252
Could this be added to the catalog?