you can now build drivers for Windows 10.
The implementation of this is a bit complex, partly to keep the manual tasks to a minimum and partly to jump through the various signing hoops and as such there are quite a few loose ends.
We’ll have to discuss the priority of these in the light of other pressing work.
Windows 7 and XP are not catered for at all right now.
Obviously with something this complex I can’t guarantee it will work smoothly immediately but it does appear to work well. Ideally I’d like you to start using this when we are both around; but if you need to release something over the weekend there’s no harm in trying so long as it’s not a critical delivery.
The following are the steps to build a driver. IMO it’s very simple and once you’ve done it once or twice I hope it will be clear.
If there is no cached package it will fail like this.
A batch job will fail and keep retrying until resolved.
I intend to have an email be sent to you and / or I when this happens but this is not currently in place.
On Webtba3 go to d:\config\v6\windows_signing (I suggest having a desktop shortcut).
There will be one or more folders with encoded names as below.
Each of these represents a job to be submitted to MS.
If there are multiple jobs you can submit them all; you don’t have to track them as the system takes care of where to apply the results.
But if you are in a hurry the folder name is the package key as shown in the tba release output and you can submit just that one if needed.
Open the folder and you should see a single file updd.cab. This is the file we will submit to Microsoft.
Go to https://partner.microsoft.com/en-US/dashboard/hardware/driver/New **using Chrome** it’s easiest to do this on webtba3 but not essential..
Log in as gary@touchbaseltd.onmicrosoft.com password Cy2ZYFqkv39Kuc4F
You should see this
Enter the product name (I see no reason to enter anything other than UPDD) and drag updd.cab to the area shown.
As a short delay the screen shows these fields and you should make the selections shown below.
This is all signatures excluding ARM64. Currently the top 2 and five remaining boxes should be unchecked.
Click submit
You now see...
Certification form complete
You have completed the certification application, but Microsoft needs to process your package before this step is marked as complete.
After a while (5 - 10 mins) you should see this. Select 'more'
And then Download files. You should do this on webtba3
Chrome will download the signed files to your downloads folder and the system can grab the needed files from there.
Generate the release again it should now work with a result like this.
The system will delete the processed interim files when no longer needed and you should not do this yourself.
If processing a batch you can run any Windows release to trigger the epilog and housekeeping processing .