Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 13 November 2017

Kernel Debugging & Crash Analysis for Windows, Nashua (Amherst) NH, 4 December 2017

Writing WDF Drivers I: Core Concepts, Nashua (Amherst) NH, 8 January 2018

WDF Drivers II: Advanced Implementation Techniques, Nashua (Amherst) NH, 15 January 2018


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 5  
10 Nov 17 09:36
Aleh Kazakevich
xxxxxx@mail.ru
Join Date: 27 Jul 2015
Posts To This List: 46
Attestation signing and debug symbols

From recent time the portal issues a warning during attestation-signing a driver: This submission does not include symbols. Future versions of Windows will require symbols to be included in the symbol path of the submission. But when i put the .pdb files in a 'Symbols' directory and re-send the .cab archive the portal reject my submission with the following text: Your submission did not meet the package format requirements for Attestation. Common reasons for this are: files at the root of your cabinet, no driver files found, your package is corrupt, or no INFs present. You can find a step-by-step guide for creating your attestation package on MSDN. You can download your full error report here for more information about what went wrong and how to fix the issue. No inf files found in driver directory/directories: Symbols. This article confirms that this is a bug in the portal: Dashboard FAQ https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/dashboard-faq Currently, there is a bug when symbol files are included in the driver package and the submission will fail. ---- So, anybody know does the MS have a plans to fix this bug or not? :) Thank you.
  Message 2 of 5  
10 Nov 17 13:32
Alan Adams
xxxxxx@novell.com
Join Date: 20 Dec 2010
Posts To This List: 24
Attestation signing and debug symbols

> But when i put the .pdb files in a 'Symbols' directory and re-send the .cab > archive the portal reject my submission with the following text: The attested signing submissions allow for submitting more than one driver. Each driver goes in a separate subdirectory, just like the first driver must be. So I expect the "Symbols" directory is being treated just as any other driver subdirectory in the .CAB would, which is why you're seeing that an .INF was expected. Since the symbols are specific to each of the driver(s) included in the .CAB, perhaps they belong in the same directory as the driver itself. What happens if you simply put the .PDBs in with the actual driver? e.g. Serial.pdb sitting at peer with Serial.sys. Alan Adams Client for Open Enterprise Server Micro Focus xxxxx@microfocus.com
  Message 3 of 5  
13 Nov 17 02:14
Aleh Kazakevich
xxxxxx@mail.ru
Join Date: 27 Jul 2015
Posts To This List: 46
Attestation signing and debug symbols

Alan Adams wrote: > > What happens if you simply put the .PDBs in with the actual driver? > e.g. Serial.pdb sitting at peer with Serial.sys. A little unexpected, but it works. Submission complete without warnings or errors. Thank you, Alan.
  Message 4 of 5  
13 Nov 17 11:29
Alan Adams
xxxxxx@novell.com
Join Date: 20 Dec 2010
Posts To This List: 24
Attestation signing and debug symbols

> > What happens if you simply put the .PDBs in with the actual driver? > > e.g. Serial.pdb sitting at peer with Serial.sys. > > A little unexpected, but it works. > Submission complete without warnings or errors. Thanks for reporting back with the confirmation that it works. Only citing "in the symbols path of the submission" in the warning message definitely was ambiguous as to where exactly the symbol files had been expected to appear. Alan Adams Client for Open Enterprise Server Micro Focus xxxxx@microfocus.com
  Message 5 of 5  
16 Nov 17 12:30
Keith Kepler
xxxxxx@microsoft.com
Join Date: 16 Nov 2017
Posts To This List: 1
Attestation signing and debug symbols

We are in the process of updating our Attestation documentation page to make this clearer for you. But, you have done it correctly. We expect your symbols to be located in the same folder as your driver. https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-s igning-a-kernel-driver-for-public-release The updates will be in both "Create a CAB Files Submission" and an updated graphic in the "Create a Multiple Driver Submission" section calling out where PDBs should go.
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 00:34.


Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license