WFP-Install Sparta Miniport接口在WIndows 8（32位和64位）上失败 [英] WFP-Install Sparta Miniport Interfaces fails on WIndows 8 (32- and 64-bit)

问题描述

当我在Windows 8上运行WFP WHCK测试时，我在Sparta虚拟微型端口的安装和卸载过程中看到了失败。

I'm seeing failures during the install and uninstall pass for the Sparta virtual miniports when I run the WFP WHCK tests on Windows 8.

每个测试都失败了2个任务。第一项任务因以下原因而失败

Each test fails 2 tasks. The first task fails because of the following

使用命令行执行任务

Cmd.Exe / C "Ver.exe |查找"6.1" > 0&& ren SpartaMini.Cat SpartaMini63.Cat&& ren SpartaMini.Sys SpartaMini63.Sys&& ren SpartaMini62.Cat SpartaMini.Cat&& ren SpartaMini62.Sys SpartaMini.Sys&&
ren Callout.Sys Callout_0x602.Sys&& ren Callout_0x601.Sys Callout.Sys"

使用ExitCode 1失败

第二项任务因以下原因而失败：

The second task fails because of the following:

使用命令行执行任务

Cmd.Exe / C" Ver.exe |查找"6.1" > 0&& ren WFPLogo.Exe WFPLogo_0x602.Exe&& ren WFPLogo_0x601.Exe WFPLogo.Exe"

使用ExitCode 1失败

测试时我没有看到这些失败在Windows 7上运行相同的驱动程序.sys。此外，过滤器不会清除这些故障。

I do not see these failures when the tests are run on Windows 7 with the same driver .sys. Further, the filters do not clear these failures.

有谁知道这些故障的根本原因是什么，以及我们需要做什么来提交日志？

Does anyone know what the root cause of these failures are, and what we need to do for submitting logs?

推荐答案

您所谈论的任务仅适用于Win7。 任务名称甚至可以影响Win7：重命名驱动程序二进制文件和Win7：重命名System32二进制文件。 这些故障可以安全地被忽略，因为它们是设置的一部分，
并且仅针对特定版本传递。 在未来的套件中，我已经消除了这种混乱。

The tasks you are talking about are applicable only for Win7.  The tasks names are even something to the affect of Win7: Rename Drivers Binaries and Win7: Rename System32 Binaries.  These failures can safely be ignored as they are part of setup, and are targeted to pass only for particular versions.  In future drops of the kit, I have eliminated this confusion.

谢谢，

这篇关于WFP-Install Sparta Miniport接口在WIndows 8（32位和64位）上失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！