Garuda renamed my hard drive in UEFI after install and now can't boot it

I don’t have a clue about anything

Everything I learned about partitions, partition-tables, BIOS, NVRAM, boot menus, boot loaders, and so on - I’ve learned in the past 2 weeks. So I’m sure that there is something I’m wrong about, but just telling me to read the Wiki doesn’t help - I’ve read about all this stuff countless times already and tried many things in an attempt to resolve my problem. Do be more specific.

To me it does stand to reason that the entries in the NVRAM act as instructions for the UEFI as to how to boot drives, else why are they there.
And that since the entry pertaining to my HDD is now missing, I’m not able to boot into it at all.

I guess this wouldn’t even be a Garuda specific problem. Were it not for the fact that before I first attempted to install Garuda, I was able to select my HDD in the UEFI menu and boot into it. And, now I’m not.
Washing your hands of the affair and saying ‘you’re on your own bro, Windows 7 is ancient’ is fine, I’m not paying anyone for technical support here, but at least in the interest of Garuda itself, which bills itself as something of an Arch for the masses - someone should probably look into this whole thing. And maybe add an option to the Boot recovery utility that’s already accessible from the Live USB, to like remove the Garuda-entered NVRAM entry and restore a default one that instructs the UEFI to just read the MBR (if it’s detected that the disk itself is formatted as MBR), or something.