New
#321
I remind you that although v1809 refused to install, insider version did.
It seems the rumors might be true... I read in another thread that Microsoft is deliberately dropping support for older hardware in newer Windows 10 builds. I also have an old Acer Extensa running some T???? Intel CPU (do not remember which) and I have recently successfully updated to Windows 10 Pro v1809 32-bit. I will tell you once I have access to it again. What if you upgrade to v1809 with one CPU and then replace it with the other? Does it work?
PS: That is why is we must always keep an older Windows 10 build available as a fallback when we download a new build.
or use either an LTSB 2015 (v1507) or LTSB 2016 (v1607) version on anything below an Intel Core 2 Duo (desktop or laptop, Conroe/Merom) or Cedarmill (Pentium 4/Celeron D) based machine, which both of those get about 10 years of cumulative updates
about the question of upgrade to 1809 with one processor then change it later. tried that when I upgraded my Dell e1405 to v1809 using the T7600 (Merom) which upgraded succesfully, then change it to the older T2700 - computer will not boot with the T2700 (Yonah) - froze on the win10 boot splash screen - no animated circling dots at the bottom; both CPUs mentioned are Socket M based processors. not experiencing that problem with v1803.
check out this awesome screenshot - crazy but true (I did this as an experiment with an old Intel motherboard using an Intel Pentium 4 524 "Prescott" chip & running 32bit Win10 v1809) [not all Prescott based CPUs may work with v1809, usually the 500 & 600 based Prescott CPUs (minimum Pentium 4 505/505J) can run at least v1809 32bit]
use Speccy or CPU-Z on that old Acer Extensa computer and see which processor it uses.
Last edited by erpster4; 04 Mar 2019 at 11:22.
screenshot of the error message after attempting to upgrade from 1803 to 1809 on the Dell laptop using an Intel Core Duo mobile T2700 (2.33Ghz) Yonah processor but failed and reverted back to 1803
(looks like the 1809 version does not like Intel Yonah and any Pentium M processor)
That's the exact error message I am getting too on another Core 2 Duo processor (maybe the same). I tried an insider preview version and it worked though. Waiting for 19H1 release although I am not keeping my hopes up.
Two oldest systems I have, both allow standard installing & running & updating of 1809 x64:
Atom N450 Pineview & NM10 Chipset - year 2010
...horribly slow, limited usage possible under linux
Core2 Quad Q9550 Yorkfield & nForce 750i Chipset - year 2008
...lack of SLAT/EPT so no 3-tier nested virtualization
Perhaps they will be supported under 19H1 too.
Not "really old hardware", only for info.
can you run the CPU-Z tool to see what Core 2 Duo CPU you have, eLPuSHeR?
I only encounter that error message with a mobile Intel Core Duo "Yonah" (32bit/x86 only) processor (it was a T2700). If I put in a Core 2 Duo mobile that is based on "Merom" (has Intel EM64T support) [ex. T7600], the error message does not appear when upgrading from 32bit v1803 to 32bit v1809.
seems like 1809 (both 32bit & 64bit) works with Intel & AMD processors that need minimum either Intel EM64T or AMD64