Windows 10 cumulative update KB 3176934 breaks PowerShell

[Karlston]

Woody's take...

Microsoft's update for version 1607 doesn't fix two widespread problems with Windows 10 Anniversary Update, and it breaks PowerShell DSC operations

Yesterday afternoon, Microsoft released KB 3176934 for those PCs running Windows 10 Anniversary Update. It's the fifth cumulative update for version 1607 (three were released before the product rolled out on Aug. 2) and brings the build number up to 14393.82. You can see the long list of official changes -- primarily bug fixes -- on the Windows 10 update history page.

 

Anniversary Update customers also received an update to the "servicing stack" -- the subsystem within Windows 10 that handles updates -- in KB 3176936.

 

There was some hope that the cumulative update would fix one of the two widespread problems with the Windows 10 Anniversary Update that I talked about last week, but no such luck. Based on reports as of very early Wednesday morning, it looks like the freeze problem is still there. In a Reddit thread devoted to the topic, poster zpoon says: "After restart I had it lock up on me within 3 minutes."

 

Microsoft has closed off discussion about the freeze problem on the main Answers forum thread, so there's nothing new. But the original Reddit thread has been updated to reflect build 14393.82, and there's no joy in Mudville. I haven't seen any reports of a solution on the freeze front.

 

The second widely reported problem -- that Anniversary Update broke Skype for those who use many popular webcams, including the Logitech C920 -- doesn't seem to have been addressed by the patch either. The MSDN thread on the topic contains no news, only repeated remonstrations about Microsoft's ability to test Windows updates with the Skype team.

 

There's also a new problem, specific to patch KB 3176934. As the Windows PowerShell Blog reported last night:

Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an "Invalid Property" error. If you are using DSC from or on any Windows client, take the following steps:

 

Uninstall the update if already installed…

 

If using WSUS, do not approve the update. Otherwise, Use Group Policy to set the ‘Configure Automatic Updates' to ‘2 -- Notify for download and notify for install'… A fix for this issue will be included in the next Windows update which is due out 8/30/2016.

DSC is PowerShell's Desired State Configuration, a set of language extensions and commands that gives admins control over networked computers.

 

We now have two examples of significant internal patching screwups with build 1607. First, Microsoft's Skype people didn't raise the red flag when they were testing 14393.0 with C920 cameras. Now, Microsoft's PowerShell people didn't raise the red flag when they were testing 14393.82 with DSC. The problem with yesterday's update, it seems, is a simple missing file.

 

The Skype team had weeks -- months -- to halt the rollout of 1607 or at least warn users in advance that 1607 would break Skype with the C920. The PowerShell team had at least a week to test 14393.82 with DSC. In both cases, Microsoft released patches that broke its own products.

 

You may recall that Microsoft instituted the Release Preview ring specifically to give admins and developers a chance to test changes to Windows 10 shortly before they're released to the world at large. In this case, Win10 Insiders on the Release Preview ring received not one but two advance warnings about this 14393.82 patch -- KB 3176932, released a week ago, and KB 3176934, which followed two days later. Microsoft has never explained the difference between the two KBs, but they both resulted in systems with version number 14393.82.

 

In the past I've admonished admins and developers to get on the Release Preview ring, so they can test their wares before Microsoft throws the forced-update switch. Now, it seems, Microsoft's own teams need to get on board as well.

 

Right hand, meet left hand.

 

Source: Windows 10 cumulative update KB 3176934 breaks PowerShell (InfoWorld - Woody Leonhard)

 

InfoWorld - Woody on Windows

 

AskWoody.com - Woody Leonhard's no-bull news, tips and help for Windows and Office

[Batu69]

Topic has been split from here.

 

Quote

Microsoft says it won't be issuing an update to fix the matter until August 30, and states, apparently without a hint of irony, that "we apologize for any inconvenience that this might cause."

 

To undo the update, uninstall it or run the following in PowerShell:

wusa /uninstall /kb:3176934

As mistakes go, this is a embarrassing cockup on Microsoft's part. Redmond has made quick'n'easy PowerShell a key selling point of the operating system to admins right from the start of its pitch for Windows 10, and the focus pleased a lot of IT managers who like the software.

 

Microsoft even went as far as to open source PowerShell last week, a move that garnered high praise in some quarters. Now it has broken PowerShell for early adopters of W10, and the multi-billion dollar company can't seem to get its act together to fix the issue until next Tuesday.

 

And Redmond wonders why people are leaving its products for open-source alternatives.

 

'We apologize for any inconvenience that this might cause'

[steven36]

Windows 10 update breaks PowerShell and Microsoft won't fix it until next week

 

Microsoft offers one more reason not to update Windows 10.

 

 

If PowerShell has stopped working after receiving the Windows 10 Anniversary Update, now you know why.

 

f you can't use Microsoft's PowerShell after the latest Windows 10 update, Microsoft has four words for you: sorry for the inconvenience.

 

Microsoft published an article giving consumers 'five reasons why you should install the Windows 10 Anniversary Update' on its website before the rollout began in August. However, since then it's given Windows 10 users at least three reasons to be wary of updates.

 

 

The latest came on Tuesday, when Microsoft rolled-out a cumulative patch for the Anniversary Update that broke PowerShell, its command line shell and scripting language. The notes accompanying the release suggest Microsoft knew the changes would stop several PowerShell features from working.

 

It's the most recent issue to emerge following the rollout of the Windows 10 Anniversary Update, which has triggered mystery freezing issues and broken USB-connected webcams.

 

Those two issues remain unresolved in Tuesday's update -- KB3176934 (OS Build 14393.82) --for Windows 10 version 1607, also known as the Anniversary Update.

 

But while the patch adds stability to Windows 10 following the Anniversary Update, Microsoft took away two features of PowerShell by not including a file.

 

Microsoft explained that due to a missing .MOF (Management Object Format) file in the build package, the update breaks PowerShell Desired State Configuration (DSC), a feature that can be used by IT admins to manage enterprise environments.

 

"All DSC operations will result in an 'Invalid Property' error," Microsoft said.

 

"In addition, due to a missing binary in the build package the update breaks PowerShell implicit remoting. Implicit remoting is a PowerShell feature where PowerShell commands work on a remote session instead of locally. Specifically, importing a remote session no longer works."

 

The glitches come just a week after Microsoft open sourced PowerShell and brought it to Mac OS and Linux distributions.

 

Microsoft doesn't expect to remedy the PowerShell issues until it releases another update scheduled for August 30.

 

For what it's worth, Microsoft is once again sorry for breaking Windows 10 features after hyping up its Anniversary Update.

 

"We apologize for any inconvenience that this might cause," it said.

 

The series of problems with the update have surfaced despite months of testing by Windows Insiders in Microsoft's preview rings. Indeed, even though Microsoft knew in January that webcams might be affected by changes it would roll-out in August, it failed to warn users.

 

As for what this latest update adds, Microsoft says it brings stability to Network Controller, DNS server, gateways, Storage Spaces Direct, Group Managed Service Accounts, remote procedure calls (RPC), PowerShell,

 

Internet Explorer 11, printer pairing and interoperability, the Windows kernel, Media Core, Windows Store, Connected Standby, Cluster Health service, the Hypervisor debugger and platform, and Active Directory. Details about additional fixes can be found here.

 

Soruce:

http://www.zdnet.com/article/windows-10-update-breaks-powershell-and-microsoft-wont-fix-it-until-next-week/