Replies

I decided to try “AutoSelectOnWebsites = True OR BrowseOnly = False” for identifying non-optional updates.

I do not see an Interactive property in the UpdateSearcher results. I tried searching with an “IsInteractive” criterion, like this:

$SearchResult = $UpdateSearcher.Search(“IsInstalled=0 and IsInteractive=1”)

That returns an error.

So I’m not seeing an Interactive property that would help me determine if a particular update is offered in the GUI. It seems more like something that is logged to indicate how the update search was performed.

P.S. I see it is my WindowsUpdate.ShowDetails.ps1 script that you were using. Nice! Now if we could just figure out what the details mean :).

Thanks for pulling together these references.

I run a daily script on all my machines to tell me what’s pending. Basically if the machine wants to apply updates (apart from Windows Defender), I want an alert.

Today I’m scratching my head about how the machine decides to NOT display Silverlight but it DOES display the pending Feature update.

Silverlight
AutoSelectOnWebsites: False
BrowseOnly: True
AutoSelection:  0 [asLetWindowsUpdateDecide]
AutoDownload:  0 [adLetWindowsUpdateDecide]

20H2 Feature Update
AutoSelectOnWebsites: False
BrowseOnly: False
AutoSelection:  1 [asAutoSelectIfDownloaded]
AutoDownload:  2 [adAlwaysAutoDownload]

And for comparison…

An “Important” .NET update (KB4601050)
AutoSelectOnWebsites: True
BrowseOnly: False
AutoSelection:  0 [asLetWindowsUpdateDecide]
AutoDownload:  0 [adLetWindowsUpdateDecide]

A “Critical” Cumulative Update (KB4601319)
AutoSelectOnWebsites: False
BrowseOnly: False
AutoSelection:  0 [asLetWindowsUpdateDecide]
AutoDownload:  0 [adLetWindowsUpdateDecide]

I read elsewhere that BrowseOnly is not reliable for distinguishing optional updates on Windows 10, so I’m now only alerting if AutoSelectOnWebsites = True. But that means I missed the Feature Update.

What combination of parameters does Windows 10 use to tell users in the GUI that an update is pending? I’m wondering if BrowseOnly = False is the better filter.

1 user thanked author for this post.

abbodi86

A recent comment in the thread Susan linked includes a link to this post about Feb 9 updates:

https://support.microsoft.com/en-us/topic/february-9-2021-kb4601318-os-build-14393-4225-c5e3de6c-e3e6-ffb5-6197-48b9ce16446e

This post now confirms, “KB4601392 has been removed and will no longer be offered to devices. We are working on a resolution and will provide an update in an upcoming release.”

Found this article with some info on the old Intel drivers and why they are showing up now:

https://borncity.com/win/2020/09/27/windows-10-bietet-alte-unpassende-intel-treiber-updates-an-sept-2020/

2 users thanked author for this post.

Alex5723, geekdom

I also have Intel System driver updates offered in WSUS, along with a Nuvoton, dated November 2011 through April 2018. Wondering why these ancient drivers are suddenly on offer–it seems they appeared after the upgrade to Win10 2004. Approve? Decline?

Thanks very much for your reply. Now I know it’s not just me and not something I can expect to see fixed.

I use several of the “old” Essentials features (RWA, VPN, RDP gateway, client backup), so 2016 is sadly the last option until I am ready to shop for a new solution to each of those.

Okay, here’s a difference.

The previous CU KB4565633 is offered through WSUS.

The new “preview” CU KB4562900 is not on WSUS (yet).

1 user thanked author for this post.

abbodi86

Well not sure what I did differently before–maybe failed to reboot–but

wusa.exe /uninstall /KB:4562900

works now to uninstall that uninstallable update.

Block code:  I pasted text, selected it, then set drop-down to Preformatted.

Thanks for this info. I’ve added that important AutoSelectOnWebSites field to my script.

Still having trouble wrapping my mind around how anything flagged as a Preview can be automatically installed, even if I “seek.” To me, “Preview” implies a look ahead at something we plan to release for real in the future. Which I’ve always interpreted as, “ignore this while others test it.”

You’re right though. On a machine where I haven’t installed 4562900, the previous CU, which is still installed, is coded the same way but does not include the word “Preview”:

Checking for update 4565633
--------------------------------------------------------

KBArticleIDs: 4565633
Title: 2020-07 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 (KB4565633)
UpdateID: a4fa30a1-592f-4d6a-9bec-d8220c91459d
RevisionNumber: 200
LastDeploymentChangeTime: 7/14/2020 12:00:00 AM
MsrcSeverity: Critical
IsDownloaded: True
IsHidden: False
IsInstalled: True
IsMandatory: False
IsPresent: True
BrowseOnly: False
IsUninstallable: True
MinDownloadSize: 0
MaxDownloadSize: 42914096
RebootRequired: False
AutoSelectOnWebSites: True
AutoSelection: 0
AutoDownload: 0
SecurityBulletinIDs:
SupersededUpdateIDs:
63ea98c8-f7c8-4581-bf9f-30c453d3bb8c

By the way, I tried using a script to uninstall 4562900 on the first machine, but it seems

IsUninstallable: False

is correct–it didn’t uninstall.

[mcbsys]

IMO there something wrong with how the .NET preview KB4562900 is coded.

Previews should be optional, i.e. with BrowseOnly=True. But this one has BrowseOnly=False, meaning that when you seek for updates on Win10 1909, the Preview gets installed:

Is there some way to tell Microsoft to fix this? In the meantime, the only safeguard I can think of is to use wushowhide to hide it.

Here are the details from my PowerShell script:

Checking for update 4562900
--------------------------------------------------------
            KBArticleIDs: 4562900
                   Title: 2020-07 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4562900)
                UpdateID: d8cbe3a9-bcf6-4b76-8e21-e6b063bdc2a9
          RevisionNumber: 201
LastDeploymentChangeTime: 7/21/2020 12:00:00 AM
            MsrcSeverity:
            IsDownloaded: False
                IsHidden: False
             IsInstalled: False
             IsMandatory: False
               IsPresent: False
              BrowseOnly: False
         IsUninstallable: False
         MinDownloadSize: 0
         MaxDownloadSize: 77610497
          RebootRequired: False
           AutoSelection: 1
            AutoDownload: 2
     SecurityBulletinIDs:
     SupersededUpdateIDs:
                          299949d5-edf0-4ab7-ad37-4d0a62fd664d

• This reply was modified 4 years, 10 months ago by mcbsys.
• This reply was modified 4 years, 10 months ago by mcbsys.

2 users thanked author for this post.

doriel, abbodi86

Did a little googling on Fresno school bus Wi-Fi. Apparently they added that to their buses in 2016:

https://www.fresnounified.org/news/stories/Pages/20160819-FresnoUnifiedOffersWiFi.aspx#.XyGUOyhKh3g

I’m guessing they’re using Cradlepoint or similar 4G hotspots (which Google kindly showed me as an advertisement in the same search).

The article Susan cited, and others, are about a short pilot program to park the buses and letting kids work outside nearby. This article equivocates:

https://gvwire.com/2020/05/15/fusd-plans-to-roll-out-buses-as-wi-fi-hot-spots/

…saying programs in other cities hadn’t been used much, and that in Fresno, “The district focused first on getting mobile hot spots into the hands of students who lacked Internet access, Henry said.” Which actually makes a lot of sense–giving/loaning 4G hotspots for use when needed vs. letting kids sit outside a bus for 3 hours a day.

1 user thanked author for this post.

OscarCP

Susan –

Love the idea of bringing Wi-Fi to underserved areas, in this case on school buses. Any idea of the tech behind it? What’s the uplink? 4G? Satellite?

Mark Berry

Susan – I will be interested in your post-mortem on this. Did somebody really decide to pull the plug because they thought everything related was deprecated? (as per https://twitter.com/mraaronjfoster/status/1286712631143915525)

More broadly, do we need to expect that Microsoft will randomly kill off services for Essentials years before the end of support? Much of my mindset is already about defending customer systems against Microsoft when it comes to updates. Do I need to defend against early service terminations as well?