News, tips, advice, support for Windows, Office, PCs & more
Home icon Home icon Home icon Email icon RSS icon

We're community supported and proud of it!

  • Tasks for the weekend – September 18, 2021 – it’s squirrel away time

    Home » Forums » AskWoody blog » Tasks for the weekend – September 18, 2021 – it’s squirrel away time

    • This topic has 43 replies, 16 voices, and was last updated 1 month ago.
    Author
    Topic
    #2390580

    (Video here) It’s squirrel away time. Time to download a copy of Windows 10 21H1 and ensure you have a copy in case you need it to do a repair install
    [See the full post at: Tasks for the weekend – September 18, 2021 – it’s squirrel away time]

    Susan Bradley Patch Lady

    3 users thanked author for this post.
    Viewing 17 reply threads
    Author
    Replies
    • #2390591

      (Video here) It’s squirrel away time. Time to download a copy of Windows 10 21H1 and ensure you have a copy in case you need it to do a repair install
      [See the full post at: Tasks for the weekend – September 18, 2021 – it’s squirrel away time]

      This is always good advice. I keep flash drives of the last two release channel versions of Windwos 10, and older versions on DVD’s. It was interesting to watch Windows 10 ISO grow from about 3.2 GB in 2015 to 5 GB starting with v.20H1.

      GreatAndPowerfulTech

    • #2390603

      I am still on Win 10 20H2 as I don’t recall you ever telling us to install Windows 10 21H1. At this point should one install Windows 10 21H1 or perhaps it doesn’t matter?

      • #2390607

        When I give the all clear for updates, I’ll remind you to go to 21H1.

        Susan Bradley Patch Lady

        2 users thanked author for this post.
      • #2390610

        Susan has been suggesting the move to 21H1 for over a month now.
        The easiest way is to set TRV to 21H1 and let Windows Update take care of it.

        1 user thanked author for this post.
    • #2390614

      Susan has been suggesting the move to 21H1 for over a month now.
      The easiest way is to set TRV to 21H1 and let Windows Update take care of it.

      Thanks to Susan and PK for clarification, which I understand to mean to do the feature update to Win 10 21H1 today.

      • #2390655

        If you use Windows Update to do the Feature Update today, you will get the September update(s) as part and parcel of the upgrade automatically. Right now, the September updates are all at level 2 of “Unless you have an immediate, pressing need to install a specific patch, don’t do it.” I take that to include performing a Feature Update at this time.

        Also, in post #2390610 just above, PK said

        The easiest way is to set TRV to 201H1 and let Windows Update take care of it.

        I added the bolding for emphasis above. The 201H1 for the setting is a simple, human, typo so please ignore it. I’m sure that PK meant to type “21H1” instead for that setting being referred to.

        Mods (Susan, PK, et. al.): If I’m somewhat misguided in the last sentence of the first paragraph of this post, please feel free to correct me.

        2 users thanked author for this post.
        • #2390657

          I use the .iso file to do feature updates because I have fewer problems than if I let Windows do it. Unfortunately, I did not understand what PK and Susan meant so I went ahead and did feature update today on 3 of 5 systems.

          This has created an unintentional mess. I didn’t realize they meant I should wait till Defcon4 for feature update since one was supposed to do feature update months ago. I wish Defcon system included information about what feature of Win10 we are supposed to be on.

          Do you think it’s necessary to somehow reverse the feature updates on 3 systems or just remove that part of it that is considered suspect?

          • #2390659

            I’ve never uninstalled a Feature Update, so ‘m not sure just what problems may arise for you, especially since you said that…

            I went ahead and did feature update today on 3 of 5 systems.

             

            This has created an unintenstional mess.

            I have checked on my systems and have found that I can uninstall the last feature Update I installed (the one from 20H2 to 21H1), using the “Programs and Features” app within Control Panel and then clicking on “View installed updates” in the upper left corner of the window. In that list is where the Feature Update to 21H1 is listed and, when I clicked on it to highlight it, the Uninstall option appeared above the listing of all of the installed updates. This shows that you should be able to uninstall it.

            However, if you do choose to uninstall the Feature update to await MS-DEFCON 3 or higher, please start a new topic for guidance from those here who can better help you should you experience problems uninstalling it or after uninstalling it and rebooting.

            1 user thanked author for this post.
          • #2390685

            Check printing make sure you can print.  If you can, leave it on.  Otherwise yes you can roll back off a feature release within 10 days of installing it.

            Susan Bradley Patch Lady

            1 user thanked author for this post.
          • #2390687

            Master Patch List @ AskWoody

            At the top of the master patch is is always the feature release version I’m recommending.  As you can see either 20H2 or 21H1 are fine.

            Susan Bradley Patch Lady

            1 user thanked author for this post.
            • #2390692

              Thanks Susan, I can still print on the updated systems so I will keep the feature update but wait to do a feature update on the final two systems till you give the go ahead.

              The Master Patch menu looks to be useful for checking the acceptable feature version. I’ll check it regularly for changes. I hadn’t been aware of it till you mentioned it.

    • #2390621

      With Win 11 released, it seems doubtful that there will be 21H2 feature release for the general Win 10 customer base.  (Perhaps something for business/enterprise customers with Win 10?)   From here out it seems most likely that Win 10 customers will receive the monthly security updates only until EOL.  Do you have other info to indicate differently?

      • #2390632

        Microsoft have confirmed a 21H2 feature release for everyone, and I’ve been running it in the Release Preview ring for more than two months:

        Today we will begin releasing 21H2 builds to Windows Insiders …

        Broad availability of Windows 10, version 21H2 will begin later in the second half of this calendar year.

        Introducing the next feature update to Windows 10: 21H2

        The exact availability date is not yet known, but it’s widely expected to be during October 2021.

        Windows 10 Pro version 21H2 build 19044.1320 + Microsoft 365 (group ASAP)

      • #2390686

        It’s literally currently in testing.  All of the marketing focus is on 11, but there for sure is a 21H2 in the works.  Windows 10 will be supported through 2025.

        Susan Bradley Patch Lady

    • #2390638

      Many thanks for this. Cute squirrel. I grabbed another copy because I think I tried the other one and had trouble with it so just to be sure!

      - ThinkPad T570-20HA, i7-7600U, 2.8GHz, UEFI/GPT, 16GB, Sammy 256GB M.2 NVMe PM961. HP M254dw & HP P1102w laserjets, Epson 2480 scanner -

    • #2390644

      Done.  I now have a shoebox full of these .iso files, in my closet next to my Palm Pilot and install disks for Office 2003.

      1 user thanked author for this post.
    • #2390691

      Windows 10 Pro version 21H1 is currently installed on my computer. After I use the Windows media creation tool to download and save an .iso file containing 21H1 is there any reason to keep .iso files of older versions of Windows?

    • #2390945

      The size of the 21H1-build .928 iso file is 4,449,344 KB. I burned it using CDBurner XP on a double layer disc (twice), but each time the verification failed with a message that there was either a problem with the CD drive or that the disc was of poor quality. But, then I put in a single layer CD and the writing process was successfully completed. The size of the SL disc in the CD drive is 4.24 GB

      The differs from the size of the 20H2-build .631 iso file, which is 4,784,256 KB. It would not burn to a single layer disc. The size of the DL 20H2 disc in the CD drive is 4.56 GB.

      Going back to the earliest one in this common core operating system, the size of 2004-build .572 iso file was 4,173,568 KB. Like 21H1, but not 20H2, it burned to a single layer disc. The size of the SL 2004 disc in the CD drive is 3.97 GB.

    • #2390962

      Huh? My Windows 10 Home system information says I’m running “Version 10.0.19042 Build 19042”. Is there a site at which I could easily get a kosher media creation tool for that? Merci.

      Finance, social and tech founder. Managing director of new crowd sourced games in pre-release development. Director on a new consortium to bring fractional ownership of heritage antiquities to the blockchain. My planet-wide talk show for people craving new stories by which to live is Casual Saints.
    • #2390998

      Huh? My Windows 10 Home system information says I’m running “Version 10.0.19042 Build 19042”. Is there a site at which I could easily get a kosher media creation tool for that? Merci.

      You can get any Windows 10 ISO from heidoc.net or using Rufus

      1 user thanked author for this post.
      • #2391038

        That’s an interesting idea, but what’s the catch? MS is not giving away Win 10 for free.

        • #2391048

          You may have to reinstall or repair your computer, you will need the installation media.
          If you get the ISO from MS, you have no choice but the latest version.
          But if what you want to reinstall or repair the previous version, for example, you need an ISO of that version to do the operation.
          So it makes sense to “squirrel away” the current ISO before the next version is released.

    • #2391055

      PK, I understand the need to have a backup Windows ISO. Askwoody regularly gives us the url to get those .iso files. But if I use an .iso file for a new build, then will it work without a  Windows product key?

      Isn’t that what I’m paying $200 for–the product key?

       

      • #2391057

        If your computer has Win already on it, it will activate automatically. The license is digitally tied to the machine online. You don’t need a key.

        You can Google “Windows 10 ISO download” and it will show you the MS website to get the ISO. But it will be an ISO for whatever the current version is, which may not be the version you have at the moment. So it you save the ISOs each time, you will be able to install the version you want.

        1 user thanked author for this post.
    • #2391063

      PK, I was thinking more about a new build. On Amazon I see this which is described as full retail version on USB flash for $119.

      Why would anyone pay $200 for a full retail version of Win 10 when one can buy it for $119 on Amazon? What am I missing?
      Windоws 10 Pro USB | English | 1 PC | USB Flash | Original Lifetime License | Windоws 10 Professional

    • #2391064

      That’s an interesting idea, but what’s the catch? MS is not giving away Win 10 for free.

      Yes, it does.
      If you don’t have a Windows license the ISO file won’t help you much.
      If you have a Windows 7, 8.1 license you can upgrade to Windows 10 for free.
      If you have a Windows 10 license (which is “written” in a component on your motherboard) you can download and choose the version you want to clean install/upgrade/repair..

      1 user thanked author for this post.
      • #2391075

        The license has to be a Retail license to move/transfer it to a different computer.
        If the license came installed on the current PC, it is probably an OEM license, which is NOT transferable to a different machine.

        2 users thanked author for this post.
        • #2391195

          The license has to be a Retail license to move/transfer it to a different computer.

          To get the skinny on your license, open a command prompt and type

          slmgr /dlv

          and hit Enter.  After a very short delay, you’ll get a message box something like this:

          Slmgr-dlv

          In the Windows Secrets days there were a couple of discussions about OEM/Retail licensing.  As it turned out at that time, upgrading an OEM Windows 7 Home license to Pro via the option available in Windows transformed it into a Retail license.

          Also, taking advantage of the Microsoft offer to upgrade Windows 7 to Windows 8/8.1/10 transformed OEM licenses to Retail.  To put this observation to the test, I migrated a Windows 10 installation to my NAS successfully about six years ago, it’s still running and still licensed, even after some hardware upgrades.

          YMMV

          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.
      • #2391202

        If you have a Windows 10 license (which is “written” in a component on your motherboard)

        The license is a hardware hash (and some other stuff) of your PC written in a Microsoft licensing server, not on a component on your motherboard.  Refer to post #2391195.

        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

    • #2391070

      So it you save the ISOs each time, you will be able to install the version you want.

      If your computer is running well with the latest Windows 10 version and you squirrel away an .iso of that version just before the next succeeding version is released is there any reason to keep .isos of older versions of Windows 10?

      1 user thanked author for this post.
      • #2391079

        Personally, I like to keep the ISO or install media from the last 2-3 versions (the ones that are not EOL). I’m a pack rat.
        But that’s up to you.

        1 user thanked author for this post.
    • #2391141
      Anyone else getting the “We need more space” error when attempting to “squirrel away” 21H1.  I got this on the 16 GB through and including a 128GB USB drive with nothing else on them…Bizarre!

      Finally last night I just had it download the iso to my HD of the computer I’m on which showed 306GB free of 908GB total.  Finally it worked.  However, now I can not copy the 4.24 Windows 10 21H1.iso file to a 16GB drive because, again there is supposedly not enough room!  Anyone got any ideas or advice?

      Could locking my computer into the 20H2 version following the one of the previous weekend tasks a while back cause this most bizarre issue?

      Thanks for any help!

      • #2391200

        I had the same problem several months ago until I reformatted my USB flash drive from FAT32 to exFAT. Alex5723 alerted me to the fact that FAT32 supports file sizes up to 4GB. The .iso that I was trying to save to the USB flash drive was larger than than that.

        1 user thanked author for this post.
    • #2391189

      How is the 16GB drive formatted?

      --Joe

      • #2391262

        It was FAT32 until I saw the (<span class=”bbp-author-name”>anonymous </span>Guest – Thank you!) post above and reformatted it to exFAT.  That was gonna be my next approach if I hadn’t gotten a solution here.  Thankfully this worked!

    • #2391322

      I installed 21H1 today using the ISO while disconnected from inet. Installed version win 10 pro ver 21H1 build 19043.928 Upon reconnect I get notification that I need updates- kb5005565 CU as well as malicious removal tool and KB4023057 (which I will not install). Update history only shows 7 updates installed as of June of this year for 20H2 and under uninstall shows 4 all installed in April. I have been installing every month and was up to date as far as Aug w/ 20H2

      From the master patch list I tried to install August patch KB5005033 for 64bit 21h1- using stand alone installer. Get message it is not the correct patch for me?  (2times)

      I’m guessing the KB5005565 CU is for September which is why I tried to install the kb5005033 CU. Based on the history of installed patches it seems I am not up to date thru Aug.

      Any help here please? What build should I be showing?

      Thank you

       

      • #2391325

        Try this. In Explorer go to This PC/ right click/properties and see what version of Win 10 is shown.

        • #2391326

          I would like to know what the bld number would be if patched up thru aug  and why the patch for Aug (as found in master patch list) will not install on my current bld.

           

          • #2391331

            Jun and Aug patch are not compatible and July is marked as Defer . I am very confused about what was actually installed today. win 10 pro ver 21H1 build 19043.928 is what winver gives me.

            I downloaded the ISO yesterday (as instructed)

            installed
            installed2

            How do I get a newer build installed?

            Sorry for the confusion. Very sorry

             

          • #2391344

            I would like to know what the bld number would be if patched up thru aug ….

            Here is the info from my system. My first upgrade to this new common core operating system was 20H1 (I skipped 2004) on April 10. I upgraded by changing TRV to 20H1.

            Then my next upgrade was to 21H1 on August 5. I upgraded by changing TRV to 21H1.

            You can see the history of Features Updates and the last CU patch that I have applied (the August patch KB5005033 on Sept 11)

            Update-History-21H1

            You can also see the build info here: It’s 19043.1165

            Build-no-August-patch-21H1

            • #2391352

              and why the patch for Aug (as found in master patch list) will not install on my current bld.

              Maybe the information in the Support page for KB5005033 will help, especially the section “How to Get this Update” and right below that “Before installing this update”.

              Here in my installed updates section about the SSU that was installed.

              SSU-for-KB5005033

              1 user thanked author for this post.
      • #2391392

        Normally, the SSU installs with the CU in Win10. But there was an SSU issued in August, KB5005260 for people that had skipped installing some SSUs because of PrintNightmare.
        I would suggest trying to install it first, restart, give it a few minutes to finish bootup, then try installing the August CU.

        1 user thanked author for this post.
    • #2391503

      Many thanks to  WCHS and PKCano

      I am now running ver 21H1 build 19043.1165 on 2 Laptops.

      It seems to have taken a long time to install the CU after a short install time for the SSU. Had me worried after ~15min of no mvmnt but then Bam! And it was done!

      Appreciatively,

      D

      1 user thanked author for this post.
    Viewing 17 reply threads
    Reply To: Tasks for the weekend – September 18, 2021 – it’s squirrel away time

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