this post was submitted on 07 Jul 2024
1183 points (98.9% liked)

linuxmemes

21041 readers
600 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    1183
    Title (lemmy.world)
    submitted 3 months ago by user@lemmy.world to c/linuxmemes@lemmy.world
    101 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] wreckedcarzz@lemmy.world 5 points 3 months ago

    I had to recover a W10 box from a family members work after windows had slowly given itself cancer of file corruption. I've dealt with this shit before and it's not a big deal... usually...

    This fucker took 3 days of babysitting to bring back to life. In-place upgrades, it required multiple (why, no fucking idea), dism, sfc just chipping away bit by bit. And no, this is a work machine, so wipe and start fresh was reserved for actual "cannot be saved" situations. It has a backup plan, and I am the unofficial/unpaid IT guy for that location, but I don't have license keys or installers for the software used (inherited situation), and it would add lots of friction to get running again. Absolutely not jumping on that grenade unless I must, it's untested if a restore causes license validation errors (time checks and other bullshit).

    After that fiasco I applied a universal scheded task of dism followed by sfc, on a monthly basis, and every six months a few automated checks but also I pop my head in for a minute (remotely) just to validate that those automated tasks are running successfully.

    It's been about... 4 years now? And it's been working as-expected. But windows obliterating itself with no user input isn't what I'd call 'a thing of the past'.

    (also it wasn't a hardware fault)