The USMT 10 files should be in the USMT5 folder (replacing the old ones). The WIM mount issue is just an oddity of removing one ADK after the other was installed. I think you can repair the installation of the ADK for Windows 10 to fix that.
Thanks, -Michael From: [email protected] [mailto:[email protected]] On Behalf Of Klish, Brian Sent: Monday, September 21, 2015 6:19 AM To: [email protected] Subject: [MDT-OSD] RE: ADK setup doesn't uninstall prior version? I uninstalled the old ADK and tried to update my deployment share. Here are the results. === Making sure the deployment share has the latest x86 tools === === Processing LiteTouchPE (x86) boot image === Building requested boot image profile. Determining if any changes have been made in the boot image configuration. No existing boot image profile found for platform x86 so a new image will be created. Calculating hashes for requested content. Changes have been made, boot image will be updated. Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used. Unable to mount the WIM, so the update process cannot continue. === Completed processing platform x86 === === Making sure the deployment share has the latest x64 tools === === Processing LiteTouchPE (x64) boot image === Building requested boot image profile. Determining if any changes have been made in the boot image configuration. No existing boot image profile found for platform x64 so a new image will be created. Calculating hashes for requested content. Changes have been made, boot image will be updated. Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim will be used. Unable to mount the WIM, so the update process cannot continue. === Completed processing platform x64 === === Processing complete === I also checked my \\deploymentserver\share\Tools\x64<file://deploymentserver/share/Tools/x64> folder and I don't see a USMT10 folder. It should be in there after a successful update? -Brian From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Sunday, September 20, 2015 6:23 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: ADK setup doesn't uninstall prior version? It used to complain if it found an older version. In any case, it is best to uninstall the old version before installing the new one. If you do this now, the next time you update your deployment share MDT should automatically update the files. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Klish, Brian Sent: Sunday, September 20, 2015 2:47 PM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [MDT-OSD] ADK setup doesn't uninstall prior version? If I remember correctly you can't have two different versions of the ADK installed at once. I thought setup would know this and uninstall the prior version for me. I guess it doesn't. I just found when I upgraded to MDT 2013 Update 1 my USMT files don't appear to be the new versions in my deployment shares. I'm wondering if it's because MDT didn't upgrade them properly since I had both versions installed. Now that I have myself in the situation how do I manually upgrade my deployment shares with the correct USMT and other ADK tools? Thanks in advance. Brian
