this post was submitted on 06 Apr 2024
790 points (96.4% liked)
Technology
59687 readers
4089 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Simply renaming the executable works to re-enable Start All Back. They are being intentionally blocked by Microsoft.
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.
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.
sounds like a 21st century version of quack3.exe.
Reference: https://techreport.com/review/how-atis-drivers-optimize-quake-iii/
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