Any and all help would be so greatly appreciated. I’ve been battling with my laptop to be able to dual-boot Ubuntu Cinnamon and Windows 10 for about four days now. I’ve probably gone down five or six different rabbit-holes of troubleshooting, GRUB command-line fun, reinstalling and updating the BIOS, trying and failing to deal with VMX and locked NVram. As of now, my system boot-loops and fails to run Windows, but paradoxically I am able to get Ubuntu running, which is what I am using now.

I’ll try to provide as much relevant information here as I can:

  • Device: HP ZBook 17, gen 6
  • Primary OS: Windows 10 Home
  • Linux distro: Ubuntu Cinnamon 23.10
  • Ubuntu location: /dev/sda3
  • grub-install --version = 2.12~rc1-10ubuntu4
  • boot-repair Boot-info summary: https://paste.ubuntu.com/p/rxZ3D5GtpP/
  • I’m more than happy to provide more information as it’s requested.

As of now, I am unable to run Windows through the BIOS. If I run via the dedicated SSD as I normally do, it boot-loops, and if I try to go through any other drives it just tells me I need to install an OS. I am currently able to run Ubuntu, but only by going through the following process:

  1. Startup menu
  2. Boot configuration
  3. Boot from EFI > Ubuntu > shimx64.efi

At this point, I am happy with two outcomes to this scenario:

  1. I am able to run my laptop with Windows 10 as the primary OS, with the ability to dual-boot to Ubuntu Cinnamon 23.10.
  2. Assuming option 1 is impossible/requires a Herculean amount of work to pull off from this state, I am willing to scrub Windows 10 from my laptop and move forward with Cinnamon as my daily driver, though I am rather inexperienced in it. I can learn to move forward as I need to and run a VM or WINE for any Windows-specific processes I still need to do. But I would rather keep this option as my dead man’s switch.
    • @the_q
      11•10 months ago

      deleted by creator

    • @[email protected]OP
      5•1 year ago

      I appreciate the elegance of your answer but it’s a bit lacking in detail. Are you saying that I should go with the nuclear option when installing Linux and remove the old files? I might just remove my HDD in that case and install Linux into the dedicated SSD.

        • @[email protected]English
          4•1 year ago

          Should definitely be mentioned that dual booting isn’t nearly the headache if you have separate drives and don’t try to have the boot loaders in the same partition. I have Win10 and its boot area on one ssd, and two distros of linux sharing the boot partition on the second ssd, and there’s been no issues. But there’s a good chance Windows boot gets screwed if you try to put it all on one disk.

        • @[email protected]OP
          3•1 year ago

          Thanks for the no-nonsense reply. I have been smelling a little bit of bullshit with the whole dual boot fiasco here for a bit. VMX not behaving, Windows’ VM utility not behaving, BIOS not behaving, it’s like goddamn if I type a command I wouldn’t mind if it stuck instead of seemingly getting thrown into a black hole.

          Going with your approach, I imagine if I pick a home distro and decide I want to move to another down the line the transition is far easier than this? Even if I am switching from say Ubuntu to Fedora?

          • @[email protected]
            2•1 year ago

            I’ve been happily dualbooting Win10/Mint for years on the very machine I’m writing from. Zero issues with boots, GRUB, no need for flatpaks, both systems work fine, both configs heavily customized.

            • @[email protected]OP
              1•1 year ago

              I’ll have to spend some time backing up and moving some files around but I think this is how I’ll move forward. I think I’ll also find a cracked Win10 image and I’ll keep it on a thumb drive if ever i need to full on run the OS. I use a few proprietary software that universally get the JUST USE FOSS ALTERNATIVES argument from people not in the know.

  • @[email protected]English
    8•1 year ago

    Sorry this isn’t an answer to the question, only a general reminder for whoever needs it to always create a disk image backup beforehand using Macrium Reflect or similar, so you can rollback nightmares like this.

    • @[email protected]OP
      5•1 year ago

      Listen to what this person has to say, you people! I ignored multiple recommendations across probably ten different webpages to create a backup disk and I could have walked a lot of this back and started over, at the very least. FWIW, I’m sure that whatever is going on now is not irreparably broken, but certainly I could have saved myself some headaches.

      • @[email protected]English
        2•1 year ago

        Again, sorry I cannot offer a solution. I’m sure it can be fixed, I’ve just never had to figure it out.

  • @[email protected]
    4•1 year ago

    Imo at this point you’re better off just nuking everything (after you backed up your important files) and reinstalling with the following process:

    • Install windows, with the linux drive removed
    • Plug linux drive back and install ubuntu on it (make sure you select the right drive in the installer) If you do this ubuntu should automatically detect windows. If it doesn’t you should still be able to boot into either one of them using your device’s bios.
    • @[email protected]OP
      -4•1 year ago

      I am going with this game plan, courtesy of ChatGPT 4. It aligns very nicely with my goals and the steps involved also seem to coincide nicely with the suggestions made in this thread. Gives me a path forward, which is really what I need now.

      1. Backup Personal Files:

        • Access your Linux partition (A:).
        • Mount the Windows SSD (C:) and HDD (F:) within Linux.
        • Carefully check for any personal files on C: and copy them to F:. Verify that all important data is on F:.

      2. Create a Full Backup of F:

        • Connect an external storage device with sufficient space.
        • Create a full backup of your HDD (F:) to this external device. This is crucial to prevent data loss.

      3. Verify Backup Integrity:

        • Ensure that the backup on the external storage is complete and the files are accessible.

      4. Prepare for OS Installation:

        • Download the latest Linux Cinnamon 23.10 ISO.
        • Create a bootable USB drive with this ISO using a tool like Rufus or Etcher.

      5. Remove HDD:

        • Power down your PC.
        • Physically remove the HDD (F:) to ensure it remains untouched during the OS installation.

      6. Boot from Linux USB Drive:

        • Insert the bootable Linux USB drive.
        • Access BIOS/UEFI and set the USB drive as the primary boot device.

      7. Install Linux Cinnamon on SSD:

        • Proceed with the Linux installation on the SSD (formerly C:).
        • During installation, select the option to format and use the entire SSD. This will erase Windows 10 and all data on it.

      8. Post-Installation Checks:

        • After installation, boot into Linux Cinnamon.
        • Check that all hardware components are recognized and functioning.

      9. Reinstall HDD:

        • Power down your PC.
        • Reinstall the HDD (F:).

      10. Mount and Access HDD in Linux:

        • Boot into Linux.
        • Mount the HDD (F:). You may need to install additional drivers or file system utilities depending on its format.

      11. Data Restoration or Access:

        • If required, restore the personal files from the external backup to HDD (F:).
        • Alternatively, if the HDD is accessible without issues, use it as is for storage.

      12. Install Necessary Software:

        • Install any Linux-compatible software that you need.

      13. Final System Checks:

        • Ensure everything is working as expected.
        • Make any necessary adjustments in system settings, drivers, or configurations.

      14. Create a New System Backup:

        • Once everything is set up, consider creating a new system image backup.
      • @[email protected]
        1•11 months ago

        You might not want to trust chatgpt with anything where accuracy and specificity are both essential to not brick a machine or lose data though. Especially since you can’t check the sources it used. It did a decent job at getting the general workflow right, but even that’s not a given. :/

  • @the_q
    4•10 months ago

    deleted by creator

  • @dis_honestfamiliar
    4•1 year ago

    It sounds like you have Windows in one disk and Ubuntu in another disk. Confirm this before proceeding.

    Now if that’s true, and what you said about dedicated windows ssd on a boot loop, it sounds like MRB needs fixing. I suggest you make yourself a windows 10 USB disk or disc. Run that and when it asks to install, you look for recovery. And try to run the fix boot and recover MRB.

    Something like these 2 commands

    Bootrec /fixboot

    Bootrec /fixmrb

    commands

    • @[email protected]OP
      2•1 year ago

      You are correct. Thank you for giving some options for processing on this path. I’m still deciding whether I want to continue trying the dual boot route, figuring out how to get VMX running, or just maining Linux and dealing with the learning curve. I do feel that my end plan, however long that would be, is to be using Linux as my primary OS anyway and there’s no time like the present, but for all I know after sleeping on it I may decide that I still want a functional Windows in my laptop.

  • @[email protected]
    3•1 year ago

    What was your starting point? Having Windows on the machine already and installing Ubuntu on top of it? (that would be commonly regarded as the ‘correct’ order) If not, and you can afford to scrap everything, that’s what I’d go for. If yes, and it’s Ubuntu that’s messing up your dual boot, I’d see if Windows can be restored after removing Ubuntu, and then try a different distro (I’d go with Mint Cinnamon, it normally provides smooth install experience).

    • @[email protected]OP
      2•1 year ago

      I’m considering other options though I’ve enough Ubuntu so far. Fedora also looks nice. I’m a complete GNU/Linux novice but I can generally work around technical sides of programs relatively fine. I’m not sure why this issue is kicking my ass so much lol

  • @just_another_person
    1•1 year ago

    You have an EFI bootloader, so your BIOS should be able to detect your Windows partition and just boot it off it’s still in good working order. Go into your BIOS boot menu and see if you can boot to Windows from there as a first test.

  • Kalcifer
    1•1 year ago

    I don’t fully understand how you are going about your installation. Are you attempting to install Windows 10, and Ubuntu onto different partitions on one drive, or each on a separate drive? Are you wanting to use grub to boot the OS of choice, or to choose the boot device from the BIOS boot device menu? In what order did you initially install the OS’s (Windows 10 first, then Ubuntu, or vice-versa)?

    • @[email protected]OP
      1•1 year ago

      Dedicated SSD (C:) has Windows on it.

      Internal HDD has F: (storage) and a partition for Ubuntu, which is the A: drive in Windows and /dev/sda3 in Linux.

      I was originally hoping to do it this way and be able to dual boot them, but the more I think about it the more I feel that just going straight to Linux and biting the bullet would be better in the long run, and I can flash Windows if I really need it.

      I was trying to get GRUB to act as boot loader but for the longest time I couldn’t even get GRUB running, even with at least 5 different troubleshooting ideas. Then once it was running, I still couldn’t get it to mount the EFI. Then I started getting the boot loop issues and Windows OS stopped working, but I figured out how to get Linux desktop running via shimx64.efi in the BIOS boot loader.

      This computer is natively a Win 10 machine, and I was trying to add Linux to it.

      • Kalcifer
        1•1 year ago

        I encourage you to read through this Archwiki page on dualbooting – it has a lot of very helpful information on the topic.

        I was originally hoping to do it this way and be able to dual boot them, but the more I think about it the more I feel that just going straight to Linux and biting the bullet would be better in the long run, and I can flash Windows if I really need it.

        It is certainly possible to dual boot (in my experience, with the occasional headache that you may, or may not be willing to deal with) Windows and Linux, but yes, the most reliable installation would be one, or the other.

        I was trying to get GRUB to act as boot loader but for the longest time I couldn’t even get GRUB running, even with at least 5 different troubleshooting ideas

        Hrm, I’m not sure how you are going about your installation procedure. You mentioned that you are installing Ubuntu, but Ubuntu should come with Grub pre packaged. Installing Ubuntu really only requires clicking a couple buttons in the install wizard.

        but I figured out how to get Linux desktop running via shimx64.efi in the BIOS boot loader.

        Im not really familiar with shim, but, from what I understand, it’s the loader for when you have secure boot enabled, but you should have that disabled.

        • @[email protected]OP
          1•1 year ago

          Hrm, I’m not sure how you are going about your installation procedure. You mentioned that you are installing Ubuntu, but Ubuntu should come with Grub pre packaged. Installing Ubuntu really only requires clicking a couple buttons in the install wizard.

          I had Linux installed on a tertiary partition of a secondary drive, my F: drive. I neglected to store it within the dedicated SSD, C:, and I believe that GRUB was just not being picked up because instead of being sda or something close to it, it was instead sda6.

          Further this with the fact that GRUB seemed to not have elevated permissions and when I eventually got into its command line, it was not able to run Linux for reasons I’m unaware. Windows BIOS menu never had Linux or any corollary term available as a boot order item, and only through digging through the Boot from EFI item and submenus was I able to find anything to actually boot Ubuntu without live CD at all. grubx.efi (or whatever it was called) black screened.

          Im not really familiar with shim, but, from what I understand, it’s the loader for when you have secure boot enabled, but you should have that disabled.

          Scout’s honor, I really did disable Secure Boot. I did so through Shell. I did so in the Windows directory. I even triple checked that it was disabled through the BIOS menu. If shimx64.efi is only supposed to work when Secure Boot is disabled, that must be because Windows has just been acting screwy as all get out.

          • Kalcifer
            1•11 months ago

            I had Linux installed on a tertiary partition of a secondary drive, my F: drive. I neglected to store it within the dedicated SSD, C:, and I believe that GRUB was just not being picked up because instead of being sda or something close to it, it was instead sda6.

            First of all sda refers to a physical drive, whereas sda6 refers to a partition on that drive. As for the rest of it, I’m not exactly sure what you are talking about – it doesn’t really matter where in your system Linux is installed; the bootloader probes for an OS, and, once found, will update its table with the position of the OS on the drive.

            Further this with the fact that GRUB seemed to not have elevated permissions

            This statement doesn’t really make sense; Grub runs independently of Linux (it even loads before initramfs), so the concept of “execution privelege” doesn’t apply. (source)

            when I eventually got into its command line, it was not able to run Linux for reasons I’m unaware.

            I will point you to this answer, if you wish to boot linux from the Grub command line.

            Windows BIOS

            There’s no such thing (well, as far as I’m aware, anyways – maybe a microsoft surface, or the like, labels it as such 😜). The BIOS is contained within a physical chip on the device’s motherboard.

            Windows BIOS menu never had Linux or any corollary term available as a boot order item

            If you’re talking abou the boot menu, it doesn’t necessarily have to list the linux distro. If you know what drive it is installed on, you select that, then the BIOS finds the bootloader from there. A boot device is just that – a device to boot from, not an OS to boot into.

            I really did disable Secure Boot. I did so through Shell.

            I don’t understand what you mean here. As far as I’m aware, secure boot is only able to be disabled within the BIOS.

            I was unsure if maybe there was some alternative command line trickery that exists to modify it that I am unaware of, but a quick websearch seems to corroborate my pre existing belief.

            Windows has just been acting screwy as all get out.

            This is an unfortunate reality of dual booting with Windows. Windows can do all sorts of trickery on your system (even when the system is powered down!). If I want to boot Windows (I keep it installed on a separate, dedicated, and air-gapped drive), I plug in its drive, and disconnect all other drives related to Linux. This has been the most reliable method that I have found to dual boot Windows. However, this method is still not without possible issue, as Windows can still leave devices in weird states that end up messing with how they are used in Linux.

            • @[email protected]OP
              1•11 months ago

              Thank you for the breakdown. I’ve learned a fair bit about the infrastructure of my computer and Linux since posting this, and I’m now dedicated Ubuntu with only needing to do some very minor work with WINE here and there in the last two weeks or so. Linux has been a blast and learning about everything has been a lot of fun so far.

              My problem turned out to be something with the BIOS. I don’t know if a switch got flipped somewhere along the way or what, but when I reset the BIOS to factory default settings in the boot menu I no longer had issues with boot looping and a CPU I could fry an egg on.

              I do believe that GRUB was initially installed on sda2 and not sda, and Windows was just taking precidence over grubx64.efi upon startup. Now that I’ve scrubbed windows from my PC I no longer have any issues booting up and my PC seems to run just about the same as before, less a few graphical funnies with some larger proprietary software I use.

              Funny enough, I tried to do a clean install of Debian with KDE on my system and I went back to having boot issues, mainly where it would just open to GRUB CL and I couldn’t get it to initialize Debian, when I was certain it was a good install. So I’m just going to stick to Ubuntu for a good while and learn it. Once I feel very confident in filesystem maintenance, command line navigation, snap/flatpak/.deb/whatever, all the major things, I’ll start shopping around for another distro again. Ubuntu has been treating me very nicely though.

              • Kalcifer
                1•11 months ago

                Thank you for the breakdown.

                You are very welcome! 😊

                I’m now dedicated Ubuntu

                A very fair decision! Dual booting can be a huge pain, and, for the average user, it really isn’t all that necessary anymore – Linux has come a very long way!

                My problem turned out to be something with the BIOS. I don’t know if a switch got flipped somewhere along the way or what, but when I reset the BIOS to factory default settings in the boot menu I no longer had issues with boot looping and a CPU I could fry an egg on.

                Interesting. I’m curious what the setting was. But, I’m glad that it worked out for you in the end!

                I do believe that GRUB was initially installed on sda2 and not sda

                I refer back to my previous comment – sda2 refers to a partition on the drive named sda. You could have a drive sda, sdb, sdc, etc. If one was given some partition sdc3 that means it is partition 3 on drive sdc. Everything gets installed into a partition on a drive.

                Windows was just taking precidence over grubx64.efi upon startup

                This can certainly happen – especially if Windows is installed after Linux. I woud refer you to this answer to fix it.

                less a few graphical funnies with some larger proprietary software I use.

                Yeah, I’m not too surprised about that (depending on the speicfic graphical issues that you are referring to, mind you) – especially if you are using Wine. If you don’t mind me asking, what software are you wanting/needing to use?

                Funny enough, I tried to do a clean install of Debian with KDE on my system and I went back to having boot issues, mainly where it would just open to GRUB CL and I couldn’t get it to initialize Debian, when I was certain it was a good install.

                Hm, this is strange. I would err on the side of a layer 8 error, but there could certainly be some other fuckery afoot.

                So I’m just going to stick to Ubuntu for a good while and learn it.

                There’s no problem with that! Ubuntu was the first distro that I used, as well, when I first got into Linux. Granted, I didn’t stick with Ubuntu for long, cause I got mildly annoyed with how it worked.

                Once I feel very confident in filesystem maintenance, command line navigation, snap/flatpak/.deb/whatever, all the major things, I’ll start shopping around for another distro again.

                Sounds like a solid plan! When you do decide to move on from Ubuntu, I’d recommend Arch LInux 😜

                • @[email protected]OP
                  1•11 months ago

                  I refer back to my previous comment

                  Yes, I am aware of how the partition naming structure works, to a degree. I am going off the fact that when I installed Ubuntu, it was installed on a partition (sda2) rather than a primary drive (sda). I’ve read that when GRUB is installed, if it gets installed to /dev/sda2 rather than /dev/sda it can cause issues with dual booting as the BIOS will read in a sequential order, and it may miss a partition if it’s “far enough down the list”. As another example, you may be in for some trouble if grubx.efi is installed on /dev/sda8 or something.

                  Everything gets installed into a partition on a drive.

                  I guess I must have gotten my preconceptions wrong, or perhaps I misread something. From my impression, certain things can be installed on the primary drive such as boot loaders, but I could be wrong.

                  If you don’t mind me asking, what software are you wanting/needing to use?

                  Finale 2012c is the main software I needed. And by funnies I mostly just mean that it’s slow to update graphics, but the program works entirely as intended. MIDI drivers work, sound libraries (Garritan and ARIA Player) function, print to PDF is fine, I’m actually incredibly impressed! I’m using WINE 8.0.1.

                  I also wouldn’t mind trying to get Cakewalk running, as my workflow is definitely more attuned to that software, but maybe trying to get all the proprietary drivers (e.g. TASCAM’s interface drivers) to work with Linux may be more headache than its worth.

                  Arch

                  I’ve heard it can be pretty challenging to get into Arch, is this true? I don’t know if I’ll ever be a “script kiddie” as it were. I plan on getting good at using bash and learning the other ones like ssh, but I don’t know how much I like the idea of having to hand-craft my OS from bare metal.