cross-posted from: https://discuss.tchncs.de/post/38448230

Source (Furaffinity)

you are viewing a single comment's thread
view the rest of the comments
[–] 29 points 1 year ago (1 child)

If you're lucky, it's still on the disk and you just need to "repair" the bootloader.

If not, well, that traumatised Mr Incredible pastiche might be at least a circle of hell too pleasant.

You have backups, right?

  • source
  • hideshow 2 child comments
  • [–] 20 points 1 year ago (3 children)

    There's no way Windows would just access non-readable partition, and do anything with it, let alone delete it. No operating system does this.

    Replacing the bootloader is of course much more likely, but the general rule is that if you can manage to install Linux, you probably can follow basic instructions to fix GRUB or whatever your bootloader is.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 12 points 1 year ago (1 child)

    There's no way Windows would just access non-readable partition

    I knew that was true back in the day, but I haven't tried dual booting in a long, long time. Also, I wouldn't put it past Microsoft's current incarnation to "accidentally" decide that that "empty" partition would be great for virtual memory and the hibernation image.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 year ago

    Oh Windows knows this is the EFI partition, there is a flag for that. Windows just doesn't care when it decides to nuke your bootloader with its own...

    And yes, it's still happening...

  • source
  • parent