Windows 10: Strange boot problem

I normally run my pc with two Samsung SSD drives, a 256gb 850EVO boot drive, and a 1tb 840EVO slave drive. Every so often I image one to the other using the Samsung cloning software.
I now wanted to use the 1TB elsewhere so simply removed it. After doing so my PC now boots only on the second start.
The first time I start I just get the flashing cursor in the top left of the screen. Power off on the start button and the PC starts fine.
If I put the slave back into my PC it starts fine.

The PC is fully up to date with driver s and updates.
There is obviously a boot issue but not sure how to fix. Any suggestions please?

Spec:
Windows 10 Professional (x64) Version 1703 (build 15063.674)
3.50 gigahertz Intel Core i7-4770K
MAXIMUS VI HERO Rev 1.xx
AMD Radeon (TM) R9 270
32gb (4x8GB) DDR3 Gskill Ripjaws

:)

 

Nokia 700 - won't start after FP1 update (112.something)

Same thing happened to me. Phone won't boot with my sim card, but with other one, boot without any problem. Very strange

 

WINDOWS 10 installation get stuck on windows boot logo - Error 0xC1900101 - 0x30017

Hi Arul_D ,

I gave a look on the links you provided but unfortunately y specific error is not present

Also my situation is not mentioned.

Could it be a boot block problem? The strange thing is that the boot logo hangs without errors, maybe its waiting for something to happen that never happens. It's strange that no timeout routines kick in to stop the process with a more specific error.

 

Your problem probably starts with having two bootable disks in your PC at the same time.

We recommend disk imaging to an external disk... having your image in the same system inevitably runs the risk of the same event corrupting both. (Think power problem, ransomware etc etc...).

Have you tried putting only one disk in your system and running Startup Repair?
If that doesn't help, Macrium Reflect's boot disk has a useful Fix Boot utility which does more.

If still problems, it would then be useful if you could post screenshot of your partitions using Minitool Partition Wizard, with columns expanded to show all text clearly.

Assuming you had both bootable disks in situ when you upgraded for example (new build), there may have some confusion.

Thanks.

 

Is the boot fix in Macrium only applicable if you used Macrium in the first place to create the cloned image?

 

No it's a general fix boot for Windows - you can find out more with Google e.g.

 

Downloaded the free version of Macrium and it doesnt appear ro be an option in any of the menus. Is there another version I should be using?

 

See my #2:

 

To clarify what @dalchina is saying - the Fix windows boot problems appears in the menu only when you boot the computer from a Macrium Reflect rescue drive.

 

I tried the Macrium Rescue CD with no luck.
I also tried a Boot repair from the Win 10 CD using Bootrec (RebuildBcd, fixboot, and fixMbr). Again no success.

 

Did you do that with only the one disk in your system? Were there any error messages?

 

Yes, just the 256gb drive. I am now edging towards a rebuild, which is going the be a challenge, trying to find all the serials, and hoping they still work...

 

Here's another approach:
1. Create a disk image of what you believe to be a working Windows (C: ) partition
2. With only 1 SSD in your PC (to ensure no partitions are created elsewhere)
Clean install Win 10 (deleting all existing partitions other than data)
3, Make sure your new Windows partition is bigger than the old one
4. Check that boots ok, and Advanced startup options (Safe Mode, Command Prompt etc) are present. (= check your Recovery partition is ok).
5. Now booting from your Macrium boot disk, restore your Windows partition, replacing the newly created one.
6. Boot from a Win 10 boot disk and run Startup Repair

 

At step 6 why not just run Macrium's built-in utility to "Fix Windows boot problems" since you would already be booted into Macrium Reflect anyway?

 

I did try that but no difference.