view the rest of the comments
Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
Microsoft deliberately fucks with your video and audio drivers before a big update so you have to reboot
This isn't a conspiracy, it is a proven fact.
I’m not one to stick up for Microsoft but uhhhhh fuck no
Does anyone have a source on this? It’s 100% believable but I’m not turning anything up and this seems like something worth knowing more about
I don't disagree, but I'd like some more info and/or sources.
I think it is more that the update fucks with drivers? As in, updates bring updated stuff that probably interferes with still-running old stuff.
If my experience is common, the update 'pre-loads' some non-locked system files as time goes on while the update is downloaded but not technically applied by the tool. So these files get changed without a reboot, and while you may not be using them at the time of overwrite, when you next load them, there are subtle incompatibilities with the previous version and your active data.
Kind of like 'The dll was replaced by the exe is still the old version', and this causes a ton of small but annoying glitches, crashes, and odd audio behavior.
Untill reboot, which happens less and less often now that windows doesn't bluescreen every few hours.
My conspiracy is that they are aware of it, and do not change it despite the risks it provides, to keep everyone in line with their update schedule, denying the user the rights to control their own hardware, again.
To be fair, the very same thing happens with Linux, when you install updates but don't restart services (or, god forbid, the whole system). Really weird tiny issues accumulate until I am fed up and hit reboot.