Windows 10: Can't install on an older machine

I'm trying to install Windows 10 on a P4HT (dual-core 64bit) IBM. I have tried flashing the ISO to a USB stick, copying the ISO onto a Ventoy USB stick and doing the first part of the install on another machine.

Doing either of the USB methods I get a black screen with a blinking cursor, no Windows flag.
Doing the first part of the install on another machine shows the Windows flag for a few seconds and reboots (no spinning dots and safe mode doesn't do anything)

I'm doing this with the recent builds of Windows, I have had Windows running previously on this machine, possibly 1909 or earlier.

The kicker is I want to install Server 2016 or 2019 on it, but those both do the same thing (AFAIK those are still based on 1909, right? Recently downloaded from the MS eval page)

Any ideas or input on getting Windows 10/2016/19 to boot on this ancient box?

submitted by /u/theogmrme01
[link] [comments]

:)

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx

 

Clean install of W10 not possible in Virtual Machine.


Please get a cup of coffee, lean back and think an answer for these two questions. Take your time, then check the answers below the questions:

Questions:

1. If you do a clean install of let's say Windows 10 Insider Build 10525 on a totally new computer which has never had an activated Windows 10 on it, does it activate?
2. If you do a clean install of Windows 10 Insider Build on a computer where the underlying Windows 10, upgraded from a qualifying old operating system has already been activated, does it activate?

Answers:

1. No, of course not.
2. Yes, of course.

Why do you think that a virtual machine would make any difference? You have tried to install Windows 10 on a totally new machine which has never had an activated Windows 10 installed, therefore the Microsoft activation servers block the activation due invalid machine ID. In the highlighted part in below quote you admit your mistake yourself, plain and simple, yet you when doing this wrong draw conclusion that even if done correctly it would not work:

What you have tried is essentially the same as if you took a brand new real physical PC without any operating system, which has never had any operating system, and then installed Windows 10 Insider Preview wondering why it does not activate! Virtual Machines behave exactly the same way; if you want to clean install Windows 10 Insider Preview and get it activated you must do it on an existing virtual machine, one which has already had an upgraded Windows 10 activated. This "computer", the virtual machine, its machine ID is marked on activation servers as valid and activated and it will of course activate.

Be it a virtual machine or a physical computer, you cannot activate a clean installed Windows 10 Insider Preview on a totally new machine. How difficult can this be to understand?

When clean installing Windows 10 Insider Preview on a computer which has already had a previous Windows 10 Insider activated, you do not use the product key! It will be asked twice, once before the installation starts and once after the last reboot to OOBE phase. In both cases you skip the product key and your Windows will be automatically activated.

 

Installing a Virtual Machine in Windows 10

Step #1 is to decide which virtual machine software you wish to install.

The three most popular choices are:

• VirtualBox (from Oracle)
• VMWare Workstation Player (from VMWare); and
• Hyper-V (from Microsoft)

Once you've made your choice you can find detailed, illustrated instructions for installing each one on the internet.

As a personal suggestion: You might find it easier to use either VirtualBox or VMWare Workstation Player. Hyper-V is more complicated to setup.

Between VirtualBox and VMWare, I think you'll find VirtualBox more user-friendly, and it has the advantage of allowing you to create checkpoints - backups of your virtual machine - whereas to do that in VMWare you'll need to upgrade to their (expensive!)
paid version.