Bug: WMF 5 Production Preview on Windows Server 2008R2 breaks sysprep
I just ran into the exact problem described in this ServerFault article:
http://serverfault.com/questions/749441/sysprep-fails-on-windows-2008-r2-after-wmf5-installation
After installing WMF 5 Production Preview, sysprep fails out, complaining that a registry key it is trying to delete doesn't exist.
The workaround in that link works. Adding:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\StreamProvider] "LastFullPayloadTime"=dword:00000000
allows sysprep to complete properly.
This appears to be related to the sysprep failure caused by WMF5 on Server 2012. The changes in Generalize.xml in that bug include the registry delete command implicated in this bug.
Lance A. Brown
shared this idea
We will make sure this doesn’t repro with WMF 5.1 release.
8 comments
-
Hugh McDaid commented
There is a fix post on the "Known Issues" page for WMF 5.0, which will probably also fix 5.1. I have not tried it myself.
https://docs.microsoft.com/en-us/powershell/wmf/5.0/limitation_overview
-
Philip Schmick commented
Still not fixed in WMF 5.1 and win updates september 17 (installed on wes 7)
-
Joey
commented
Yup, still not fixed in 5.1
-
Ernie
commented
Can confirm WMF 5.1 still fails, even in May 2017 with all Windows Updates
-
Andy
commented
SYSPREP still fails on 2008R2 using the new released WMF 5.1 code
-
Anonymous
commented
Just tried 5.1 preview, the issue is still happening
-
Anonymous
commented
In troubleshooting a sysprep issue and eventually finding this bug, this issue is also present in WMF4 and WMF 4 Hotfix. Only effects 64 bit OS's
-
Anonymous
commented
Is still not fixed in the (rereleased) RTM version. The workaround worked for me.