How to fix "No SKU information file" when calling icd.exe

Question

Here is my customization.xml template from the official Microsoft blog: https://learn.microsoft.com/en-us/windows/configuration/provisioning-packages/provisioning-multivariant

<?xml version="1.0" encoding="utf-8"?>
<WindowsCustomizations>
 <PackageConfig xmlns="urn:schemas-Microsoft-com:Windows-ICD-Package-Config.v1.0">
   <ID>{6aaa4dfa-00d7-4aaa-8adf-73c6a7e2501e}</ID>
   <Name>My Provisioning Package</Name>
   <Version>1.0</Version>
   <OwnerType>OEM</OwnerType>
   <Rank>50</Rank>
 </PackageConfig>
 <Settings xmlns="urn:schemas-microsoft-com:windows-provisioning">
   <Customizations>
     <Common>
       <Policies>
         <AllowBrowser>0</AllowBrowser>
         <AllowCamera>0</AllowCamera>
         <AllowBluetooth>0</AllowBluetooth>
       </Policies>
       <HotSpot>
         <Enabled>0</Enabled>
       </HotSpot>
     </Common>
   </Customizations>
 </Settings>
</WindowsCustomizations>

I`m trying to use the icd.exe CLI tool to create the PPKG following the official documentation: https://learn.microsoft.com/en-us/windows/configuration/provisioning-packages/provisioning-command-line

Here is my command and error output:

icd.exe /Build-ProvisioningPackage /CustomizationXML:customizations.xml /PackagePath:enrollment.ppkg
Microsoft (C) Windows Imaging and Configuration Designer
ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'AllowBrowser' is not a valid child node for /Policies
ICD.exe : ERROR: C:\Users\milki\OneDrive\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20230801-160759-632_17636.log

Here is the full error log:

8/1/2023 4:07:59 PM Info ICD Started 8/1/2023 4:07:59 PM Info Command line input: "C:\Users\milki\AppData\Local\Microsoft\WindowsApps\ICD.exe" /Build-ProvisioningPackage /CustomizationXML:customizations.xml /PackagePath:enrollment.ppkg 8/1/2023 4:07:59 PM Info Current directory: C:\Users\milki\Documents 8/1/2023 4:07:59 PM Info Attempting to DPAPI decrypt customization XML C:\Users\milki\Documents\customizations.xml. 8/1/2023 4:07:59 PM Info Customization XML could not be decrypted as it's most likely not encrypted. The data is invalid.  8/1/2023 4:07:59 PM Info StoreFile path: C:\Program Files\WindowsApps\Microsoft.WindowsConfigurationDesigner_2023.728.0.0_x86__8wekyb3d8bbwe\ICD\Microsoft-Common-Provisioning.dat 8/1/2023 4:07:59 PM Info Loaded Knobs schema hive at C:\Program Files\WindowsApps\Microsoft.WindowsConfigurationDesigner_2023.728.0.0_x86__8wekyb3d8bbwe\ICD\Microsoft-Common-Provisioning.dat 8/1/2023 4:07:59 PM Error WpxGetFileEdition (onecore\base\ntsetup\wpx\core\store.cpp:103) - 0x80070002: 8/1/2023 4:07:59 PM Error     No SKU information file C:\Program Files\WindowsApps\Microsoft.WindowsConfigurationDesigner_2023.728.0.0_x86__8wekyb3d8bbwe\ICD\Microsoft-Common-Provisioning.sku.xml available for store file C:\Program Files\WindowsApps\Microsoft.WindowsConfigurationDesigner_2023.728.0.0_x86__8wekyb3d8bbwe\ICD\Microsoft-Common-Provisioning.dat 8/1/2023 4:07:59 PM Info Loaded settings from Windows Unknown Unknown 8/1/2023 4:07:59 PM Error WpxConfig::FindSchema (onecore\base\ntsetup\wpx\core\config.cpp:162) - 0x80070490: 8/1/2023 4:07:59 PM Error     Couldn't find schema path for AllowBrowser under /Policies 8/1/2023 4:07:59 PM Error WpxSetting::GetChild (onecore\base\ntsetup\wpx\core\setting.cpp:249) - 0x80070490: 8/1/2023 4:07:59 PM Error     Couldn't find schema for answer path /Policies/AllowBrowser 8/1/2023 4:07:59 PM Error WpxWpafReader::ReadSettingsTree (onecore\base\ntsetup\wpx\file\wpafreader.cpp:628) - 0x8007000d: 8/1/2023 4:07:59 PM Error     Unrecognized child AllowBrowser specified for tree setting /Policies 8/1/2023 4:07:59 PM Error WpxWpafReader::ReadSettingsTree (onecore\base\ntsetup\wpx\file\wpafreader.cpp:639) - 0x8007000d: 8/1/2023 4:07:59 PM Error     Couldn't read answers under /Policies 8/1/2023 4:07:59 PM Error WpxWpafReader::ReadCommonSettings (onecore\base\ntsetup\wpx\file\wpafreader.cpp:197) - 0x8007000d: 8/1/2023 4:07:59 PM Error     Couldn't read common settings 8/1/2023 4:07:59 PM Error WpxWpafReader::Read (onecore\base\ntsetup\wpx\file\wpafreader.cpp:78) - 0x8007000d: 8/1/2023 4:07:59 PM Error     Failed to read common settings node 8/1/2023 4:07:59 PM Error WpxConfig::ReadAnswerFile (onecore\base\ntsetup\wpx\core\config.cpp:598) - 0x8007000d: 8/1/2023 4:07:59 PM Error     Failed to load answer file 8/1/2023 4:07:59 PM Error The following errors were detected in customizations: Settings were not found in the store file. Parse error (0x80070490): 'AllowBrowser' is not a valid child node for /Policies  8/1/2023 4:07:59 PM Error Microsoft.Windows.ICD.Common.Exceptions.CustomizationsException: The following errors were detected in customizations: Settings were not found in the store file. Parse error (0x80070490): 'AllowBrowser' is not a valid child node for /Policies     at Microsoft.Windows.ICD.Provisioning.ImageCustomization.ImageCustomizations.ReadAndValidateWPXAnswerFile(Config wpxConfig, XDocument wpxDocument, Boolean ignoreWpxParseErrors)    at Microsoft.Windows.ICD.Provisioning.ImageCustomization.ImageCustomizations.Load(XDocument customizationsXDoc, Boolean onlySettings, Boolean ignoreWpxParseErrors)    at Microsoft.Windows.ICD.Provisioning.ImageCustomization.ImageCustomizations.CreateAndLoadAnswers(XDocument customizationsXDoc, IStoreConfig storeConfig, Boolean ignoreWpxParseErrors, Boolean isMobile)    at Microsoft.Windows.ICD.Core.Common.Project.LoadCustomizations(XDocument customizationsXDoc)    at Microsoft.Windows.ICD.Core.Common.Project.CreateFromStoreFile(IEnumerable`1 storeFilePaths, String location, XDocument customizationsXDoc, InvocationMode invocationMode)    at Microsoft.Windows.ICD.Core.CLI.BuildPackageCmdHandler.Execute()

What im doing wrong? Is there any issues with my system or with the documentation?
My OS specs:
Windows 11 Pro 22H2

Thanks for any help!

Answer 1

Hello there,

The error message "No SKU information file" typically occurs when calling the "icd.exe" (Intel(R) Integrated Clock Driver) executable on Windows. This error indicates that the necessary SKU (Stock Keeping Unit) information file is missing or not accessible to the icd.exe application. To fix this issue, you can try the following steps:

Check if icd.exe is in the correct location: Ensure that icd.exe is present in the correct directory from which you are trying to execute it. If it's not in the same directory, either move icd.exe to the correct location or specify the full path when executing it.

Check for missing dependencies: icd.exe may require specific DLL files or other dependencies to function correctly. Make sure that all required dependencies are present in the same directory as icd.exe or installed in the system.

Update the driver: If you are using icd.exe to manage Intel Integrated Clock Driver, check if there is a newer version available for download. Updating the driver to the latest version may resolve the issue.

Run as Administrator: Sometimes, the error can be caused by insufficient permissions. Try running the command prompt or the script that calls icd.exe as an administrator. Right-click on the Command Prompt or the script and choose "Run as administrator."

Check for Antivirus or Security Software: It's possible that antivirus or security software is blocking the execution of icd.exe due to false positives or unknown behavior. Temporarily disable such software and see if the error persists.

Check Event Viewer: If the error persists and you cannot find a solution, check the Windows Event Viewer for any additional error messages or clues that might shed light on the issue.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer--

Answer 2

I've been working a lot with WCD recently, and have been experiencing issues whereby the Bulk Token is expiring. Which led me down the path of finding ways to recreate the bulk token for an existing provisioning package. As a result, I stumbled across Michael's blog post at Simplify the process of generating an AAD bulk enrollment provisioning package – Out of Office Hours (oofhours.com)

Which then sent me down another rabbit hole, of wondering if I could simply create my desired PPKG automagically, using this code.

Seeing that Michaels script simply builds the XML on the fly, I thought I could be clever and simply throw in the XML code from customisations.xml which was generated by the WCD GUI.

In doing so, this returned errors similar to the above.

Reviewing the generated log file referenced in the error, hinted at the Store File being the issue.

12/29/2023 1:17:59 PM Info StoreFile path: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.dat
12/29/2023 1:17:59 PM Info Loaded Knobs schema hive at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.dat
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM Info Loaded settings from Windows Unknown Unknown
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
12/29/2023 1:17:59 PM 
Settings were not found in the store file.
Parse error (0x80070490): 'DevDetail' is not a valid child node for /

Being familiar with Windows Configuration Designer and Answer Files and what not, I am familiar with the different layers and levels of customisations. As such, I explored the Store File referenced, and found there is a variety of Provisioning DAT files. (HoloLens, Desktop, Team, Mobile etc)... as an attempt at a quick fix, I simply renamed Microsoft-Desktop-Provisioning.dat to Microsoft-Common-Provisioning.dat, backing up the old file in the process, and attempted to generate the PPKG again using Michaels script.

This time it was a success. Suggesting that the COMMON.dat being called by default isn't all encompassing.

Further reading of the ICD help articles on the Microsoft site revealed that you can indeed call the specific Store file, so appending /StoreFile:"$kitsRoot\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Desktop-Provisioning.dat" should work, but it seems like there's a bug in ICD preventing more than two params being called.

As such, I created a hacky song and dance in the script that renames the existing Microsoft-Common-Provisioning file, creates a copy of the Desktop file in its place, creates the package, and then returns things to normal.