Hi Kai!
In my experience, I have seen this failure once.
It was due to syntax errors in the INF driver file.
I suggest you check it.
Hope this helps.
[HLK] Driver attribute test fails with "Driver package folder not found"
![](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(294.40000000000003, 78%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKL%3C/text%3E%3C/svg%3E)
Kai Liu
0
Reputation points
Hello,
I am using HLK (Server Side) to execute HLK test cases for my TouchScreen device system 25H2 (Client Side).
All test cases are passing except the Driver Attribute Test. The test report shows the following error :
Test Authoring and Execution Framework v10.99k for x64 StartGroup: Microsoft.Hardware.Kits.Tests.DriverCatalogHlkTest.DrvCatHlk.ValidateWDKDriverAttributes Verify: IsNotNull(WEX.TestExecution.TestContextImplementation) Error: Driver package folder not found: C:\Windows\System32\DriverStore\FileRepository\input.inf_amd64_11c43843cd0e7ff2 EndGroup: Microsoft.Hardware.Kits.Tests.DriverCatalogHlkTest.DrvCatHlk.ValidateWDKDriverAttributes [Failed]
I noticed that on the HLK Server, the driver package path ends with input.inf_amd64_xxxxxx9a46d8, while on the Client device, it is input.inf_amd64_xxxxxxa38ce.
It appears that the server consistently keeps referencing a path ending with something like e7ff2. However, this directory does not actually exist on the system.
Would removing and re-adding the device ( which would require re-running all tests ) actually resolve the issue, or is there a better solution ?
Thank you.
Windows development | Windows Driver Kit (WDK)
-
Kai Liu 0 Reputation points
2026-06-24T07:06:30.12+00:00 Additionally, could this issue be caused by an incomplete HLK Client installation on the client side, such that reinstalling the HLK Client would resolve it ?
Alternatively, could this be due to a missing or incorrect driver package provided by the OEM?
Sign in to comment
1 answer
Sort by: Oldest
-
Darth Tester 70 Reputation points2026-08-17T14:14:57.8533333+00:00 -
Kai Liu 0 Reputation points
2026-08-20T09:16:01.8+00:00 Hi Darth. Thanks for your suggestion.
This issue appears to be that the server continuously requests an INF file that does not exist, while the client machine does not have the corresponding INF file available.
Perhaps removing and re-pairing the HLK client could help resolve the issue. Alternatively, the ODM could provide another machine for me to verify the issue.
However, as all testing has already been completed, and in my case the device is the touchscreen, I would prefer not to re-run everything from the beginning.
-
Kai Liu 0 Reputation points
2026-08-25T05:35:26.39+00:00 Update: Verification passed on a new system provided by the ODM, which suggests the failure was related to platform differences on the original system.
-
Sign in to comment -