• It’s time for 20H2

    Home » Forums » Newsletter and Homepage topics » It’s time for 20H2

    Author
    Topic
    #2355229

    PATCH WATCH By Susan Bradley Are you ready for 20H2? I am! If your computer hasn’t yet been offered 20H2, you aren’t alone. I’ve seen several laptops,
    [See the full post at: It’s time for 20H2]

    Susan Bradley Patch Lady/Prudent patcher

    4 users thanked author for this post.
    Viewing 24 reply threads
    Author
    Replies
    • #2355256

      Is this column a rerun?  You say “it’s clear that 20H2 will appear in May or June.”   My computer tells me it installed 20H2 last August (8/3/2020, to be exact).

      That said, one reason that’s bitten me more than once for not being offered the upgrade is the presence of a removable drive (a USB HDD or SDD, a flash drive, an SD card). I have a number of machines which, once I removed the drive, were immediately offered the upgrade and installed it quite handily. I mention this because this never gets mentioned yet it simple to check for and resolve.   (if one’s primary drive is without sufficient space for the upgrade, there is a process for using a flash drive during the upgrade process, as Susan points out, but Windows will ask for it when it’s ready – don’t try to get ahead of the game).

      With respect to the Dymo printing issue, I’ve updated two small LANs (mine and one client) that have Dymo Label printers (a Turbo 400 and a Turbo 450, respectively)  shared on them.   The updates were done on or after March 29th and Windows update offered only KB5000802 (2021-03 Cumulative Update), not the other ones you mention in the Patch List.   After the upgrades, I did install the updated software that Dymo released last month and had no problems using either printer on its respective LAN from any PC on the LAN.

      Updates on all machines had been paused so the first time they saw 802 was when I started the upgrade process.  I presume the patch Microsoft offered at the end of March was revised from the initial one offered last Patch Tuesday.

       

      2 users thanked author for this post.
      • #2355261

        Is this column a rerun?

        20H2 was released in October 2020 but as 1909 was stable and supported there was no pressing reason to update. With the end of updates for 1909 that has now changed.

        cheers, Paul

      • #2355316

        Thanks to all who caught this typo. The paragraph that reads

        What’s a person to do? Given rumors and the fact that Microsoft itself has stated that 20H2 is in final testing, it’s clear that 20H2 will appear in May or June. We also know that 1909 will be out of support in May of 2021. So, it’s time to plan your upgrade to 20H2.

        Should read

        What’s a person to do? Given rumors and the fact that Microsoft itself has stated that 21H2 is in final testing, it’s clear that 21H2 will appear in May or June. We also know that 1909 will be out of support in May of 2021. So, it’s time to plan your upgrade to 20H2.

        (emphasis mine)

        This typo has been fixed in the online version of the newsletter.

        I apologize for the error.

    • #2355282

      Susan, I am confused about your article … quote … ” … Microsoft has stated that 20H2 is in final testing, it’s clear that 20H2 will appear in May or June.”

      Are you referring to May or June 2020 ?

      My 20H2 install date shows as 12th January 2021, so, if it’s in final testing will we be offered a revised install for 20H2 ?

    • #2355283

      Susan, ignore my last Post. I have just clicked on your Microsoft link and it is clear you meant 21H1. Typos eh, they drive us nuts !

      • #2355363

        I screw up the numbering system of this new fangled way EVERY TIME.  Ugh!  I think I’m just going to start calling it 2104 or 2105 as that sticks in my head better than 21Hwhatever.

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
        • #2355556

          I’m with you, Susan! Microsoft Speak is soooo hard to parse!

          -- rc primak

    • #2355294

      You mention the registry editor — isn’t it easier just to use gpedit, adming, windows componenets and edit the “desired version” right there?

      1 user thanked author for this post.
      • #2355310

        Users of Windows 10 Home do not have the group policy editor.

        --Joe

        2 users thanked author for this post.
      • #2355430

        Most Windows 10 users have the Home edition, so since GPedit is only available in Pro, the registry method is advised since anyone can apply it.

        Edit: Sorry, Joe. Didn’t see your posts at first 🙂

        • This reply was modified 3 years, 11 months ago by Coldheart9020.
        • #2355559

          Susan recommends Pro, and in the Lounge there are instructions for Pro’s Group Policies. Thanks, PK Cano!

          -- rc primak

      • #2355557

        You mention the registry editor — isn’t it easier just to use gpedit >> admin >>windows components and edit the “desired version” right there?

        [edited for typos]

        Given Susan’s recommendation to upgrade to Pro, I was thinking the same question.

        -- rc primak

        • This reply was modified 3 years, 11 months ago by rc primak.
    • #2355325

      I understand that, but Susan doesn’t even *mention* the gpedit path, whereas if you /pro using it ought to be your _first_  choice, no?

      1 user thanked author for this post.
      • #2355345

        Perhaps. The article presents an easy method for everyone. No need for a second set of instructions which could lead to extra questions and confusion for some. For those who are used to GPedit, your method is an easy way to accomplish the same thing.

        --Joe

        1 user thanked author for this post.
      • #2355409

        IMHO the reg key method is the easiest way.

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
        • #2355561

          And there are instructions for the Group Policies in the Lounge. Those could be referenced in the article. Since your recommendation is for users to upgrade to Pro, this is one of the prime reasons to do so. GPEdit is safer than editing the Registry.

          -- rc primak

    • #2355341

      Susan, I’m on Version 2004 (OS Build 19041.870). My GP for feature updates is set for 2004. Everything is working just fine for me.

      I’m confused why you’re suggesting an upgrade to (OS Build 19042.572) What advantages are there for me to change things now? Did I misread your post?

      I’m using Win 10 Pro. A Belarc scan today says I’m up to date.

      Peace,

      CAS

      • #2355353

        20H1 and 20H2 have the same code base. To upgrade to 20H2 from 2004, you install a simple enablement package turning on code that is already there. If you are already on 2004 the upgrade should be quick and painless. BUT, always make a system backup before beginning the upgrade process. You’ll end up with version 19042.870.

        The primary reason Susan recommends 20H2 is the longer support window. It is supported until March 2022. The support time frame for Windows 10 Home & Pro is 18 months from release. 2004 will be out of support this fall.

        --Joe

        3 users thanked author for this post.
        • #2355376

          actually joep517, support for Win10 version 2004 will end in December 2021 as noted here (12/14/2021 to be exact)

          and support for Win10 version 20H2 Home/Pro will be up to May 2022 (not March 2022) as noted in the link page

          1 user thanked author for this post.
      • #2355361

        Support window. It gets you to a longer window of time for updates.

        Susan Bradley Patch Lady/Prudent patcher

        2 users thanked author for this post.
        • #2355379

          What changes should I make to my group policy settings before and after the upgrade? I’ll likely do it sometime this week.

          Thanks for helping me to understand things. That’s why this site is the first I open once I’m online.

          CAS

          1 user thanked author for this post.
          • #2355396

            From 2004 to 20H2, none that I have seen. The upgrade takes a couple of minutes.
            The same will happen with 20H2 to 21H1.

            • This reply was modified 3 years, 11 months ago by Alex5723.
            1 user thanked author for this post.
            • #2355470

              Alex, you are correct. It only took a few minutes to install 20H2 but it took a bit more time for me to disable MS Edge the best I could using Revo and group policy settings. I’m now On 20H2 (OS Build 19042.870).

              CAS

          • #2355402

            Once you upgrade to 20H2, you will need to change the TRV setting to 20H2 or turn TRV off (if you have it set. If you do not do so, you may not get updates. The Microsoft documentation says:

            When you set the target version policy, if you specify a feature update version that is older than your current version or set a value that isn’t valid, the device will not receive any feature updates until the policy is updated. When you specify target version policy, feature update deferrals will not be in effect.

            2 users thanked author for this post.
    • #2355412

      20H2 was released in October 2020

      Wonder why all my computers say it was installed on 8/3/2020.

      • #2355415
        1 user thanked author for this post.
      • #2355576

        20H2 was released in October 2020

        HCLV941 wrote: 

        Wonder why all my computers say it was installed on 8/3/2020.

        This appears to be an internal Microsoft date. They finalize the code for a new Feature Update some time before the Feature Update is actually rolled out.

         

        -- rc primak

        • This reply was modified 3 years, 11 months ago by rc primak.
        • This reply was modified 3 years, 11 months ago by rc primak.
        • This reply was modified 3 years, 11 months ago by rc primak.
        • This reply was modified 3 years, 11 months ago by rc primak. Reason: Several rounds of HTML Code removal
    • #2355511

      I installed Windows 10 Pro 1909 last year on a new PC I built, however I’ve never used it. Here it is about 8 months later & figured it’s time to update the PC & put it to use. What would be the best way to do Windows updates?

      Update to 2004 & then 20H2, or go directly to 20H2  ?

      Do a fresh install of 20H2 ? I’d have to re-install the chipset, graphics & audio drivers. In which case why not just update to 20H2?

      The simplest way would be to connect the PC to the Internet & just let it do its thing.

      Any suggestions & comments would be appreciated.

      Thanks.

       

    • #2355517

      Go to https://www.microsoft.com/en-us/software-download/windows10 and click on update now.  You’ll get 20H2.  I wouldn’t do a fresh install.

      Susan Bradley Patch Lady/Prudent patcher

      3 users thanked author for this post.
      • #2355524

        Is it advisable or indeed needed, to either disable TRV in GPedit or to change it to 20H2 (currently at 1909) before going ahead with the update?

        • #2355567

          Is it advisable or indeed needed, to either disable TRV in GPedit or to change it to 20H2 (currently at 1909) before going ahead with the update?

          I usually update the Targeted Release Version to the next level I’m upgrading to, before actually doing the upgrade. I don’t know what the official advice is.

          (I am posting anonymously because the automatic spambot detectors in the Lounge blacklisted me tonight. )

          — rc primak —

          1 user thanked author for this post.
    • #2355526

      A question for Susan Bradley:

      Is the method that you that describe in this week’s AskWoody Plus Newsletter 18.12.0 for upgrading to Windows 10 20H2 your preferred methodology even when 20H2 is offered by Windows Update? If so, why do you prefer your methodology over simply letting Windows Update install 20H2?

      Thanks.

    • #2355533

      Go to https://www.microsoft.com/en-us/software-download/windows10 and click on update now.  You’ll get 20H2.  I wouldn’t do a fresh install.

      It looks like the installation media can be used for a fresh install of Windows 10 or to upgrade Windows 10.

      When upgrading it says “Select Change what to keep to set whether you would like to Keep personal files and apps, or Keep personal files only, or choose to keep Nothing during the upgrade.”

      If I want to keep the drivers that I’ve installed does that fall under personal files or apps?

      If I choose Nothing, how does that differ from doing a clean install?

    • #2355657

      Thanks Susan for the detailed video on how to get 20H2.

      Quick question though; I am still running 1909 and by using your method, will this correct any underlying issues that I may have experienced with my original build?

      By underlying issues – as an example; to date I have yet to be able to install a Cumulative Update for KB5001028 along with all previous iterations since roughly KB4577671.  (Note: KB5001028 has now been replaced by KB5000808 and possibly others which again, I doubt will also install correctly on my system!)

      • #2355660

        In technology I can never guarantee….but yes this is a way to kick WU components into working order. I once fixed a misbehaving 1809 by going to 1909 using the same methodology.

        Susan Bradley Patch Lady/Prudent patcher

        • #2356261

          Thanks for the information Susan.

          I decided to give this a go following the details outlined in your video and the process appeared to be running okay – taking roughly 45 minutes to an hour.

          As I was working on my tablet, I could keep an eye on my desktop and noticed the message about the system needing to reboot several times.  However, there was something ‘hinky’ as it was rebooting quickly and only displaying the ‘HP’ logo which went on for about 5 minutes in a continuous loop until I intervened.

          After trying a few of the boot options to no avail, I booted from a YUMI USB drive and examined the system with Acronis Disk Director only to find that the system partition (C:)  was empty and unformatted (leaving my other two data partitions intact).

          Luckily, I have been able to restore my system image (taken just prior) and I’m back to where I started.  Not sure why this occured, but I think my only option to get to 20H2 is a clean install?!

          • #2356407

            Is your disk set up unusually? You should have a small (100MB) partition and then C:, followed by any recovery partition and then maybe data.

            cheers, Paul

            • #2356457

              Thanks Paul T.

              My apologies; should have elaborated a bit more!

              My system has a 100MB EFI System Partition, C: (System) and then two data partitions.

              The Recovery Partition (of 500MB) I removed as it was only a 128GB SSD (i.e., 119GB usable space) and on hindsight, I’m not sure if by doing that may have caused this specific issue?

              Would appreciate your thoughts but am thinking a ‘clean install’ will clear up any niggly issues.

            • #2356598

              If you had already removed the recovery partition and it still worked, then the issue is elsewhere.

              I see 2 options:
              1. Restore from backup, including the recovery partition – 500MB is <0.5% of your space – and upgrade. You may still run into the problem.
              2. Reinstall from USB booted Windows installer.

              cheers, Paul

    • #2355682

      Hi Susan,

      It’s not often I need help but This 20H2 has got me going!

      I’m having to use my old Acer Laptop, Aspire 9304WSMi at present due to failure of main PC. Now this started life with Vista , wayback to 29 April 2008 as a big screen machine for my wife to mark Exam Papers for UK Education,

      This has progressed through Win7 to Win10 and has generally worked well except for the first version of win7 which dumped the original screen driver which was an Acer Special for this early large screen format. This was 2007 tech with a 17″ screen, 1440 x 900 Resolution. AMD Turion 64 X2,2GB Ram and  160GB disk. The disk has only used about 50GB of the 160Gb so space isn’t the problem.

      Last weekend I had the message that the HN09 that was running was OOD and was to be replaced regardless!  It churned away for what seemed like hours, hanging at something like 91% for an hour.

      Then comes the fun, reinstalling the Utilities for email and browsing. My email is Thunderbird and that went in OK with no serious problems. Just seems very slow downloading but otherwise OK

      But and it’s  Big ‘but’, Firefox seems a no go, hanging, not responding, not able to install from Task Bar ,slow download! Looking at File Explorer was no help, So gave up and tried Edge as provided, which gives a wonderful quick response, very stable. The question in my mind has MS done something to discurage other browsers? There’s also the problem  with this Edge that all calls for website are sent to Bing first and without trying the website? And then  there is also this mystery utility which turns up preventing shut down! Am I expecting to much?

      Suggestion to speeding up response appreciated

       

      • #2355726

        Could you translate HN09 and OOD?

        • #2355735

          HN09 I think he is referring to possibly 1809 or 1909 Win10, and OOD means out of date, i.e. end of service (or near).

          oldpaul – Something you could try is, in Command Prompt as an Administrator, run the following commands (in the order provided):

          DISM /online /cleanup-image /restorehealth

          sfc /scannow

          I recently (a few hours ago) updated from 1909 to 20H2 and after both commands issues were identified and fixed, as can be seen from the screenshot I’ve attached. After running both, reboot and hopefully it will help with stability.

    • #2355793

      I’ve been offered 20H2 as an optional feature update for several months.  I’m currently on 20H1, Windows 10 Home, version 19041.804 (I haven’t updated March yet), managing updates with a metered connection and wushowhide.

      It sounds like it might be time to take that big step.

      • #2355805

        It’s a little step from 20H1 to 20H2. Should take about 20 minutes – after a full backup, of course.

        cheers, Paul

    • #2356357

      So I don’t forget, I am using win10 pro version 2004 (OS Bld 19041.870)

      I have TVU set to 2004.

      Awhile back, it was suggested we ‘squirrel’ away the 20H2 ISO from Heidoc site- 21Feb21

      As patch Tues is approaching, would I be better off installing from the external copy while offline so I can get group policy settings to my liking and also avoid the upcoming patch?

      (after imaging off course!)

      Many thanks and stay well!

      D

      PS I did watch your video-clear and concise!

      Just noticed offered KB5000842 optional QU preview ?? What to do…I want to skip this as it’s a preview- I don’t know why I got this as I haven’t been getting previews for awhile . I think I set grp policy to NO previews? Not sure.

      • This reply was modified 3 years, 11 months ago by DriftyDonN.
      • This reply was modified 3 years, 11 months ago by DriftyDonN. Reason: corrections and date added
      • #2356373

        Since you have Windows 10 Pro, you can apply the settings within the Windows Update for Business portion of Group Policy. They’re listed under the “folder” for Windows Update. Simply set the “Select when Preview Builds and Feature Updates are received” setting to Enabled and then specify either zero or one days’ deferral time for the number of days to defer the update. DO NOT enter a date in the box below the one for the number of days’ deferral. Also be sure to set the drop-down box above that to “Semi-Annual Channel” to help ensure you only get the updates that are formally released for the general public and are not beta (or preview) releases.

        Also, ensure that you have enabled the setting for Quality Updates’ deferral and either set the number of days’ time to either zero or 1. Also leave the box below that blank, DO NOT enter a date.

        That should keep you from seeing any previews of any kind, including the monthly .NET previews that usually come out in the third or fourth week of the month.

        R/

        Bob99

        2 users thanked author for this post.
        • #2356475

          Most interested in going from 2004 to 20H2- from ISO downloaded in Feb or update as indicated in video. I have been using the ISO manual method up til now. If I use the feb ISO I got from Heidoc, and install offline, how many updates will I have missed? Looks like I may go with Susans’s online method this time.

          The preview settings you mentioned also include feature releases?

          I have WU settings at 2-Notify, DONT download (PKano method)

          • This reply was modified 3 years, 11 months ago by DriftyDonN. Reason: clarify
    • #2356395

      I’m still not sure about the Windows update settings.

      I have Windows 10 Pro version 1909 and opened the Local Group Policy Editor, then Computer Configuration, then Administrative Templates, then Windows Components, then Windows Update, then Windows Update for Business. I then went to Select the target Feature Update version, Enabled it and entered 20H2.

      What about settings in Local Group Policy Editor > Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Automatic Updates? IOW the non-business settings?

      Currently mine is set at Non Configured, but I’m not sure if that’s the default or what it should be because I did change some settings long time ago. In a previous guide it was suggested to Configure automatic updates = Enabled, value 2 (notify download/install). Should I still do that even though the target feature update is set at 20H2?

      Lastly, I hope, what should the GUI settings be? Should the feature updates be deferred for 0 days or 365 days? And defer the quality updates for 30 days?

      Any suggestions & comments would be appreciated. Hopefully I’ll get Windows 10 properly setup & updated this weekend.
      Thanks.

      • #2356396

        Since you have set the targetreleaseversion setting, there is no need to set the feature release of 365 days.

        I don’t defer quality updates for 30 days, IMHO that’s too much. Something in the middle that makes you feel comfy is better…say 15 days?

        Non configured is the default settings.

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
    • #2356402

      Since you have set the targetreleaseversion setting, there is no need to set the feature release of 365 days.

      I don’t defer quality updates for 30 days, IMHO that’s too much. Something in the middle that makes you feel comfy is better…say 15 days?

      Non configured is the default settings.

      But what should the feature updates deferred setting be set at in order to avoid any potential conflict? The choices are all numbers from 0 to 365. There is nothing such as “does not apply”.

       

      • #2356405

        From 2000016: Guide for Windows Update Settings for Windows 10

        **NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both to achieve update control. If you use TargetReleaseVersion, you should also ***set deferrals to 0 0r 1 instead of 365 as shown in the second screenshot in #2275043. They are going to be ignored anyway.

        cheers, Paul

        1 user thanked author for this post.
    • #2356419

      But what should the feature updates deferred setting be set at in order to avoid any potential conflict?

      With TVR set, no deferrals needed.
      Set ‘Configure Automatic Updates’ = enable – 2 notify for download. This way you control when and what to update / hide (using WUmgr)

    • #2356427

      From 2000016: Guide for Windows Update Settings for Windows 10

      **NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both to achieve update control. If you use TargetReleaseVersion, you should also ***set deferrals to 0 0r 1 instead of 365 as shown in the second screenshot in #2275043. They are going to be ignored anyway.

      cheers, Paul

      Thanks for the reply.

      I was referring to the GUI settings.

      I click on the Windows search bar in the lower left corner of the screen & it opens a window where I can click on “Settings”. This opens a window called “Windows Settings” where I then click on “Update & Security”. That takes me to a window menu where I can click on “Advanced options”. The last two items are under a subtitle called “Choose when updates are installed”. For feature updates I have to select a number from 0 to 365. There is no option to leave it blank, and you cannot select “not configured” as in the group policy editor.

      Windows 10 is still new to me & from my perspective it seems the group policy editor & the GUI settings are both controlling updates, and I don’t know which one takes precedence. I’ll set the GUI setting to “0” deferred days for feature updates since it cannot be disabled.

      Thanks

      • #2356435

        Use Group Policy Editor to set the update arrangement. The W10 GUI does not have the options you need – MS took them away.

        cheers, Paul

        2 users thanked author for this post.
      • #2356468

        @BrerBear

        What folks are trying to tell you is that, although you still have the GUI settings in the Advanced options of Windows Update on your installation of version 1909, once you make the jump to 20H2, they will be gone.

        In 20H2 (and 2004 for that matter), MS replaced some of the Advanced options in the GUI with the equivalently-named settings in Windows Update for Business within GPEdit, which you sound like you’re already somewhat familiar with.

        Lastly, I hope, what should the GUI settings be? Should the feature updates be deferred for 0 days or 365 days? And defer the quality updates for 30 days?

        While you’re still on 1909, I would keep the settings in the GUI set as recommended on this thread for Feature Updates (enabled but set the number of days’ deferral to either zero or one) and set the Quality Updates to 15 for now.

        Bear in mind that setting the Quality Updates deferral determines how long until you’re offered the update. Setting it to 15 means that, for April, Windows Update will offer you the monthly Quality Update starting on April 28th, which is around the time that we may get the go-ahead to install the April monthly Quality Update from Susan.

        Since you’ve set the Target Release Version to 20H2, you should be offered the upgrade to 20H2 any day now, maybe even as you’re reading this entry. If you haven’t been offered the update to 20H2 within about a week from now, check back here and we’ll help you find out why.

        Also, please keep in mind that if you’re offered the upgrade to 20H2 after 10AM Pacific Time April 12th, it will include the April monthly Quality Update as part of the upgrade process.

         

        1 user thanked author for this post.
    • #2356483

      Thanks Paul T and anonymous.

      I followed the instructions in message #2355537 and did the update to 20H2. I let it run overnight because my Internet is not the fastest. Restarted the PC this morning & it now has 20H2.

      As you mentioned above, it no longer has the same GUI advanced settings available. The Group Policy Editor still shows the Target Release Version of 20H2 and I set the Quality Updates deferral to 15 days.

      Everything looks good & now to install some software & start using Windows 10.

      Thanks everyone for all your help.

    • #2357916

      From 2000016: Guide for Windows Update Settings for Windows 10

      **NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both to achieve update control. If you use TargetReleaseVersion, you should also ***set deferrals to 0 0r 1 instead of 365 as shown in the second screenshot in #2275043. They are going to be ignored anyway.

      cheers, Paul

      I set the TargetReleaseVersion to 20H2 and that is what I now have. What happens when/if there is a new build for that version (or any given version)? Can it be delayed or will Windows 10 automatically download & install the new build?

       

      • #2357937

        If you read AKB2000016, you will find the answers to youe questions about Windows Update Settings.

        If you are on an earlier version, AND you set TRV to a later version, Windows Update will offer you the later version through Windows Update. It is one way way to upgrade to the later version. That is what you are asking for.

        If you are on a given version AND you set TRV to that same given version, Windows Update will not offer you a later version until you reset TRV to that later version. It will hold you on your set version. That is what you are asking for.

        If you set Automatic Updates = Enabled, value = 2 “(notify download/install), whatever updates are offered by Windows Updates will NOT download/install, but remain in the update queue, until you click on the “Download” button. In that case you do not need Deferrals (they should be set to 0 or 1), Pause, or Metered connections.

    • #2358013

      I was wondering about build versions vs feature update versions.

      I have Windows 10 version 20H2 with build 19042.867.

      This lists a build of 19042.928 with date of 2021-04-13, and it’s still for 20H2.

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

      If TRV is set to 20H2 and I already have 20H2, that should mean I will not get any updates. How would I get build 19042.928, presuming I wanted it?

       

      • #2358017

        20H2 is a version. Build 19042 signifies it is version 20H2.
        2004 is a version. Build 19041 signifies it is version 2004.
        Both of these are Feature (version) Updates.

        Build 19042.867 is version 20H2 with the March Monthly Cumulative Update KB5000802 installed.
        Build 19042.928 is version 20H2 with the April Monthly Cumulative Update KB5001330 installed.
        The .xxx on the end of the Build number tells you which Quality (Monthly) Update is installed.

        TRV selects the version you are on. It regulates the Feature (version) Upgrades.
        It does not effect whether you get Monthly updates or not.

         

        1 user thanked author for this post.
    • #2359271

      Anyone know if there is a way to roll out TargetedReleaseVersion in a user-friendly way yet?

      We’ve got a handful of organizations that we support who run Windows 10 Pro, and have now realized that they don’t need shared office space any longer, so they’re running standalone computers from home. It’s not effective for us to make 3-4 home visits to set a 10-minute setting, but if someone’s come up with a little UI that provides a list of versions and sets it, we could teach them to use that.

    • #2359421

      The issue here is that the user needs to run any command / program with elevated permission.
      The easiest is to run the appropriate REG file as provided by Susan.
      Alternatively, you can provide users with a simple batch file to change the registry value.

      If you still need a GUI type app to let your users make the required change, let us know and we’ll see what we can come up with.

      cheers, Paul

      1 user thanked author for this post.
    • #2360726

      Today I noticed that last week windows update tried to install feature update from 1909 to 2004 and failed.  So I went to the microsoft download site and clicked update to install that way.  First time it failed and I rebooted and turned off antivirus and then it worked, I am typing from 20H2 now.  I can’t tell any difference, the install took many hours after the download.  Hopefully it was worth it for security.  At least I didn’t have to do clean install or reinstall any apps, it was seamless once I got it to work.

    Viewing 24 reply threads
    Reply To: It’s time for 20H2

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

    Your information: