We are using MDT 2010 to image our systems with a LiteTouch deployment. 

I have a new system to image and the network controller is new to our environment so I Update the deployment share and regardless if I ask the system to completely regenerate the Boot media or Optimize it I get the same error below

System.Management.Automation.CmdletInvocationException: The process cannot access the file 'D:\WDS\Boot\LiteTouchPE_x86.iso' because it is being used by another process. ---> System.IO.IOException: The process cannot access the file 'D:\WDS\Boot\LiteTouchPE_x86.iso' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.Delete(String path)
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Since I can not generate the boot media for any systems now I am at a standstill with most imaging.

Any help would be great. Thanks.
3 Comments   [ + ] Show Comments

Comments

  • What steps have you taken to determine whether the file at 'D:\WDS\Boot\LiteTouchPE_x86.iso' is locked by some other process? If a VM has accessed this file, for example, a file lock will remain on this file until the VM is rebooted. It is important not to assume that the error message is wrong without exploring all possibilities. Can you rename this file, for example? If you cannot, then there is definitely something locking that file.
  • I have checked on the server to see if any files or shares were open and closed and restarted it. I also tried moving the file to a new location and tried to have the tool completely regenerate the boot.wim without luck.

    We do have a VM on a separate system but it is not currently running. Following your advice I have started it, powered it off, and powered the host down entirely to remove it from the equation.

    Thanks for the suggestion.I will post an update tomorrow.
  • No luck so far. I did try to rename the file and got the following error

    "The action can't be completed because the file is open in System."

    I've tried to "Close the Handle" using ProcessExplorer and get the following error.

    "Forcing a handle closed cal lead to an application crash and system instability" When I click yes the following is displayed "Error opening process: The handle is invalid."
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.

Share