this post was submitted on 06 Apr 2024
789 points (96.4% liked)

Technology

59596 readers
4182 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
789
Microsoft is blocking Windows Customization Tools (www.neowin.net)
submitted 7 months ago by quantumcog@lemmy.world to c/technology@lemmy.world
266 comments fedilink hide all child comments
 

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

One more reason to switch to Linux

you are viewing a single comment's thread
view the rest of the comments
[–] kadu@lemmy.world 85 points 7 months ago (1 children)

They're not exactly "being blocked" but rather the legacy ability to tell explorer.exe to load the older style Taskbar, which those apps load then modify, is going away. I'm not defending this nor do I like it, but it would be like saying some Linux distro is BLOCKING customization because some legacy app dependent on Xorg will not work after they switch to Wayland.

[–] BombOmOm@lemmy.world 66 points 7 months ago* (last edited 7 months ago) (3 children)

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 26 points 7 months ago* (last edited 7 months ago) (1 children)

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.

[–] ChunkMcHorkle@lemmy.world -2 points 7 months ago* (last edited 7 months ago) (1 children)

deleted by creator

[–] kadu@lemmy.world 9 points 7 months ago (1 children)

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.

[–] ChunkMcHorkle@lemmy.world -1 points 7 months ago* (last edited 7 months ago)

deleted by creator

[–] A_Random_Idiot@lemmy.world 10 points 7 months ago* (last edited 7 months ago) (1 children)

sounds like a 21st century version of quack3.exe.

[–] ChaoticNeutralCzech@feddit.de 4 points 7 months ago* (last edited 7 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