Posted on 12/26/2015 11:23:20 PM PST by dayglored
(This is a follow up to an earlier thread http://www.freerepublic.com/focus/f-chat/3374828/posts)
WMF 5.0 has 'bug which resets the PowerShell module environment during installation'
The revolution has been postponed: the long-awaited update to PowerShell that yesterday we reported as having launched, has now been pulled by Microsoft.
Redmond says its reversal is due to “a bug which resets the PowerShell module environment during installation†that “can have a serious impact on our customers†because it “resets the PSModulePath environment variable to default values, losing any changes made prior to the WMF 5.0 RTM installation.â€
Windows Management Framework (WMF) 5.0 has therefore been pulled from downloads. Microsoft is also “unpublishing Azure DSC Extension Handler versions 2.11 and 2.12 as they automatically install WMF 5.0 RTM.â€
Unpublishing?
It's Christmas Eve and the subs won't mind. Microsoft's clearly didn't.
There's doubtless egg on faces at Microsoft over this mistake, and not because beardies had have been sipping seasonally rum-infused beverages. The company realises it's been naughty and promises a nice new version of all WMF-related code “ as soon as the issue can be isolated, corrected, and validated.†The smart money's on that not being in 2015, what with imminent events.
Well, that sucks. Sounds like it should be an easy fix, though.
I downloaded and installed it on my W7 workstation before it was pulled. I haven't needed to modify the default module path, so I wasn't affected.
One thing I have found is that while WMF 5 was back-ported to W7, the KB that adds the security bits required to enforce transcription is only for W8 and up. You do get the Invocation Header and automatic file naming, which provides some valuable data for security application and diagnostics.
Forcing reverts to factory defaults makes sense. Some of the spyware might not work if users customize the software.
my command line days are way behind me.
Do I care about this ?
This is one of those rather specialized things. So if you’re not using PowerShell, probably not.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.