I cannot actually share the inf. However, it is in this format:
[SourceDisksNames.x86]
1000 = %str%,“”,\serial\i386
[SourceDisksNames.amd64]
1000 = %str%,“”,\serial\amd64
[SourceDisksNames.arm]
1000 = %str%,“”,\serial\arm
[SourceDisksFiles]
driverName.sys = 1000
*Warm regards,*
Parinitha Kashyap
On Tue, Oct 17, 2017 at 5:34 PM, Zac Lockard
wrote:
> Can you share your INF? If it’s happening in the 1703 version it’s likely
> a real INF error
>
>
>
> From: Parinitha Kashyap [mailto:xxxxx@gmail.com]
> Sent: Tuesday, October 17, 2017 4:57 PM
> To: Windows System Software Devs Interest List
> Cc: Zac Lockard
> Subject: Re: [ntdev] [SourceDiskNames] failure in DF - InfVerif INF
> Verification test: Error 1273
>
>
>
> Hello,
>
>
>
> I installed HLK version 1703 and installed a new windows version 1703
> build as well on my client machine to get rid of [SourceDiskNames] error as
> per the above mail while running DF - InfVerification test on my usb serial
> driver. However, I am still getting the same error 1273 “source file —
> uses disk id 1 which is not listed under [SourceDiskNames].” Again, I
> applied the latest HLK filters to the test. I am still failing with the
> same error.
>
>
>
> Please help.
>
>
> Warm regards,
>
> Parinitha Kashyap
>
>
>
> On Fri, Oct 13, 2017 at 2:28 PM, Parinitha Kashyap <
> xxxxx@gmail.com> wrote:
>
> The following is specified in this blog:
>
> https://blogs.msdn.microsoft.com/windows_hardware_
> certification/2017/04/05/submissions-using-windows-10-
> version-1703-are-now-being-accepted/
> https:
>
>
>
> “When submitting a Windows 10, version 1703 HLK package for validation,
> you must use Windows 10, version 1703 build 15063 or newer on the test
> device. The submission will otherwise be rejected.”
>
>
>
> So do I need to update my client windows build to 1703 as well or can I
> continue running 1607 while I update my HLK build to 1703?
>
>
> Warm regards,
>
> Parinitha Kashyap
>
>
>
> On Fri, Oct 13, 2017 at 2:22 PM, Parinitha Kashyap <
> xxxxx@gmail.com> wrote:
>
> Oh. So I need to install HLK 1703? I have the client running windows
> version 1607. Is that ok? Can I submit a package of client running 1607 via
> HLK running 1703?
>
>
> Warm regards,
>
> Parinitha Kashyap
>
>
>
> On Fri, Oct 13, 2017 at 2:12 PM, xxxxx@microsoft.com <
> xxxxx@lists.osr.com> wrote:
>
> This is fixed in any newer version of the HLK, the 1607 InfVerif did not
> like architecture decorations in SourceDisksNames/Files
>
>
>
> From: xxxxx@lists.osr.com [mailto:bounce-639959-173172@
> lists.osr.com] *On Behalf Of *xxxxx@gmail.com
> Sent: Friday, October 13, 2017 12:00 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] [SourceDiskNames] failure in DF - InfVerif INF
> Verification test: Error 1273
>
>
>
> Hello all,
>
>
>
> I am running the above test on USB serial driver. However, the error I am
> getting is 'Disk id [some number] specified in the [SourceDiskFiles]
> section is not mentioned in [SourceDiskNames]. But, the no. is mentioned in
> specific architecture [SourceDiskNames] sections like
> [SourceDiskNames.x86], [SourceDiskNames.amd64] etc.
>
>
>
> I am using HLK version 1607. I have found similar threads on msdn forum
> but there have been no answers yet. Is there any workaround for this? I
> have also tried applying the latest hlk filters but its still no use.
>
>
>
> Looking forward to your suggestions. Thank you.
>
>
>
> Warm regards,
>
> Parinitha Kashyap
>
> — NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
> on crash dump analysis, WDF, Windows internals and software drivers!
> Details at To unsubscribe, visit the List Server section of OSR Online at
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev
> https:>
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:> https:>
>
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer
> https:>
>
>
>
>
>
>
>
></https:></https:></http:></https:></http:></https:>