My laptop is (maybe was) Linux and Windows 10 dual booted. I was reinstalling
the Linux OS and in the process I accidentally formatted the Windows 10 boot
partition. At least I think it is the boot partition because I don't really
know how Windows works (or doesn't work amirite).
This is the lsblk output:
$ lsblk -f
NAME FSTYPE FSVER LABEL [...] MOUNTPOINTS
nvme1n1 zfs_member 5000 zroot [...]
├─nvme1n1p1 vfat FAT32 [...] /boot/efi
├─nvme1n1p2 swap 1 [...] [SWAP]
└─nvme1n1p3 zfs_member 5000 zroot [...]
nvme0n1
├─nvme0n1p1
└─nvme0n1p2 ntfs
The nvme0n1p1 is the one related to booting. I accidentally formatted it.
I have a Windows 10 USB prepared. I tried looking online and I never found
a question asking exactly for this. The ones I found that were similar enough
suggested different commands.
Anyone has experience with this?
Thanks in advance.
Ok so, a while back my windows did a fucking weird thing where I cloned an OS drive and later on down the road I went to wipe the OLD OS drive after I had been using the new one for months. Well my PC randomly decided to boot from the OLD drive and fucked up the boot on the NEW one. To this day my best IT friend that has seen just about everything, has no idea what happened because wid ows is just fucking stupid sometimes.
So anyway, I got this program Macrum Reflect and went through a tutorial of making a recovery media. I did that AFTER an official windows recovery media failed.
The Macrum Reflect recovery media fixed the boot in, not shitting you, less than 5 seconds after I ran it. I'd say it took it less than 2 seconds really. I clicked run and it was done. It was so fast I initially thought it just didn't work.
My PC booted right up using the new drive and have zero problems.
So yeah, maybe try Macrum Reflect recovery media. You'll need a working PC to set it up.
I've been told (but I cannot verify) that windows' default behaviour is to install an EFI partition on every internal drive, and update them all in the event of an update.
I know from experience that windows only expects to see itself installed and will happily fuck up your bootloader with whatever garbage it wants to.
I suspect that these two "characteristics" together are what is to blame here.
To add to this, if you ever have to clone a drive, look up Veeam backup. It's the best backup and cloning software I've ever used. So Macrum and Veeam go on every PC I have now. lol