Solved installation-setup: winload.exe digital signature verification failure

[Protheos]

My Goal, is to put a windows 7 and a 10 OS, from each of two smaller HD (both previously used on my machine) onto different partitions of a new bigger HD, keeping all my old programs and data...so I can boot into either as I may prefer.

I purchased a new 1.8 TB Hard Drive, and partitioned it into two partitions. I cloned my original OS 7 HD and all its partitions onto one (C) of the two partitions on my new 1.8TB HD. Booting into windows 7 worked fine. I then cloned my newer OS 10 main partition from, a later used, small HD, all from the same machine, onto the second partition (D) of the new drive. I then used easyBCD to create a new entry in the boot menu, directed to the windows 10 partition, I had copied to the new 1.8 drive, on its own D partition. This gave me choice at boot up, of booting into windows 7 or 10, at start up. Windows 7 boot up choice works fine.

However, when I reboot the computer and select the boot into windows 10 option, and push enter, I immediately get the message "windows can not verify the digital signature for this file" File: /windows/system32/winload.exe . I will attempt to add a shot of this screen. Cant get it to post.... see it here: IMG_20180221_090707.jpg - Google Drive


Also pushing f8 when the windows 10 install is selected, during start up, only brings up the same exact error message. So I cant use that F8 method to disable driver signature verification in the 10OS install. How can I fix this, does Megahertz07 or anyone else have any ideas????Thank you.



PS I did turn off signature verification in the windows 7 OS install, but still get this same above message when I try to boot to OS10. I also tried replacing the winload.exe file on the 10 partition with a direct copy of that file from the original, smaller, OS 10 disk, I had cloned from, but no change. Thus I speculate... that the winload.exe file is probably not actually corrupt or unsigned, indeed it says it is signed in it's properties, but probably the boot up partition data is somehow still not right. (perhaps not actually directing properly to the winload.exe file, or some other issue? Any ideas on what I can try now? THANK YOU!

PSS I just got this advice from Megahertz07 via a PM.

"Protheos , you should create a new thread under /installation-setup, post the above message so other people could also help you.
On a private message other people with similar problem can't learn the solution we find to your problem.

Did you try to do a startup repair with Win 10 installation disk?"

My reply to this NOW is: Thank you, I have now tried this, but startup repair, after a diagnosis, simply says, "startup repair couldn't repair your PC"

Does anyone have any ideas for what I can try from here? Thank you!

 

[samuria]

Can you post a screenshot from disk management showing all the details. A lot will depend on what disk type your using is mbr , gpt ,uefi

 

[Protheos]

Can you post a screenshot from disk management showing all the details. A lot will depend on what disk type your using is mbr , gpt ,uefi

Yes, thank you. Here is the screenshot of the disk in disk managment. This is the new 1.8 TB disk. C has the OS7 and D has the OS10.

 

[samuria]

d is a logical parition it needs to be a primary active in order to boot windows you havent cloned all the paritions as it should have a boot one as well

 

[Megahertz07]

Protheos, I didn't like the partitions on your disk. You have a 10 G Unallocated partition on the beginning of the disk and then a 100M un format partition.
You should stat over again.
As Win 10 creates more partitions, you should clone the Win 10 disk fist (same size) then on the remaining space copy Win 7 and leave a big partition for data.

 

[Protheos]

Can you post a screenshot from disk management showing all the details. A lot will depend on what disk type your using is mbr , gpt ,uefi

I thought I saw a post from samuria that the disk needed to be set to primary. I thank you, and wanted to let you know I tried setting it to primary, using EaseUS partition, but unfortunately, the attempts to boot the windows 10, still result in the same message. Any thoughts on a next step I can try? I will now try Megahurtz07 suggestion, though this will take some time. I will post back.

 

[Protheos]

Protheos, I didn't like the partitions on your disk. You have a 10 G Unallocated partition on the beginning of the disk and then a 100M un format partition.
You should stat over again.
As Win 10 creates more partitions, you should clone the Win 10 disk fist (same size) then on the remaining space copy Win 7 and leave a big partition for data.

Thank you for your help. The reason for the unallocated partition is I deleted a unneeded 10 G restore partition. The 100M partition is upon close inspection, actually not unformated, but this is cut off in the posted image I put up and so it looks like it is unformated.

I am going to go ahead and do as your suggesting. I will wipe the new drive, partition it into two partitions. I will place only the 100M (boot?) and the main OS10 partitions back on the new drive, on one of the partitions, 1st this time. Then, if it boots ok, I will add back onto the other main partition, the OS 7 Main partition only. I will then use the Easy BCD program to add a new entry pointing to the OS 7 partition. IF I have all that right, or not, please advise.

 

[Megahertz07]

Clone the Win 10 disk (all partitions) on the new disk.
See if it boots on win 10.
You will have a big unallocated partition on the end. Create 2 partitions: One 85G for win 7 and a big partition for Data to be used by win 7 and win 10.
Copy the win 7 partition to the 85G partition and any data to the new partition.
Use Easy BCD to add a win 7 boot option to win 10.

 

[Protheos]

Clone the Win 10 disk (all partitions) on the new disk.
See if it boots on win 10.
You will have a big unallocated partition on the end. Create 2 partitions: One 85G for win 7 and a big partition for Data to be used by win 7 and win 10.
Copy the win 7 partition to the 85G partition and any data to the new partition.
Use Easy BCD to add a win 7 boot option to win 10.

I have cleaned the new 1.8tb disk and started over. I have cloned the windows 10 OS to the new disk, and it works. When I cloned I did not select the 10GB restore partition in Macrium, and for some reason it put a 10GB unallocated section in front of the 100MB boot area, but everything works fine to boot into windows 10 on the new 1.8TB disk.

I next put the windows 7 OS main partition on the new 1.8TB drive. I created a new partition on the drive big enough for the windows 7 OS main partition, it has to be bigger then you suggested because of all the programs and such in the windows 7OS partitioin to be restored. I first restored from an image,
When I completed the restore from the image, I then added a new entery to boot into OS7. IT worked and booted, HOWEVER something has gone wrong. The 7OS has many folders and files on the desktop that were not on the original disk before I imaged it...and many many files and folders can not be launched. When click on them, I get a message that the object does not exist

After some frustration... I tried to clone using Marcuim. It kept stalling part way through and saying read error. After several fails I read someone with this problom used AOMEI successfully. SO I used that clone program and it worked. I used Easy BCD to add a new entery directed to the new partition. NOW it works OK and I am happy.

I MUST however select every time I boot, ..to go into boot menu and tell the machine to use the Hard drive. Then it starts, gives me a choice of windows 7 or 10, And after I select it will boot either as I need, all apps and data have been preserved. If anyone knows how I can make the system skip directly to the chose which OS screen with out me needing to select the Hard drive to boot from every time, then all would be perfect. IF no one answers me I may close this as solved, as otherwise than this little glitch it is solved at LONG last. I thank all who helped me!!!

Thank you so much
PS adding picture of the drive as it looks now

 

[Protheos]

The system has started booting to the chose OS menu perfectly. I do not know why. Anyway, I wish to thank all who helped me, and mark this case solved. Hopefully it will help others who what to do the same.