I am getting the same error in wdk 11. I have researched the error for 4 days. It looks like a permissions or dependencies error. the wdtfinstall.dll is uncompressed from the cab file during install, and then gets deleted after the install fails. I checked on my machine for the dlls it depends on and all are installed. I followed instructions on adding permissions to the temp folders and moving the install to a different folder and nothing worked. This is happening on a dual xeon server and an i7 laptop. the server is running windows 10 pro and the laptop is running windows 10 home. I have just installed the os on the server in a new partition without any luck installing wdtf. I tried many times on the laptop without success, and got into a failed provisioning process so I reset the laptop to a clean os. Both computer are running vs pro 2019. 20h2 windows 10 and all the latest updates. Both computers have office 365 installed.
Provisioning a host computer for driver development fails
I am trying to provision a remote computer for driver testing according to the instructions here:
https://learn.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/provision-a-target-computer-wdk-8-1
The target (test) computer has FRESHLY INSTALLED Windows 10 (build 19043) plus the WDK downloaded from the MS website (10.0.22000.1), plus the WDK Test Target Setup MSI executed.
The host and target PCs are connected on a point-to-point network and are able to communicate (each one can ping the other successfully and firewalls are off).
Visual Studio Community (16.11.3) on the development computer (Windows 10 build 18362) runs the provisioning "wizard" with "Provision device and choose debugger settings" and it almost works completely, but I get an error stating:
Installing driver test framework
ERROR: Task "Installing driver test framework" failed to complete successfully. Look at the logs in the driver test group explorer for more details on the failure.
The logs in the driver test group explorer indicate:
MSI (s) (18:28) [17:54:21:656]: Note: 1: 1723 2: WDTFInstall_InstallIoSpyFilterDriver 3: WDTFInstallIoSpyFilterDriver 4: C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\WDTF\RunTime\WDTFInstall.DLL
CustomAction WDTFInstall_InstallIoSpyFilterDriver returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (18:28) [17:54:21:656]: Product: Windows Driver Testing Framework (WDTF) Runtime Libraries -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action WDTFInstall_InstallIoSpyFilterDriver, entry: WDTFInstallIoSpyFilterDriver, library: C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\WDTF\RunTime\WDTFInstall.DLL
Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action WDTFInstall_InstallIoSpyFilterDriver, entry: WDTFInstallIoSpyFilterDriver, library: C:\Program Files (x86)\Windows Kits\10\Testing\Runtimes\WDTF\RunTime\WDTFInstall.DLL
09/27/2021 17:54:21.660 [3864]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 393
I'm following the instructions exactly and this fails every time I try to provision the target computer. Help please!
8 answers
Sort by: Most helpful
-
-
njk@ut 11 Reputation points
2021-10-25T13:43:40.73+00:00 I also downloaded the new VS 2022 RC2 and was crossing my fingers that there was a fix for this. But unfortunately there is not yet an available WDK extension supporting VS2022 (hopefully this will be provided along with the final production release of VS 2022 in November???).
-
SteveP 256 Reputation points
2021-10-23T22:18:57.993+00:00 I'm also having this issue. Microsoft: PLEASE HELP!!!
-
SteveP 256 Reputation points
2021-10-25T20:30:47.5+00:00 I emailed wdkfeedback@microsoft.com and got a response from a WDK developer. No solution yet. I'll keep y'all posted.
-
SteveP 256 Reputation points
2021-10-27T02:25:54.293+00:00 It is not at all obvious that a WDK that targets multiple OS versions installs a WDTF that can only target one OS version... but that's what's going on here.
WDTF requires the same WDK on both the host and the target.
In my case, targeting Server 2016, WDK 1607 WDTF requires VS2015. Bah!
I have requested WDTF improvements ...
- detect and report mismatched or unsupported host/target WDK combinations.
- support targeting of the down-level OS versions that are supported by the WDK installed on the host.