gaqdia.blogg.se

Because all updates are now rolled into a single package, there’s no way for a user who wants the WiFi fix KB 3124200 includes but doesn’t want to risk their Word customizations to install one and not the other.įor all their decades of close cooperation, Microsoft seems to have missed a lesson Intel learned 10 years ago. Because Windows 10 now forces updates by default, the system will continue to download and attempt to apply KB 3124200, even if the update is repeatedly hanging on install or having other problems.

Developers are now expected to do much of the code testing that was previously outsourced to other groups, even if they don’t have much experience in testing code.Ĭombine that shift with the new, mandatory update policies and you get the current situation.

After the layoffs, that ratio is reportedly 1:1. Previously, Microsoft had roughly twice as many QA testers as developers working in the Operating Systems Group. When Satya Nadella took over at Microsoft, one of his changes was to radically overhaul how Microsoft handled QA (Quality Assurance). has compiled a list of problems users have encountered with the latest version of Windows 10, including the Edge browser refusing to close, Explorer, Outlook 2016, and Calculator all refusing to start, and the Windows Store, Calendar, and Maps applications all refusing to run. The problems aren’t limited to wholesale replacement of Word customizations. The problem occurs because the latest update accidentally renames the old file where such information was stored (Normal.dotm) to one of several alternatives: “, NormalPre, NormalPre15, NormalOld, or OldNormal.” That’s a direct quote from Microsoft’s article on resolving the problem, which raises a significant question: Why doesn’t Microsoft, which wrote the patch that broke its own software, know what the backup file name is actually called? It would be one thing if the files had version numbers that corresponded to the user’s Office version, like “”, “”, etc. The problem is serious enough that Microsoft has published its own KB on fixing the issue, KB 3129969. It also reverts any custom spell check options you may have stored. Reports indicate that in at least some cases, KB 3124200 nukes all Microsoft Word customizations, including custom templates, AutoText, macros, envelope addresses, autocorrect, and AutoFormat settings.