New Windows 10 build 10586.122, KB 3140743, brings few fixes but some significant changes

Topic

New Reply

I’ve got to admit it’s getting better A little better all the time.,.. Really. InfoWorld Woody on Windows
[See the full post at: New Windows 10 build 10586.122, KB 3140743, brings few fixes but some significant changes]

Reply | Quote

Replies

C’mon, Woody…

If you’re going to quote the Beatles, quote the entire lines…

I’ve got to admit it’s getting better (Better),
A little better all the time (It couldn’t get much worse)…

Now that puts things in better perspective!

🙂

Reply | Quote

Woody,
I have Win 10 Pro. I have a little flexibility when updates come along. Can I go ahead and let my PC install KB3139907 and KB3140743?

Reply | Quote

Woody,
Doesn’t part of the refrain say, “Can’t get no worse”?
Morty

Reply | Quote

HA!… since you’ll be mine….

Reply | Quote

I haven’t heard of any major problems yet. In general, the Win10 cumulative updates have been relatively benign, except for the ongoing problems with installing them.

Reply | Quote

Edited for brevity??? 😉

Reply | Quote

I got 2 updates today KB3140743 and KB3139907 which brought me to 10586.122 and fixed a network problem I have had since 10586.104.
Until the new updates, none of my other networked computers showed up in file explorer>network. They now show up so that I can access them.

Reply | Quote

Excellent! Another bug squashed….

Reply | Quote

On a system that had been quieted, no new attempts to communicate online have been detected after these updates (I got KB3139907 and KB3140743 together).

For what it’s worth, Microsoft actually HAS provided all people need to take control over WHEN and WHETHER updates are applied to Windows 10.

Between the Microsoft Show or Hide Updates tool (KB3073930) both showing the list of available updates, and the abilities to reconfigure local policy or even go so far as to Disable the Windows Update service, any user willing to follow a small procedure can be in complete control.

I’d wager most folks don’t realize the Microsoft Show or Hide Updates tool can be employed as a “what’s available”.

Of course, they could just come here, or go to Microsofts “Windows Update History” log to see if something new worth considering has arrived. This blog is how I knew to look for the 10586.122 update…

-Noel

Reply | Quote

Interesting. How to use wushowhide to show you what’s available — in other words, to pre-emptively keep patches from installing, before they’re installed on a Win10 machine?

Here’s my experience with wushowhide: http://www.infoworld.com/article/3022984/microsoft-windows/outlook-2010-patch-kb-3114570-reintroduces-calendar-bugs.html

I’d sure love to find out how to teach that old dog a new trick…

Reply | Quote

I have my daughter using the wushowhide tool this way, as well as making sure she stays on a metered connection.

At this point should she and others keep KBs 3140743 and 3139907 hidden observing the fallout, then and wait for you to let us know when to install them, or should we all take the plunge and do it?

Thanks Woody!

Reply | Quote

the metered connection should keep the cumulative updates from installing. Yes, she should turn off the metered connection, and let the patch apply itself (unless she uses an Xbox One game controller).

The MS-DEFCON levels include Windows 10. Watch the notifications.

Big question: HOW do they use wushowhide to block cumulative updates? I’m going to try to use wushowhide when the next cumulative update comes around – but it won’t be easy. I think – think – it’ll work if I can run wushowhide after the cumulative update becomes available at my location, but before Windows Update catches it. (I’m still not sure precisely when Windows Update goes looking for new patches.)

Do you have any insight?

Reply | Quote

So both patches are problem free-KBs 3140743 and 3139907? I have to check to see if her friends use X-box on it.

This is what has been done on the Win 10 computer. Let me know if this has a problem or not?

We downloaded KB3073932 (the wushowhide tool) to her desktop. When we hear there are new updates, or even if we don’t hear, we check periodically. We double click it, hit next and then you are given two choices. The first is to hide an update, and the second is to show hidden updates.

When you choose the first to hide an update the tool goes searching through the computer searching for problems. Then a list of updates is presented. It has a lot of other updates also such Intel and the keyboard and so on. You just go through the list and check the box of the ones to hide. We did this with KB3135173. It disappeared from the hidden list a few days before KBs 3140743 and 3139907 came out.

When you are done you exit the tool.

If you want to see what is hidden, you start the tool up, and click next and then you click show hidden updates. For her computer she has KBs 3140743 and 3139907 and a MS validation tool she heard would slow her computer down.

I believe the use of the metered connection to first stop download as soon as updates released is the first step to protecting ourselves, and then once we know new updates have been released, we go into the tool to find the new updates and hide them until you give us the word regarding their safety or crippling effects.

The only problems that exist would be 1. The reissue of updates–but you can always check to see what is there for download before going off the metered connection, and 2. Weeding out the MS updates from all the device, etc., updates. One way around that would be to use the snipping tool and paste the snips of the list in a document to check for changes.

I did notice something was different when we hid KB3135173 versus these last two. Windows 10 notified us there were updates ready when KB 3135173 so it was in the update list under Settings-Windows update even after we hid it.

For KBs 3140743 and 3139907 I was online within a few hours after their release, and I jumped in and hid them. As a result, they are not on the ready to be updated list. It says your device is up to date.

Once we did try to update this new computer yesterday with the February updates, it took a long time for them to show up and notify us they were ready. We ignored them at first, and the list disappeared, and she then installed new malware protection and she did a restart, and the list didn’t show up again. After 18 hours or so I got worried and we installed the MSRT from the Windows support site, and instantly we were notified the others from February were there. I have no idea if this is related to once having the new computer set to a metered connection, or if it was just some bizarre snag.

If there is a problem with this approach of searching, hiding, and then showing again in order to update or install the KBs please let us know. Because KB3137173 disappeared, we have not yet tried to show one of our hidden updates. We will try it tonight. However, this technique is just what Noel C. is talking about above, I believe.

Reply | Quote

Regarding your statement about MS Defcons, I just assumed until you heard reviews regarding behavior of an update you would notify us, but we all know making assumptions is a poor idea. We will unhide KBs 3140743 and 3139907 if there is no X-box game playing to be done in the near future.

Reply | Quote

Actually, you’re fine playing Xbox games. It’s just the Xbox One game controller that’s shafted. (The controller is a hand-held thing that looks like, well, like a game controller.)

Reply | Quote

Sounds great, and thanks for the detailed recap! As I mentioned to RC, I’m going to try to catch the next CU between the time it’s released and the time it’s installed on my Win10 machines. With metered connection turned on, that should be easy. But I wonder how hard it’ll be to do with a “normal” connection…

Reply | Quote

We opened up the wushowhide and un-hid the two updates. After clicking to “show” them the tool did some more scanning of the computer and a note came up saying that minor changes had been made to the computer. That disturbed us a bit.

When the computer restarted it took forever to restart. It’s a new computer that started very quickly before. It took about 4 minutes. To test it again, we restarted it, and it was a bit faster, but seemed forever–this time maybe 2 minutes.

Unfortunately, I found she had added AdBlock Plus to the computer prior to this, and did not create a system restore point before it,or tell me she did it. That could be slowing the computer down–one of the blocks has to do with malware, so I will try to disable it and see if that speeds things up.

It could be the two updates, or whatever the wushowhide tool did.

Reply | Quote

I swear I posted this, but I don’t even see it waiting for review. The updates slowed the start up of the computer by 4 minutes. I went back to find a restore point, and it didn’t create one. I hastily made one when the download had just started at about 5-10%, would it be wise to do a system restore using that point, or just uninstall those two updates? There are no critical restore points at all before any of the updates occurred. I have checked over and over again. System Restore is configured and on. Something is very strange.

Thanks Woody!

Reply | Quote

I personally approve every post on the site. That’s why it can take some time before your posts show up. Sorry, but that’s the compromise I finally came to – it allows for completely anonymous posts, and I can simply refuse to post something if it’s offensive.

Reply | Quote

I understand. I just did not see the waiting for review and thought I just failed to submit.

Now, for my question.

I took out the adblocking she put in and it is still slow at startup.

Considering I created a manual restore point at about 5-10% of downloading the two updates, should I do a system restore, or remove the updates to see what increased the startup time by 4 minutes?

Thanks again!

Reply | Quote

Personally, I’d try the restore.

Reply | Quote

The key is to configure your local policy (gpedit.msc) for Computer Configuration > Windows Components > Windows Update : Configure Automatic Updates to “Disabled”. Then Windows won’t automatically update, but will wait for you to start the Settings App and request it.

Then, if you use the KB3073930 Show or Hide Updates tool, it will check for available updates and show them to you, but WILL NOT install them.

At this point you have options:

1. Do some research (e.g., starting at AskWoody.com) to find out if any of the available updates are problematic.

2. Choose to wait (i.e., just don’t go into the Settings App and click through the Updates button.

3. Choose to hide an update in the list (e.g., a driver) that you’ve determined (by research) is likely to cause a problem.

If you want to be doubly sure Windows doesn’t install something secretly, you can choose to disable the Windows Update service, and only re-enable it and start it when going through the above procedure – but that’s for dyed-in-the-wool geeks who suspect Microsoft of being sneaky. Just the policy change will prevent Windows from doing updates until you request them.

I’ve been following this strategy since just after the first Windows 10 preview came out. It works.

-Noel

Reply | Quote

Thanks! I’ve played with that a bit – but never tried it in conjunction with wushowhide. So now I’ve switched one machine over to disable Configure Automatic Updates. We’ll see how that works in a real-world situation, to prevent a single Cumulative Update from installing.

Three questions:

Will some future patch change this setting?

What else won’t install? Have I just disabled all of Windows Defender updates, or MSRT tool runs?

How to do this on Home machines? gpedit always has registry change analogs. How can Home users take advantage of the same setting?

(I’m also curious how this differs from disabling the Windows Update Service, in the Windows Update Properties dialog. And I wonder how it interacts with the “Defer Upgrades” check box in the Windows Settings Update/Advanced Options dialog.)

If you have answers, I’d sure appreciate hearing about them….

Reply | Quote