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
  • It’s official 20H2 is now out

    Posted on Susan Bradley Comment on the AskWoody Lounge

    Home Forums AskWoody blog It’s official 20H2 is now out

    Viewing 16 reply threads
    • Author
      Posts
      • #2305722 Reply
        Susan Bradley
        Da Boss
      • #2305736 Reply
        Microfix
        AskWoody MVP

        Lawrence Abrams over on bleepingcomputer provides a method to download the ISO without the need for the MCT when using Chredge or Chrome in Windows. A browser Useragent extension provides the same result for Firefox in Windows.

        Looks like MSFT have ramped up security in 20H2, which can only be a good thing IMO
        Info on this over on: bleepingcomputer

        No problem can be solved from the same level of consciousness that created IT - AE
        2 users thanked author for this post.
      • #2305741 Reply
        Lars220
        AskWoody Lounger

        And do not forget important article by well known and respected authors concerning the shiny new 20H2 Windows 10 feature update.

        How to block the Windows 10 October 2020 Update, version 20H2, from installing

        By Susan Bradley and Woody Leonhard – Computerworld – OCT 12, 2020

        My Favorite Authors! (along with Microfix, PKCano, Rick Corbett, and all MVP’s)

        1 user thanked author for this post.
      • #2305746 Reply
        DRW
        AskWoody Lounger

        Haven’t been nagged yet (I use Pro to require my giving permission to download and install). But I guess it’s time for my daily backup to be safe.

      • #2305747 Reply
        EP
        AskWoody_MVP

        Official 20H2 ISOs & ESDs seem to have build 19042.572 (KB4579311 CU integrated)

        ok bbearren, wherever you are – go ahead and try out 20H2 now

        • This reply was modified 1 month ago by EP.
        • #2305760 Reply
          abbodi86
          AskWoody_MVP

          AFAIK, ready ISOs are 19042.508

          WSUS ESDs are also 19042.508

          2 users thanked author for this post.
          • #2305773 Reply
            anonymous
            Guest

            The ISO I just downloaded with MCT is 19042.572 (as checked with dism /get-wiminfo /wimfile).

        • #2305826 Reply
          bbearren
          AskWoody MVP

          Official 20H2 ISOs & ESDs seem to have build 19042.572 (KB4579311 CU integrated) ok bbearren, wherever you are – go ahead and try out 20H2 now

          Got it this morning, but the MCT was having trouble creating the USB version, so I downloaded the ISO, mounted it, and did an in-place upgrade on the A side of my daily driver.  No, I did not disconnect from the internet for the upgrade.

          20H2

          So far, so good.  It took about as long as 2004 for the installation, but no hiccups.  It has found a ‘bad parameter’ in Windows Apps, but that is not what I consider a real issue, since I don’t really use apps, anyway.

           

           

          Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
          "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns
          "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

          Attachments:
          1 user thanked author for this post.
          • #2305840 Reply
            Bob99
            AskWoody Plus

            How did you find out about the “bad parameter” in the Windows apps? Event log entry, or a note pop up on the screen momentarily during 20H2’s post-installation configuration phase?

            • #2305858 Reply
              bbearren
              AskWoody MVP

              How did you find out about the “bad parameter” in the Windows apps? Event log entry, or a note pop up on the screen momentarily during 20H2’s post-installation configuration phase?

              After the “Hi” session finished and the normal desktop appeared.  So far it only has an effect on Solitaire, but I’ve got most of the others removed, anyway.

              Edit: The same popup occurs on a reboot, but then I don’t reboot that often, either.

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns
              "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

              • This reply was modified 1 month ago by bbearren.
          • #2305877 Reply
            bbearren
            AskWoody MVP

            So far, so good. It took about as long as 2004 for the installation, but no hiccups.

            One hiccup so far; it brought back all those “Special Folders” for which I have absolutely no use.  Thankfully, I have a couple of .reg files that yanks them out by the roots.  They’re gone, now.

            Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
            "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns
            "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

            2 users thanked author for this post.
            • #2305999 Reply
              bbearren
              AskWoody MVP

              It has found a ‘bad parameter’ in Windows Apps

              The “bad parameter” seems to have sorted itself out.  Earlier this morning I booted in to the B side to do some stuff, and when I booted back into the A side, no popup, and the Solitaire icon has reappeared on my Taskbar.

              Other than the “Special Folders” (which I’ve already removed), there are some changes in Control Panel/Settings, but nothing glaringly obnoxious in my view, and none of my settings have been reset to Default.

              Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
              "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns
              "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

      • #2305753 Reply
        PKCano
        Da Boss

        I reduced the Feature Update Deferral in my v2004 from 365 days to 0 days.
        Ran wushowhide and v20H2 is available.
        I’m not ready yet, so I reset the Feature deferral to 365.

        Just wanted to see if it was out there!

        3 users thanked author for this post.
        • #2305841 Reply
          Bob99
          AskWoody Plus

          So, if I understand the deferral days feature correctly, since I’m on 2004, if I set the Feature Update deferral next Tuesday to 7 or less, then 20H2 should show up in wushowhide, correct?

          The way I understand it from reading the AKB, it amounts to the number of days deferral for a feature update released after the one we’re currently on. So, since I’m on 2004, if today I were to set my Feature Update deferral to 14 days, then on November 3rd, I’d be offered 20H2 by Windows Update for download and installation since I have Automatic Updates set to 2, correct?

          • #2305842 Reply
            PKCano
            Da Boss

            Today is Feature deferral = 0, tomorrow deferral 0 or 1, Thursday 0 – 3, etc. for 20H2.
            As long as you don’t set Pause or Metered connections, with the “2” setting it should hang up in the queue until you say “GO.”

      • #2305796 Reply
        cyberSAR
        AskWoody Plus

        Just fired up a fresh 1909 VM that hasn’t been updated since Feb. Dropped Feature update to 0 and left Quality Update at 30. 20H2 started downloading and installing. No Click here to upgrade offered.

        In my mind when I’m ready (and it won’t be soon) to upgrade production machines I’d just as soon skip 2004 and go straight to 20H2 as long as it doesn’t introduce more bugs than 2004

        • #2305797 Reply
          PKCano
          Da Boss

          But 2004 and 20H2 are the same thing except for the new features being turned on in the latter. The core is the same, they have the same updates. I can’t imagine 20H2 not having the same problems.

          • #2305798 Reply
            cyberSAR
            AskWoody Plus

            I know. It just eliminates a step. When doing a bunch of machines it does save a considerable amount of time with reboots and such. I’m just hoping they get some of the stupid 2004 bugs fixed

      • #2305815 Reply
        Barry
        AskWoody Plus

        I just downloaded and installed it. It did not show up when I checked for updates so i used the upgrade assistant.

        It took longer than I expected about a hour and 15 minutes mostly install. So much for the intermediate upgrades being faster.

        This brings me up to version 19042.572

        I was under the impression this had the new start menu but I sure done see any changes.

        Barry
        Windows 10 Home V 20H2

      • #2305992 Reply
        dhdoyle
        AskWoody Plus

        I have weaponized my Windows update blocking by installing StopUpdates10. I pause it when Woody recommends that we go ahead and get patched.

        It seems to absolutely stop Windows Update. With the hard block running, I can’t even install stand-alone updates that I download.

        1 user thanked author for this post.
      • #2306230 Reply
        bbearren
        AskWoody MVP

        The B side of the dual boot on my daily driver constrains 20H2 to a “Keep nothing” in-place upgrade.  The B side is split up into an unsupported configuration; the major Windows folders (Windows, Program Files and Users) are on three separate SSD’s.

        My alternatives are to put it back together, upgrade, then split it back up, or to crack open install.wim and edit the .XML file(s) to suit my configuration.  I haven’t quite decided, but I’m leaning strongly toward editing the .XML file(s), as that will probably be quicker, and no doubt I’ll learn a few things in the process.

        I know that editing the .XML file will work on a clean install, but I don’t know if it will work for an in-place upgrade.  That will be the first hurdle, which adds a level of interest to going that route.

        Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
        "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns
        "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

      • #2306282 Reply
        abbodi86
        AskWoody_MVP

        Not yet known issue:
        you cannot do in-place upgrade for 20H2 OS using 20H2 ISO

        CONX   CHostIsNewerChecker invoked.
        CONX   pGetHostCSDBuildNumber: 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CSDBuildNumber' does not exist. Assume 0
        CONX   Host OS version: 10.0.19042.0  (0.0) Platform 0x2, SuiteMask 0x300, ProdType 0x1
        CONX   Target OS version: 10.0.19041.572
        CONX   ConX::Compatibility::CSystemAbstraction::HostIsNewer: Host is newer than target.
        CONX   CHostIsNewerChecker: checked HostIsNewer, found HardBlock.
        
        2 users thanked author for this post.
      • #2306285 Reply
        Alex5723
        AskWoody Plus

        you cannot do in-place upgrade

        You mean upgrade or repair ?
        This example is downgrading not upgrading.

        • #2306324 Reply
          EP
          AskWoody_MVP

          what he means is that you can NOT do an in-place “repair” upgrade from an older or IP 19042.x build to the “final” 19042.508 or 19042.572 build (it’s a confirmed bug)

          this same problem occurred with the 1909 ISOs with build 18363.418 last year, Alex
          the options to keep existing files & apps were grayed out in 1909/19H2 setup
          that in-place upgrade repair problem in 1909 was fixed with 18363.446 & higher builds

          and now is “un-fixed” in 20H2 from builds 19042.508 to 19042.572

          edit – an inplace upgrade from an older Win10 version (like 2004 or 1909) to 20H2 will still work and have options to keep existing user files & apps

          • This reply was modified 1 month ago by EP.
          • This reply was modified 1 month ago by EP.
          • This reply was modified 1 month ago by EP.
          2 users thanked author for this post.
          • #2306336 Reply
            joep517
            AskWoody MVP

            I downloaded the ISO yesterday, mounted it, ran setup.exe and I got the option to keep existing files and apps.

            Was running 19041.572 Pro.

            --Joe

            • This reply was modified 1 month ago by joep517.
          • #2306530 Reply
            abbodi86
            AskWoody_MVP

            It’s unfixed in any 19042 build, not necessary the final ones 🙂

            i think they fixed it for 1909 using the compatibility shim (appraiser.sdb or sysmain.sdb)

            • This reply was modified 1 month ago by abbodi86.
      • #2306377 Reply
        AlexEiffel
        AskWoody_MVP

        I guess Woody will not have had time to green light 2004 before it got replaced by 20H2. I suppose in theory after a few weeks one that likes running the latest and… <stridulation>… <stridulation> well.. should skip 2004 and directly go to 20H2 from 1909.

         

        1 user thanked author for this post.
      • #2306546 Reply
        geekdom
        AskWoody Plus

        I had a 2004 ISO disk dated May 2020. I installed from the disk while disconnected from internet.

        I then connected to internet and installed the latest 2004 cumulative update. The OS and Build for that computer is now 2004.19041.572; on minimal preliminary testing all seems to boot and run without error.

        G{ot backup} BetaTest
        offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WUMgr
        online▸ Win10Pro 2004.19041.630 x64 i5-9400 RAM16GB HDD Firefox84.0b4 WindowsDefender TRV=2004 WUMgr
        • This reply was modified 1 month ago by geekdom.
      • #2306565 Reply
        DriftyDonN
        AskWoody Plus

        I am using ver 1909 and want to continue to do so. Are  2004 and 20h2 FEATURE updates? Since we haven’t been given the GO for 2004 what advice re: 20h2?

        • #2306584 Reply
          Paul T
          AskWoody MVP

          Whatever 2004 and 20H2 are, they are not recommended for install by Woody.
          Stick to 1909, it’s supported for ages.

          cheers, Paul

          2 users thanked author for this post.
        • #2306625 Reply
          geekdom
          AskWoody Plus

          Practically, 2004 and 20H2 are for beta test.

          Stay with known and vetted versions.

          MS-DEFCON is the better guide for reliability and stability of versions and patches.

          G{ot backup} BetaTest
          offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WUMgr
          online▸ Win10Pro 2004.19041.630 x64 i5-9400 RAM16GB HDD Firefox84.0b4 WindowsDefender TRV=2004 WUMgr
          • This reply was modified 1 month ago by geekdom.
          1 user thanked author for this post.
      • #2306776 Reply
        firstmerk
        AskWoody Plus

        Downloaded and did a fresh install of 20H2. No problems, installed fine. I also have a test bed with 2004. It’s a raw install at this point, but I literally can’t tell the difference. Ability to do 1909 and earlier update controls in PRO are still gone. Only [Pause Updates] is available.

        IMO there is absolutely no compelling reason to update to 2004, and I see no reason to go to 20H2 either. Seems they offer no benefits, and may subject users to additional problems.

        Used to be reasonable to stay 6 months behind the update curve. Now its up to 1 year+. I think it may soon be 2 years…..if at all. What’s the point? More and more hassle, for less and less.

        Jeez, just gimme an OS that WORKS, and LEAVE ME ALONE!

        2 users thanked author for this post.
      • #2308024 Reply
        bbearren
        AskWoody MVP

        After 8 days of daily use on the A side of my dual boot daily driver, I’ve come across a small hiccup.  I have an all-in-one HP Officejet Pro 8600.  It has performed as usual until today when I wanted to scan a hard copy to my computer to turn it into a digital copy.  Scan to computer did not work.

        To make things simple, I decided to uninstall/reinstall the HP software/drivers.  I launched Process Hacker, then using Run as trusted installer I launched Revo Uninstaller Pro (this combination works much better and more cleanly that HP’s uninstaller) and uninstalled everything related to the all-in-one.

        I then reinstalled the software suite and ran quickly through the setup routine.  Scan to computer works again.

        Create a fresh drive image before making system changes/Windows updates, in case you need to start over!
        "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns
        "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

        1 user thanked author for this post.
    Viewing 16 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: It’s official 20H2 is now out

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.