this post was submitted on 06 Apr 2024
787 points (96.3% liked)
Technology
59207 readers
2520 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
Remember the days when Microsoft would block ClassicShell the same way they did StartAllBack here, on Win10?
Pepperridge farm remembers :V
.... I don't, actually, I've been using ClassicShell basically since the day Win10 came out and it's always worked perfectly. Don't think I've even updated it actually.
Its something happened waaay back during the technical preview days. Just like with this instance, the workaround was to rename the installer executable.
https://winaero.com/microsoft-to-block-classic-shell-in-windows-10-here-is-why/
And I think you should update to OpenShell at least.