signtool failure running msbuild SDV target due to invalid signtool switch /fdws

Wang, James H 21 Reputation points
2022-11-19T05:28:51.74+00:00

How do i get the tools to not generate a "/fdws" switch or the correct replacement?

I am using vs2017 and vs2019 with older WDK.

c:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Tracker.exe /d "C:\Program Files (x86)\MSBuild\15.0\FileTracker\FileTracker32.dll" /i C:\Users\xxx\test\repo3\zzzz\xxx_driver\x64\Release\xxx_ins.C1A4245F.tlog /r C:\USERS\xxx\TEST\REPO3\ZZZZ\XXX_DRIVER\X64\RELEASE\XXX_DRIVER.SYS /b MSBuildConsole_CancelEvent5923f589ec6a4fc78dbde34edb521498 /c "C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\signtool.exe" sign /ph /fd "SHA256" /fdws /sha1 "0041BB187ECD1C59A3C9F3DD8E7A93EA801B422C" C:\Users\jameswan\test\repo3\applications.wifi.killernetwork.metee\icps_install_driver\x64\Release\icps_install_driver.sys
SIGNTASK : SignTool error : Invalid option: /fdws [.........................]

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wang, James H 21 Reputation points
    2022-11-19T16:51:30.927+00:00

    sorry, another nevermind, please close this...

    it's just some kind of multi-WDK conflict.
    use vs2019 + WDK 10.0.22000.0, bypasses this problems, though i run into a different with with SDV CL failing (error MSB6006: "CL.exe" exited with code -1073740791)

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.