SSD wiped itself

Meaning that EFI partition shouldn't be available, it also shouldn't be assigned a letter.
Did you or anyone else assign a letter to this partition?

axe0 said:

Meaning that EFI partition shouldn't be available, it also shouldn't be assigned a letter.
Did you or anyone else assign a letter to this partition?

In your opinion, what would happen if the disk was originally GPT and was converted to MBR?
Would that explain what we are seeing here:
SSD wiped itself - Page 3 - - Windows 10 Forums

This is a fairly new, recent laptop (Gen 7 processor) so I'd bet money it was originally GPT when he got it.

What do you think would happen if he converted back to GPT?
Do you think Startup Repair would work then?

Converting from GPT to MBR is possible without too much issue (except for risk of data loss), but I don't know what could happen when attempting to convert with this kind of partitioning.

Startup repair won't work, because the partitioning is messed up. It doesn't know what to repair. Conversion probably won't help.

Likely is no partition marked as active, or not the right one, what makes that the OS doesn't know what to do from the beginning to start the boot process after the BIOS.

The easiest solution would be to backup anything that you wouldn't want to loose, then wipe the drive completely from installation media and install Windows after wiping the drive. Of course, make sure that you're booting UEFI.

IMHO, I don't think it would be worth it to go through all the trouble attempting to recover the system to a proper bootable partitioning (except if a partitioning guru provides assistance). The risk of something going wrong while trying to recover is quite high.

I agree with Axe0. There is too much weirdness going on to justify the time trying to sort it all out.

Suggest you backup all your user files and clean install Windows 10 in UEFI mode.

@axe0

Replace o with 0 (zero)

It would be easier to reinstall your drivers too, finding them would be a lot of work.

It's no bother, it's just that one mentions an inactive user when using the o

It could work, but it would be a lot of work to search for the right files and to verify that you indeed have the right onces.
Searching in the drivers folder in system32 for 'company:microsoft' there are 334 .sys files by Microsoft on my system, less than a 100 by hardware/software. However, you also need any other file that is being used by the devices shown in device manager. An example, NVIDIA drivers, using over 50+ other files (dll's, executables, bins) located at different places.
Device drivers (both software and hardware) aren't just .sys files, it is a package of files.