This question already has an answer here:

After running linux in a virtual machine for a while, i decided to try to dual boot it on my 2014 i5 linux desktop (not sure exact model). After following many guides and about 5 hours of installations, updates, changing settings etc, my computer gave up. It stopped working, and would not even load the bios. It black screened and would do nothing at all when turned on. after trying for days to fix it i gave up andf bought a new pc.

I now have a HP Pavilion 550-153na but i am very weary of dual booting it with ubuntu after what happened last time. Could someone please help me with an in depth explanation of how to to this process? If there is already a guide that will definitley will work with my PC please do link me to it, if not hopefully someone could advise me what to do.


marked as duplicate by amc, karel, David Foerster, Kevin Bowen, Zanna Jul 25 '16 at 18:10

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 3
    Read the install guide - It does not sound as if your previous computer problem had anything to do with Ubuntu as you could not even reach the BIOS, that suggests a critical hardware failure unrelated to your operating systems. Why do you blame Ubuntu and not windows ? – Panther May 11 '16 at 22:27
  • I apologize for blaming ubuntu, it just seemed strange that my computer worked fine for many years, and had an issue while trying to dual boot with ubuntu. However i am not trying to place blame, simply trying to make sure i don't mess it up again! Thank you for the links. – Seb9095 May 11 '16 at 22:34
  • 2
    If the old computer did not even boot to the bios there is (was) a significant hardware failure which happens with computers that are long in the tooth. If the problem were with the operating system, ubuntu or otherwise, it would at least boot to bios. – Panther May 11 '16 at 22:41
  • I agree with bodhi.zazen. I've had different computers refuse to turn on after tweaking them for hours. I called it a night and went to bed, then suddenly they boot fine again the next day. That was back when I was still using primarily Windows. – David Foerster Jul 24 '16 at 6:56

Whilst I have different hardware, I suspect you probably have a similar scenario to mine.

Lots of suggestions from @oldfred and @fords in response to my post - so credit to them for taking the time to respond.

If yours is a new machine and already came with w$ 10 preinstalled i.e an OEM installation, it'll be UEFI enabled and so the suggestions should help. They all tend to say

  1. Disable secure boot in your BIOS (I don't think this is strictly true - but I need to reboot the machine I'm typing on to check what I have in the BIOS)
  2. Disable fast boot in your BIOS

It is possible to do this with w$ installed first (some posts suggest the opposite but I found I didn't need to put ubuntu on first).

Once you have ubuntu installed from a live-usb, I think it's just a case of running bcdedit from w$ (see @fords comment on my post for how to do that).

I happened to update my BIOS to the latest version (I suspect that was not necessary but I was clutching at straws ....) and re-install grub (more clutching I reckon).

Naturally, to be safe, I'd backup your w$ partitions and data (there are various w$ tools to do that) if possible before messing about. I had a free upgrade to w$10 so I was able to create a separate w$10 installation boot disc - so if it all went pear shaped I could always resort to flattening the whole box and starting again. That may be an option for you too.

Good luck

Not the answer you're looking for? Browse other questions tagged or ask your own question.