Forum Discussion
Driver signing (EV certificate) fails before 9am.
I would be nice to be able to codesign my driver before 9am sometimes, being in Japan that presumably means before midnight GMT. If I try, I get an error "future date" from the Validation section in New Hardware Submission. Unless it is something I do wrong? I do use " /uselocaltime".
This is not a new issue, never been able to. Wait until 9am and codesign of the very same binary works fine.
1 Reply
The failure before 09:00 Japan time is consistent with mixing local-date and UTC validation. The uselocaltime option makes Inf2Cat evaluate DriverVer against the local calendar date, while Microsoft’s signing pipeline and other packaging steps can evaluate timestamps in UTC. Before 09:00 JST, Japan is already on the next date while UTC is still on the previous date, so a package stamped with Japan’s date can appear future-dated. For a release package, remove uselocaltime and use UTC consistently when StampInf and Inf2Cat generate and validate DriverVer. Rebuild the catalog from the final INF files rather than reusing an earlier catalog. Then sign the catalog with SignTool using SHA-256 for both the file digest and RFC 3161 timestamp digest, and verify the completed signature. Keep local-time validation only for a controlled workflow where every tool uses the same basis. This avoids a daily time-dependent submission failure.
