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

    Posted on Susan Bradley Comment on the AskWoody Lounge

    Home Forums AskWoody blog Patch Lady – downloading the 1809 iso

    This topic contains 37 replies, has 15 voices, and was last updated by

     JohnW 2 days, 10 hours ago.

    • Author
      Posts
    • #343569 Reply

      Susan Bradley
      AskWoody MVP

      So given that the tea leaves look like that 1903 is coming soon, I’m making sure that I’m downloading 1809 from the media download site and parking it
      [See the full post at: Patch Lady – downloading the 1809 iso]

      Susan Bradley Patch Lady

      10 users thanked author for this post.
    • #343686 Reply

      CADesertRat
      AskWoody Plus

      I downloaded 1809 Bld 17763.1 this morning to a Flash Drive for safe keeping. I’m still on 1803 but at some point I’m sure 1809 will be in my future.

      Don't take yourself so seriously, no one else does 🙂
      Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

      • #343709 Reply

        EP
        AskWoody_MVP

        OH NO!

        The 1809 ISO that you should be downloading should be at least the build 17763.107 version. the 1809 iso download that had build 17763.1 had the user file deletion problem and was pulled several days later and MS re-released the 1809 ISOs on Nov. 13, 2018, containing the 17763.107 version which fixed the problem.

        • This reply was modified 4 weeks ago by
           EP.
        • This reply was modified 4 weeks ago by
           EP.
        • This reply was modified 4 weeks ago by
           EP.
        1 user thanked author for this post.
        • #343718 Reply

          mn–
          AskWoody Lounger

          … and the Media Creation Tool has been creating 17763.253 ISOs for a couple of months now, that one seems to fix some more problems.

          • #343749 Reply

            Alex5723
            AskWoody Plus

            I just tested Media Creation Tool which downloaded 17763.1.

            • #343754 Reply

              mn–
              AskWoody Lounger

              Ok, I officially label this thing WEIRD.

              I have:

              E:\>dism /Get-WimInfo /WimFile:e:\sources\install.esd /index:5
              
              Deployment Image Servicing and Management tool
              Version: 10.0.17763.1
              
              Details for image : e:\sources\install.esd
              
              Index : 5
              Name : Windows 10 Pro
              Description : Windows 10 Pro
              Size : 14 470 554 883 bytes
              WIM Bootable : No
              Architecture : x64
              Hal :
              Version : 10.0.17763
              ServicePack Build : 253
              ServicePack Level : 0
              Edition : Professional
              Installation : Client
              ProductType : WinNT
              ProductSuite : Terminal Server
              System Root : WINDOWS
              Directories : 21460
              Files : 96294
              Created : 8.1.2019 - 3.44.15
              Modified : 17.1.2019 - 23.30.07

              That’s my first .253, I’ve gotten more of them since (again this week) but haven’t bothered to archive subsequent ones separately.

              And I’ve run the tool from W10 1709, W10 1803, and W7… at home and at the office…

              I’ve also got an install.esd in here instead of install.wim and the index only goes up to 6. (Home, Home N, Education, Education N, Pro, Pro N)

              Oh and mine isn’t the en-US language version. I wonder if that’s significant…

              • This reply was modified 4 weeks ago by
                 mn--. Reason: fixed formatting
              • This reply was modified 4 weeks ago by
                 mn--. Reason: Is the language version significant?
        • #343740 Reply

          CADesertRat
          AskWoody Plus

          I used the MCT this morning to create the USB ISO and to see what build it was, I right clicked on setup.exe>properties, that’s where I got that build number from. Maybe I am looking in the wrong place?1809-setup-exe

          Don't take yourself so seriously, no one else does 🙂
          Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

          Attachments:
          You must be logged in to view attached files.
          • #343748 Reply

            EyesOnWindows
            AskWoody Lounger

            Use dism /Get-WimInfo /WimFile:X:\sources\install.wim /index:1 in an Administrator command prompt window (use the USB ISO’s drive letter in place of the X: shown here) and look at:

            Version : 10.0.17763
            ServicePack Build : 107
            ServicePack Level : 0

            It is the same for all other indices as well.

            Note: Use dism /Get-WimInfo /WimFile:X:\sources\install.esd /index:1 if the ISO was downloaded using the Media Creation tool.

            HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 1803
            Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 4.00 GB
            EyesOnWindows

            • This reply was modified 4 weeks ago by
               EyesOnWindows. Reason: Mention using install.esd instead of install.wim
            3 users thanked author for this post.
            • #343764 Reply

              CADesertRat
              AskWoody Plus

              It say’s it can’t find the file specified.

              Microsoft Windows [Version 10.0.17134.590]

              (c) 2018 Microsoft Corporation. All rights reserved.

              C:\WINDOWS\system32>dism /Get-Wiminfo /WimFile:F:\sources\install.wim /index:1

              Deployment Image Servicing and Management tool

              Version: 10.0.17134.1

              Error: 2

              The system cannot find the file specified.

              The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

              Don't take yourself so seriously, no one else does 🙂
              Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

              1 user thanked author for this post.
            • #343789 Reply

              Alex5723
              AskWoody Plus

              Got the same error. There is no install.wim file in this 1809 iso file.

            • #343800 Reply

              CADesertRat
              AskWoody Plus

              It seems really odd to me that previous downloaders of the ISO got current Bld’s and that the ISO today would be clear back to the 1st Bld. Evidently I am not looking where I need to be looking to find the Bld on this ISO unless MS played a switcheroo.

              Don't take yourself so seriously, no one else does 🙂
              Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

            • #343809 Reply

              EyesOnWindows
              AskWoody Lounger

              From “How to Extract Install.ESD to Install.WIM (Windows 10/8)

              When you download a Windows 10 or 8 ISO file, by using the Media Creation tool, you will realize that there is an “install.esd” file under the “sources” folder (X:\Source\install.esd). The install.esd file is a compressed and encrypted file that contains a full copy of the Windows operating system in a protecting container.

              From “Find the Windows version, build and edition from ISO or DVD

              5. Open an elevated Command Prompt window, and then type the following command:

              dism /Get-WimInfo /WimFile:F:\sources\install.wim /index:1

              In the ISO file, if you have install.esd instead of install.wim, you’d type:

              dism /Get-WimInfo /WimFile:F:\sources\install.esd /index:1

              DISM can handle both these file formats (.wim & .esd), at least in Windows 10.

              HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 1803
              Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 4.00 GB
              EyesOnWindows

              2 users thanked author for this post.
            • #343818 Reply

              CADesertRat
              AskWoody Plus

              Ahhh, thanks, that did it. So it’s bld 253

              Deployment Image Servicing and Management tool

              Version: 10.0.17134.1

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

              Index : 1
              Name : Windows 10 Home
              Description : Windows 10 Home
              Size : 14,446,840,204 bytes
              WIM Bootable : No
              Architecture : x64
              Hal : <undefined>
              Version : 10.0.17763
              ServicePack Build : 253
              ServicePack Level : 0
              Edition : Core
              Installation : Client
              ProductType : WinNT
              ProductSuite : Terminal Server
              System Root : WINDOWS
              Directories : 20506
              Files : 93685
              Created : 1/7/2019 – 6:36:05 PM
              Modified : 3/20/2019 – 9:56:29 AM
              Languages :
              en-US (Default)

              The operation completed successfully.

              Don't take yourself so seriously, no one else does 🙂
              Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

            • #343907 Reply

              Alex5723
              AskWoody Plus

              Thanks.
              Got the same. But I need Windows 10 Pro x64, Not Windows 10 Home.

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

              Index : 1
              Name : Windows 10 Home
              Description : Windows 10 Home
              Size : 14,446,840,204 bytes
              WIM Bootable : No
              Architecture : x64
              Hal : <undefined>
              Version : 10.0.17763
              ServicePack Build : 253
              ServicePack Level : 0
              Edition : Core
              Installation : Client
              ProductType : WinNT
              ProductSuite : Terminal Server
              System Root : WINDOWS
              Directories : 20506
              Files : 93685
              Created : 08-Jan-19 – 3:36:05 AM
              Modified : 20-Mar-19 – 10:31:09 PM
              Languages :
              en-US (Default)

              edit: I suppose the index 2….N will display additional Win 10 versions 🙂

              • This reply was modified 4 weeks ago by
                 Alex5723.
            • #343986 Reply

              CADesertRat
              AskWoody Plus

              W10 ISO’s usually have ALL versions in them. The “Home” version is generic.

              Don't take yourself so seriously, no one else does 🙂
              Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

    • #343736 Reply

      EyesOnWindows
      AskWoody Lounger

      Got my copy back on Thursday, ‎February ‎21, ‎2019 using wget.exe which reported:

      Content-Disposition: attachment; filename=Win10_1809Oct_English_x64.iso
      Date: Thu, 21 Feb 2019 21:51:15 GMT
      Last-Modified: Wed, 31 Oct 2018 19:03:31 GMT
      Content-Length: 5075539968

      Running fciv.exe -both Win10_1809Oct_English_x64.iso gives:

      MD5: 7a19f70f948614b55b716a6ee0ca5274
      SHA-1: bee211937f3ed11606590b541b2f5b97237ac09d

      To check that the iso file contains the 17763.107 version I use information from “How to determine the version of your Windows ISO file“. In Windows 10 I click on Win10_1809Oct_English_x64.iso to mount it, in my case this is on G:, then open an Administrator command prompt window and enter this:

      dism /Get-WimInfo /WimFile:G:\sources\install.wim /index:1

      Index : 1
      Name : Windows 10 Home
      Description : Windows 10 Home
      Size : 14,367,948,244 bytes
      WIM Bootable : No
      Architecture : x64
      Hal : <undefined>
      Version : 10.0.17763
      ServicePack Build : 107
      ServicePack Level : 0
      Edition : Core
      Installation : Client
      ProductType : WinNT
      ProductSuite : Terminal Server
      System Root : WINDOWS
      Directories : 19280
      Files : 89357
      Created : 10/29/2018 – 4:53:01 PM
      Modified : 10/29/2018 – 5:33:20 PM
      Languages :
      en-US (Default)

      Perhaps also of interest I enter:
      FOR /L %v IN (1,1,11) DO @dism /Get-WimInfo /WimFile:G:\sources\install.wim /index:%v|findstr “Name”

      Name : Windows 10 Home
      Name : Windows 10 Home N
      Name : Windows 10 Home Single Language
      Name : Windows 10 Education
      Name : Windows 10 Education N
      Name : Windows 10 Pro
      Name : Windows 10 Pro N
      Name : Windows 10 Pro Education
      Name : Windows 10 Pro Education N
      Name : Windows 10 Pro for Workstations
      Name : Windows 10 Pro N for Workstations

      Note: Use install.esd instead of install.wim where shown above if the ISO was downloaded using the Media Creation tool.

      HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 1803
      Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 4.00 GB
      EyesOnWindows

      1 user thanked author for this post.
    • #343739 Reply

      Mr. Natural
      AskWoody Plus

      I think my plan will be to keep 1803 people on 1803. I’ve updated around 10 pc’s from 1803 to 1809 with no problems but I want to see how this new build shakes out and perhaps later this year we standardize to 1903….we’ll see.

      New installs get 1809 but I’m not putting people through a version upgrade twice a year.

      Red Ruffnsore reporting from the front lines.

    • #343762 Reply

      anonymous

      I’ll just keep 1803 (and the iso I burned sitting on my desk) until 1903 is stable (the 1903 pain should subside after 30 days). Then I’ll just update from 1803 to 1903. Why would I want a copy of 1809 considering all the problems it has had and continues to have?

      • #343775 Reply

        anonymous

        Because the cost of materials and time is very small. Because having it on hand, not installed, does not harm your computing experience. Because things can always get worse. And when they do, having more options always beats less options. Even when you do not use those options. Think of it in terms of the same reasons you keep multiple backups in different locations. For some this seems like overkill. But a lot of geeks were scouts. And “Be prepared” sticks with you.

        6 users thanked author for this post.
        • #343886 Reply

          anonymous

          Because why would I want something that has been proven broken and Microsoft has proven incapable of getting fixed? I would never download 1809 because I would never install something that broken.

          • #343891 Reply

            mn–
            AskWoody Lounger

            Well the .253 is actually quite a bit less broken than some others.

            In particular it would ATM be my installer of choice for starting to bring old/neglected W10 systems up to current, unless there are some of those applications where it’s contraindicated (old “Access format” databases as one example).

            Say, upgrades from 1511 or 1607 or… because it seems to behave better with drivers than upgrades to 1803.

          • #343913 Reply

            Noel Carboni
            AskWoody_MVP

            What do you feel is broken? Specifics please.

            Bear in mind I’m using it professionally and don’t find it particularly broken.

            -Noel

            3 users thanked author for this post.
    • #343796 Reply

      Elly
      AskWoody MVP

      I am not someone who likes or approves of W10… and yet I’ve downloaded an ISO for every version. When I have extra time and energy, I can check it out on a VM, especially since I’m the sort that does better seeing and experiencing, rather than just trying to learn its terminology at a greater distance. It certainly helps to be on the same page as other people.

      Some ISO versions I’ve used on friends’ computers. Its amazing how someone will need something once it is no longer available.

      It is a sometimes useful resource and cheap insurance… and although 1809 has had its share of problems, it is currently at its most stable. Based on past experience, it is unlikely that 1903 will start out more stable than 1809 currently is… and if someone gets a new computer after 1903 is pushed out, they may well want to go back to an older, more stable version. It isn’t unheard of an update failing, and then rolling back versions failing (hmm… seen it, been there). An ISO is invaluable at that point. And yes, whether its my computer, or a friend or family member’s, I’m compulsive about backing up, so the data is never at risk.

      Win 7 Home, 64 bit, Group B

      3 users thanked author for this post.
      • #344806 Reply

        Microfix
        Da Boss

        Curiosity will get the better of us (or not?), I’ve gotta try out W10 versions but I find the tweaks/countermeasures/ configuring and avoidance are starting to outweigh the benefits with every new iteration as it progresses (regresses?) IMO. The svhosts bandwidth is increasing and I’m not so sure I’ll stick with it. Yes W10 v1803 is quick on our Haswell and Ivybridge devices but it just lacks love! I don’t like it even with openshell, I don’t trust it.. (took me long enough to say that)
        Thanks MS I’ll stick with W8.1 until it’s EOL if not sooner no thanks to your direction

        However, my alternatives are somewhat time consuming (linux distro hopping) just to get that ONE Distro that suits. (with removals/ replacements, hacks and tweaks) I actually get better kicks from linux distro hopping than I do with W10 as it’s more customisable. In the end, each nearly gets there but not as fluid as Windows for my liking…oh dear, lol

        I’m contemplating bringing ‘olde faithful’ W7 Pro image back online for curiosity in the run up to EOL (hardware install not VM) I’d rather counter something that is worth it’s weight in gold to me that has given so much computing pleasure over the years (same ilk as XP, W2k pro and the 98SE-gaming m/c). When the time comes, I’ll disconnect W7 from the interweb and keep it running prior to eventual hardware failures and a funeral service.. I’m sorta fortunate in a way having W8.1 also on devices but, I’m even more wary of every patch now and in the future..

        ..the future is so bright, I’ve gotta wear shades 8)

        | W8.1 Pro x64 | Linux x64 Hybrids | W7 Pro x86 | XP Pro O/L
    • #343842 Reply

      Speccy
      AskWoody Lounger

      OK, here goes a less than brief (but, hopefully, enlightening and not too technical) explanation to help our puzzled readers out there while downloading 1809 (and 1903 and other, future Windows 10 ISOs)… 🙂

      When executed, the Media Creation Tool creates a few temporary directories:

      C:\$WINDOWS.~BT
      C:\$WINDOWS.~WS
      C:\ESD

      The files at

      C:\$WINDOWS.~WS\Sources
      (keep in mind that ‘C:\$WINDOWS.~WS‘ is a hidden directory)

      do seem to be referring to v10.0.17763.1… but digging into the main log file

      C:\$WINDOWS.~WS\Sources\Panther\setupact.log

      and searching for “Download Url” reveals that the OS image being downloaded by the tool is actually the v10.0.17763.253 one:

      MOUPG GetWebSetupUserInput: Execute: Download Url X64 = [http(...)/17763.253.(...).esd].
      Once the ISO file finishes downloading, if you “mount” it and take a closer look at its contents you will find that the tool downloads the v10.0.17763.1 “BASELINE” (ignore the tool’s Jan 8, 2019 date stamping – to match the KB4480116, OS Build 17763.253: it is misleading, because the files are digitally signed Sep 15, 2018… matching the timeline of the last preview builds and the public release of OS Build 17763.1 on Oct 2, 2018!) – and adds (only) 3 files to the ‘sources’ directory:

      ws.dat
      boot.wim
      install.esd

      Now open up an elevated command-line. Peeking into the first file (replace the X: below for the drive letter you’re “mounting” the ISO on)

      type X:\sources\ws.dat
      only adds to the confusion, because the first three lines of the output misleadingly read:

      [WebSetup]
      ClientVersion=10.0.17763.1
      IsUpgradeNow=FALSE

      The key point to figure out what’s going on here is to understand the nature of those other two files. By typing

      dism /Get-WimInfo /WimFile:X:\sources\boot.wim|findstr "Name"
      dism /Get-WimInfo /WimFile:X:\sources\install.esd|findstr "Name"
      you learn that ‘boot.wim‘ is a container for both Windows PE and the Windows Setup and that ‘install.esd‘ is a compressed, encrypted copy of several OS “editions” in a protecting container (as noted here). In fact, these two files act as the core elements of how the “BASELINE” ISO gets “updated” to the more recent build being offered (currently, v10.0.17763.253)!

      Thus, typing (again, replace the X: below for the drive letter you’re “mounting” the ISO on)

      dism /Get-WimInfo /WimFile:X:\sources\boot.wim /index:1
      and
      dism /Get-WimInfo /WimFile:X:\sources\boot.wim /index:2
      and
      dism /Get-WimInfo /WimFile:X:\sources\install.esd /index:N
      (with N being any integer between 1 and the total number of indexes, or OS “editions” included in your ‘install.esd‘ file – usually 7 or more)

      confirms on all outputs (in the “Version” and “ServicePack Build” text lines) that, indeed, you’ve downloaded:

      Version : 10.0.17763
      ServicePack Build : 253

      Last but not least: if you’re NOT planning to upgrade to 1809 yet, after you’re done with the ISO download make sure to get rid of (remove) those

      C:\$WINDOWS.~BT
      C:\$WINDOWS.~WS
      C:\ESD

      directories… 😉

      7 users thanked author for this post.
      • #343990 Reply

        CADesertRat
        AskWoody Plus

        I deleted Folders C:\$WINDOWS.~BT, and C:\ESD, but had to turn on “Hidden Files/Folders to see C:\$WINDOWS.~WS before deleting.  Just a “Heads Up” if you don’t see the WS folder.

        I see that it was mentioned at the start of the helpful instructions but I previously missed it.

        Don't take yourself so seriously, no one else does 🙂
        Grp. A with 2 Win 7 Pro, also 2 Win 10 Pro currently 1803 (1 Desktop, 1 Laptop).

        • This reply was modified 3 weeks, 6 days ago by
           CADesertRat.
    • #343999 Reply

      JohnW
      AskWoody Plus

      I grabbed the Media Creation Tool, and built the USB installer for 1809, so it is ready to go when I need it! 🙂

      I did this on my Win 10 Pro 1803 workstation, but I also have a laptop with Win 10 Home 1803.

      Can the same installer be used to update either a Pro or Home edition?

      • #344007 Reply

        BobbyB
        AskWoody Lounger

        yep just add and ei.cfg to your sources folder, just copy and paste the following in to a notepad file, save as “all files” with the name ei.cfg toss it in to the Sources folder either Burn .iso or recreate the .iso and you get a choice or which version during install, just check per advice above as to what indices the .wim or .esd contain, likely in any event, Pro and Home will be in there. Handy for those that upgraded to Pro or the Bios does not have a key for Pro, which will give you the default Home and saves the hassle of doing an upgrade later.

        [EditionID]

        [Channel]
        OEM
        [VL]
        0

      • #344839 Reply

        JohnW
        AskWoody Plus

        When I ran the Media Creation Tool for 1809 I was puzzled that it did not ask about which edition of Windows 10 to build for (Home or Pro, etc.). The only edition available in the tool was “Windows 10”.

        So I found this recent “How-to” guide that illustrates what I saw during my USB build process. How to install Windows 10 from USB with UEFI support

        It appears that Microsoft has streamlined the media build process and now provides for all editions of Windows 10 by default. The chart in step 4 in the “to install Windows 10 on a different PC” section of the installation media guide appears to confirm that “Windows 10” is currently the target edition for all Windows OS install/upgrades now. Create Windows 10 installation media

        1 user thanked author for this post.
    • #344066 Reply

      Alex5723
      AskWoody Plus

      Microsoft started to push 1809 to everyone (except those with the incompatible Intel display driver) :

      Get the Windows 10 October 2018 Update :

      Windows 10 will automatically download the October 2018 Update on your eligible device if you’ve turned on automatic updates in Windows Update settings. When the update is ready, you’ll be asked to pick a time to install it. After it’s installed, your device will be running Windows 10, version 1809. (To check whether you’re already running the version 1809 update, click View update history on the Windows Update settings page.)…

      https://support.microsoft.com/en-us/help/4028685/windows-10-get-the-update

      Last Updated: Mar 20, 2019

      1 user thanked author for this post.
    • #344196 Reply

      b
      AskWoody Plus

      A beta version of Rufus released five days ago includes a feature/script which downloads most ISOs from Microsoft sources:

      Rufus 3.5 with Windows 10 and 8.1 download option (at ghacks.net)

      Cannon fodder Chump Daft glutton Idiot Sucker More intrepid Crazy/ignorant Toxic drinker Saluted blockhead "Finger sharpener" (Group ASAP) WX1903

      5 users thanked author for this post.
      • #344253 Reply

        EyesOnWindows
        AskWoody Lounger

        See “Fido: Full ISO Download Script (for Windows retail ISOs)” for “A PowerShell script to download Windows retail ISOs”.

        Fido is a PowerShell script that is primarily designed to be used in Rufus but that can also be used in standalone fashion, and that automates access to the official Windows retail ISO download links.

        HP Compaq 6000 Pro SFF PC / Windows 10 Pro / 1803
        Intel®Core™2 “Wolfdale” E8400 3.0 GHz / 4.00 GB
        EyesOnWindows

        • #344297 Reply

          Alex5723
          AskWoody Plus

          I have tested both, Rufus beta and Fido script. Both failed with the same ‘Internet explorer…’ error on my 1803 Pro.

    • #346057 Reply

      EP
      AskWoody_MVP

      oh abbodi86:

      I ran the 1809 Media Creation tool just now and it is now downloading newer refreshed 1809 ESDs/ISOs with build 17763.379 (1809 + March 2019 CU). products.xml file now has a date of 3/14/2019

      1 user thanked author for this post.
      b
    • #346355 Reply

      EP
      AskWoody_MVP

      also NEW refreshed 1809 ISOs available from MS Techbench starting March 28 that have build 17763.379:

      Win10_1809Oct_v2_English_x64.iso
      Win10_1809Oct_v2_English_x32.iso

    • #435137 Reply

      anonymous

      I just downloaded the 1809 version today (Media Creation Tool to create and burn to USB rather than saving the ISO), and I also got v 10.017763.379 as confirmed by running DISM cmd. I wonder when/if they’ll replace the ISO with April’s updates?

    • #441029 Reply

      JohnW
      AskWoody Plus

      Probably soon. I just updated a recalcitrant laptop today to 1809 that has been stuck on 1803, by going directly to the Microsoft website and clicking “update now”.

      It seems that I received 10.017763.437 (the April update). As there was no monthly update for April waiting for me after the feature update, I ran “Winver”, and sure enough I was up to date!

      The good news is that it seems to be running well. Disclaimer: I am running Windows Defender on this laptop, so no 3rd party AV to cause trouble here! 🙂

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

    Reply To: Patch Lady – downloading the 1809 iso

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

    Your information:


    Comments are closed.