Errors and Solutions When Submitting Device Metadata Experiences

When you submit device metadata experiences for validation and publication, you may see errors that can affect the release of your experience.

Common errors

Here are some of the most common errors, listed in alphabetical order, and including solutions if available.

To solve common errors

Error	Suggested solution
[CategoryName] Category id is incorrect in Behavior.xml. Correct Category id is [CategoryId]	For more information, see the Microsoft Device Experience Development Kit.
[CategoryName] Guid [CategoryId] is required for your device in Behavior.xml.	For more information, see the Microsoft Device Experience Development Kit.
[FolderName] folder is missing.	One of your folders is missing. For more information, see the Microsoft Device Experience Development Kit.
[FolderName] folder name is required in <PackageStructure> element in PackageInfo.xml.	You must include the correct folder name reference in PackageInfo.xml. For more information, see the Microsoft Device Experience Development Kit.
[ImageType] Image – [FileName] size for [SplitType] split is invalid. Valid size(s) are: [ListOfAllowedSizes]	For more information, see the Microsoft Device Experience Development Kit.
[ImageType] Image – [FileName] size is invalid. Valid size(s) are: [ListOfAllowedSizes]	For more information, see the Microsoft Device Experience Development Kit.
[TaskGroupName] Guid [TaskGroupGuid] is not referenced for the task [TaskId] in Behavior.xml	For more information, see the Microsoft Device Experience Development Kit.
[TaskName] Task – [TaskId] is required for your device within the System Settings category in Behavior.xml.	The Action Center task and System Settings task must appear under the System Settings category in Device Stage for your device. For more information, see the Microsoft Device Experience Development Kit.
[TaskName] Task – [TaskId] should reference taskGroupGuid [TaskGroupGuid] for your device in Behavior.xml.	For more information, see the Microsoft Device Experience Development Kit.
[TaskName] task [TaskId] is required to exist at root for your device in Behavior.xml.	For more information, see the Microsoft Device Experience Development Kit.
DeviceStageDevice[Locale] and DeviceStageDevice folders should have same files.	If this package is set to be the default locale, the locale directory and the language-neutral directory must have the same files. For more information, see the Microsoft Device Experience Development Kit">.
A .cab submission needs to contain either Hardware and/or Model information. Please correct the .cab or modify the existing .cabs.	Your package must contain at least one hardware ID or model ID. For more information, see the Microsoft Device Experience Development Kit.
A Hardware ID in this .cab is in conflict and the .cab cannot be uploaded. Please ensure no other experience you have created uses this Hardware ID.	Your hardware ID has been used in another one of your experiences. On the dashboard, under Device metadata, open the Manage experiences page. In the filter, enter the hardware ID to find the other experience. You can then resolve any conflicts. For more information, see Device Metadata Business Rules.
A Hardware ID in this. cab is in use by another company and the .cab cannot be uploaded. Please verify this Hardware ID.	The hardware ID you have included in your package is in use by another company. You can't submit a hardware ID for another company. Make sure that your hardware IDs are not misspelled. If you still receive an error message, contact Dashboard Support.
A live submission already exists for this locale in this experience.	Delete the existing live package for the locale before you upload a new package for the same locale.
A live submission already exists with default locale set to true in this experience.	Only one live package in an experience can be set as the default package. For more information, see Device Metadata Business Rules.
A logo submission for a MultiPurpose device does not match the submission category.	The device category listed in your logo submission doesn't match the primary device category of your device metadata package. To resolve this problem, follow these steps: - Correct the device category for your logo submission. - Create a new experience and only bind the correct logo submissions.
A Model ID in this cab is in conflict and the cab cannot be uploaded. Please ensure no other experience you have created uses this Model ID.	Your model ID has been used in another one of your experiences. On the dashboard, under Device metadata, open the Manage experiences page. In the filter, enter the model ID to find the other experience. You can then resolve any conflicts. For more information, see Device Metadata Business Rules.
A Model ID in this cab is in use by another company and the cab cannot be uploaded. Please verify this Model ID.	The model ID you have included in your package is in use by another company. You can't submit a model ID for another company. Make sure that your model IDs are not misspelled. If you still receive an error message, see Partner Center dashboard technical support.
A non-preview live package cannot be promoted to live.	You can't promote a live package to Live status.
A package with a status of error cannot be promoted to live.	You can't promote a package that contains errors to Live status.
A preview submission already exists for this locale in this experience.	To resolve this problem, try the following: - Delete the existing preview package for the locale, and then upload a new preview package for the same locale. - Promote the current preview package for the locale to Release status, and then upload a new preview package for the same locale.
A preview submission already exists with default locale set to true in this experience.	Only one preview package in an experience can be set as the default package. For more information, see Device Metadata Business Rules.
All device metadata .cab files in an experience must support the same Hardware IDs. Please correct the .cab.	This package does not have the same list of model IDs that the other packages in the experience have. Correct the model ID list in the package and upload the package again. For more information, see Device Metadata Business Rules.
Allowed Domain should not be empty for task [TaskID] in Tasks.xml.	For more information, see the Microsoft Device Experience Development Kit.
An unexpected file was found:'[ExtraFile]'. Please ensure you follow the architecture or reference all root files in PackageInfo.xml.	There are extra files at the root of your package. For more information, see the Microsoft Device Experience Development Kit.
An unexpected folder was found: ‘[ExtraFolder]'. Please ensure you follow the architecture or reference all root folders in PackageInfo.xml.	For more information, see the Microsoft Device Experience Development Kit.
CommandLine URL should not be null for task [TaskID] in Tasks.xml.	For more information, see the Microsoft Device Experience Development Kit.
Device Category not found in DeviceInfo.xml .	You must set a primary device category that is one of the pre-defined options. For more information, see the Microsoft Device Experience Development Kit.
Device folder not found in DeviceStage folder	For more information, see the Microsoft Device Experience Development Kit.
Device icon information not found in DeviceInfo.xml	If you include a device icon in the DeviceInfo.xml file, you must also include the device icon information. Device icons are required for Device Stage packages. For more information, see the Microsoft Device Experience Development Kit.
Device Metadata Category for this submission needs to match the existing experience category.	The category for the device in this package doesn't match the category in the other packages in this experience. Revise your device category and resubmit the package.
Device Metadata Submission Type for this submission needs to match the existing experience category.	The device metadata submission type is defined as either Device Stage or Devices and Printers. Only Device Stage packages can be included in a Device Stage experience. Similarly, only Devices and Printers packages can be included in a Devices and Printers experience.
Device Stage inbox submissions are not allowed for the computer device class.	If your package and experience are for Device Stage and a computer device, you must have already certified them for a logo, or you must certify them for a logo within 90 days.
Device Stage is not supported for this device.	The device category you have chosen is not supported in Device Stage.
Device Stage metadata cannot be submitted for your device [DeviceCategory]	Device Stage submissions are allowed only for the following devices: - Portable media players - Digital still cameras - Cellular phones - Printers or fax machines - Scanners -Computer systems
Device Stage requires either Marketing Bullets or Status Items to be present in Behavior.xml.	For more information, see the Microsoft Device Experience Development Kit.
Device Stage requires LaunchDeviceStageFromExplorer to be set to true for your device in WindowsInfo.xml.	For more information, see the Microsoft Device Experience Development Kit.
Device Stage requires LaunchDeviceStageOnDeviceConnect to be set to True for your device in WindowsInfo.xml	For more information, see the Microsoft Device Experience Development Kit.
Device Stage requires ShowDeviceInDisconnectedState to be set to True for your device in WindowsInfo.xml.	For more information, see the Microsoft Device Experience Development Kit.
Devices and Printers requires LaunchDeviceStageFromExplorer to be set to False for your device in WindowsInfo.xml.	For more information, see the Microsoft Device Experience Development Kit.
Devices and Printers requires LaunchDeviceStageOnDeviceConnect to be set to False for your device in WindowsInfo.xml.	For more information, see the Microsoft Device Experience Development Kit.
Error in xml file [FileName] : [Error]	The specified .xml file has failed because it contains one or more errors. Verify that the file is compliant with its corresponding schema and that the namespace is correct. For more information, see the Microsoft Device Experience Development Kit.
File [FileName] is different in DeviceStageDevice[Locale] and DeviceStageDevice folders.	If you have set this package as the default locale, the locale directory and the language-neutral directory must contain the same files. One of the following errors has occurred: - Files that have the same specified name exist in both directories but the files are different. - The specified file exists in only one directory.
File Name PackageInfo.xml is expected in <PackageStructure> element in PackageInfo.xml.	Your PackageInfo.xml file isn't correctly authored for your package. Each root object in the package must be referenced in the PackageInfo.xml file by using a <PackageStructure> node. For more information, see the Microsoft Device Experience Development Kit.
Filename [FileReference] is incorrect in <PackageStructure> element in PackageInfo.xml. Correct filename: PackageInfo.xml	The file name that you referenced by using the <PackageStructure> node in the PackageInfo.xml file is misspelled. Correct the error and resubmit your package. For more information, see the Microsoft Device Experience Development Kit.
For Printing and Scanning Devices, LaunchDeviceStageOnDeviceConnect needs to be set to False in WindowsInfo.xml.	For more information, see the Microsoft Device Experience Development Kit.
HardwareIDs in this submission: [list of Hardware ID(s)] are not owned by your company.	The hardware IDs listed use VIDs that your company does not own according to the respective SIGs. If this is incorrect, cpmtact Dashboard Support.
Hardware IDs in this submission: [list of Hardware ID(s)] do not match the expected list of Hardware IDs from SMBIOS.	The hardware IDs you have submitted are not generated from the SMBIOS information that you submitted together with the SMBIOSFields.xml file. Try one of the following solutions: - Regenerate the hardware IDs and include the correct hardware IDs in your package. - Update the SMBIOSFields.xml file to include the fields that are used to generate the correct hardware IDs. For more information, see the Microsoft Device Experience Development Kit.
Hardware IDs in this submission: [list of Hardware ID(s)] fail the Inbox Driver Distribution Agreement (IDDA) list validation.	The hardware IDs you have included in your package are not listed in the Inbox Driver Distribution Agreement (IDDA) with Microsoft. Remove these hardware IDs and resubmit.
Invalid scheme [Scheme] in Allowed Domain for task [TaskID] in Tasks.xml	URLs must begin with HTTP or HTTPs. For more information, see the Microsoft Device Experience Development Kit.
Locale not found or is incorrect in PackageInfo.xml	The locale tag in the PackageInfo.xml file must exist, be formatted correctly, and comply with RFC 4646. Correct the locale, and then resubmit your package.
Missing resource reference for [Id] in Resource.xml file in DeviceStageTask[TaskID][Locale] folder	For more information, see the Microsoft Device Experience Development Kit.
Model IDs are not allowed for [Device Class] submissions.	You can't use model IDs when you submit device metadata for this type of device class. Instead, use only the hardware IDs for your device. To find the hardware IDs for a computer device, see the Microsoft Device Experience Development Kit.
Model Name not found in DeviceInfo.xml	Your DeviceInfo.xml file isn't correctly authored. For more information, see the Microsoft Device Experience Development Kit.
No preview key can be found for this organization.	You must set your PreviewKey before you upload a preview package. For more information, see Device Metadata Business Rules.
PackageStructure node in PackageInfo.xml is invalid.	Make sure that your PackageInfo.xml file is correct. For more information, see the Microsoft Device Experience Development Kit.
Task [TaskGUID] is required for your device in Behavior.xml.	For more information, see the Microsoft Device Experience Development Kit.
Task [TaskID] should not use taskGroupGuid [TaskGroupGuid]	For more information, see the Microsoft Device Experience Development Kit.
TaskGroupGuid [TaskGroupGuid] should not be used by your device for task [TaskId]	You are trying to use a reserved GUID that doesn't apply to your device. Try one of the following solutions: - Do not use GUIDs for tasks that your device can't support. - If you are trying to create a task, generate a new GUID for the task. For more information, see the Microsoft Device Experience Development Kit.
TaskGroupGuid incorrect for taskId [TaskId] in Behavior.xml	Correct the task GUID, and then resubmit the package. For more information, see the Microsoft Device Experience Development Kit.
The [FileName] icon file in [FolderName] folder is missing image MissingImageSize.	Verify that the image size is present. If not, add the image size to the icon, and then resubmit the package. Note 256x256 image layers must be in the PNG compressed format. BMP format for this size is not allowed. If this size is present but in the BMP format, create the image in a PNG format for the size, add this image to the icon, and then resubmit the package. For more information, see the Microsoft Device Experience Development Kit.
The cab Friendly Name is not unique to the Experience. Please choose another name.	Create a new friendly name for the experience, and then resubmit it.
The CommandLine argument should point to a valid URL beginning with HTTP or HTTPS for task [TaskID] in Tasks.xml.	For more information, see the Microsoft Device Experience Development Kit.
The device category reported in your Device Metadata package and Logo Submission don't match. If the device category in the package is incorrect, please fix and upload again. If the device category in Logo Submission is incorrect, please fix in Submission Manager and try uploading your package again: [list of links per offending logo submission to SubmissionManager]	Device categories between bound logo submissions and device metadata must be identical for a submission to pass. Verify that your logo submissions all have the same device category, and that the device category is the same as the device category for your package. The links provided point to the Submission Manager, which will allow you to change the device category in the logo submission, if the category is incorrect. After all issues are resolved, resubmit your package.
The Device Metadata Category for this submission does not exist.	The device metadata category that you have used isn't valid. You must choose from the pre-defined device metadata categories outlined in the Windows Hardware Certification Kit (HCK).
The Experience name already exists for this organization.	Create a new experience that has a different name.
The provided Logo submissions do not share Hardware IDs or Model IDs with the Device Metadata submission.	The bound logo submissions must contain the hardware IDs in the device metadata packages in the experience.
The reference in PackageInfo.xml, DeviceInformation, was not found in the package.	The DeviceInformation folder reference is missing from the PackageInfo.xml file. For more information, see the Microsoft Device Experience Development Kit.
The reference in PackageInfo.xml, DeviceStage, was not found in the package.	The reference in the <PackageStructure> element in the PackageInfo.xml file is either misspelled or isn't located in the root in the package. Remove the reference, or add the correct file or directory. For more information, see the Microsoft Device Experience Development Kit.
The reference in PackageInfo.xml, WindowsInformation, was not found in the package.	The WindowsInformation folder reference is missing from the PackageInfo.xml file. For more information, see the Microsoft Device Experience Development Kit.
The submission contains [list of Hardware ID(s) and/or Model ID(s)] that are not covered via a logo submission.	Your package contains hardware IDs or model IDs that your logo submissions don't cover. Try one of the following solutions: - Correct the hardware IDs or model IDs in your device metadata package. - Create a new experience and bind only the associated logo submissions.
The system manufacturer for this computer submission does not match the organization of the submitting user.	The system manufacturer in the SMBIOSFields.xml file you submitted doesn't match the manufacturer in our records. Try one of the following solutions: - Correct the name of the system manufacturer, and then resubmit the package. - If the system manufacturer field is correct and your file doesn't pass, Go to Partner Center dashboard technical support.
The TaskID [TaskID] cannot be used with multiple TaskGroups.	Your Device Stage package contains a TaskID that is used with different TaskGroups. TaskIDs must be unique per TaskGroup and per task. For more information, see the Microsoft Device Experience Development Kit.
This preview key has been rejected. Please choose another value.	The PreviewKey you set by using the Dashboard isn't accepted. Submit a new PreviewKey.
Unexpected file found in [FolderName] folder- [ExtraFile]	There is an issue with your package structure. For more information, see the Microsoft Device Experience Development Kit.
Unexpected file found in [Path] folder – [ExtraFile]	There is an issue with your package structure. For more information, see the Microsoft Device Experience Development Kit.
Unexpected file found in the [locale] subfolder of task [TaskGroupGuid] folder – [FileName]	Remove the specified file, and then resubmit the package. For more information, see the Microsoft Device Experience Development Kit.
Unexpected folder found in [FolderName] folder- [ExtraFolder]	There is an issue with your package structure. Note This error may occur if the device category in the DeviceInfo.xml file isn't set correctly. For more information, see the Microsoft Device Experience Development Kit.
Unexpected folder found in [Path] folder – [ExtraFolder]	There is an issue with your package structure. For more information, see the Microsoft Device Experience Development Kit.
URL should not be a localhost for task [TaskID] in Tasks.xml.	For more information, see the Microsoft Device Experience Development Kit.
URL specified in the commandLine is not valid for task [TaskID] in Tasks.xml.	For more information, see the Microsoft Device Experience Development Kit.
Valid logo submission(s) are needed for [SubmissionType] metadata for [DeviceClass]	Digital still cameras and portable media players must have one or more Windows 7 or Windows Vista® logo submissions. Cellular phones must have one or more Windows 7 logo submissions.
You already have a preview submission for this Operating System Version. Remove the current Live submission.	You are trying to promote a preview package for a locale, but there is already a released package for that locale. If you want to promote this preview package, delete the released package first, and then try again.
You do not have access to this experience.	You are trying to gain access to an experience that doesn't belong to your company.
Your device cannot have the command value set to HostedSiteWithDevice for task [TaskID] in Tasks.xml.	For more information, see the Microsoft Device Experience Development Kit.
Your submission is blocked due to a Dashboard error. Go to [Partner Center dashboard technical support](./hardware-submission-support.md#technical-support-issues) for a resolution.	Contact Dashboard Support.

Related topics

Create a Device Metadata Experience

Submit a Device Metadata Package (Dashboard help)

Device Metadata Business Rules