- cross-posted to:
- tech_memes@lemmy.world
- cross-posted to:
- tech_memes@lemmy.world
You must log in or register to comment.
Getting ready to go back to Linux, just waiting to get some other stuff out of the way. Taskbar autohide on my Win10 box stopped working this morning. Minor annoyance, I looked it up and found a simple fix - restart the Windows Explorer process. Okay, did that, autohide started working. Bur srsly, the taskbar is almost 30 years old, low-level shit like this SHOULD JUST WORK. Now 12 hours later I just noticed it’s not working again. What the Actual Fuck, guys? Unbelievable.
And for some reason the file Explorer and the Desktop/Taskbar are connected and you can end up with just a black Screen
LOL yeah I wasn’t even gonna get into asking why TF hiding the taskbar has anything to do with Explorer.
chkdsk /scanIf any errors found, stop and /f themThen:
DISM.exe /Online /Cleanup-image /RestorehealthFinally:
sfc /scannowIs that command line stuff? Hard pass for Windows users.
Edit: I guess the Windows users didn’t like that joke
yes, it is. those are pretty much the definitive windows commands to try to fix random stuff like this too, if they fail then it’s reinstall time lmao
Is fixmbr still used?
Sure, but then they shouldnt complain. Stuff break on linux too and when fixing them you also often have to open a terminal. When things are broken, a terminal is often the goto on any system…
Does removing old drivers would affect compatibility for older hardware?
Have you seen old 80’s-90’s style C driver code? Lines of code is an even more terrible metric for this than it usually is.
I think the fact that any old code is being removed at all is a good thing. The point of the post (at least from my perspective) is that deleting old code is something necessary for prolonged support of a codebase and it’s not something Microsoft is or maybe even ever will prioritize.
Fixed m$ brainwashing presentation
I’m sure a lot of people started taking unnecessary code executed at low levels a lot more seriously after the Crowdstrike fiasco.
Well, Windows implemented kernel-level protection to prevent another Crowdstrike situation. lt actually makes kernel-level game anti-cheats to break.
Source? I only see thing about not do that. Maybe plan (unsure?), but not done.
ESET: … It remains imperative that kernel access remains an option for use by cybersecurity products to allow continued innovation and the ability to detect and block future cyberthreats.
another based on above:
One that has been really doing the rounds lately, especially across Reddit and other social media is from Notebookcheck, with a rather sensational article title of “Microsoft paves the way for Linux gaming success with plan that would kill kernel-level anti-cheat”.
Here’s the thing: Microsoft don’tactually say they will kill off kernel-level access, and if they tried that (again - they tried with Vista before), they will no doubt again face some pretty serious push-back from both cybersecurity vendors and regulators across various countries. Something that would likely be more hassle than its actually worth. What Microsoft doactually talk about, is providing additional options that are outside of kernel mode - a whole new platform to “meet the needs of security vendors”.
Source? I doubt they could do that so quickly, plus I haven’t heard of it.
SO.MANY.DEAD.CODES.
