What September’s patching frenzy lacked in fireworks, it greater than compensated for in quantity – and belligerence. Server 2016 hiccups on Safety Choices. Win10 model 2004 surprises – Lenovo nonetheless hasn’t mounted its Blue Display screen-inducing Biometric Safety setting; the TRIM perform nonetheless tries to trim spinning exhausting disks; for some, Begin goes wonky, Motion Middle disappears, and there’s the same old litany of strange, one-off bug experiences.
As of early at the moment, we’re nonetheless ready for the Win10 model 2004 “non-compulsory, non-security, C/D/E Week” patch, however the entire different anticipated September patches are in.
Defrag woes in Win10 model 2004 largely mounted, however TRIM nonetheless nips
As I’ve talked about many instances, Home windows 10 model 2004 shipped with a bug that causes the Home windows Optimizer Drives defrag instrument to skip updating the completion date on defrag runs. Consequently, defrags happen way more ceaselessly than crucial. Microsoft has recognized concerning the bug since January – months earlier than 2004 shipped — however didn’t hassle to acknowledge it till a repair appeared this month.
This month’s repair, within the September cumulative replace for Win10 model 2004, doesn’t repair one other defrag bug. The still-outstanding bug has Home windows run the TRIM perform on exhausting disks. (TRIM ought to solely be run on SSDs.) Once more, Microsoft has recognized concerning the bug for a lot of months. Once more, it hasn’t been formally acknowledged.
Home windows Server 2016 throws an MMC error
After you put in the September cumulative replace on Server 2016, KB 4577015, navigating the Group Coverage Editor to Pc Configuration > Home windows Setting > Safety Settings > Native Coverage > Safety Choices throws the wsecedit.dll error proven within the screenshot under.
Microsoft lists the bug in its Home windows Launch Info Standing web page as “Mitigated,” however the one repair I’ve seen (aside from coming in by means of a distant again door) is on Günter Born’s Tech and Home windows World web page.
Lenovo ThinkPads get the Biometric Safety blues
Microsoft nonetheless hasn’t mounted the bug that triggers a blue display on Win10 model 2004 Lenovo computer systems (and presumably another manufacturers) which have Enhanced Home windows Biometric Safety enabled within the UEFI. That bug appeared within the July “non-compulsory, non-security, C/D/E Week replace” and continued in each the August and September cumulative updates. As Microsoft explains it:
The system experiences a Cease error (also referred to as a bugcheck or blue display error). The codes which might be related to the error are “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” (within the Cease error message display) and “0xc0000005 Entry Denied” (in reminiscence dumps recordsdata and different logs). The related course of is ldiagio.sys.
Lenovo has printed a workaround – directions for disabling Home windows Biometric Safety.
As soon as once more, Microsoft hasn’t written concerning the bug within the Home windows Launch Info Standing web page, nor has it talked about the issue within the related Data Base articles. It’s clear that the Lenovo firmware is at fault, however there’s been no repair in virtually three months.
Home windows Subsystem for Linux 2 in Win10 model 2004 broke
For all two of you who really use Linux below Win10, there’s a tough bug that throws an “Ingredient not discovered” error. I talked about it shortly after the September cumulative replace appeared.
Microsoft mounted the issue within the newest non-security patch for Win10 model 20H2 – that’s the following model of Home windows, as a consequence of be launched any day now. Nevertheless it hasn’t been mounted for model 2004. I count on we’ll see a repair within the anticipated “non-compulsory, non-security, C/D/E Week” patch for model 2004, which might arrive within the subsequent week. Or two.
Blue screens, Begin funnies, Motion Middle woes in Win10 model 2004
I don’t need you to assume that I’m selecting on model 2004, however there are much more experiences of strange conduct in 2004 after putting in the September cumulative replace, KB 4571756. Mayank Parmar at Home windows Newest offers the small print:
Efficiency points, Begin Menu crashes, sign-in points, non permanent consumer profile bug, Blue Display screen of Dying, and a raft of different minor bugs.
In abstract, Win10 model 2004 continues to obtain an infinite variety of bug fixes each month. Only a few – virtually none – of the bugs are listed on the official Launch Info Standing web page. Even bugs which were reported extensively on Microsoft’s Solutions Discussion board, and within the Suggestions Discussion board – even bugs which were round for months – don’t appear to warrant inclusion on Microsoft’s official bug checklist.
In case you assume Win10 model 2004 is prepared for prime time, I've some severe examine materials for you.
However 2004 is rolling out, even the place it’s not needed
Each time we get a brand new model of Home windows, I hear complaints from individuals who get their machines pushed onto the brand new model, despite the fact that they don’t need it – despite the fact that they actively block the improve, and swear they didn’t click on something to permit the brand new bits onto their machine.
More often than not, there’s sufficient shadow-of-a-doubt to dismiss the undesirable upgrades as consumer error.
This time, although, Patch Woman Susan Bradley has a machine that acquired bit – pushed from model 1909 to model 2004 with out permission – and she or he is aware of Home windows Replace higher than anyone. “I didn’t click on to approve to put in this.”
Did you get pushed? Underneath what circumstances? Be a part of the dialogue.
This month additionally noticed an Outlook 365 bug, launched with the most recent updates: Altering a contact threw a “Your adjustments can't be saved” error. Microsoft mounted that one just a few days after it appeared.
Patching issues? Hit us on AskWoody.com.