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-inducing Biometric Safety setting; the TRIM perform nonetheless tries to trim spinning arduous disks; for some, Begin goes wonky, Motion Heart disappears, and there’s the standard litany of wierd, one-off bug experiences.
As of early immediately, we’re nonetheless ready for the Win10 model 2004 “optionally available, non-security, C/D/E Week” patch, however all the different anticipated September patches are in.
Defrag woes in Win10 model 2004 largely mounted, however TRIM nonetheless nips
As I’ve talked about many occasions, Home windows 10 model 2004 shipped with a bug that causes the Home windows Optimizer Drives defrag device to skip updating the completion date on defrag runs. Consequently, defrags happen way more ceaselessly than obligatory. Microsoft has recognized in regards to 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 arduous disks. (TRIM ought to solely be run on SSDs.) Once more, Microsoft has recognized in regards to 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 (apart from coming in by 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 screen on Win10 model 2004 Lenovo computer systems (and probably another manufacturers) which have Enhanced Home windows Biometric Safety enabled within the UEFI. That bug appeared within the July “optionally available, non-security, C/D/E Week replace” and continued in each the August and September cumulative updates. As Microsoft explains it:
The gadget experiences a Cease error (also called a bugcheck or blue display screen error). The codes which might be related to the error are “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” (within the Cease error message display screen) and “0xc0000005 Entry Denied” (in reminiscence dumps information 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 in regards to the bug within the Home windows Launch Info Standing web page, nor has it talked about the issue within the related Information Base articles. It’s clear that the Lenovo firmware is at fault, however there’s been no repair in nearly three months.
Home windows Subsystem for Linux 2 in Win10 model 2004 broke
For all two of you who truly use Linux underneath 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, because of be launched any day now. However it hasn’t been mounted for model 2004. I count on we’ll see a repair within the anticipated “optionally available, non-security, C/D/E Week” patch for model 2004, which may arrive within the subsequent week. Or two.
Blue screens, Begin funnies, Motion Heart woes in Win10 model 2004
I don’t need you to suppose that I’m selecting on model 2004, however there are much more experiences of wierd conduct in 2004 after putting in the September cumulative replace, KB 4571756. Mayank Parmar at Home windows Newest offers the main points:
Efficiency points, Begin Menu crashes, sign-in points, non permanent consumer profile bug, Blue Display of Demise, and a raft of different minor bugs.
In abstract, Win10 model 2004 continues to obtain an unlimited variety of bug fixes each month. Only a few – nearly 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.
For those who suppose Win10 model 2004 is prepared for prime time, I’ve some critical research materials for you.
However 2004 is rolling out, even the place it’s not wished
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 he or she 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 a couple of days after it appeared.
Patching issues? Hit us on AskWoody.com.