This doesn't work though. I was banned there without as much as a single-line explanation after 10+ years of being a normal rule-abiding user which didn't change even up to that point. Maximum stuff they might not like I did is visiting through a proxy due to my country's circumstances. Right after that I tried appeals daily nearly for a week with no reaction whatsoever. So I just deleted my acc, less value for them is better.
The comments section there says everything about how many people process such questions:
- historical ignorance;
- economical ignorance;
- repeating mass media propaganda narrative word for word;
- hubris.
I do hope europeans will start working as hard and as low-waged as chinese people did last two decades though, so those tech transfers will actually be on point. They lived too comfortably recently, forgetting that you always bear the hidden price for that in some way. No cheaply available products reality _is_ the norm, after all.
AFAIK there are two ways for this, neither of which is convenient to use: install all extensions from the source (you can unpack an existing crx for it or use their clonned repo if it's opensource) or use a group policy to disable extensions autoupdate and update each of them manually when the new version has something you want.
That reminded me of how Windows abuses my HDD by regularly writing dozens of logs I won't ever need unless I'm both knowledgeable enough and debug for specific errors.
And also about WinSxS/Temp/InFlight folder that gets filled with an undeleted garbage of unknown purposes. You can't safely delete files there (with elevated System privileges) even after finishing delayed patching and dism cleanup operations because some of them are still used by the system somehow despite it being a "temp" folder. While thousands of empty subfolders there slow dism/TrustedInstaller runs to a crawl on their enumeration.
More like false advertising and platform abuse, but given that this doesn't incur any loss unless you were actually hired and then dismissed, it's also not really actionable. The best measure here is for job search platforms to curate the whole process and deprioritize the companies caught doing that.
The thing is it was pretty obvious from the update description that something like this will happen. But the update in question is cumulative so even among advanced users that know how to restrict autoupdates many were forced to install it to prevent even more scary exploits for which there are no separate patches.
And now people need to disable Secure Boot entirely to avoid the side effects. Way to improve worldwide security, MSFT.