Provisioning package error on windows 10 mobile 1607 for “Privacy/AllowInputPersonalization” customization RRS feed

  • Question

  • Using Windows imaging and configuration designer, I created a provisioning package containing only one customization. The customization is about setting the value of “Privacy/AllowInputPersonalization” to 0. At https://msdn.microsoft.com/en-us/library/windows/hardware/mt627979(v=vs.85).aspx it is stated that this setting can be applied to Windows 10 mobile.
    However when I try to add this package to windows mobile 10 1607 I get a provisioning error, I attach the detailed error.

             <Message>Provisioning failed.</Message>

    Can anyone help me in order to apply successfully the package?
    Thanks a lot

    • Edited by Ms578458 Sunday, August 28, 2016 9:36 PM
    Thursday, August 25, 2016 8:53 AM

All replies

  • The customizations.xml file related to the above provisioning package is:

    <?xml version="1.0" encoding="utf-8"?>
      <PackageConfig xmlns="urn:schemas-Microsoft-com:Windows-ICD-Package-Config.v1.0">
      <Settings xmlns="urn:schemas-microsoft-com:windows-provisioning">

    The provisioning error happens on a clean install of windows 10 1607. The problem happens also building the same package customization with the desktop as the target. Opening the Project_33.ppkg file with notepad I can read these xml lines:

      <characteristic type="Policy">
        <characteristic type="Config">
          <characteristic type="DataProtection">
            <parm name="AllowInputPersonalization" value="0" datatype="integer" />

    Maybe the "DataProtection" node should be "Privacy". But I am just guessing. I hope someone at Microsoft will look into this.

    • Edited by Ms578458 Sunday, August 28, 2016 9:36 PM
    Sunday, August 28, 2016 9:25 PM
  • Hello Ms578458,

    could you tell me how you created a package for your 1607 build of mobile?

    Could you please get the latest version of the ADK (link) please?

    Wednesday, September 14, 2016 10:57 PM
  • As I wrote on my first post I used Windows imaging and configuration designer, in particular I am using Windows ADK for Windows 10, version 1607.

    Thursday, September 15, 2016 8:22 AM
  • Ms578458,

    I just tried this on my end and had no problems. While that doesn't necessarily help you, atleast I can tell its not a bug in general. Its possible the engine that processes the package has managed to corrupt itself somehow though. Could you try removing the package and retrying please?

    Barring that, a full device reset may be the only way to recover at this point.

    Thursday, September 29, 2016 10:05 PM