• Tasks for the weekend – February 20, 2021 – it’s Squirrel away time

    Home » Forums » Newsletter and Homepage topics » Tasks for the weekend – February 20, 2021 – it’s Squirrel away time

    Author
    Topic
    #2344986

    (Youtube video here) Microsoft just announced 21h1 is in the final testing. That’s a sign to me that I need to “squirrel away” a copy of the current I
    [See the full post at: Tasks for the weekend – February 20, 2021 – it’s Squirrel away time]

    Susan Bradley Patch Lady/Prudent patcher

    2 users thanked author for this post.
    Viewing 29 reply threads
    Author
    Replies
    • #2345028

      I’m running 20H2 19042.804  and have a copy on a thumb drive.  I’m also fully updated, with multiple weekly drive images—I don’t need the latest ISO.  Drive image restoration is much quicker than running an in-place upgrade.

      As for drivers, I don’t routinely search for new drivers in the absence of driver-related issues or a need for new features.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

      1 user thanked author for this post.
      • #2345073

        Before the next feature release, I do.  I make sure there is no bios or video card update pending.

        Susan Bradley Patch Lady/Prudent patcher

        • #2345775

          Before the next feature release, I do. I make sure there is no bios or video card update pending.

          In the event an update failed because of a driver-related issue, I would simply restore my last drive image, search for a driver update, then try again.

          There is no scenario from which I cannot recover by restoring my latest known-good drive image.  I’ve mentioned this elsewhere, likely more than once, but I recovered completely from a house fire that destroyed two (fully imaged) PC’s.  I had to get the hardware together in order to have a platform to which I could restore the image, but I didn’t lose a thing.

          And yes, I have multiple copies of my drive images, including a pair of HDD’s stored offline.

          Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
          We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
          We were all once "Average Users".

    • #2345029

      I have one favor to ask.  Can you code HTML links so they open in a new window rather than leaving the site.  I think your default is usually to close out of Ask Woody and move onto the new link.  As a user I realize that I can select a choice by right clicking the mouse button but I am accustomed to links opening in a new tab.

      Thanks!

      1 user thanked author for this post.
      b
      • #2345032

        I have one favor to ask. Can you code HTML links so they open in a new window rather than leaving the site.

        It’s readily available in the “Link” dropdown.  Click on the gear icon, and put a tick in the box beside “Open link in a new tab”.

        That’s what I do every time I include a link in one of my posts.

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
        We were all once "Average Users".

      • #2345042

        Middle click the link? (press the wheel down)

        cheers, Paul

      • #2345058

        There is a check box for that in the ‘insert link’ dialog box. I usually try to tic it.

        🍻

        Just because you don't know where you are going doesn't mean any road will get you there.
        2 users thanked author for this post.
    • #2345053

      HeiDoc offers 20H2 from October and ’20H2 v2′ from December. I assume v2 is an update to the October release and v2 is the one to download and use, when needed, correct?

      Thanks!

    • #2345057

      Is there a recommended computer vendors update app for updating drivers?  What is the easiest way to do this?  Thanks!

      • #2345075

        What brand of computer do you have?  HP and Dell both have an app you can install to check for driver updates.

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
        • #2345086

          Thanks, I regularly use Dell Updates but was just wondering if there were apps that checked for other than Dell drivers on the computer and facilitated downloading.

    • #2345099

      Thanks, I regularly use Dell Updates but was just wondering if there were apps that checked for other than Dell drivers on the computer and facilitated downloading.

      Don’t trust any 3rd party drivers update.
      Use your PC vendor or better still download from hardware’s OEM site (Intel, Nvidia, Realtek…)

      • #2345146

        I somewhat agree with the premise that you shouldn’t rely on 3rd party driver updaters but I “use” WinzipDriverUpdatre to check to see if updates are available.  It’s just a prompt to remind me what I *may* need to consider updating.

        https://www.winzipdriverupdater.com/

        It’s owned by Winzip and I’ve had good luck with it in the past.

    • #2345140

      In October Microsoft stated that the following problem may occur in certain instances when updating from an ISO:

      “System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.”

      My computer is running Windows 10 Pro version 2004 build 1904.746 (January 2021 patches installed).

      Could updating my computer some time in the future with a 20H2 ISO created today or in the future result in the problem Microsoft noted above?

      • #2345251

        That is a problem of the users making and does not apply to version updates >1809 that are installed via Windows Update.

        cheers, Paul

        1 user thanked author for this post.
        • #2345518

          But what about updating Windows version 2004 with an ISO copy of version 20H2? Could the problems that Microsoft notes above arise?

    • #2345148

      Sorry, I’m having a foggy day. I don’t see an ISO to download at the link you provided.

    • #2345196

      I have a copy of the 20H2 ISO that I downloaded on February 1. It’s the “v2” ISO. I have not installed the upgrade yet, mostly because upgrades take so unimaginably long on my HDD laptop. My current daily driver is a MacBook Pro with an SSD, and I run Windows 10 on a Parallels virtual machine on there. Both the virtual machine and the HDD laptop are running v1909. I will most likely upgrade that one first, then upgrade the HDD laptop later on (though the latter is not high on my priority list as I don’t really use that laptop for work these days).

    • #2345266

      Sorry, I’m having a foggy day. I don’t see an ISO to download at the link you provided.

      You have to download the tool MediaCreationTool20H2.exe in order to download the ISO from Microsoft.
      The same applies to Heidoc.net. Download the tool Windows-ISO-Downloader.exe in order to download the ISO.

    • #2345305

      I don’t want to alarm anyone, but I just downloaded and saved what I though was going to be the Win10 20H2 ISO using the MS Windows Media Creation Tool.

      During the download, the <products.xml> file at  $Windows.~WS\Sources apparently correctly showed that the build would be 19042.631 (i.e. the Win10 Home x64 version 20H2 build made available on 19 Nov 2020), however, after the download had completed I decided to check what I had actually received, by mounting the ISO and using the MS DSIM Tool to interrogate the <install.esd> file, only to find that it is actually (according to the DSIM result) 19041.631 **NOTE 19041 NOT 19042** which is the Win10 Home x64 version 2004 build made available on 19 Nov 2020 !

      My first instinct is to assume I am doing something wrong, so please someone, put me right here!  Has anybody else double-checked too?  But if what I am seeing is true, this looks to me like a serious drop-off by Microsoft, let’s hope not …

      This worried me enough to go and check using the DSIM Tool the Win10 Home x64 version 1909 ISO that I thought I had downloaded at Woody’s suggestion some time ago (27 May 2020), only to find that is actually (according to the DSIM result) build 18362.418 which is version 1903 **NOTE 1903 NOT 1909** made available on 08 October 2019!

      So now I’m really confused and seriously concerned, and look forward to others’ views, experiences and findings on this all-important “squirrelling away” topic – thanks in anticipation!

      1 user thanked author for this post.
      • #2345335

        1903 and 1909 have the same core, get the same updates (CU, SSU, .NET).
        2004 and 20H2 have the same core, get the same updates (CU, SSU, .NET).

        The difference between the two versions with the same core is, the latter of the two has the Enhancement Pack turned ON (enabled).
        If you downloaded from MS Download (or HeiDoc.net) an ISO represented as the latter of the two with like core, you are getting the core (Builds 18362 or 19041 which shows up with DISM) PLUS the Enhancement Pack turned on (enabled). This gives you the latter Builds of the two with the same core (18362+EP=18363 or 10941+EP=19042).

    • #2345401

      The difference between the two versions with the same core is, the latter of the two has the Enhancement Pack turned ON (enabled).

      I also downloaded the Microsoft “MediaCreationTool20H2.exe” file and ran as instructed.

      The resultant ISO file was examined with DISM with this result:
      —————-
      Deployment Image Servicing and Management tool
      Version: 10.0.19041.746

      Details for image : I:\sources\install.esd

      Index : 6
      Name : Windows 10 Pro
      Description : Windows 10 Pro
      Size : 15,720,710,878 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : acpiapic
      Version : 10.0.19041
      ServicePack Build : 631
      ServicePack Level : 0
      Edition : Professional
      Installation : Client
      ProductType : WinNT
      ProductSuite : Terminal Server
      System Root : WINDOWS
      Directories : 24132
      Files : 96477
      Created : 11/18/2020 – 10:01:10 PM
      Modified : 2/21/2021 – 1:41:37 PM
      Languages :
      en-US (Default)

      The operation completed successfully.
      —————-

      So my question is how do I verify that the enhancement pack is ENABLED?

      I do not see it in the DISM data.

       

    • #2345407

      Ah thanks PKCano for that explanation – much appreciated – I did wonder at the time why the release notes for both 19041 & 19042 builds are covered by the same MS KB number.

      I downloaded the ISO using the MS <MediaCreationTool20H2.exe> which is why I was so surprised to see the version represented as 2004 in the build information shown by DSIM.

      I am currently running 1909, so if I understand you correctly, that means I have the choice to use the same “squirrelled” ISO image to either upgrade from 1909 to 2004 (since AFAIK 2004 is no longer available via Windows Update), or to skip 2004 entirely and upgrade from 1909 to 20H2 (i.e. after 20H2 is replaced soon by 21H1 on Windows Update, which is the reason Susan suggested “squirelling” now) – is that right?

      … and if so, at which stage of the ISO installation process am I offered the option to leave the EP (AKA “20H2 Enablement Package” I believe) ON or to switch it OFF, depending on which of the two destination versions I choose (i.e. 20H2 or 2004 respectively)?

      Thanks for your continued help.

      • #2345414

        No, that 20H2 ISO does not give you the choice. It will install 20H2 (with the Enhancement Pack turned on).

        If you want the ISO for 2004, you should go to Heidoc.net download the Windows ISO Download Tool, place it on your desktop, and download the latest of the Win 2004 ISOs for your PCs specs. The 2004 ISO gives you v2004.

    • #2345498

      If we can use Group Policy Editor to specify a Target Release Version of Windows 10, what is the purpose of making a copy of the current ISO from Microsoft’s download page?

      • #2345511

        What happens if an update goes pear-shaped? Or you have to do a repair install? Or you have to reinstall Win and you don’t want the current version, but an older one that is more stable?

        Worst case scenario. That’s what the ISO is for.

        1 user thanked author for this post.
        • #2345516

          PKCano – Thanks. Now I understand. As long as Windows Update is working and I can use Group Policy Editor and Target Release Version to select and install an older more stable version of Windows 10 everything is fine. But, as you said, if Windows really gets tangled up, an ISO will come in very handy, especially if I don’t want to install the most recent version of Windows.

        • #2345776

          What happens if an update goes pear-shaped? Or you have to do a repair install? Or you have to reinstall Win and you don’t want the current version, but an older one that is more stable? Worst case scenario. That’s what the ISO is for.

          Restore my latest known-good drive image(s).  It is much quicker and is hassle-free.

          Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
          We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
          We were all once "Average Users".

          1 user thanked author for this post.
          • #2345797

            If I am following this discussion correctly it occurs to me that perhaps having both an ISO and a system image on separate drives might be a good idea just in case one of those backup drives fails.

            • #2345815

              If I am following this discussion correctly it occurs to me that perhaps having both an ISO and a system image on separate drives might be a good idea just in case one of those backup drives fails.

              There is no scenario from which I cannot recover by restoring my latest known-good drive image. I’ve mentioned this elsewhere, likely more than once, but I recovered completely from a house fire that destroyed two (fully imaged) PC’s. I had to get the hardware together in order to have a platform to which I could restore the image, but I didn’t lose a thing. And yes, I have multiple copies of my drive images, including a pair of HDD’s stored offline.

              Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
              We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
              We were all once "Average Users".

              1 user thanked author for this post.
            • #2345833

              Am I correct that after restoring your computer with one of your stored system images you could upgrade Windows 10 to a newer, but not the newest, version of Windows 10 via Windows Update by utilizing Group Policy Editor and the Target Release Version function?

            • #2345901

              Am I correct that after restoring your computer with one of your stored system images you could upgrade Windows 10 to a newer, but not the newest, version of Windows 10 via Windows Update by utilizing Group Policy Editor and the Target Release Version function?

              I’m already running 20H2 Pro Version 19042.804.  I have driver updates blocked via Group Policy, but I don’t follow the common pause/delay advice at AskWoody.

              My systems are fully updated (other than drivers), and so my drive images are the latest, up-to-date versions of Windows 10 Pro.

              I do have older, archived images of earlier versions, but no reason to restore any of them.

              Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
              We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
              We were all once "Average Users".

              1 user thanked author for this post.
    • #2345637

      Hi,

      Clarification on 20H2 “repair-install” bug :

      1) As mentioned above, the MediaCreationTool20H2 tool at present download and create the Windows 10 20H2 ISO/USB Media build 19042.631 which is the build released on November 19, 2020.

      Re : https://support.microsoft.com/en-us/topic/november-19-2020-kb4594440-os-builds-19041-631-and-19042-631-out-of-band-0b3ef07e-dbac-d445-7e90-80a717b101e0

      2) According to https://www.bleepingcomputer.com/news/microsoft/windows-10-20h2-update-fixes-broken-in-place-upgrade-feature/
      and https://www.reddit.com/r/Windows10/comments/jfa6vb/repair_install_or_in_place_upgrade_is_broken_in/?sort=new
      the “repair install/in-place upgrade” bug was reportedly fixed with the release of the optional CU Preview KB4586853 on November 30, 2020 which also happens to be the next build at 19042.662.

      Don’t know if I got this right. It appears the build 19042.631 (the build before 19042.662) may not have the “repair install” fix yet. I am on 2004 and unable to test the ISO to confirm.

      Wondering if someone already on 20H2 who have downloaded this ISO/USB Media build 19042.631 would be willing to test if the bug is also fixed?

      Cheers.

    • #2345752

      IF you’re a regular Macrium Image maker — (+) Just Before a Feature Upgrade — IS THERE a scenario that you’d regret Not having this ISO of the current OS Ver? — Images aren’t mentioned at all — so it implies there may be more to this.

       

      W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

      • #2345778

        @CraigS26,

        IF you’re a regular Macrium Image maker — (+) Just Before a Feature Upgrade — IS THERE a scenario that you’d regret Not having this ISO of the current OS Ver?

        In my opinion, no. YMMV

        And not restricted to Macrium.  I use Image for Windows from TeraByte, and TeraByte has not failed me in two decades.

        I download the initial release of a new ISO to use for upgrading my daily-driver desktop.  I wait for the push on my other machines.  After that I wait for a new release, and re-use the same USB stick for the new ISO.

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
        We were all once "Average Users".

        1 user thanked author for this post.
    • #2345805

      Will the 20H2 iso file fit on a single-layer DVD (4.78 GB)?

      If not, I’d like to ask some other questions:
      I have a DVD device that I plug in to my laptop. I have been able to make ISO dvd’s for 1909 and 2004, which WILL fit on a single layer dvd. So, if I must use a double-layer dvd to make a 20H2 iso file,

      Can I burn a double-layer dvd (using CD Burner) in this device that has burned single layer DVDs? Or do I have to get another dvd device that will burn a double-layer dvd?

      If I have to burn a double-layer DVD, will CD Burner automatically recognize that a double-layer disk is in the device? Or do I have to change some settings in CD Burner?

      • #2345813

        That depends on the hardware you have.
        My DVD burner is capable of reading and writing to single and double layer CD/DVDs.
        Your PC’s information should tell you. If not, you can use some software like Speccy.

        Type msinfo32 in the searchbox and open it to Components. The drive should be under Multimedia or Storage. If the information is not there, try Device Manager.

        • #2345853

          The DVD drive is not built in; it’s an external DVD drive which I plug into a USB port. Do I have it plugged in when I type msinfo32 and open it to components? I have the CD Burner XP Pro software installed to burn the DVD. (I think you use CD Burner XP Pro, also).

      • #2345843

        The size of 20H2 ISO is: 4.56 GB (4,899,078,144 bytes)
        The file has been created on Dec. 26, 2020

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

          I ran into a problem with not having a DVD that was large enough to burn the 20H2 ISO. It turns out that even though the label on a SL DVD disc says 4.7 GB capacity, when checking its properties, the capacity is actually 4.37 GB (4,700,372, 992 bytes). For a DL, the disc label says 8.5 GB capacity, but when checking its properties, the capacity is actually 7.96 GB (8,547,991,552 bytes). Is it standard for the GB capacity of a DVD to be overstated on the label like this (i.e. using 1000^3 as the divisor to convert from bytes to GB instead of using 1024^3)?

          • #2346908

            You need a DVD+R DL for a 64-bit ISO
            When you burn an ISO to a DVD it actually expands the single .ISO file to a bootable Win10 installer.

            • #2346914

              Yes, I was able to get it on a DL DVD after trying to put it on a SL first. Initially, I was going by the capacity indicated on the external label of the SL disc, which said 4.7 GB and I thought the 20H2 .iso file of 4.56 GB would fit. But, it turns out that even though the external label of the SL DVD said 4.7 GB, its maximum capacity is actually 4.37 GB. So, it appears that manufacturers of DVDs misstate the actual capacity of a DVD because they use 1000^3 to convert bytes to GB, instead of using 1024^3.

              I was wondering if this is standard practice for external labels on DVDs to overstate the GB capacity like this.

    • #2346121

      20H2 is what I’d call the first Windows 10 version I was able to say was ready within a modest time of release for upgrade to corporate systems. Compared to other releases, it has been relatively trouble-free.

      I always capture an ISO when a version comes out, and I usually hold that ISO through the next two versions (seeing as the current version and previous two are considered supported).

      We are SysAdmins.
      We walk in the wiring closets no others will enter.
      We stand on the bridge, and no malware may pass.
      We engage in support, we do not retreat.
      We live for the LAN.
      We die for the LAN.

      • #2346215

        How do you determine if an update is ready?
        Why is 20H2 OK but not 20H1?

        cheers, Paul

    • #2346227

      When 1909 will be EOLed on May 2021 all current supported Windows 10 versions : 2004, 20H2, 21H1 will get the same updates.

      • This reply was modified 4 years, 3 months ago by Alex5723.
    • #2346594

      Is it necessary to keep prior saved versions – 1809, 1909, 2004? Or should we just replace it with the most recent version – 20H2?

      Thanks.

      • #2346597

        No need to keep old versions unless you plan on reinstalling one of them from scratch – why would you want to do that?

        cheers, Paul

        1 user thanked author for this post.
    • #2346678

      Thanks.  Best to keep it on computer or on a USB drive?  If downloaded to computer can it be copied to a USB drive?

      Also – at the end it offers an option to burn it to a DVD?  Was not sure what to do so I skipped the option and went to next.

      • This reply was modified 4 years, 2 months ago by ECWS.
      • This reply was modified 4 years, 2 months ago by ECWS.
      • #2346718

        Either place as long as you remember where you put it 🙂

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
    • #2346696

      Thanks Susan. Appreciate the video.

      Noticed that Windows downloaded a Media Creation20H2 to my download folder. Do I need to keep it?

      • This reply was modified 4 years, 2 months ago by ECWS.
      • #2346719

        You can remove it.

        Susan Bradley Patch Lady/Prudent patcher

        1 user thanked author for this post.
    • #2346966

      I was wondering if this is standard practice for external labels on DVDs to overstate the GB capacity like this.

      This is the standard practice for HDDs/SSDs.. too.
      Formatting HDDs, DVDs.. take their toll of total storage as well leaving less free space.

    • #2348255

      I have Windows 10 (Pro). I am still on version 1909. In anticipation of the release of 21H1, recently (Feb 26 to be exact), I downloaded the MCT to squirrel away a 20H2 ISO file in order to have it before it’s too late. Consequently, I have two folders $WINDOWS.~BT and $WINDOWS.~WS in the C:\ root directory. From what I’ve read here, these two folders are supposed to be removed afterwards, but evidently this didn’t happen, in my case.

      I have read an old post from an anonymous poster that in a Feature Upgrade, Windows Update will try to create folders with the same name, but will not be able to, and so will fail in the upgrade.

      I am planning on changing TRV from 1909 to 2004 in mid-March (i.e., after I install the February patches this weekend but before DEFCON gives the green light for the March patches.)

      Do I need to do something about these two recently-created folders before upgrading to 2004?

    • #2348256

      Do I need to do something about these two recently-created folders before upgrading to 2004?

      No, they can be left as is and Windows will (hopefully) clean them up for you.

      If you are using TRV you don’t really need to squirrel anything away. MS seem to be honouring TRV and you have a backup in case of disaster, so you can do without the extra work / data.

      cheers, Paul

      • #2348267

        If you are using TRV you don’t really need to squirrel anything away. MS seem to be honouring TRV and you have a backup in case of disaster, so you can do without the extra work / data.

        I don’t understand this part. Why is there always “squirrel away” advice offered just before a new version release, then?? I am on 1909 right now and I have a refreshed ISO of 1909. I was under the impression that if I needed to get version 1909 back in working order, I would use the ISO file to get it back. Same, too, once I move to 2004.

        • #2348280

          Reverting with the ISO requires a complete reinstall, so it’s only for those who need this ability.

          A backup pre upgrade will get you back to a working system without reinstalling.

          cheers, Paul

          1 user thanked author for this post.
    • #2348333

      Windows 10 PRO Version 20H2 19042.844

      I have that folder ($WINDOWS.~BT) – after saving a copy of 20H2 in the Document Folder –

      Will Disk Cleanup remove it?  Some concern now since seeing the comment “Windows will (hopefully) clean them up”

      • #2348344

        No concern. Leave the folders be. Microsoft may removed them in the future.

        • #2348386

          Then, there is no truth to the statement in #2276031 that “a file called “$WINDOWS.~BT” in the root of the C drive can be used to block feature updates indefinitely. Windows Update fails with error 0x800700b7 because it tries to create a folder with the same name.”??

          I have $WINDOWS.~BT in the root directory (C:\), but I want to be able to upgrade to 2004 by changing TRV from 1909 to 2004, as spelled out in AKB2000016: Guide for Windows Update Settings for Windows 10 , Section 5, as well as making other changes in the Group Policy to prevent Cumulative Update Previews — all necessary since the Feature deferral pull=downs in 1909 are no longer there in 2004.

          • #2348424

            Windows automatically cleans up these leftover folders after 10 days (If I’m remembering that right).  Disk clean up will remove it as well.

            Susan Bradley Patch Lady/Prudent patcher

            • #2355303

              Consequently, I have two folders $WINDOWS.~BT and $WINDOWS.~WS in the C:\ root directory.

              Windows automatically cleans up these leftover folders after 10 days (If I’m remembering that right).

              Those two folders, created on 2/25/2021, are still there today almost six weeks later.  So, it appears that Windows is remiss.

    • #2348433

      Then, there is no truth to the statement in #2276031 that “a file called “$WINDOWS.~BT” in the root of the C drive can be used to block feature updates indefinitely. Windows Update fails with error 0x800700b7 because it tries to create a folder with the same name.”??

      Indeed, there is no truth.

      I have both files in my C: drive since Dec. 26 2020. They were not deleted yet (updated to 20H2 on ‎03-‎Nov-‎20, now with Feb 2021 updates).

      • #2354961

        Indeed, there is no truth.

        I have both files in my C: drive since Dec. 26 2020. They were not deleted yet (updated to 20H2 on ‎03-‎Nov-‎20, now with Feb 2021 updates).

        That doesn’t disprove the theory, as you haven’t done a feature update since the folder date. And it was talking about using a file to block creation of a new folder.

    • #2354944

      Re: Create Windows 10 installation media fails.

      Following Susan Bradley’s tutorial I tried and failed to create an ISO of Windows 10 20H2 on a USB flash drive. The download completed and was verified. The “creating installation media” process started but when it reached 97% a message stating that more space was needed was displayed.

      Before the download started the USB drive had 114 GB of free space and a few preinstalled SanDisk files. On October 5, 2020 I had successfully created an ISO of Windows 10 2004 on this same USB but I deleted it prior to attempting to create an ISO of version 20H2.

      Any ideas why 20H2 failed?

      Thanks.

      • #2355043

        There is no need to create a bootable USB for an upgrade.
        Download the ISO, double click on it and run setup.exe from the resulting Explorer window.

        Once you have an ISO on disk, you can use Rufus or Ventoy to make a bootable USB from it.

        cheers, Paul

        1 user thanked author for this post.
    • #2354953

      Any ideas why 20H2 failed?

      The USB stick should be empty before creating a bootable USB.
      You can download an ISO file(s) and use the free portable Ventoy app
      to create a multiple ISOs(with various OSs) on one bootable USB stick.

      1 user thanked author for this post.
      • #2354959

        The preinstalled SanDisk files consist of the following:
        1. PDF document offering SanDisk cloud storage for the USB drive.
        2. An application described as a SanDisk “private vault” for files on the USB drive.
        3. A folder with two PDF documents that have instructions for using the “private vault” application.

        To the best of my recollection these files were on the USB drive when I purchased it. That I was able create an ISO of Windows 2004 on the drive but not 20H2 is a bit mysterious.

        I will delete these files and try again to create an ISO of Windows 10 version 20H2.

      • #2355155

        I deleted the preinstalled SanDisk folder and files on my SanDisk flash drive and attempted again to make an ISO on it following Susan Bradley’s tutorial. Just as with my first attempt, after the “creating installation media” process reached 97% a message stating that there was not enough space was displayed.

        Could it be that that the flash drive needs to be reformatted?

        • #2355156

          How much space is on the flash drive?

          Susan Bradley Patch Lady/Prudent patcher

          • #2355161

            The stated size of the drive is 128 GB.
            File explorer indicates that 114 GB are available and 128 KB are used but no files are listed.

            • #2355162

              Try after formatting the drive.

              1 user thanked author for this post.
            • #2355188

              I reformatted the flash drive with File Explorer using the following default settings:
              File system: exFAT
              Allocation unit size: 128 kilobytes
              Quick format: Yes

              After reformatting I was able to create an ISO of Windows 10 20H2 on the flash drive following Susan Bradley’s tutorial.

              Note: Prior to reformatting the flash drive the file format was FAT32 and after the reformatting it was exFAT. Perhaps that file format change made all the difference between success and failure.

              Thanks.

            • #2355223

              Now you need to test it by booting from it.
              https://www.askwoody.com/forums/topic/getting-ready-for-upgrade-to-20h2/#post-2350120

              cheers, Paul

              1 user thanked author for this post.
            • #2355458

              Now you need to test it by booting from it.

              I have read and bookmarked the link that you provided and I will reread it later. It has been years since I booted to anything other than my C: drive and I don’t want to do anything that might create a problem before I finish my tax returns. I will wait to test the drive until then.

              Thanks.

            • #2355562

              You can’t break anything by testing your bootable USB / disk.
              If try to make changes to your machine from the booted USB, then it may be possible to break things.

              cheers, Paul

              1 user thanked author for this post.
    • #2355228

      Prior to reformatting the flash drive the file format was FAT32

      Fat32 support file size up to 4GB. The ISO is larger.

      1 user thanked author for this post.
    • #2355428

      Fat32 support file size up to 4GB. The ISO is larger.

      That is a good thing to know. File Explorer indicates that the ISO of Windows 10 version 20H2 now residing on my flash drive is slightly less than 4.8GB.

      Thanks.

      • #2355446

        I have a question for you concerning terminology.

        An ISO is a single, compressed file, with the extension .ISO at the end of the name. The fact that it is a single file makes it easy to download. You can actually copy/paste the .ISO file to save it to a Flash drive, for example. The name will be “whatever.ISO”

        When you “burn” and ISO to a DVD or Flash drive, it expands the compressed file into its individual files and creates bootable Install Media. In that case, you will not see a single file with the extension “.ISO,” but the individual files contained in the ISO, like “setup.exe.” And, if inserted into the computer, you can actually boot from the install media without using the OS installed on the HDD/SDD.

        This is similar to what you see if you mount an .ISO file stored on the computer, as a separate drive, by double clicking on it and/or opening it with File Explorer. But I don’t believe this mounted drive with the install media is bootable. It is mounted in a running Operating System.

        So, my question is, what do you have on your Flash drive when you look at the contents with File Explorer, a single .ISO file or install media? Do you see a single file with the extension .ISO? Or do you see install media with individual files, like “setup.exe?”

        1 user thanked author for this post.
        • #2355452

          PKCano

          There is a single file on the flash drive. When it was first created by the Windows Media Creation Tool its name was Windows.iso. I changed its name to Win10 20H2.iso.

          Incidentally, when asked by the Windows Media Creation Tool which media I wanted to use I chose “ISO file” not “USB flash drive”.

          1 user thanked author for this post.
          • #2355454

            Just checking. Good for you knowing what you really have. Many wouldn’t.

            • #2355471

              I had been thinking that the .iso file on the flash drive could be used to install Windows 10 20H2 on my computer if it crashed and I could not boot into Windows normally. But based on your reply #2355446 I am now thinking that the .iso file is not bootable and that to use it as described in the previous sentence I would first need to either:

              1. Reinstall Windows 2004 from one of the Windows images that I make and store monthly on an external USB spinning hard drive. (I use Macrium Reflect.), or
              2. Use the recovery flash drive that I created when I first purchased the computer to boot into Windows.

              Am I correct?

            • #2355479

              If the computer will not boot, you will need some bootable media to access the computer.
              You can use the .ISO to create bootable install media (like the disks you used to get with a new computer) by “burning” it to a DVD+R DL  (if it’s 64-bit, it’s too big for a regular DVD).
              Or you can use Rufus (or other app) to create a bootable Flash drive with the install media on it.
              Booting from the install media will do a clean install.

              If you want to upgrade, saving your apps and/or data, you need to run setup.exe from within the running OS. In other words, boot the computer and use File Explorer to access setup.exe. This will let you upgrade without doing a clean install. So you can “mount” that ISO from within Windows to do this.

              1 user thanked author for this post.
            • #2355486

              Thanks for all the information. I think I understand now.

              • This reply was modified 4 years, 1 month ago by 280park.
    Viewing 29 reply threads
    Reply To: Tasks for the weekend – February 20, 2021 – it’s Squirrel away time

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

    Your information: