Windows 10: ntoskrl digital signature error after NX/PAE hacking

Hello!

Following a guide in another forum, I was able in the past to install Windows 8 in an old Pentium 4 system without NX/PAE support. I'm not going to go into details here, but the process involved extracting the installation files from install.wim to a hard disk and patch certain files to bypass compliance check. One of them is ntoskrnl.exe. I was wondering if this is possible with Windows 10. So I followed the guide and managed to install Windows 10 to a VMWare virtual machine (I didn't have a real machine available). Yes, Windows 10 work, so at least in theory it should also work on a real machine. The problem is that in every startup I get a BSOD that ntoskrln.exe digital dignature cannot be verified or similar. I already tried to enable test mode and ignore signatures, as well as disable Windows Defender, but the problem persists! In order to load Windows I have each time to press F8 to get into advanced startup options and then select 7 to ignore driver signing. How can I disable system file check at startup so I don't get this message? Any ideas? Before you rush to say "why bother", I answer "for the challenge, because I can".

DESKTOP-JRBA5S1-Sat_09_26_2015_123403_03.zip

:)

 

The Windows 10 App Says My CPU Is Unsupported

Windows 10's required CPU features are the same as Windows 8.1:
PAE, NX and SSE2. You may need to switch on NX (aka Data Execution Prevention) in your BIOS settings.

 

Upgrading from Windows 7 to 10

To install Windows 10 on your PC, the processor (CPU) must support the following features: Physical Address Extension (PAE), NX, and SSE2. Most CPUs have support for these features, so if you receive this error, it is likely because the
NX feature is not enabled on your system.

-------------------------

To resolve this error, follow manufacturer guidelines to enable NX (“No eXecute bit”), or the equivalent XD (“eXecute Disabled”), feature within the BIOS settings. This feature is typically found in the Advanced or Security tabs within
the BIOS settings, and can be referred to by a variety of names, including but not limited to:

· No Execute Memory Protect

· Execute Disabled Memory Protection

· EDB (Execute Disabled Bit)

· EVP (Enhanced Virus Protection)

If the BIOS setting for the NX (XD, EDB, or EVP) support option is not available on your system, you may need to contact the manufacturer to update the BIOS. Note that some very old processors may not contain these features and will be
incompatible with Windows 10.

A whitepaper has been published with further details about the PAE/NX/SSE2 requirement for Windows 10, error cases and scenarios that customers encounter when machines fail to meet the requirement, and what to do to install Windows 8 on
their PC’s. You can download the whitepaper at
http://msdn.microsoft.com/en-us/library/windows/hardware/hh975398.aspx.

If you are using a virtualization product to install a Windows 10 virtual machine (VM) and receive this error (or error 0xC0000260), you must enable PAE (or PAE/NX) in the virtualization product’s settings or configuration manager when
setting up the Windows 8 virtual environment.

Note that if you tried to install Windows 10 on the VM hosted on a system running a previous version of Windows with NX disabled, you will need to enable NX on the system before PAE/NX can be enabled for the VM. Please follow the instructions
described in the whitepaperunder
“How Do I know if My System Supports NX or SSE2?” and “If NX Is Supported on My System, How Do I Turn on NX?” to enable NX on the system.

Error when installing Windows 8 Release Preview: “Your PC’s CPU isn’t compatible with Windows 8.”