HomeWinBuzzer NewsMicrosoft Windows 10 Anniversary Update Build 14393.105 Fixes PowerShell DSC Problem

Microsoft Windows 10 Anniversary Update Build 14393.105 Fixes PowerShell DSC Problem

Yesterday’s Cumulative Update for Windows 10 Anniversary Update saw Microsoft fix a problem it created in PowerShell DSC about a week ago. The company replaced a missing .MOF file in the latest patch.


Yesterday, we wrote about the Cumulative Update for the . The focus of the update was fixing some issues with the platform. A PC freezing problem has been solved in this update. On top of that, also used the August 31 release to fix a problem in PowerShell.

Users were left frustrated last week when Microsoft released the August 23 Cumulative Update. That Anniversary Update roll out (Build 14393.82) caused problems with PowerShell. Namely, a missing file resulted in issues with the Desired State Configuration (DSC). Microsoft actually knew about this problem.

The previous update broke the DSC feature. This is a PowerShell feature used by admins to manage their enterprise systems. We wrote about this problem when it first occurred over a week ago.

“On August 23, Windows update KB3176934 released for Windows Client,” said the PowerShell Team at the time. “Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an ‘Invalid Property' error.”

Luckily the company has acted quickly to send out a fix. The problem was caused by a Management Object Format (.MOF) file that was missing from Build 14393.82. The latest release, Build 14393.105, reintroduced that file.

Latest Update

As we mentioned yesterday, the August 31 Cumulative Update lacked new features. Instead Microsoft focused on clearing up some issues with the Anniversary Update. It was the third such update from the company in the month since it launched the upgrade. Expect more to follow as some problems still persist with the build.

One other key fix introduced with the latest update solved a persistent problem with PC freezing. More specifically, machines were becoming unresponsive when logging in. Microsoft attributed the issue to the OS and apps being stored on separate drives. Build 14393.105 fixed the problem.

Luke Jones
Luke Jones
Luke has been writing about all things tech for more than five years. He is following Microsoft closely to bring you the latest news about Windows, Office, Azure, Skype, HoloLens and all the rest of their products.

Recent News