How do I get a usb stick with linuxlite 3.4 to boot up on a windows 10 HP?

[bitsnpcs]

Hello bluzeo,

if you install Windows in VirtualBox -

• click from the top menu File>Preferences>Network>Host Only Network (tab)
• click + icon, it will make a virtual network
• click OK
• right click on the Windows VB machine, a menu will appear, click on "Settings"
• click Network in the left pane/menu.
• click downwards arrow button to the right of "Attached to", and select "Host-only Adapter", the name should be the same as at #2 above.
• click OK

If you don't open any files from media of unknown sources using it, it should be OK, and clamtk won't be needed.

[bluzeo]

For me I'm debating on Vming windows 10 but I don't want clamtk....


God Not dead.

[pingball57]

I've since checked the bios. the little arrows have gone. I tried to boot from UEFI but was informed no OS could be found so Win x has def. gone. Good riddance if you ask me. I still have it on my other m/c to annoy myself with if I'm feeling masochistic but I've got the feeling even that's days are numbered.
CHeers everyone.

[gold_finger]

@ pingball57,


Congrats on getting LL installed -- hope you like it.  Feel free to post any future questions that may arise here on the forums.


Don't worry about Win10 being gone.  Worst case scenario, if you decide you do need/want it back you can still download the Win10 ISO file from MS and make an installation USB following instructions here.  (Easiest to do that from a Windows computer using the Rufus program to make the install USB in my opinion.)  Since it was already on the computer before, it will automatically be verified/authenticated by MS servers when/if you re-install it, so no need to worry if you didn't write down product key.  (Note: that only applies to you re-installing it to same machine it was originally on, not another machine.)

[bluzeo]

Get etcher.io App untbootin doesn't work....


God Not dead.

[pingball57]

Having spent over an hour just reading half the suggestions & struggling to understand half of that i realised i'm suffering mission creep. My objective was actually:

1. Getting away from Windows.
2. Which should also result in spending less time trying to get the computer to work & doing more work on the computer.

So spending a lot of time trying to save Win 10 was defeating the object, so in compliance with aim 2. i installed LL to see what happens. Installed fine but it looks like Win 10 is toast -  bo-ho.
 Thanks everyone.

[pingball57]

All that looks like a lot to get through so it might be a while for me to let you know how I get on. I'm not desparate to keep Win 10 but as this backup laptop outperforms what it's backing up, by some margin, i thought it might be useful to keep Win 10 in case i ever needed it, & make it my primary comp.

I posted in this thread as my original problem was identical & the only solution for me was to f9 & select boot option from there so i thought it migh be useful for anyone else in this posistion.

 Thanks for the input, fingers crossed.

[trinidad]

https://www.tenforums.com/tutorials/85195-check-if-windows-10-using-uefi-legacy-bios.html

https://www.tenforums.com/tutorials/5831-boot-uefi-firmware-settings-inside-windows-10-a.html

Let's verify what's actually installed here first and then check the firmware version.

TC

[gold_finger]

@ pingball57,


Going to expand on what firenice03 said.


LL can not (easily) be installed in UEFI mode, but can be installed in Legacy mode.  Result -- you won't be offered choice of which OS to boot on each startup.  Instead, to boot Windows set computer to boot in UEFI mode; to boot LL, set computer to boot in Legacy/CSM mode.  However, you said:

There is a comments box next to all this that reads:
When legacy  support is enabled, UEFI Boot order & legacy boot order are both avaiable and UEFI boot order has higher priority than legacy boot order.

So, I'm not 100% sure that computer will allow booting LL after install if it automatically looks for an gives priority to UEFI installed systems.  (Only way to find out is to install LL and try booting to it afterwards.)

EDIT:  Just saw trinidad's post after posting this.  Maybe info he posted would solve problem booting LL in Legacy mode if you run into any problems.

My recommendation is to NOT select any install option for LL to automatically install to the disk, because it might wipe out Windows accidentally.  Instead use the "Something Else" manual installation choice where you can manually direct exactly where LL gets installed.


BEFORE INSTALLING, boot into Windows and do the following:

• Use disk management to shrink main Windows partition (probably "C:drive") to make room for LL installation.  Free up at least 20-25GB; 50-100GB or more is preferable if you have room for that.  DO NOT create any partitions in the resulting free space -- leave unformatted and unpartitioned.
• If you haven't already done so, create a Windows Recovery USB to have in case of emergency.
• If you haven't already done so, create a Windows Installation USB to have in case of emergency.
• Turn OFF Windows Fast Startup, which is on by default in Windows 8-10 systems.

To install LL follow this tutorial for installing in Legacy mode to GPT formatted disks.  Skip warnings about Windows in the tutorial.  Go straight down to "Instructions" heading for the install.  Skip first few steps about wiping out current partitions on the drive and creating a new GPT partition table.  You do not want to do that in your case because you're keeping the Windows OS on the computer.  Instead, open GParted program as described, then skip down to "Make your new partitions" step and proceed from there.

[trinidad]

https://www.lifewire.com/how-to-access-advanced-startup-options-in-windows-10-or-8-2626229

Start here. The easiest way to fix this is with a Windows 10 installation disk. If not try some of the suggestions above. You are having an EFI problem that is not really the fault of EFI. On some EFI Windows installations UEFI will not release the media channel because of BIOS bugs are the fault of the OEM. In other words even though you enable Legacy in the BIOS the Windows 10 UEFI won't recognize the change. You must make the change to Legacy boot from the Windows 10 blue advanced options screen. If you have a Windows 10 Pro installation disk this is easy to do if not you must use one of the other methods to get to the blue screen and UEFI change settings. It should be available if your Windows 10 build is above 1700. Get this part figured out if you can first. It's easy after this if you can get through it but you will have to use the 'other' option in the LL installer when you get that far. Defrag Windows before you do anything. Shrink your Windows partition from Windows and leave the resulting empty space unformatted and unallocated. Do not use gparted to do this. Use Windows disk tools. The rest is cake.

TC

[firenice03]

Although similar issues - you may still want to open a new thread.. BUT....

I say half solved. I was wanting to install as a dual boot & when the install of LL reaches the install options it says:

'This computer currently has no detected operating system, what would like to do?'

So I don't get the option to install alongside, only erase disc & install.

I would rather dual boot. Any Ideas?

Yes you're closer than you know
Windows is installed in UEFI/Secureboot and LL will be installed in default BIOS... Both will reside on the same system but they have different front ends they won't see each other.
BIOS isn't UEFI, they're separate boot ups ... Hense why no prompt for along side.


You can move forward with LL install as normal. If you want to boot to Windows go back in and enable UEFI Windows will be available.. Legacy BIOS LL will be available. They wont be side by side as with Legacy installed Windows & LL..


You could reinstall Windows in Legacy mode to have both without changing BIOS options OR
You can search the forums for UEFI and see how others have gone around..
Here's one tutorial
https://www.linuxliteos.com/forums/tutorials/tutorial-how-to-set-up-a-winll-dual-boot-with-uefi-fully-enabled/

[pingball57]

Hi. I've the exact same problem. As I stated in my intro post. I've mot been here lately & was just about to start a new thread on this same subject. but thought I'd check for any new posts - and found this thread.

I recently bought a backup notebook from fleabay – vendor said from an office clearance. It's got a replacement screen (a tad too small) & the model was stated as HP 15-R125NA (intel N3540 quad) but the model No has been (deliberately?) scratched off the lable. So who knows what it is for sure.

I have exactly the same problem as Dana. Whatever I try it will always start in Win 10. Holding shift down on shutdown has no effect neither does a 'hard reset' , both mentioned above. I have left the BIOS in the following config (having tried every combination i could think of):

  Boot Options
  Post hotkey delay (sec)               <0>
  CD-ROM Boot                          <enabled>
  Internal Network Adapter Boot    <Disabled>
   Network Boot Protocol               <IPV4 (legacy)>
  Legacy Support                  <enabled>
  Secure Boot                      <Disabled>
  Platform Key                          Enrolled
  Pending Action                  None
  Clear All Secure Boot Keys
  Load HP Factory Default Keys             [can't get the enables etc. to line up properly]

  UEFI Boot Order
  USB Diskette or Key/USB Hard Disk
>OS Boot Manager
  USB CD/DVD ROM Drive
  Internal  CD/DVD ROM Drive
! Network Adapter

  Legacy Boot Order
  USB Diskette or Key/USB Hard Disk
  USB CD/DVD ROM Drive
>Notebook Hard Drive
  Internal  CD/DVD ROM Drive
! Network Adapter

( The > infront of OS Boot Manager & Notebook Hard Drive, are solid wedges & not the > I have put. it doesn't matter where i put these options in the stack they always have this >)

There is a comments box next to all this that reads:
When legacy  support is enabled, UEFI Boot order & legacy boot order are both avaiable and UEFI boot order has higher priority than legacy boot order.

If I disable legacy support then Secure boot automaticaly becomes enabled & only UEFI Boot Order is highlighted & not both as here.

I have only tried to install  Linux distro's on 2-3 laptops & have never encountered a BIOS that looks like this. I think it's Microsoft deliberately trying to 'dissuade' people from getting rid of Windows x.

On the plus side, all this has been half solved by 'TheDeaD's post above. If I go f9 on bootup & select the boot option for USB from there (with the USB in place from the beginning) it will boot to Linuxlite from the live USB.

 I say half solved. I was wanting to install as a dual boot & when the install of LL reaches the install options it says:

'This computer currently has no detected operating system, what would like to do?'

So I don't get the option to install alongside, only erase disc & install.

I would rather dual boot. Any Ideas?

[TheDead]

I did not see in the thread if pressing the F9 and selecting the boot device from the quick boot selector was tried (without entering the BIOS and "saving" the boot sequence). I guess fast boot was the key but in is it not possible to just delete the hibernation file on boot by pressing F8? I dont have Win8/10 but this was possible in Win7/Vista.

Cheerios!

[bitsnpcs]

Thank You @trinidad 

[trinidad]

Yes that is often the case with Windows machines. If it does not work your other alternative is shut down and disconnect all power from the machine battery and/or AC. (hard reset) Windows is normally set to hibernate to recall uninstalled updates, and to enable faster system load of the UI. The shift key works, but you still have to boot the media from the boot device menu. (HP I think is F12) Setting the boot device order has no effect on the hibernated system. You must manually select the media channel but you can't from hibernation mode on many newer machines.

TC