Security updates for Windows 10, version 1803 will be available via our standard servicing outlets: Windows Update, Windows Server Update Services, and the Microsoft Update Catalog. You will not need to alter your current update management workflows.
After May 11, 2021, devices running the Enterprise, Education, and IoT Enterprise editions of Windows 10, version 1803 will no longer receive security updates. Organizations should plan to update their devices to the latest version of Windows 10 to remain supported after this date.
For a comprehensive list of end-of-service dates for all versions and editions of the Windows client and Windows Server operating systems, bookmark the Windows lifecycle fact sheet or use the Microsoft Lifecycle Policy search tool to find lifecycle information for all commercial Microsoft products. We also recommend you bookmark the Windows message center and follow @WindowsUpdate for the latest news and announcements.
Does anybody know what is the reason? Is this valid for all systems with the same configuration or it is just my bad luck? Is there any way how to make build 1809 working on these old pieces of hardware?
Hi, Petr! It's good to hear from you!
I imagine it's the lack of processor support for some instruction that wasn't required before and now suddenly became mandatory.
In case I'm right, it's happened before, not so long ago, on the transition from 8 to 8.1...
My take: the only really strong reason to remain at 8.0 is to avoid decommissioning (= retiring) perfectly good and healthy older hardware, which is Jody's original reason. Of course, one can stay on 8.0 for other reasons, all perfectly reasonable, but deciding to keep one's loved/trusty hardware may compel one to stop at 8.0, if one wishes to use the x64 version (the hardware requirements discussed in the quotations below apply to x64 only!).
It seems to me that Intel processors that are unable to run 8.1 and 10 lack PREFETCHW, which all multicore AMD processors do include, whereas most multicore AMDs that are unable to run 8.1 and 10 lack CMPXCHG16b, instead. However, at this point, this is little more than just a guess. I know for sure all Athlon XPs cannot run even 8.0, because they lack SSE2, among other things, but not all Athlon 64 X2 and later AMD processors are able to run 8.1 or 10 but all seem to be able to run 8.0...
It's no guess anymore, but fact. Of course we're talking about processors Intel from Jan 2006 or newer.
Later Addition: It turns out that the 1st Intel processor to support PREFETCHW was Cedar Mill, the 65 nM final revision of the Pentium 4 released on January 5, 2006. And it seems that the 1st AMDs to support CMPXCHG16B were the Bulldozers, from late 2011!!!
Sysinternals' CoreInfo is the right tool to test whether a machine has those requirements or not.
It may simply be that they've given the next mini-step and are now refusing processors not supporting x86-64 mode even when installing a x86 version of Win 10. Of course it's nonsense to require x86-64 support to run in x86 mode only, but MS stopped trying to make sense long ago, so it'd not surprise me if this guess turns out to be right.
Just stop using this trash, v1809 is the worse of all versions, I do not use 10 as my every day OS, but I have a partition with 1709 updated to Dic 2017 and all is working fine, updates service is disabled and metered connection selected just in case, to aboid updates.
I got version 1803 on my desktop. I found some under-the-hood changes beneficial in my every day usage. Didn't really think I'd be saying that after the experience from a year or two ago. I don't intend to switch to newer build at this time. I doubt anything that would interest me is coming, plus, the split personality between Settings app and Control Panel remains irritating.
oh yes I do run a Win10 LTSB 2016 version on one of my old PCs (using onboard nVidia nforce 430 / Geforce 6150SE graphics chipset) and it runs just fine. plus LTSB/LTSC does not get any "feature updates", meaning no upgrades to newer Win10 builds.
I tried to boot from Win10 v1809 install media (either the regular Win10 1809 versions or the LTSC 2019 release) on an old Dell Inspiron e1405 laptop [which also uses Intel 945GM chipset] and it would just hang on the Windows logo screen for many hours doing nothing (no spinning dots on that boot screen). That is until I changed the processor from an Intel Core Duo T2700 (Yonah) to an Intel Core 2 Duo T7600 (Merom). After upgrading the CPU to the T7600, I booted again from the v1809 usb install media and it went through with no problems and no lockups.
Edit 2/28 about the Dell e1405: It seems the v1803 release of win10 worked fine with the Intel Yonah Core Duo CPU on the dell e1405 laptop but not the v1809 release; only when I upgraded the CPU to any Socket M based Intel Merom CPU that I can run the 1809 version.
And for the MSI 915GM Speedster-FA4 computer, you are better off running Win10 LTSB 2016, which is based on v1607 (see that is why I like to run the older LTSB/LTSC editions of Win10 on old hardware that can't work with newer Win10 releases, except for LTSC 2019 which requires newer hardware)
well Petr the Intel T2300E processor and other Yonah based processors actually worked on at least the 1903 (May 2019 update) release as I tested this myself several months ago (and of course they'll work with 1909 since that one is basically a 1903 SP1)
it was only the 1809 version that totally broke support for Intel Yonah & Intel Pentium "Dothan" series of CPUs - let's not forget, the 1809 release was rushed by MS in which it first deleted user files upon upgrading to it (when first came out as build 17763.1 back in early Oct. 2018) and got several re-releases after it. MS never figured out how to make 1809 work with these old mobile/laptop PCs, not even with the recent 1809 cumulative updates like KB4523205 released in Nov. 2019 and 1809 refused to boot up with these old laptop CPUs.
I was wondering Petr, if you still have that old MSI 915GM Speedster-FA4 device, can you try installing 32bit Win10 v1903 or v1909 on there? (using the ISO method - aka install any of those versions from a local usb flash drive or dvd disc). this guy from this Ten forums thread was able to install 1903 on his old 2006 laptop that uses an old Pentium M cpu chip several months ago thru a 1903 ISO and it worked.
If that fails, you can download Windows 1803 (April 2018) from the Microsoft website and use the media creation tool to either create an ISO file to mount to a virtual drive or burn to a bootable USB. If you are mounting the ISO to a virtual drive, you be able to click on the virtual dive letter and select Setup. I've found it to be the second easiest method.
If that fails, you can try booting from a bootable USB. When booting from a USB, you should perform a clean boot by holding down Shift while powering off the machine. If you have an EFI BIOS, your HDD's/SSD's partition table will likely be set as GPT, and you will need to select the corresponding EFI USB device. In my own personal experience, the EFI installs tend to be more tempermental, and sometimes it will take multiple attempts to complete sucessfully. If your system is using an older legacy BIOS, you will select the option that doesn't contain EFI in the label. An EFI boot device cannot be used on an MBR drive and vice versa. Once you've booted into the installation media, it will prompt you to select the destination drive for the install. Select your C: drive or wherever your OS is installed. It will then ask you if you'd like to upgrade your system while keeping your files and settings or if you want to perform a custom install. Select Upgrade while keeping everything. It will then prompt you to remove the USB media, reboot the computer normally, re-insert the USB drive, and select Setup.
The only known mainboard/BIOS compatibility problem with 1803 is with ASUS motherboards. Microsoft has reportedly blocked the update on those machines. There are other compatiblity issues with display drivers, Intel HDDs, Alienware systems, and others. You might want to check to make sure your hardware is compatible with the 1709 or 1803 update. When using the Windows Update Assistant, it should scan your hardware and check compatibility before starting to download the update.
I definately would not use the standalone BIOS updater on the HP Support website. I've bricked a nice Dell laptop after a failed BIOS update using the manufacterer's updater. I've never had a problem flashing the BIOS on a machine the old-fashoned way with either a USB floppy drive, USB flash drive, or CD. I would suggest searching your machine's model number with various BIOS update methods to see which ones tend to be more reliable.
d3342ee215