During the startup, you encounter a GRUB interface.
During the startup, you encounter a GRUB interface.
Mount the partition on a live USB and transfer files to another location
Ensure functionality is active. Hidden folders like .sample, .log, and .config are ready.
(sigh) this is still an issue with current Windowses? I though people haven't needed to deal with this kind of S**** since the UEFI booting came along. I only thought windowses overwrote MBRs (and in the very early days of UEFI though they were the only OS in the EFI, but that could have also been buggy/half-***ed UEFI implementations). Anyways, in this kind of situation grub has booted properly but it can not find it's configuration file. There are (at least) two places where it can reside in: in grub's dedicated folder "grub" in the root of EFI (I believe this is a bit non-standard but tolerated by UEFIs), or in the Linux installations dedicated boot partition or (more often these days) the root partition (and no dedicated boot part) So Windowses are (just deleting) the grub folder from the EFI partition?!?? Unacceptable! People should file antitrust lawsuits against Microsoft, and also lawsuits for damaging their H/W (installations) / deleting data without users consent. No OS has anything to do within the EFI partition save their own entries (unless the user specifically uses an application to make changes). TBH there are other reasons grub may not find the config file (for example: many grub installations in EFI, one of them from a previous installation, and their priorities got shuffled for some reason, and the old one is now looking in the wrong place for the configuration). In case it still has found it's file system modules, you may be able to load the configuration file manually. The command line has a kind of tab-completion, so you may be able to figure it out. Try 'ls' and 'configfile (hdX,X)/grub/grub.cfg' (obviously fill in in the X's and the path appropriately for your system with the help of tab-completion and this page ). That way you may once boot into your Linux OS, and if successful, it is then only a matter of manually re-installing grub. EDIT: You can even manually load in a Kernel and boot it, but that is a bit more involved but not hugely difficult process, either. EDIT: You could also check from your BIOS menus if there are many Linux/grub entries in there, and boot a non-default one. This can happen if you have had installed previously some other Linux, or updated a distributions major version but the installation/upgrade failed halfway. If the configuration file for grub exists (and it is a matter of wrong grub instance being set as default), re-adjusting the EFI entries priorities from Linux is quite simple with efibootmgr - or you can also do it from BIOS (actually, this is probably easier). YMMV, re-installation may be easier for you. Edited February 4, 2021 by Wild Penquin minor clarifications, TYPOs... and then some more