Upgrade windows 10 1803 to 1903 or 1909 ,or 2004 ERROR

Luong Lindquist 81 Reputation points
2020-12-14T15:52:44.387+00:00

Hello

I have download the ISO from Mircosoft Volume Licensing Service Center 1903 , 1909 and 2004 ISO.
I had Add Operating System Upgrade Package for all 3 Iso . I stop the WIM services and restarted and aslo reboot my SCCM server but still getting the same erros below:

What is the fixed for this? what is the support number for SCCM support?

Error: Data Source Information
• Source location: \*******\os\window 1909

Error: Index Export Information
• Image Index: 5
• Image Index Name: Windows 10 Pro

Error: Package Information
• Name: window 1909

Error: Errors
• The SMS Provider reported an error.
• ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
• Description = "Failed to export a single index to destination from a source WIM file";
• ErrorCode = 1078462229;
• File = "..\sspbootimagepackage.cpp";
• Line = 4928;
• ObjectInfo = "DISM.EXE";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
};

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,882 questions
0 comments No comments
{count} votes

Accepted answer
  1. Simon Ren-MSFT 29,956 Reputation points Microsoft Vendor
    2020-12-16T02:01:22.91+00:00

    Hi,

    Thanks for your reply and sharing.

    Microsoft distributes the last upgrades of Windows 10 builds in the install.esd format. In addition, recently in all distributions of Windows 8.1, Windows 10, instead of the install.wim file, install.esd is located. The file size with the esd extension is smaller, because it is compressed more strongly (a new type of compression is used). This compression type packs the Windows installation files even more and, as a result, the size of the install.esd file becomes less than the install.wim file by 30%.

    The inconvenience of using the install.esd file is that Dism refuses to mount this image and SCCM hasn't caught up yet. Accordingly, in such an image it is impossible to inject drivers and updates. Therefore, in this situation, the easiest way is to use DISM command to convert the install.esd file into install.wim and then copy this install.wim into the sources folder, delete install.esd and try the import again, it will now be successful.

    A similar thread for your reference: Importing a Windows 10 1903 OS Upgrade Package to SCCM

    Thanks for your time.
     
    Best regards,
    Simon


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Youssef Saad 3,401 Reputation points
    2020-12-15T07:22:41.313+00:00

    Hi @Luong Lindquist ,

    What is your current ConfigMgr version?

    Have you updated the Windows 10 ADK and WinPE? If not yet, you can follow the below guide:

    • Uninstall first Windows 10 ADK and winPE.
    • Restart the site server.
    • Download and install Windows 10 ADK and WinPE for 2004 version, I've written an article about this (you can use the translate option in the top-right of the blog if needed):
    • Windows 10 ADK and WinPE 2004 installation guide

    Regards,


    Youssef Saad | New blog: https://youssef-saad.blogspot.com
    Please remember to ** “Accept answer” ** for useful answers, thank you!

    1 person found this answer helpful.
    0 comments No comments

  2. Simon Ren-MSFT 29,956 Reputation points Microsoft Vendor
    2020-12-15T07:28:00.737+00:00

    Hi,

    Thanks for posting in TechNet.

    May we know what version of ConfigMgr you are you using? It's recommended to upgrade to latest ConfigMgr version 2006 or 2010 to get better support for Windows 10. How about creating a upgrade package that include all image indexes?

    Starting in ConfigMgr version 1910, we can extract a specific image index from install.wim file of selected upgrade package and then select an image index from the list, this option automatically imports a single index rather than all image indexes in the file.

    Please refer to: Manage OS upgrade packages with Configuration Manager

    Thanks for your time.
     
    Best regards,
    Simon


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Luong Lindquist 81 Reputation points
    2020-12-15T13:43:10.977+00:00

    I was able to get it working. What I did was downnload microsoft creation tools and download the windows 10 as ISO. ( latest windows version 20H2)
    I took the Install.esd and convert it to Install.wim then create my operating system Upgrade Packages with no issued then did a test deploy to a test pc and it went through with out any issued.

    I guess the 3 ISO from Mircosoft Volume Licensing Service Center 1903 , 1909 and 2004 Install.wim is no good? Not sure
    when i try these the ISO i get the above error.