PowerShell problems with KB 3176934, the new Win10 v 1607 build 14393.82

Topic

New Reply

Don’t these people even talk to each other? Right hand, meet left hand. InfoWorld Woody on Windows
[See the full post at: PowerShell problems with KB 3176934, the new Win10 v 1607 build 14393.82]

Reply | Quote

Replies

In the words of the immortal Casey Stengel, “Can’t anybody here play this game?”

Reply | Quote

This is exactly what worries me with the new cumulative update rollups which M$ is intending to implement in Windows 7 and 8.1 come October.

One rapidly gets the feeling that Microsoft is beginning to treat us all like guinea pigs with no thought given to how novice users with automatic updates configured will resolve an issue if a rollup contains a bad patch and bricks the machine on reboot.

Also there have been instances where a patch would simply not install on some equipment such as KB2919355 a.k.a. Windows 8.1 Update producing error 0x80073712 even though the machine was up to date prior to trying to install it. Microsoft finally resolved it with a Servicing Stack, but it took about six weeks to fix if my memory serves me correctly.

But with security updates rolled into the same bundle it puts users at risk if they have to uninstall the whole rollup and then hang around while Microsoft gets its act together.

Yes, they can install the security-only package but how many users know how to download and install a .cab file?

Reply | Quote

Good points. We’re going to have to find a way to explain to “normal” people how to protect their systems.

Reply | Quote

Maybe MS should include a scheduled daily automatic system image to a recovery partition, with a big “Go back to yesterday” button in the start menu … 🙂

Reply | Quote

Hey, I’d buy it. A Tardis button…

https://www.amazon.com/TARDIS-Pinback-Button-Machine-Doctor/dp/B003ZMDTM6

Reply | Quote

You can always create one yourself for which you’ll need an external hard drive with at least 45GB of free space. The menu is accessible on Windows 7 in Control Panel —> Backup and Restore.

On 8.1 via Control Panel —> File History and then click the link in the bottom left hand corner called “System Image Backup”.

You can also wind back the clock to a time prior to installing something using System Restore. It’s also a good idea to create manual System Restore points from time to time and especially so immediately prior to installing software or Windows Updates.

Reply | Quote

Woody:
Thanks for telling it like it is. I, too, have been hornswoggled by some of the recent issues that have popped up. For example: why did MS add the print to 3d builder printer shell extension universally, without checking to see if users had a compatible device installed? Sheesh.

Keep those zingers coming. I need all the help I can get keeping up with what’s broken, and to steer around the potholes.

Best wishes,
–Ed–

Reply | Quote

In a way Woody cs did give some hints to protect oneself. I think its unspokenly rude to treat people like Micro$oft does. For normal / common people hardly to follow, if one ever find the time to do so. Most people try to work for a living.
Is there in the US and Eur no civilized legal way to to MS understand to live up to some standards of quality?
Or is all moral doomed?

Reply | Quote

It’ll never happen. Sooooo many people are just going to get abused. They don’t know what their computer does, don’t want to know – they just use it. A lot of them are like, “do we get updates? how do I know?” I’m not exaggerating.

I just showed one User the settings he agreed to when he setup his Win10 computer with an express install. It was “Oh, no, I don’t want to do that.” He just clicked the biggest button through the setup without knowing what he was doing. Bigger is better, right?

I’ve been dealing with the reality especially for the last year and a half since GWX. It’s almost impossible to reach the technically challenged (“normal”) User. Up until now we’ve trusted Microsoft to take care of them with Automatic Updates.

Who trusts Microsoft anymore???

Reply | Quote

+1

Reply | Quote

Hey, Ed!

Good to see you here.

Some of this stuff is merely dumb. Some of it is… self-defeating.

Reply | Quote

Hi Woody – every time I read one of your articles about another glitch with a Windows 10 update, it just reinforces that I made the right decision not to upgrade. Keep ’em coming!

Reply | Quote

The first level testing appears to be rudimentary. The second level appears to be feedback from the Insiders Group (cheap labour for MS). Third level testing is the Enterprise IT Pro and the Home User (more cheap labour for MS). They have guttered their own staff and have become way too reliant on doing it on the cheap. No wonder they are suffering from fainting goat syndrome.

Many, many years ago someone associated IBM with the rhinoceros, probably because of their large size, processing capabilities and thick protective skin.

If I were to associate an animal with Microsoft, I would choose the fainting goat.

Reply | Quote

I just updated a dev system at work from 8.1 to 10 using the ‘assisted technologies’ loophole, so it went to 10 AU…and started doing the ‘freeze’ after 1 minute of boot time right off the bat. Ugh. Back to 8.1 it goes…

What a mess. Way to demonstrate the follies of living on the bleeding edge by forcing updates, Microsoft!

Reply | Quote

How much risk is realistically there if a Security patch is not installed for few weeks after its release? Aren’t most of us doing this all the time with critical computers right now?

Reply | Quote

Good one 🙂

Reply | Quote

For those of us who work in Enterprise environments it is a well-known fact that the majority of the software companies make more money from supporting their products than from selling software. There are 2 ways to resolve this issue. Large organisations can afford and for them is more cost-effective to have full support agreements than to have highly skilled people in house. Smaller organisations rely on skilled engineers or sometimes on a hybrid model with some support for major problems.
Maybe it all comes back to the original model where regular end users who are not able or interested to fully support their computers should use just plain “dumb” terminals?

Reply | Quote

I work at a small non-profit business and using 10 pro on all user PC’s and laptops. This should not be happening to users at a business, wth is wrong with them!?!?! The printing issue is totally unacceptable! I had to go in and set ethernet to metered to turn off auto-updates.

Reply | Quote

Good solution.

Reply | Quote

It looks like the powershell dsc problems from KB3176934 might be fixed in the upcoming KB3176938 update for Win10 but it also looks like the KB3176938 update seems to break remote desktop connections as been reported on this web site:
http://windowsreport.com/kb3176938-breaks-remote-desktop-connection/

MS fixes one thing and breaks another.

Reply | Quote