This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 0%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENU%3C/text%3E%3C/svg%3E)
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!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 66%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESN%3C/text%3E%3C/svg%3E)
Hello All,
I am also facing the same issue and tried having the same OS version on the Host and the Target PC but it didn't work.
I have 21H2 Windows 10 Pro in both host and target.
I don't know what else to try to resolve this error.
Does anyone has any solution to resolve this?
Regards
Shaurya
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 53%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGI%3C/text%3E%3C/svg%3E)
The only way I was able to find around this issue was to use visual studio 2015 as the dev environment on a windows 10 machine, with the target computer running visual studio 2015 on server 2016 os. any later target os would not work. and if you use windows 10 for the target I do not know of a way to prevent it from updating to a later version which wont work. It's piss poor customer service for microsoft to have broken this middle of last year and it still be broken now.
Dear Greglven,
Thanks for your quick reply, could you please tell me the compatible version of wdk and sdk to be installed with these Operating systems at Target and Host PC.
Best Regards
Shaurya
I don't remember but if you go to the wdk and sdk pages and look at the older versions it will tell you which one to use for the target environment. Use the same for the dev computer as you use for the target computer.
SteeveP-2730 So you got your working? An it was an incompatability between the target os wdk and the host compiler version?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 36%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
The incompatibility is between the WDTF runtime .msi files that are part of the WDK installed on the host and the OS of the target.
VS Driver Test copies WDTF runtime .msi files from the host to the target during provisioning (Driver Test target device configuration). If the target is an earlier OS version than the host there is a very good chance (i.e. 100% in my case) that the copied WDTF runtime .msi will fail to install on the target when the host attempts to deploy a driver for testing.
WDTF runtime .msi files appear to be very OS-version sensitive yet they do not verify compatibility. This isn't reasonable but it's what we have to deal with.
I have asked MS to publicly document this ASAP. We'll see.
Thanks alot for the info. I'm guessing (hoping) that in my case the difference between home and pro was the problem. I have a new hard drive coming tomorrow the old has already been removed so I'll have to wait to check until the new drive and os upgrade to pro is done. It still doesn't explain the standalone install failing on the pro machine but if I can get it working on the target that will be good enough. From what few posts i've seen it looks like microsoft isn't putting a lot of development time into the wdtf so prolly not much support either.