Microsoft admits that its latest Windows 10 update causes PowerShell to crash

And you'll have to wait a week until the latest fix is fixed

Microsoft's latest update to Windows 10 - intended to fix problems caused by its big Anniversary Update - is itself creating new problems for Windows 10 users, including causing PowerShell to crash. Microsoft says that fixes for the latest update glitches won't be released for another week.

Microsoft rushed out Windows 10 build 14393.82 on Tuesday. The company promised initially that the update contained fixes for PowerShell, but has since admitted in a blog post that it has totally borked it.

"Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an 'Invalid Property' error," the blog post reads.

"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."

What's more, Microsoft has said that it won't fix the update until 30 August.

"We apologise for any inconvenience that this might cause," Microsoft said, advising users that the update can be removed by running the following in PowerShell: wusa /uninstall /kb:3176934.

Windows 10 build 1493.82 does actually fix some things, though, including the operating system's Network Controller, DNS server, gateways, Storages Spaces Direct (the Server 2016 feature that pools server storage for scalable software-defined solutions), Windows Store and Active Directory.

Internet Explorer 11 also receives an update, including a fix to do with 'mouse events' not working correctly and a user interface glitch.

There's not much to report with regards to Edge, despite the browser still being plagued by problems first seen soon after Windows 10's launch, although there is a small fix involving Edge's new extensions.

Less core fixes are for Xbox One media casting via cast to device, and a problem with nodes being disconnected from the Windows Cluster service "intermittently".

Cortana is mentioned as being fixed, as is an incorrect lock screen UI after resuming from hibernate or sleep.

Beyond these desktop fixes, Windows 10 Mobile is a large focus, although we still wonder why Microsoft bothers given its low audience share in mobile these days.

Anyway, changes include a fix for 3G and 4G options "not appearing correctly in Windows 10 Mobile settings". Quite a major problem, we'd imagine.

Mobile device management enrolment in Azure Active Directory has also been a problem for some, as well as streaming to Xbox One's Netflix app from (we'd imagine) a phone.

It all seems quite fair and reasonable, but we'd still be interested to see a fix for Windows 10 Anniversary to allow it simply to install, as there still seem to be a wide number of systems, particularly those with SSDs, rendered completely unusable after applying the update.