none
Windows 10 LTSC 1809 , After Sysprep default user account does not contain sideloaded apps RRS feed

  • Question

  • Hi,

    Environment : Windows 10 LTSC 1809

    1) Loaded modified WIM file in to tablet.

    2) Create default user (Test)

    3) Sideload custom apps using default user. (DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:"c:\Setup\UI\xx.appx" /SkipLicense)

    4) Create multiple users.

    5) Sideloaded apps are available automatically in all user accounts.

    6) Login to default user (Test).

    7) Perform Sysprep with generalize, OOBE & Shutdown option.

    8) Sideloaded apps are not available in default user account from where sysprep operation was performed, Available in other user accounts.

    Another issue:

    If Sysprep is performed again, the apps which are provisioned using '/SkipLicense' are not running (Apps show as installed but cannot run them)
    Monday, May 27, 2019 2:34 PM

All replies

  • Hi,

    Thank you for posting in Microsoft TechNet Forum.

    Sideload Apps are only applicable in win10 Enterprise. In order to successfully sideload the app into the operating system, you need to either configure a particular group policy setting if the device is joined to a domain, or edit the local device policy settings (typing "gpedit.msc" into run prompt) if the device is not joined to a domain or can be locally configured within domain:

    Best regards,

    Hurry


    Please remember to mark the reply as an answer if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Tuesday, May 28, 2019 3:03 AM
  • Yes this policy is enabled but still not enabled in default user account.

    Another issue:

    If Sysprep is performed again, the apps which are provisioned using '/SkipLicense' are not running (Apps show as installed but cannot run them)

    The following is the unattended.xml file used during sysprep

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
    <InputLocale>en-us</InputLocale>
    <SystemLocale>en-us</SystemLocale>
    <UILanguage>en-us</UILanguage>
    <UILanguageFallback>en-us</UILanguageFallback>
    <UserLocale>en-us</UserLocale>
    </component>
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
    <UserAccounts>
    <LocalAccounts>
    <LocalAccount wcm:action="add">
    <Password>
    <Value>pa123</Value>
    <PlainText>true</PlainText>
    </Password>
    <Name>Operator</Name>
    <DisplayName>Operator</DisplayName>
    <Group>PowerUsers</Group>
                        </LocalAccount>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>pa123</Value>
                                <PlainText>true</PlainText>
                            </Password>
                            <Name>Admin</Name>
                            <DisplayName>Admin</DisplayName>
                            <Description>Admin</Description>
                            <Group>Administrators</Group>
                        </LocalAccount>
          <LocalAccount wcm:action="add">
                            <Password>
                                <Value>12345</Value>
                                <PlainText>true</PlainText>
                            </Password>
                            <Name>Service</Name>
                            <DisplayName>Service</DisplayName>
                            <Description>Service</Description>
                            <Group>Administrators</Group>
                        </LocalAccount>
                    </LocalAccounts>
    </UserAccounts>
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <HideLocalAccountScreen>true</HideLocalAccountScreen>
    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    <ProtectYourPC>1</ProtectYourPC>
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <NetworkLocation>Work</NetworkLocation>
    </OOBE>
    <TimeZone>Eastern Standard Time</TimeZone>
    <ComputerName>*</ComputerName>
    </component>
    </settings>
    <settings pass="generalize">
    <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
    <DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
    <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
    </component>
    </settings>
    </unattend>

    Tuesday, May 28, 2019 5:38 AM
  • Hi,

    Thank you for your feedback.

    As the article mentioned: Update a provisioned LOB app to a Windows image must be done for each user that has signed in to the PC running the Windows image.

    Please try to upgrade your windows to the latest version and check.

    Best regards,

    Hurry


    Please remember to mark the reply as an answer if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, May 29, 2019 8:10 AM
  • Hi,

    Is there anything else I can do to help you on this issue?

    Please feel free to contact me if you have any questions.

    Best regards,

    Hurry


    Please remember to mark the reply as an answer if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, May 31, 2019 1:12 AM
  • I have an issue for apps which are installed with /SkipLicense.

    During Audit mode sysprep, apps installed with /skiplicense works well.

    Running sysprep for the second time removes apps which were installed with /SkipLicense in audit mode.

    When I remove /Generalize option apps run without issue but I see Rearm count being same. This indicates that the sysprep is not successful.

    Friday, May 31, 2019 12:17 PM