none
SplitWim option makes Media creation fails: Could not find file RRS feed

  • Question

  • Hi all,

    I want to use the SplitWim option in order to create a UEFI Media but when I set SkipWimSplit to False in my Settings.xml file I keep getting an error when I attempt to generate the Media.

    I can see MDT splitting my wim file into swm pieces but it throws the error below and cancels the operation:

    Starting MDT Media Update
    Opened the media deployment share.

    System.Management.Automation.CmdletInvocationException: Could not find file 'X:\MDTBuildProd\Operating Systems\REFW10-X64-001\REFW10-X64-001.wim'. ---> System.IO.FileNotFoundException: Could not find file 'X:\MDTBuildProd\Operating Systems\REFW10-X64-001\REFW10-X64-001.wim'.
       à System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       à System.IO.FileInfo.get_Length()
       à Microsoft.BDD.PSSnapIn.GenerateMDTMedia.ProcessRecord()
       à System.Management.Automation.CommandProcessor.ProcessRecord()
       --- End of inner exception stack trace ---
       à System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
       à Microsoft.BDD.Wizards.GenerateMediaProgress.WizardProcessing()
       à Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

    There is only one OS in my console (and in the OperatingSystem.xml) and I renamed it with the .WIM extension, no clue:

    Windows_10_Enterprise_x64_v1607_FR_Production_Image.WIM

    I had a look at the thread below but the answer did not solve my issue, I even tried to create a new test selection profile...

    Offline Media creation Fails If Split WIM is attempted

    I know Rufus can create a UEFI bootable USB key with NTFS support but you have to disable Secure Boot to boot with keys generated with this tool.

    Any help would be much appreciated.

    I am using MDT 8443 and ADK1703 (it didn't work with 1607 either).


    Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene


    Thursday, May 4, 2017 6:09 PM

Answers

  • Don't know if this will help but I had the same issue and found a resolution.

    control\settings.xml - <SkipWimSplit>False</SkipWimSplit>
    Wim file must be named in deployment share description as wimfilename.wim
    os wim must be in ROOT of deployment share GUI 'Operating Systems' (not in a sub-folder)

    The last item was my issue as I had my deployment wim in a sub-folder 'Windows 10'

    Friday, June 30, 2017 10:34 AM

All replies

  • One more thing, my wim file contains only one index:

    dism /get-wiminfo "/WimFile:X:\MDTBuildProd\Operating Systems\REFW10-X64-001\REFW10-X64-001.wim"

    Deployment Image Servicing and Management tool
    Version : 10.0.14393.0

    Details for image : X:\MDTBuildProd\Operating Systems\REFW10-X64-001\REFW10-X64-001.wim

    Index : 1
    Name : REFW10-X64-001CDrive
    Description : <undefined>
    Size : 23 307 489 931 bytes

    The operation completed successfully.

    Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene


    Friday, May 5, 2017 7:07 AM
  • It's been a month and I am still struggling with this issue.

    I added the DISM drivers update for ADK 1703 to my DISM folder, just in case, but still no clue.

    I can see the process starting:

    

    In my DS's OS folder, I can see the swm files creation, I don't know why but MDT splits my original WIM into 1GB pieces instead of 4GB.

    Then, the error occur, could not find file...

    ...and all the swm files are gone:

    Has anyone has experienced this problem before?

    I am doing my best but I still have no idea what's going on.


    Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene

    Friday, June 2, 2017 5:06 PM
  • Don't know if this will help but I had the same issue and found a resolution.

    control\settings.xml - <SkipWimSplit>False</SkipWimSplit>
    Wim file must be named in deployment share description as wimfilename.wim
    os wim must be in ROOT of deployment share GUI 'Operating Systems' (not in a sub-folder)

    The last item was my issue as I had my deployment wim in a sub-folder 'Windows 10'

    Friday, June 30, 2017 10:34 AM
  • It helps a lot Andy, you totally made my day!

    My wim was in a Windows 10 folder too, I put it in root and everything went fine.

    Thank you so much for your answer!


    Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene


    Friday, June 30, 2017 11:45 AM
  • Hi Mathieu, 

    May I know how did you put the wim to root of the Operating system folder? Because when i try to import a wim file, it ask me to select a path to store the WIM. So i can't put the wim to the root of the Operating system folder. 

    @Andy, do you have any idea?

    Thanks a lot!


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, March 29, 2019 9:29 AM
  • We mean the root of the OS container within MDT console

    Twitter: @MatAitAzzouzene | Linkedin: Mathieu Ait Azzouzene

    Saturday, March 30, 2019 9:35 AM