News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • abbodi86

    Forum Replies Created

    Viewing 15 posts - 1 through 15 (of 1,626 total)
    • Author
      Posts
    • in reply to: Hello! Has anyone seen 2004? #2285802
      abbodi86
      AskWoody_MVP

      I think they can enhance the optional update section to offer 2 or 3 updates simultaneously:
      the next Feature Update
      the Preview Windows Cumulative Update
      the Preview .NET Cumulative update

      but that would mean they will slowly restore old Windows Update panel (W7/W8.1) behavior 😀

      1 user thanked author for this post.
      in reply to: WSUS Missing Updates #2285637
      abbodi86
      AskWoody_MVP

      WU and WSUS only show/offer the bundle Rollup for all .NET versions (e.g. KB4566519)

      the separate rollups updates for each .NET version are only offered via MU catalog

      (yes, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 are all one version per update)

      abbodi86
      AskWoody_MVP

      First of all, the new .NET CU Preview is nothing different from all previous non-security .NET CU
      it just has the term “Preview” in label

      in my understanding, BrowseOnly attribute has no effect on Windows 10, thus not used

      if you compare the attributes of .NET CU Security vs non-Security you notice this difference

      .NET CU Security
      AutoSelectOnWebSites : True (automatically selected by Windows Update as important update)
      AutoSelection : 0
      AutoDownload : 0

      .NET CU non-Security (Preview)
      AutoSelectOnWebSites : False
      AutoSelection : 1
      AutoDownload : 2

      this is the visible difference
      there are also another hidden difference related to Interactive configuration in the search criteria, which

        only WU can set and change

      in the case of Interactive scan (i.e. Seeker):
      .NET Preview CU will be offered and installed regardless

      in the case of non-Interactive scan (i.e. scheduled scan):
      – if .NET Security CU is not yet installed, .NET Preview CU will be flagged as potentially superseded, and WU will not offer it
      – if .NET Security CU is already installed, .NET Preview CU will be offered and installed

      p.s. how did you managed to insert the details here as block code? 🙂
      for me it won’t work and get the code in one line

      1 user thanked author for this post.
      in reply to: July 2020 Patch Tuesday #2285634
      abbodi86
      AskWoody_MVP

      the sc.exe schedule tasj is not the one directly responsible for the daily or scheduled scans
      it’s merely insure the WU service starts daily, and the service itself checks its trigger timers and schedule span

      you can see some of those trigger info with this command
      powercfg /waketimers
      sc qtriggerinfo wuauserv

      or convert WU trace logs to normal text log using powershell cmdlet Get-WindowsUpdateLog

      the triggers and schedule scans are also affected by server-side Assessment, represented by registry key
      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WaaSAssessment]

      by the way, code 2147943456 = 0x80070420 = An instance of the service is already running
      so it’s not really an error

      i highly doubt if .NET update has anything to do with this weirdness 🙂

      2 users thanked author for this post.
      in reply to: New Win7 Extended Security Updates licensing package #2285346
      abbodi86
      AskWoody_MVP

      It apply to all supported ESU editions, including Ultimate, Embedded, and Servers

      if you are ESU user, yes it’s OK to install

      abbodi86
      AskWoody_MVP

      Probably because viruses are usually exe files

      abbodi86
      AskWoody_MVP

      download.windowsupdate.com links are http

      that does not mean the files (or links) are not safe

      abbodi86
      AskWoody_MVP

      It’s not the first time they release D Week CU on last days of the month

      KB4568831 have been in Release Preview Channel since 2020-07-24, and got two versions

      2 users thanked author for this post.
      abbodi86
      AskWoody_MVP
          File: dotNetFx4_ESU_Installer_r.zip  
      
         SHA-1: 574937759d3dface77aa91082d80808ef093d65f  
      
       SHA-256: 3e1f48478404cc3fc372d4b8d00cc5e5b532bee64ab9d78f5ecf2ddda49e1227
      1 user thanked author for this post.
      abbodi86
      AskWoody_MVP

      Yes, i just tested TargetReleaseVersion 1803 on Home 1803
      no feature update offered

      but like anonymous said, windows update queue should be clear

      after setting the registry, run these in command prompt as administrator, then reboot
      https://pastebin.com/mwKtTf5N

      2 users thanked author for this post.
      abbodi86
      AskWoody_MVP

      I think this new version adds support for activating ESU licenses via KMS

      of course, the required GVLK/CSVLK are unknown yet

      1 user thanked author for this post.
      in reply to: Patch Lady – so why did I get that? #2284137
      abbodi86
      AskWoody_MVP

      Nothing i’m aware of
      Settings WU page always tend to be difficult
      you could try these command to clear the queue
      https://pastebin.com/Ec5SxTMg

      after UsoClient.exe RefreshSettings, wait a few seconds before opening WU page and running UsoClient.exe StartScan

      1 user thanked author for this post.
      in reply to: Patch Lady – the different “offerings” #2284124
      abbodi86
      AskWoody_MVP

      If you have 2020-07-14 Security .NET CU installed, the 2020-07-21 Preview .NET CU will be detected and offered during the scheduled scans (technical term Non Interactive)

      and since it’s handled by the legacy WU agent, the only way not to get it auto-installed is either metered connection or policy AUOptions = 2

      if you don’t have the Security installed, the Preview one won’t show up during the scheduled scans

      1 user thanked author for this post.
      abbodi86
      AskWoody_MVP

      I did not verify it, but i think the TargetReleaseVersion registry works for Home editions too

      if he want to try

      reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /f /v TargetReleaseVersion /t REG_DWORD /d 1

      reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /f /v TargetReleaseVersionInfo /t REG_SZ /d 1903

      2 users thanked author for this post.
      in reply to: Patch Lady – so why did I get that? #2284115
      abbodi86
      AskWoody_MVP

      but a Week “C” Optional Cumulative Update Preview is in the same category as a Feature Update?

      Yes, thus it’s affected by Feature Deferral

      the “B” Security CU is affected by Quality Deferral

      1 user thanked author for this post.
    Viewing 15 posts - 1 through 15 (of 1,626 total)