Windows 10 won't boot

[TripleMonkey47]

This is propable the only place I can get help now.

After stumbling all across the web, I've found nothing on this case. 
I recently bought a netbook, Jumper Ezbook 3 Pro, which has m.2 slot. So I plugged in my new 120GB WD Green SSD, extracted product key using PowerShell and proced to clear install Win10. I wiped all drives and partitions clean, both the SSD and soldered on 64GB eMMC storage which defaultly contained Windows, when it came to me. Right now, I've been trying to install Win10 for like 8 hours. It sometimes won't install at all, giving 0x80070057 error, sometimes it will instal normally, but then BIOS won't find it as a bootable drive, despite me seeing around 10 gigs taken up on that drive. When trying to install on this drive again it warns that it will create windows.old. My BIOS is very limited, it came that way from the manufacturer and I can't flash unlocked BIOS, because I can't boot into windows. I also tried creating partition to install windows on using diskpart, but I can't seem to manually create GPT partition.

[homeap5]

It's too late of course, but stop fixing problems that don't exists. If you have working operating system - use it and don't try to reinstall or made improvements if you have no experience. Once a week I see posts here from people that have problems, because they decided to made "clean install".

 

Btw. Install win10 on other computer, then plug disk back.

[TripleMonkey47]

I was trying to reinstall from an eMMC memory to an SSD, because eMMC memory is conciderably slower and thus was hindering that netbooks performance. I have experience, but this is something I've never encountered. Don't talk shit just to feel smarter.

 

I've thought of installing it through another machine, but right now it's not an option for me and I need this netbook working ASAP preferably

[homeap5]

Don't talk shit? If you're so experienced, then why you just dont copy your system to m.2 drive? Then you can check if it's working and THEN you can format your internal drive.

 

And what is wrong with system.old? Is this any problem that installer create that directory? Why?

[TripleMonkey47]

I've not expected everything to crash on me. I've reinstalled windows numerous times, never with troubles like this. 
I'm not saying it's wrong, I'm just pointing it out, to show, that installator does in fact detect a system there

[homeap5]

So install it anyway, even if installer detects os. Or use bootable partition manager like gparted, to be sure that you clean drives completely.

[TripleMonkey47]

I tried installing it, still drive not detected, tried restoring mbr with bootrec, nothing happened

[LinuxTek]

what options do you have under the Bios boot menu?

 

 

 

 

[homeap5]

Drive must be GPT prepared, not MBR.

[TripleMonkey47]

2 hours ago, LinuxTek said:

what options do you have under the Bios boot menu?

 

 

 

 

Pendrive I have windows on and built-in EFI shell
 

 

2 hours ago, homeap5 said:

Drive must be GPT prepared, not MBR.

It wouldn't even allow me to install windows 10 on MBR partition

[homeap5]

But maybe after first boot on your old os, you initialize that m.2 disk as mbr. I'm just checking all options.

 

Do you try that gparted?

 

IMO the only good option is to install os using other computer, remove all partitions except system and let installation disk create them by fixing boot. This method may work because Windows may detect both drives, creates boot partition on eMMC and your system partition will be on m.2. Somehow probably your laptop can't boot from SSD or detect it as boot drive.

 

This may be helpful: https://www.easeus.com/partition-master/restore-repair-deleted-efi-boot-partition-in-windows-10-8-7.html

Method 2 - It's about restore EFI partition and move it to the same drive as sysetm, but in your case it may be useful if you creates EFI partition on eMMC and point boot drive on SSD, so your boot partition and system partition will be on separate drives - boot on eMMC visible by BIOS and after boot, your system will load from m.2.

 

OT. And as you see, i'm spend some time answering you and trying to find a solution, so maybe it's time to edit your rude post about talking shit?