TLDR: StartAllBack, ExplorerPatcher and some other projects are being blocked on 24H2.

One more reason to switch to Linux

  • BombOmOm@lemmy.world
    link
    fedilink
    English
    arrow-up
    75
    arrow-down
    9
    ·
    edit-2
    9 months ago

    They’re not exactly “being blocked”

    Simply renaming the executable works to re-enable Start All Back. They are being intentionally blocked by Microsoft.

    Like in the case of StartAllBack, you can bypass the block by simply renaming the executable to something else. If you want to upgrade to a newer build, delete the app, update your system, and then launch it using a renamed executable.

    • kadu@lemmy.world
      link
      fedilink
      English
      arrow-up
      31
      arrow-down
      5
      ·
      edit-2
      9 months ago

      Not if you’re using the preview build, where the entire functionality is removed. The warning is just a preemptive preparation for beta users. The bottom of the article indirectly mentions this.

      But sure, downvote me.

        • kadu@lemmy.world
          link
          fedilink
          English
          arrow-up
          10
          arrow-down
          1
          ·
          9 months ago

          The article is actually incomplete. Some insider builds already lack the old taskbar, it can’t be invoked and if an application relies on it you simply get a crash.

          This is not new behavior from Windows. When legacy features are going to be removed, they do stagger updates when users have known software conflicts installed, they also might throw warnings. This is exactly what we are seeing now.

          Though the fact this small article is just reporting on Reddit information rather than testing insider builds is not my fault nor my concern.

    • ChaoticNeutralCzech@feddit.de
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      9 months ago

      They are, to the best of Microsoft security professionals’ abilities

      Just kidding, the devs are probably using ExplorerPatcher themselves and are sabotaging this asshole move