It would be. AIUI that would have a Pentium M cpu. I've tried W10 on an old laptop with an AMD V120 and that ran like treacle. Win7 runs fine - W10 crawls. The Passmark benchmarks say my cpu's benchmark is 50% higher than yours...
PassMark | CPU Performance Comparison - V120 vs. Pentium M
IME a benchmark of at least 1000 is needed to run W10 at any sort of usable speed.
Unfortunately while both Intel 915 and 925 had the potential for Aero graphics, they were not too fast, so Intel decided not to include WDDM drivers for these chipsets leaving out a lot of netbooks and old notebooks. The first Intel chipset to have WDDM drivers is 945G. For NVidia this is FX 5 series (GeForce 4 and earlier only have XPDM drivers). For ATI I don't know, never liked ATI so I never had one.
I found that the early Windows 10 Insider preview x86 and Threshold builds up to 10240 and some Redstone 1 Insider preview builds failed during upgrade from Windows 7, and would not clean install on an Acer Travelmate 2423 notepad with Celeron M 1.50 GHz and Mobile Intel® 915GM/GMS, 910GML Express Chipset Family (2nd PC spec). The setup failures would occur during the OOBE phase, tending not to create a new user structure, or failure to initialise the network due to Network and WIFI drivers not installing correctly. They would terminate setup with the indeterminate " Something happened..." error message, and setup needed to be terminated uncleanly, unable to proceed further.
Upgrading Windows 7 Pro to Redstone 1 14393, Anniversary Update, on a non-GPT partition did lead to a working system but with some elements of the PNP system being scrambled during the OOBE phase of device setup. Once the system finally started, it was almost totally paralysed due to system interrupts overloadinging the CPU 100%. By patient sloooow use of Device Manager on an almost unusable system and disabling all conflicting devices (modem, network, WIFI, and graphics controller) the system interrupts would die down, to allow one of the network devices to be re-enabled, so that the system to be used with reasonable speed, except with any graphics-heavy process such as video streaming &c.
The notebook remained unable to upgrade or clean install with setup for any Redstone 2 (Creators Update) or any more recent build. Applied wim deployment results in the plug and play situation remaining a catastrophe, with many devices having phantom twin entries in Device Manager, all with device driver failures, however, the system interrupts problem vanished, since the devices were not using resources.
I am not sure if there is a way to edit the registry to remove these duplicated device references - does anyone know?
The system also seemed to work better because of these free resources and the Microsoft basic graphics driver runs the system adequately. As long as I add a USB WiFI dongle, the system runs fine even up to insider skip ahead build 17618, but with some of the onboard devices not working.
It seemed to me that Windows Setup itself fails because WinPE from Redstone 2 and later also does not have the capacity to install or use the older intel chipset drivers and cannot properly probe the pnp/pci bus to accommodate the devices.
Last edited by Fafhrd; 15 Mar 2018 at 05:03.
Now that you know that specific devices cause the problem, you could try disabling them in BIOS (if possible) before clean-install RTM (10240) or TH2 build. Even better, you could first install Windows 7, disable these devices in Device Manager and then try to upgrade to 10. After successful installation of Windows 10, try manually forcing the Windows 7 drivers from Acer's site and then use show/hide tool to block all driver updates. Then create a restore point that you can try getting back if anything happens. Disable the devices again (just in case) and try upgrading to a more recent Windows 10 version. If you succeed reinstall Windows 7 drivers and block updates with show/hide tool. Post your results here to let us know.
I just install Win 10 in the same config on Compaq nc6120 (my acer have same CPU and memory and work with win10 too)
With fresh install it's work, but for the first time I need install winXP/7 on it to install win10)
the driver for GPU is basic driver from M$ but work on 15inc native resolution XGA 1024*768)
Your case proves that there is a driver issue in Windows 10. So for a clean installation of 10 we must disable any device that might cause a blue screen because of a faulty driver. If unsure, I would disable all not-critical devices, such as audio, LAN, Wi-Fi, Bluetooth, card reader, whatever not necessary to install Windows 10. This is provided we can disable them through BIOS or otherwise. If we cannot, then we must first install Windows 7, disable all these devices in Device Manager and then upgrade to 10. Once we have a successful Windows 10 installation, we can install all available Windows 7 drivers for these devices and disable Windows Update to make sure we won't end with a blue screen after the first update.
re all I guess question goes to Fafhrd, what build of win10 did you manage to install on Celeron M PC?
I tried installing Win10 on a Celeron M Notebook a couple of years ago and it failed, problem with PAE/Physical Address Extension.
Quote
