如果在映像捕获之前未运行sysprep，则WES8 CTP2映像无法启动 [英] WES8 CTP2 Image does not boot if sysprep has not run before image capture

问题描述

创建一个WES8 CTP2图像&然后捕获图像（.wim文件）而不执行sysprep。在目标客户端上部署.wim文件后，设备无法启动并出现错误"无法找到或损坏winload.exe。错误代码：0xc000000e"。请
请注意，磁盘有单个分区（系统，启动和操作系统分区相同）。

Hi,
Create a WES8 CTP2 image & then capture the image (.wim file) without doing sysprep. After deploying the .wim file on destination client, the device does not boot and gives an error "winload.exe could not be found or currupted. Error code:0xc000000e". Please note that disk has single partition (system, boot & OS partitons are same).

如果我们运行sysprep然后捕获映像（.wim）然后将其部署到目标客户端上，则不会出现上述问题。

The above issue does not appear if we run sysprep and then capture the image (.wim) and then deploy it on destination client.

在WES7中，我们可以在不执行sysprep的情况下捕获和部署wim文件。

In WES7, we can capture and deploy the wim file without doing sysprep.

尽管我知道sysprep对于克隆是必需的，但这似乎是一个错误。

Even though I know sysprep is mandatory for cloning but this seems to be a bug.

推荐答案

如您所述，重新部署需要sysprep。否则，您可能会遇到各种问题 后期阶段。话虽如此，启动问题（无法找到操作系统加载程序），您看到应该是一个单独的问题。 从您的参考图片中捕获的bcd商店
可能不会直接在新系统上运行。要验证这一点，您可以启动到winpe，运行bcdedit / enum / store c：\ boot\bcd并观察输出并验证它是否已正确设置为从新系统启动。如果你看到
之类的东西，比如"device  unknown"或"os device unknown"，然后bcdstore中存在一些问题。 您可以使用bcdboot设置启动项。

As you mentioned, sysprep is needed for the re-deployment. Otherwise, you might run into various issues at  later stages. That being said, the boot problem (OS loader could not be found)  you saw should be a separate issue.  The bcd store catpured from your reference image might not directly work on the new system. To verify that, you can boot into winpe, run bcdedit /enum /store c:\boot\bcd and observe the output and verify it is set correcly to boot form your new system. If you see something like "device unknown" or "os device unknown", then there are some problems in the bcdstore.  You can use bcdboot to set up the boot entry.

这篇关于如果在映像捕获之前未运行sysprep，则WES8 CTP2映像无法启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！