Sysprep fails if Metro Apps have been "updated"

Well, here is a fun one. A coworker spent the entire day getting a Windows 8 machine up and ready for imaging. As part of the process, he went ahead and let it update the metro apps from the store.

Big mistake: Apparently updating Metro apps breaks sysprep;
Sysprep giving "fatal error" -- but *only* after updating Metro apps?

Here is a KB article on the issue;
Removing or Updating Windows 8 built-in Windows Store apps causes Sysprep to fail

It's even being reported that simply "opening" a metro app will cause sysprep to fail on Windows 8;
Techy Geeks Home: SCCM capture of Windows 8 fails during Sysprep stage - Fatal error occurred while trying to sysprep the machine


Needless to say, my coworker was pretty miffed about losing an entire day on this particular issue.

Hi,

Thanks for pointing to the KB article! I've had scenario 3, and ended up reinstalling the OS I had prepared on a VM. The KB article suggests removing all updated apps, so it wouldn't work for my purposes anyway.

I also had a sysprep issue when simply installed an app from the store. But in that case I managed to remove it manually after analyzing the sysprep log.

Vadim

Very strange. I have sysprepped a lot of both 7 & 8 images and systems, also existing 8 systems with updated Windows Apps. The absolutely most common reason for sysprep to fail (a subjective personal opinion!) is the Windows Media Network Sharing service (WMPNetworkSvc); stop it, sysprep again and usually it will work.

It's so usual I have a habit to stop the service always in Audit Mode before sysprepping, just to be sure.

Anyway, if even after stopping the said service sysprep fails, the KB2769827 mentioned by Pparks normally works. However, I have to say this: I have only needed it a few times, usually there's no issues after the WMP sharing service is stopped.

Kari

Hi Kari,

Note that the KB article doesn't say "fails", it says "may fail", meaning it may not

Vadim

Yes, as I mentioned it has mostly worked for me, only a couple of times have I needed that workaround.

Honestly geeks, try stopping the Windows Media Player Network Service before sysprepping and you will notice how seldom it fails.

Turning WMPNS off takes care of the WMPNS problem (drmv2clt.dll,Sysprep in the log), but doesn't take care of other problems, like the one we discuss here.

Let's try once again: The WMPNetworkSvc failing the sysprep is far more common than the Win App Package doing it. When sysprepping fails, checking the WMPNetworkSvc should IMO be the first thing to do, after doing it there's quite often no need for the KB fix.

I am not trying to step anyones toes here, just telling about my experience.

Kari
System Preparation Tool - Use to Customize Windows - Windows 7 Help Forums

Kari said:

When sysprepping fails, checking the WMPNetworkSvc should IMO be the first thing to do

Click to expand...

No, the first thing to do is to inspect the sysprep log I'm not saying that turning off WMPNS preemptively is a bad idea. I'm talking about the correct troubleshooting approach.