Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 10 won't boot anymore after connecting new hard drive


  • Please log in to reply
24 replies to this topic

#1 Snowcrystal

Snowcrystal

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 20 February 2017 - 12:03 PM

Hey, i'm new here and hopefully i'm posting this in the right place. Will try to explain as best as i can.

I have 2 drives, a SSD that contains Windows 10, and HDD that contains other files.

Yesterday i replaced the 160GB HDD with a 1TB one, and this is where problem started.

Initially Windows wouldn't boot as normal, but instead tried to "fix disk errors" and then told me that Windows couldn't start. I tried the start-up repair option but it didn't help. Later two blue screens appeared (UNMOUNTABLE_BOOT_VOLUME),

Right now it appears that Windows tries to boot, as there is the Windows logo, and these "loading floating dots", but then it all disappears and all that's left is a black screen. When i move the mouse, the cursor appears for a second and then disappears.... And that's all i can do, it won't go past the black screen. Disconnecting the 1TB drive or connecting the old one doesn't change a thing.

Will be most grateful if someone could help me.

Cheers



BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 20 February 2017 - 02:22 PM

Try the following first. Create a DVD or USB or Windows 10 using the Media Creation Tool. Boot the install media and when you see the screen with the Repair Computer link click it. Troubleshoot > Advanced Options and do a Startup/Automatic Repair. Do this without the HDD attached. It may take up to three attempts for the startup repair to complete all repairs.

 

Windows-10-repair-your-computer.png



#3 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 06:12 AM

Thanks for hearing me out.

Unfortunately that didn't appear to do a thing. The repair attempt always results in "Startup repair couldn't repair your pc"

Windows boot behavior is still as it was.



#4 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 21 February 2017 - 08:34 AM

With the HDD detached boot the install disk and at the screen asking for language press Shift + F10. This will open a command prompt. Type the following commands.

 

diskpart

list disk

select disk 0

list volume     Post the output

list partition    Post the output



#5 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 08:47 AM

list volume output   http://pastebin.com/cbRWiCdk

list partition output    http://pastebin.com/Ug5DmaFZ



#6 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 21 February 2017 - 09:22 AM

Is this an OEM computer that came pre-installed with Windwows 10 or 8. If not what is the make and model of the motherboard. 

 

After inputting the list disk command is there an asterisk under the GPT column?



#7 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 09:31 AM

I built this pc myself over a year ago, motherboard is MSI H81M-P33

There is no asterisk under the Gpt column.



#8 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 21 February 2017 - 09:40 AM

According to the specs of the MB it is UEFI.

 

The MSI Click BIOS 4 is the latest UEFI BIOS with optimizations for Windows 8. Not only reacting faster and running smoother, it also has better mouse support. This is all comes with many cool features, such as Hardware Monitor, Board Explorer, and OC Profile Preview.

 

 

If UEFI mode is enabled in your settings and not Legacy or CSM boot then the disk will not be able to boot if not listed as GPT. On a GPT disk there should be a FAT32 partition listed labeled as System. If an MBR disk there should be a System Reserved Partition marked as active.  If the computer booted fine before then I surmise the EFI partition for booting was on your other disk but I am not sure why the computer no longer boots when replacing the original drive.

 

Run diskpart again and type the following.

 

list disk

select disk 0

list partition

select partition 2

detail partition     Post the output.


Edited by JohnC_21, 21 February 2017 - 09:40 AM.


#9 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 10:04 AM

Partition 2
Type : 27
Hidden: Yes
Active: No
Offset in Bytes: 249586253824
 
 
 
Volume ### Ltr Label        Fs     Type        Size      Status        Info
---------- --- -----------  -----  ----------  -------   ----------    --------

* Volume 1   E                NTFS   Partition   450 MB    Healthy       Hidden



#10 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 21 February 2017 - 10:37 AM

I am not sure what happened but if you have UEFI mode set then the SSD will not boot. It will not boot even if you have Legacy or CSM boot enabled as the partition is not active. The only chance you have of booting this drive is to make the partition active and change your UEFI settings to Legacy or CSM mode unless the MB can autodetect which some do.

 

Make the partition active by doing the following commands in diskpart.

 

list disk

select disk 0

list partition

select partition 2

active

exit

exit

 

Try rebooting. If it does not boot then there is are some additional commands that we can try. If we cannot get the disk to boot how hard would it be for you to reinstall Windows 10 on the SSD? From scratch we can create a GPT disk which is better than MBR. 



#11 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 10:49 AM

Now i get this message :

"An operating system wasn't found. Try disconnecting any drives that don't contain an operating system.

Press Ctrl+Alt+Del to restart"

 

I have some files that i would need to copy before reinstalling, but there would be trouble with copying my custom modded Skyrim as it's pretty big and i would need to do a research on to what files i need to copy over precisely.



#12 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 21 February 2017 - 10:52 AM

Now that partition 2 is marked active do the following command at a command prompt (Shift + F10) , not the diskpart prompt.

bcdboot C:\Windows /s E:

Reboot


Edited by JohnC_21, 21 February 2017 - 10:54 AM.


#13 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 10:59 AM

"Failure when attempting to copy boot files."

 

For some reason C: is now my pendrive and D: is now the SSD with Windows files.



#14 JohnC_21

JohnC_21

  • Members
  • 24,024 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:23 PM

Posted 21 February 2017 - 11:10 AM

At a command prompt type:

bcdboot D:\Windows /s E:


#15 Snowcrystal

Snowcrystal
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:03:23 AM

Posted 21 February 2017 - 11:17 AM

Once again, the same error message...






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users