New
#311
Good day.
In this case the driver that worked was the one installed from WU.
Good day.
In this case the driver that worked was the one installed from WU.
I had this problem on a Celeron M (XP Acer Travelmate laptop from 2006). I believe that the cut-down Acer BIOS, and the unsupported chipset/device drivers did not permit Windows setup to probe the system in order to integrate the devices with the resources that should have been allocated to them.
I wrote about the problems with the system here:
Let's run Win10 on really really old hardware - Page 22 - Windows 10 Forums
Let's run Win10 on really really old hardware - Page 15 - Windows 10 Forums
It currently runs 1803, but will neither upgrade nor install from Windows setup - I have to apply Install.wim to the drive with DISM or imagex, and run bcdboot to load windows. I then need to disable several devices in order to allow the system to run usably.
Now that 1809 has been re-released, I'll load it on the Acer in the same way, and drop an update in this thread.
I'm running a T6700 prone to overheating and I found a couple of things that helped :
- Start Throttlestop to undervolt CPU *before* logon. Run it as a service using NSSM
- Uninstall Skype app with powershell as it takes huge CPU on logon if you ever used it or not. Probably other apps do but that is the worst.
- Add fan control software as startup item (or service depending if you can).
The worst startup thing I have now is defender - it surges on boot - often enough to shut down my PC before it gets to desktop. Not sure whether to stop it or not. I feel if I start ripping pieces out of Windows I'm not running Windows any more and it is time to update my (2006) hardware.
well folks it looks like running either win10 v1803 or v1809 on really old hardware (ex. an old machine with an intel pentium m 750 dothan cpu on intel 915gm) causes either bsod on startup or will freeze/hang on the windows logo boot screen for other users as this fella from the msfn forum found out the hard way.
i wonder if you could upgrade the cpu on your old laptop to a mobile Intel Core 2 Duo (Merom)?
I could not run Win10 v1809 x86/32bit on an old Dell Inspiron e1405 laptop that had an Intel Core Duo [Yonah] T2700 processor as it will always freeze/hang on bootup. It was only after I changed the CPU from the T2700 to the Intel Core 2 Duo T7600 Merom processor that I can safely run the v1809 version.
The issues could be due to drivers. You have to disable all not-critical devices (see my earlier posts in this thread) and any startup application (including your Antivirus) before attempting to upgrade. For a clean installation disable all devices you can in BIOS before installing. Once successfully into Windows, you can enable them one-by-one and install drivers.
Last edited by spapakons; 28 Feb 2019 at 08:35.
um Steve, I think you double posted (aka. said this twice). remove one of them if possible
upon further testing on the Dell e1405 laptop (a 2007 model using Intel 945gm chipset), I can do a clean install of Win10 v1803 on there and the 1803 version runs fine after I switched back the CPU chip to the old Intel Core Duo T2700 Yonah processor. I tried to perform the upgrade from 1803 to 1809 (not thru Windows Update but thru installation media - I have a bunch of spare usb pen drives to create different win10 installation media) and after installation of 1809 and a reboot, it would completely freeze on the windows logo boot screen (w/ no spinning or circling dots) for many hours. I then powered off the laptop, turned it on and it would boot but would not complete the 1809 installation and reverted back to the 1803 version with an error message saying it could not install 1809.
for my situation with 1809, it was not the drivers - it was the hardware (aka. the CPU)
the 1809 release does not seem to work with Intel Yonah CPUs on the Dell laptop. only after switching from the Intel Yonah CPU (T2700) to the Intel Merom CPU (a T7600), the 1809 version of win10 will install & run succesfully on the Dell laptop.
It is really getting to a point where current & future builds/versions of win10 may break support for older Intel/AMD processors & chipsets (or perhaps drop support for them altogether), especially what happened to the Intel Atom Cloverview or Clover Trail chipsets, which are only supported up to v1607.