3 ms·
This has to be trivially solvable in a backwards-compatible manner (at least if the library at fault is one of windows' own which they update with windows updat
by alkonaut 11y ago
This has to be trivially solvable in a backwards-compatible manner (at least if the library at fault is one of windows' own which they update with windows update). Win 8.1 is an OS they actively update.
So why isn't this just fixed in the next update?
It would be one thing if they had to research the problem, and presented a workaround in the meantime. But they appear to have found the cause! To me it seems it would take ten times longer to find this bug, than to fix it. Once they spent the effort to find it, why not patch it?
- MichaelBurge 11y agoThey still need to write up the article, and it looks like they write the articles assuming you won't upgrade.
- forgotmypassw 11y agoProbably because sysadmins aren't willing to push updates to their Windows machines because they tend to change system settings nowadays.
- lagadu 11y agoThis sounds like there's a functionality that depends on usernames having "user" in their name. Maybe there's no trivial way of distinguishing between what the system is looking for and a "legitimate" user and fixing that would require a change to the user accounts model. I'm purely speculating here but I've seen my fair share of seemingly simple-to-fix bugs requiring huge changes.