Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
IPXE :: Windows 10 iSCSI disk installation, second stage fails (error 0xc0000428)
2019-09-13, 08:47 (This post was last modified: 2019-09-13 08:59 by Andromeda_x.)
Post: #1
IPXE :: Windows 10 iSCSI disk installation, second stage fails (error 0xc0000428)
Hello,

VM (Legacy/BIOS mode) in VMware Workstation 14 boots through iPXE and proceeds to Windows 10 installation. First stage goes well and copies files on iSCSI disk.

After reboot when second stage starts (sanattach replaced with sanboot) I get following error message.

Is there the solution for this error?

Thank you,
Andromeda_x

--- Error Message -----------------------------
Recovery

Your PC/Device needs to be repaired

The operating system couldn't be loaded because digital signature of a file couldn't be verified

File:\\Windows\System32\drivers\e1i65x64.sys
Error code: 0xc0000428

You'll need to use recovery tools. If you don't have any installation media (like a disk or USB device), contact your PC administrator or PC/Device manufacturer.
Find all posts by this user
Quote this message in a reply
2019-09-13, 09:29
Post: #2
RE: IPXE :: Windows 10 iSCSI disk installation, second stage fails (error 0xc0000428)
So the part that actually gives us information is "digital signature of a file couldn't be verified" there probably is an UPPER_CASE_ERROR as well?
How did you install the nic drivers?
have you worked thru all already existing threads about iSCSI with windows 10 that are on the forum?

To even have a chance of getting this to work, I would use clean Microsoft ISO provided winpe, without mods, also use the drivers that comes with windows, without adding your own, since that does give these kind of issues a lot it seems. But then again, you probably will get other BSoDs instead as discussed in other threads.

Read FAQ before first post!
Are relevant ipxe.org error urls and PCIIDs included?
Visit this user's website Find all posts by this user
Quote this message in a reply
2019-09-13, 18:04 (This post was last modified: 2019-09-13 19:16 by Andromeda_x.)
Post: #3
RE: IPXE :: Windows 10 iSCSI disk installation, second stage fails (error 0xc0000428)
Hi NiKiZe,

well, winpe was prepared with adding iSCSI optional packages according Microsoft website, iscsicpl.exe and required library files was copied manually before image was 'dismounted'. My procedure of integrating packages is based on the following article with some improvements [achitecture, for loops, debugging].

Installation media for Windows 10 Enterprise was downloaded from internet and not from Microsoft itself as I could not find direct link on 'Enterprise' version.

ISO: en_windows_10_enterprise_2016_ltsb_x64_dvd_9049483.iso
MD5: e39ea2af41b3710682fe3bbdac35ec9a
SHA256: 3874bc7160ed10f28744dc2b00f9518af99e706296b969fb7eaf26009e1caf76

Right now I try to install from stock ISO image (Windows 10 Pro) downloaded from Microsoft website, ISO image mounted in Linux and shared with Samba over network.

ISO: Win10_1903_V1_English_x64.iso
MD5: 8ba0e81b276d9052e8538deb0cf6c7d0
SHA256: 9846dfbdd7c39eb8d025e0f28e180c6f4084ecf87ecd11805cd19c205f7a3b4e

Network driver (e1000e) at first stage is coming from winpe image and for second stage should come from ISO image.

The image with 'Enterprise' in image name might been altered in some way although I do not think that NIC drivers (or other drivers) was added to it.

Is there any Microsoft website where I could get MD5, SHA256 sums to compare if ISO images are 'prestine'? Microsoft provides a list of releases withougt control sums.

I did some reading on internet about 0xc0000428 error and it looks like people had this problem UEFI secure boot process which is not applicable in my case as I boot virtual machine in Legacy BIOS mode.

I will skim through the forum on Windows 10 installation, a quick search for error code 0xc0000428 came 'empty' and I decided to add new post.

Andromeda_x
Hi,

installation from stock ISO image downloaded from Microsoft website failed after first reboot with following message bellow

This time installation is complaining about NDIS driver and particularly it refers to IRQL.

Ok, time to check forum if somebody already stumble on this issue.

Andromeda_x

---- Message -------------------------------------------
Your PC ran into a problem and needs to restart. We'll restart for you.

For more information about this issue and possible fixes, visit https://www.windows.com/stopcode

If you call a support person, give them this info:
Stop code: DRIVER IRQL NOT LESS OR EQUAL
What failed dump NDIS.SYS
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)