Win10 cumulative updates KB 3213986 and KB 3210721 have multi-monitor problems

Topic

New Reply

Other problems few and far between for the security-light 14393.693, 10586.753, and 10240.17236 patches. But note that we’re still on MS-DEFCON 2: The
[See the full post at: Win10 cumulative updates KB 3213986 and KB 3210721 have multi-monitor problems]

Reply | Quote

Replies

KB3216986 has issues installing. I’ve tried over 20 times with both Windows Update and downloading it directly from Microsoft’s Update Catalog.Both ways have failed ech time I’ve tried. I just had 2 surgeries last week for a complex left ankle fracture & dislocation.Thanks to a gog biting my other leg while I was riding my mountain bike. Surgeon said it was the worst breaks he ever saw or treated. No clue how many metal plates and screws are holding it together.
No time right now to waste on buggy updates.
My legs both get sore after 20 minutes at my pc.

Reply | Quote

I have to admit I am impressed by the work they appear to be doing, however, it appears to be closing the barn doors after the horses (releases) have left. A bit of testing and error fixing before a slavish push of an update would go a long way.

I know internet forums and blogs are not indicative of the totality of an issue be it software or cars, and magnify the negative (which is their goal if you want to know about and address problems), but I am increasingly hearing from colleagues of similar instances on their home PCs, and they are nowhere as tech savvy as readers here or the posters at Reddit.

The attitude of many of them is they are PO’ed, but as long as the PC still boots and works for email, minor word processing, and browsing, who cares if it updates, while others are moving to Apple iPads with BT keyboards or MacBooks or Macs, some have just reverted to older PCs that do not run Win10, and others are mentioning they heard about something called Linux.

I still believe I will eventually have an interest in Win10, but even if the spying and forced updates were to disappear, I still would be hesitant as I want a PC that works and does not get broken by updates.

It just seems that these versions are more to say we have a new coat of paint than actually deliver customer end user value.

Let’s just hope none of these autonomous, self-driving cars have MS software. Car insurance rates would skyrocket.

Reply | Quote

Don’t worry about it! We’re on MS-DEFCON 2, and it isn’t worth the hassle.

Reply | Quote

I have to agree with you, that more and more people are expressing frustration with Win10 in real life. I work at a library, and I’ve heard numerous people complain about Win10, and most of these people have no idea how to find answers to their issues. Today, one of my coworkers was frustrated, since she was trying to get onto her computer at home to get to her copies of all of the stuff needed to apply for a promotion (HR lost her originals – thankfully, her supervisor knew she had applied, so she’s set for an interview but has to resubmit). Sure enough, Win10 reboots to update thanks to Patch Tuesday (which, like most people, she didn’t know is a thing), and she couldn’t wait as she had to go to work. She told her family to stay away as they didn’t want to her what she was saying about that. (g) I forwarded her the link to your tips, Woody, but she was thinking about seeing if she still had the Win7 discs so she could go back to that (although this site will be good for her for that as well!).

Reply | Quote

Hi Woody,

The ‘Set as metered connection’ wi-fi trick on Windows 10 Pro doesn’t seem to work anymore for me. It used to work until last December when it updated on itself and it happened again for this month’s update.

Has this happened for anyone else using the trick? I don’t mind helping to diagnose what went wrong but have no idea where to start.

Reply | Quote

Weird. It’s working for me.

Do you only have a Wi-Fi connection?

Reply | Quote

Does anybody know how to enable the greyed-out button Restore default setting for this plan?
This is about the Power Options plans/schemes.
The symptoms are like here:
https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/power-options-edit-plan-settings-advanced-settings/2ed6844a-608e-439c-9d0e-03cf006ddfed
or here
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/option-to-restore-default-settings-for-stock-power/a8849e6a-7526-4cbb-9116-fd9b1115c09b

Please do not reply to reinstall Windows 10, I already know that solution. I am interested in learning what is the issue for the future and less to resolve it quickly.
This system was upgraded in place from Windows 7 to Windows 10 1607 and the symptom is more common than someone would expect based only on Google Search hits.

Reply | Quote

Yeah, only Wi-Fi. My laptop has never connected to the internet using Ethernet too. The ‘Set as metered connection’ option was enabled when both forced updates occured.

Reply | Quote

It just hit me, does using a VPN cause Windows to treat the connection as Ethernet despite actually being on Wi-Fi? Just noticed the Network and Internet status is currently listed as Ethernet.

Reply | Quote

i just bought a MacBook For my work specialy after a guy here told me if i do not like MS to switch to another OS, instead of fixing thier stuff they act rude, from Aug 2016 till jan 2017 Windows became a usless OS because of guys like him

Reply | Quote

Shouldn’t make a difference.

Reply | Quote

Oh boy. I wonder if anybody else has hit this?

Reply | Quote

If its got you stumped then all I could suggest its locked out in GPEDIT, I looked in the settings under Power and regular “lockout” policies and theres nothing there specific to your described problem. Your not on 1607 Home ver.? As a long shot its not an Inherited condition/setting from Win7? Looking at the time line, let us know as you have probaly solved it by now and I have never had that before.

Reply | Quote

Crazy as it sounds Driver issue? Win7 to Win10 there’s some but not a lot of difference in drivers most are interoperative.

Reply | Quote

Not crazy at all, I thought about Graphics Card drivers for a while, but I didn’t test.

Reply | Quote

Not in gpedit, but your previous suggestion about driver issues makes a lot of sense.
Now the problem is which driver, if any?
On 1607 Pro, I would not use Home Version under any circumstances and this is true not only for Windows 10.

Reply | Quote

Not resolved and I cannot sniff any registry key producing this behaviour. The only workaround was to use a software called Winabler which enables greyed-out buttons temporarily.
https://www.raymond.cc/blog/how-to-enable-and-access-disabled-grayed-out-buttons-windows-and-checkboxes/
http://www.tinkertoys.net/Products.html

It may be inherited from Windows 7 during the upgrade in place and this is likely, but I just don’t want to reinstall Windows 10 in upgrade mode. It is not causing issues at the moment, I only want to understand what can produce that behaviour, difficult to reproduce in general.

Reply | Quote

Well very sorry but you have me stumped. Best I can come up with in the Dvr stakes is linked to ACPI battery and mains power supply but quite a bit of power handling is done with “Firmware” ACPI is more with the controlability ie on and off monitors sleep mode etc. If its a desktop then even less so as the battery handling is out of the equation. I was going to suggest copying and pasting hardware ID’s in to M$ catalogue but I know youve already done that and the results arent always reliable or matched properly. From your posts in here I know youve already covered everything and more beside than I would do and I am hesitating to suggest…… well you know.

Reply | Quote

@ Jerry ……. Probably, M$ knew that u had been using the Wifi metered connection to defer cumulative updates and/or feature updates/upgrades for quite a while(= a few months), which is against the Win 10 EULA and so, M$ hv taken “punitive” action against u by disabling yr setting for Wifi metered connection.
……. Those who use the Wifi metered connection to defer cumulative updates for a month or 2 won’t be “malwarized” by M$.

Reply | Quote

It would be a bit scary if they actually took the effort to check whether my connection was actually metered or not…

For now I guess I’ll use Woody’s Group Policy Editor mthod instead until that defer update option leaves beta.

Reply | Quote

@ Jerry ……. Likely, it is quite easy for M$ to write code for their Windows Update Service to detect every Win 10 cptr that has deferred their mandatory cumulative updates, eg for 3 months or more, then to know how the “illegal” deferral was being done by scanning these “recalcitrant” cptrs, n lastly to take possible “punitive” actions.

The in-built AllowExperimentation Registry setting in Win 10 allows M$ to reset the configuration settings or perform experiments(eg disable certain features) with nearly every Win 10 cptr.
……. Only business users(= Win 10 Pro & Ent) who hv subscribed to M$-Intune could disable AllowExperimentation. M$-Intune costs a minimum US$6 per month per user/employee.

Reply | Quote

@BobbyB
Thanks for your replies and trying to assist.
I finally got at the bottom of it.
Under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPowerUser, there are 2 other main branches – Default and PowerSchemes

Default was there by name, but nothing else underneath, which explains the error message: “The power scheme, subgroup or setting specified does not exist.”

PowerSchemes was there but messed up and I compared to a known computer and resolved it after taking ownership and deleting the offending keys.

After importing Default from the known good computer, this was fixed.

Not sure why this happens though, but I assume it to be a side effect of importing older settings from Windows 7 during the upgrade process.

As usual, it is highly recommended to install clean where possible.

Reply | Quote

Actually, after testing a little bit more, I found that what is under PowerSchemes does not matter at all if powercfg -restoredefaultschemes is run from the command line as administrator.
The PowerSchemes key will be replaced with what is under Default.

Reply | Quote

Glad you got it fixed. Yeah my favourite is, was and always will be (new editions permitting in the future) a clean install be it in a VHD, Hyper-V or partition (if memory serves me even win8 to 8.1 M$ says its too much of an upgrade for any kind of a VM/VHD but never even tried it). Gave it a try upgrading from 1511 to 1607 (in a reg. partition) not only takes longer but creates an extra (hidden) partition. A real pain on multi-boot but as I label my partitions and VHD’s “no worries,” and duly deleted.

Reply | Quote

Most people would find a use for the hidden partition as it has the recovery files.
I am not in favour of that extra partition on my systems, because I prefer the files to be on the C: drive for easy manipulation of partitions, but for most people for who testing and production systems are a lot more separate than mine, it may prove a good idea to keep the recovery partition separate for production systems.

Reply | Quote

Regarding this one, there are actually a number of power options that got gimped in a recent update (not sure which one, sorry, just noticed a large number of machines at work that no longer have much available at all by way of power management, which is problematic especially with surface pro’s, ironically)

The fix is to do a quick regedit and reboot:

HKLMSystemControlSet001ControlPower and change CSEnabled from 1 to 0.

After doing the above and rebooting all power options will be available again, including the Restore Plan Defaults option.

Bit of a daft and somewhat irritating thing for Microsoft to do, if you ask me, given the frequency of which we have to take their Surface Pro’s off Battery Saver for the wireless to function properly when not hooked up to a power source. But that in part is due to an internal wifi network only the Flintstones would be proud of.

Reply | Quote