[HLK] Driver attribute test fails with "Driver package folder is not specified."

Question

[HLK] Driver attribute test fails with "Driver package folder is not specified."

Abhishek Naik 20

Hello,

I am using VHLK to execute HLK test cases for my PCIe device.

All test cases are passing except the Driver Attribute Test. The test report shows the following error: Screenshot from 2026-02-20 12-22-36

From the logs, it appears that HLK Studio is unable to locate the driver package installed for the device.

However, I do not see any option in the test parameters to specify or provide the driver package path.

Is there a way to manually provide the driver package folder path?
Or is there a specific packaging or submission step that I may be missing?

Any guidance would be greatly appreciated.

Thank you.

VHLK Version: [Please specify version here]

Screenshot from 2026-02-20 12-24-44

Screenshot from 2026-02-20 12-25-33

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Tom Tran (WICLOUD CORPORATION) 4,765 Microsoft External Staff Moderator

Hi @Abhishek Naik ,

Thanks for sharing your details and screenshots!

From my understanding, the Driver Attribute Test (ApiValidator) depends on an internal parameter named QueryValidateDriverFolder, which represents the path to the driver package being validated. If HLK cannot resolve this path, the test will fail early with the message you’re seeing. Microsoft’s test definition confirms that this parameter must point to the driver folder under validation.

In HLK, this value is not manually entered in the test UI. Instead, it is automatically populated from the driver package that is associated with the project in the Package tab.

In most cases, this failure occurs when the driver package has not been added (or does not match the installed driver) in the project package configuration.

Could you please verify the following:

Open your project in HLK Studio
Go to the Package tab
Confirm that your driver was added using Add Driver Folder

Per the HLK workflow, the driver package used for testing should be added from the Package tab prior to running ApiValidator/Driver Attribute tests.

I also found a similar post, perhaps you could find some useful information in it:

https://community.osr.com/t/hlk-apivalidator-queryvalidatedriverfolder-missing/59336/2

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classifies as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Hope this helps! If you have any questions, please feel free to comment below. I'll be happy to assist!

Tom Tran (WICLOUD CORPORATION) 4,765 Reputation points Microsoft External Staff Moderator

2026-03-02T06:53:41.7+00:00

Hi @Abhishek Naik ,

I'm just checking in to see if you have any questions, please feel free to comment below. I'll be happy to assist!
Tom Tran (WICLOUD CORPORATION) 4,765 Reputation points Microsoft External Staff Moderator

2026-03-10T02:29:17.4233333+00:00

Hi @Abhishek Naik ,

It's been a while since we last heard from you. Hope things are going well.

If you're still interested or have any questions, feel free to reach out whenever it works best for you.
Tom Tran (WICLOUD CORPORATION) 4,765 Reputation points Microsoft External Staff Moderator

2026-03-16T07:01:23.4766667+00:00
Hi @Abhishek Naik ,

Thanks for the update.

Looking at the Required Driver Attributes test failure, HLK is able to resolve the expected driver path (system32\drivers\simamladrv.sys), but the test fails when Windows attempts to query file attributes for that driver binary. The 0xC0000225 status indicates that the driver file being queried cannot be located or does not match what HLK expects at runtime.

In practice, this usually points to a mismatch between the driver package added under the Package tab and the driver that is currently installed on the test machine. For example, this can happen if the driver was rebuilt or reinstalled after it was added to the project, or if the INF references a different .sys file name than the one that is actually loaded.

I would suggest checking the following:

The driver package added in the Package tab is the same build as the driver installed on the test system.

The INF file references the correct .sys file name.

After any rebuild, the driver is reinstalled on the test machine and the updated package is re‑added to the HLK project before rerunning the test.

Share via

[HLK] Driver attribute test fails with "Driver package folder is not specified."

0 additional answers

Your answer