Recently I had a hiccup with my main SSD drive. I have a dual boot Win/Kubuntu setup. Linux was crashing hard and Windows was giving me blue screens. After I resolved the issue (cooling/loose connection, idk) my Linux was doing fine, but Windows was giving me blue screens. I think it was doing an update when it crashed.

After a couple of hours messing with my recovery USB and booting in safe mode, I was able to fix the bad update and reboot normally.

I tried to open Firefox and it couldn’t find the executable. Looking into the Program Files Mozilla folder, I found the .exe files had been renamed to .exe.sig???

Then looking for the Edge browser, I suddenly found out that Microsoft Copilot AI had been installed!?!?!?!?!?!?

What the actual fuck???

I never wanted that trash on my PC! That’s one of the reasons out of the many that I didn’t want to use Windows 11.

And it’s a weird fucking coincidence that Firefox was fucked. I couldn’t even rename the files to .exe because they wouldn’t execute. Looks like they were encrypted or some shit? What the fuck is Microsoft pulling?

It’s a happy coincidence because you know what? I’ve been thinking about going full Linux install since all my games and Windows applications work with Steam, Proton and Bottles now.

I really don’t see any fucking reason to keep using Windows. Fuck this shit and fuck Microsoft.

Edit: Oh and that’s on top of all the other bullshit like forcing users to create a MS account to install Windows 10 now and having to jump through hoops to have an offline installation. And also defaulting to having all your user folder documents into their fucking One Drive cloud.

I’m done.

  • refalo@programming.dev
    9·
    4 months ago

    system files getting corrupted under linux is way harder to fix than on windows… most distros do not even have a tool to check for integrity/existance of all the necessary base system package files.

    • UnityDevice@startrek.website
      7·
      4 months ago

      Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.

      Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.

    • Cyborganism@lemmy.caOP
      6·
      4 months ago

      As long as your home directory is intact, you can simply reinstall. You can also easily reinstall individual modules and overwrite bad file. There’s so many ways you can fix a Linux installation.

    • Rob Bos@lemmy.ca
      4·
      4 months ago

      Most package managers store md5sums. A few times I’ve used that to validate package binaries. I’m not sure what tool you’d use for it, since I always just whip up a bash one-liner for it.