M
M
Maxim Tarasov2017-09-06 12:27:22
Windows
Maxim Tarasov, 2017-09-06 12:27:22

Why is Windows 7 being installed, but windows 8 (and beyond) is not?

Good afternoon.
There is some computer. With a clean installation of Windows 7 on it (from a USB flash drive, from a DVD, over a network via WDS), everything goes fine. When you try to install Windows 8, Windows 8.1 or Windows 10 on the same machine, the machine is reset even before the installation starts: a window appears on the screen that hangs for 10-15 seconds, and then without any additional messages and a blue screen, the computer goes to reboot. After shaking the iron, I came to the conclusion that the problem is connected somehow with the motherboard. Yes, the board is ancient, but Windows 10 should be fine for itself. Everything would be fine, but now I got a second such board in my hands. Different manufacturer, slightly different specifications, but the symptoms are the same. The BIOS on both boards is up to date.
Any thoughts in which direction you can dig? Has anyone met with something like this?

Answer the question

In order to leave comments, you need to log in

5 answer(s)
G
Garik_Shuster, 2017-09-06
@Garik_Shuster

In the requirements for Win 8 and above, there are requirements that the processors support certain commands (instructions). In the old prots they are not. I don't remember where I read it, I've been trying to solve the same problem for a long time.

A
apreobr, 2017-09-06
@apreobr

To work with win8+, the processor needs to support execute disable bit (NX-bit). It appeared (emnip) at Intel since Prescott and AMD since ClawHammer. Without processor support for this instruction, the system cannot be installed in a regular way.

K
Konstantin Tsvetkov, 2017-09-06
@tsklab

Why is Windows 7 being installed, but windows 8 (and beyond) is not?
Not compatible, for example, in bit depth.

S
Serezha, 2017-09-06
Ahen @Ahen

Roll win10 onto the screw, connect this screw to that pitch? (on the extremes they did it, it works)

E
Ethril, 2017-09-06
@Ethril

Try switching the BIOS to the Secure boot/UEFI option.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question