Windows 10: Boot Trouble, system partitions and UEFI

Hi,

So I thought I'd sling a new disk in my system. And then the OS wasn't seeing it so instead of looking in disk manager I just swapped the cables for my D: drive and powered on. The boot config was missing and Win 10 wouldn't boot. Somehow my D: drive had been set as a system drive. So I put back the cable from the new drive in the old D: drive. Still got the error that the boot config was missing or corrupted and so I booted up to system install/repair and followed this guys instructions on You Tube.

So now I've got a system that doesn't boot unless the win 10 installation USB stick is in the system. It won't even boot to the install anymore. Here's a picture of what's going on in disk manager




I've had a look at a few threads on the matter that Google threw up from the Win 7 forums but they're not very helpful for various reasons. Does anybody out there know how to go about untangling this mess so that my system will boot up from my C: drive without the USB stick. Thanks.

:)

 

Windows 10 0xc000000f

Lenovo M73 + Samsung SP600 - 128GB SSD :
solution with UEFI BOOT & GPT partition table is now 100% tested - IT WORKS !

So now we can do the summary:

Problem exists on small system partitions (>120GB), on disks with MBR partition table format.

TWO SOLUTIONS ARE 100% TESTED AND WORKING:

1. FOR PC's SUPPORTING UEFI: enable UEFI/SECURE BOOT and partition Your HDD/SDD using GPT partition table format. No more trouble, and this
solution is independent on Your HDD/SSD size.

2. FOR PC's without UEFI SUPPORT: install at least 240GB HDD/SSD, create a system partition on a whole disk surface (the size of system partition
should not be smaller than 200GB).

I think there is still one mystery: one of us have a hybrid disk, which was bricked - as he claims - during this update. In my opinion it is not possible, but what if I'm wrong?

 

Windows 10, Fixboot - Access Denied

If you are running a Legacy system, there is no need for a FAT32 partition to boot.

For an NTFS partition to be bootable, it needs to be marked as active.

Still not sure exactly what you are trying to do.

Secure Boot is a component of Win 10 when installed in the UEFI mode.... UEFI systems need FAT 32 partitions to boot.

 

unplug all HDD's except the windows OS Disk 0

leave the USB in the drive to boot up back into windows..

once windows is loaded - remove the USB

Open Command Prompt (Admin) and type >

bcdboot C:\Windows /s C: /f BIOS

reboot and windows should boot up on is own - without any other drive connected

 

Thank you very much Kyhi that's worked brilliantly, you're a star!