I tried to configure a dual operating system setup with Windows 11 and Chrome OS, but encountered an issue.
I tried to configure a dual operating system setup with Windows 11 and Chrome OS, but encountered an issue.
Soooo... I purchased an Asus Vivobook running Windows 11 Pro, with 40GB RAM and a 1TB NVMe SSD.
I recently came across instructions on installing Chrome OS onto a partitioned section of the SSD, which created a second drive letter for that operating system. Everything seemed to work fine at first.
Then I followed the steps to install Grub2Win, and everything proceeded smoothly. After rebooting, I expected to see a Grub Menu, but it didn’t appear—nothing happened. The computer just kept booting into Windows as usual.
As I investigated further, trying to figure out if something was wrong or if there had been an error, I finally accessed the BIOS screen and discovered where my system was set up on and the EFI boot path.
After making some adjustments and saving changes to set EFI Grub2Win as the menu, I finally accessed it. However, when I selected "Brunch," which was supposed to take me to the Chrome OS partition, nothing happened. The system would then restart back to the Grub2Win menu, but never reach the path for booting into ChromeOS.
This has led me to several questions:
If I wanted to undo all changes before installing WSL commands, creating the second partition, and setting up the Grub2Win menu, what should I do next?
At the moment, I managed to remove Grub2Win using the "bootrec /fixmbr" command.
But I still have the Chrome OS partition running with Chrome installed. Should I delete or format that partition?
How would I remove the Ubuntu features?
Or... is there a way to restart my process? Because when I try to do so, the system says all files exist and won’t even overwrite anything.
I’d like to be able to dual boot Windows 11 and Chrome OS, but I’m not sure if the steps I followed might have missed something important.
Any advice or suggestions would be greatly appreciated. Thanks.
Visit the internet and look for comparable tutorials and "how-to" guides.
Compare various approaches and settings.
The aim is to identify potential mistakes in omission or execution.
For example, overlooked steps, wrong routes, errors, etc.
Expand the search to include dual-boot configurations.
I hope only minor adjustments led to the issues.
Be cautious of sites offering utilities or software that modify settings, or those that suggest registry changes.
I researched various guides and discovered they all followed a consistent route. I tried another installation after a different procedure, but I'm encountering the same issue. My EFI seems to hang when booting. Grub2Win adds the entry, yet setting it as priority boot doesn't get me to the menu, and manually entering an entry by linking to the EFI file still doesn't work—I end up booting but never reach the ChromeOS drive. Any advice? Also, I'm using the BRYA Image with the latest Brunch update.
The link I used this time is:
https://shakeuptech.com/dual-boot-chrome...ows-10-11/
I'm sure I'm handling the steps correctly, but the problem must lie in my EFI Boot settings within BIOS—fast boot is disabled and security is off. I'm at a loss.
Thanks in advance.
Check if this tool works. No prior experience.
Watch: https://www.youtube.com/watch?v=BeXfHvZZnrU
I've faced many issues with Windows and Linux boot managers, so I mostly rely on VM now. I suspect the hacked Chrome OS won't run in a VM, which might mean a better solution is using a fast USB drive or an eternal NVMe SSD inside a USB 3.x enclosure.
I've tried Grub, Win2grub, reFIND, but none worked. Now installing multiple Windows versions on one drive is consistently failing.
This task was quite effective, helping me clean up my bootloaders. I also followed another method to reinstall ChromeOS using Brya image, and discovered a crucial step. The latest guide recommended setting up a Brunch folder on the ChromeOS partition and storing those files there. Now the grub2win Brunch section will recognize that folder in the same partition. Everything is functioning properly now.
Hey everyone... I've been assisting you so far, but I still have a confusing issue. My ChromeOS drive, which I partitioned with the Brya Image, is labeled as 64 gigabytes. After installing and setting up the operating system, it displays 14 gigabytes in use out of 48 gigabytes available. However, after updating my last three applications, I receive a warning from Chrome that my drive space is low and urgent action is needed to free up more storage. Despite having only six apps installed with the OS, I'm unsure how to make the system use the full 48 gigabytes available. Any tips or advice would be really helpful...