I am not clear for how to package our firmware binary update package for windows -based uefi

yifei fan 0 Reputation points
2026-02-05T07:33:13.16+00:00

My requirement is: We produce touchscreen chips and are currently collaborating with HP/Lenovo to integrate them into HP tablets as touchscreens. HP/Lenovo plans to install the Windows operating system on these tablets. The firmware update for our touchscreen will be completed through Windows' firmware update uefi process. How should we package our touchscreen firmware update, and ultimately provide it to Windows Update? (As far as I know, it seems to require files like touchscreenfirmware.bin, INF, .cap, .cab, etc.). Is there a specific packaging process, as well as the tools used? Thank you.

Microsoft Partner Center API

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. AI answer

    2026-02-05T07:33:26.5666667+00:00

    To package your touchscreen firmware update for Windows-based UEFI, you will need to follow the guidelines for creating a firmware update package that aligns with the Windows UEFI firmware update platform. Here are the key steps and components involved in the packaging process:

    1. Firmware Update Package Structure: Your firmware update package should include the following components:
      • A binary file containing the firmware image (e.g., touchscreenfirmware.bin).
      • An INF file that describes the firmware update and its installation process.
      • Optionally, you may also include a .cap file if needed, and you may package everything into a .cab file for distribution.
    2. Driver Package Creation: The firmware update should be delivered as a device driver package (INF). This allows Windows to manage the update process using existing deployment and servicing tools. The INF file should specify the firmware binary and any necessary metadata about the update.
    3. Using UEFI UpdateCapsule: Once the firmware update package is on the end user's system, Windows will utilize the UEFI UpdateCapsule function to hand off the firmware payload to the platform firmware for processing. This is a critical step in ensuring that the firmware is applied correctly.
    4. Certification and Signing: After authoring the update package, it must be submitted to Microsoft for certification and signing. This step is essential to ensure that the firmware update is trusted and can be delivered through Windows Update.
    5. Testing and Validation: Before distributing the firmware update, it's important to validate that the update process works correctly on the target devices. This may involve checking that the devices are functioning properly after the update and ensuring that rollback policies are in place if necessary.
    6. Tools: You may use various tools provided by Microsoft for authoring and testing your firmware update package. Ensure that you are familiar with the Windows Hardware Dev Center and the tools available for driver package creation.

    By following these steps, you can effectively package your touchscreen firmware update for integration with Windows Update and ensure a smooth update process for end users.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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