KB5077181 was released about a month ago as part of the February Patch Tuesday rollout. When the update first arrived, users reported a wide range of problems, including boot loops, login errors, and installation issues.

Microsoft has now acknowledged another problem linked to the same update. Some affected users see the message “C:\ is not accessible – Access denied” when trying to open the system drive.

  • AeonFelis@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    46 minutes ago

    You don’t need C:\. All your data should be in the 365 cloud anyway. Storing files locally in C:\ leads to antipatterns like not paying Microsoft for 365 access (a.k.a “Software Piracy”)

  • kreskin@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    2 hours ago

    Security to some level is important, but whatever idiot at msft sold exec on “user access control” as a standard service really effed windows hard. Security types have a role in the world, but a lot of them are authoritarian idiots. One of those idiots wrote this patch, and msft was so used to UAC problems in everything, they just let it on through during testing.

  • thethunderwolf@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    4 hours ago

    Solution: install linux

    Just like I have been calling macOS “NonfreeBSD” I will now be calling Windows 11 “Slop_OS”

  • Meeech@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    7 hours ago

    Hmm… I should start updating my work computer since the “IT” got upgraded my pc to 11 to fix a problem that wasn’t fixed with the upgraded.

  • fne8w2ah@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    8 hours ago

    This should be yet another opportunity for Windows refugees to come to the Kingdom of Torvalds.

  • mkhopper@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    7
    ·
    9 hours ago

    Ugh… I’m so tired of “microslop” and “AI slop”.

    I’m not defending Microsoft in any way, but they were releasing buggy updates long before the rise of AI.

    • Buddahriffic@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 hours ago

      You know what’s going on inside the large companies that are hoping to cash in on the AI thing? All workers are being pushed to use AI and goals are set that targets x% of all code written be AI-generated.

      And AI agents are deceptively bad at what they do. They are like the djinn: they will grant the word of your request but not the spirit. Eg they love to use helper functions but won’t necessarily reuse helper functions instead of writing new copies each time it needs one.

      Here’s a test that will show that, with all the fancy advancements they’ve made, they are still just advanced text predictors: pick a task and have an AI start that task and then develop it over several prompts, test and debug it (debug via LLM still). Now ask the LLM to analyse the code it just generated. It will have a lot of notes.

      An entity using intelligence would use the same approach to write the code as it does to analyze it. Not so for an LLM, which is just predicting tokens with a giant context window. There is no thought pattern behind it, even when it predicts a “thinking process” before it can act. It just fits your prompt into the best fit out of all the public git depots it was trained on, from commit notes and diffs, bug reports and discussions, stack exchange exchanges, and the like, which I’d argue is all biased towards amateur and beginner programming rather than expert-level. Plus it includes other AI-generated code now.

      So yeah, MS did introduce bugs in the past, even some pretty big ones (it was my original reason for holding back on updates, at least until the enshitification really kicked in), but now they are pushing what is pretty much a subtle bug generator on the whole company so it’s going to get worse, but admitting it has fundamental problems will pop the AI bubble, so instead they keep trying to fix it with bandaids in the hopes that it’ll run out of problems before people decide to stop feeding it money (which still isn’t enough, but at least there is revenue).

    • stoly@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      It’s because they got rid of testing and quality control. They are only doing minimal testing now in controlled environments while the world is messy.

    • Cyberwolf@feddit.org
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      7 hours ago

      It’s hilarious that the issues people think Linux has, like for example the disk deleting itself, are exactly what happens on Windows lol.

  • rodneylives@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    16 hours ago

    There was a story going around back in September ago about the person whose wife used OneDrive on her phone. It had taken upon itself to copy 25+GB of data on the phone into OneDrive, despite only having the free account tier, and copying it to their Windows 11 PC. There it completely filled up its small SSD boot drive, putting it into a condition of extremely low disk space, which in made it impossible for Windows to boot. Here it is.