It's not you, Kari. It's me. Your instructions are fine. That's the path I finally used. Works fine.
I got all the way through finally entering the correct paths. The last step:
Attachment 150006
When I press enter I get this after a flash of another screen:
Attachment 150007
I also moved those updates to another folder I made in C:, but still failed.
Perhaps this is because I downloaded and used the latest ISO via MCT and it has the updates added already?
Yes, that would be the reason. Updates were rejected because your ESD made to WIM already contains them. Didn't think of adding an explanation there, should I?
Other than that, when you finally got correct paths entered, was it too complicated to use? Did you try to write ISO files to USB, or just quit?
Yes, if that be it. I'm learning a lot here. Your update script works great when I enter everything correctly. Here's my notes on steps I take. I realize this is not all the scenarios.
Create folders:
C:\ISO_Files
C:\ TempMount
C:\ Update_Files
Download update files to C:\ Update_Files
Copy ISO files to C:\ISO_Files
Open PowerShell ISE as admin
Check the available editions (index values) via DISM:
dism /Get-WimInfo /WimFile:F:\Sources\install.esd
Convert MCT ESD media to WIM via DISM:
dism /export-image /SourceImageFile:C:\ISO_Files\Sources\install.esd /SourceIndex:1 /DestinationImageFile: C:\ISO_Files\install.wim /Compress:max /CheckIntegrity
Delete install.esd and replace with install.wim in Sources folder
Enter update script in PS ISE Script Editor and close
Set Execution Policy:
Set-ExecutionPolicy Unrestricted -Scope CurrentUser
Press F5 to run script
Enter: C:\ISO_Files
Enter: ImageIndex 1
Enter: C:\Update_Files
I'm curious about this - I did a fresh download of the MCT itself at the weekend, and used it to download an installer to a USB drive.
But as far as I could tell, the install.esd was the same as the install.esd from an MCT I'd downloaded back in April. Same file size and I think same properties too.
It didn't seem to download updates during that process, even though I'd hoped it would.
Regarding the highlighted item in above quote, I think I need to explain something about PowerShell scripting language.
A line starting with hash (#) is a comment, remark line that will not be executed but is included in script to explain to anyone not only using the script but also reading it what's happening, what will be done next.
In below code box lines 43 to 45 from the script:
Code:########################################################## # Create a temporary working folder C:\TempMount, delete # old one first if folder with such name already exists ##########################################################
The above lines do not mean you should create the C:\TempMount folder manually, they only explain that in next lines the folder will be created by the script. In fact, if you create the TempMount folder manually or if it exists for any reason, it will be deleted by the script and then recreated. Look at the script lines 48 to 51:
Code:cls $Mount = 'C:\TempMount\' if (Test-Path $Mount) {Remove-Item $Mount} $Mount = New-Item -ItemType Directory -Path $Mount
Line 48 contains the Clear Screen (cls) command which clears the PowerShell window placing cursor on top, row 1 column 1. The next line then sets value (path) C:\TempMount to variable $Mount.
Following line, the so called IF statement checks if folder C:\TestMount exists from an earlier run, and if yes, removes it. Finally, a new item, a folder (ItemType Directory) will be created and named as C:\TempMount.
Short: each line in script starting with # is a comment, an explanation about what the script will do next. These lines will be ignored when script is run. They are not instructions to user but instead exist to make reading and understanding the functions of the script easier for those reading it, and also for the user who wrote it, in this case me; the script contains over 400 lines, if / when I need to edit it I can find correct place faster by checking the comments before each section.
Kari
Very similar concept to the Hosts file.
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Thanks for explaining, Kari. I read through the script and wondered what the hash tags were for. Now I know. :)
I assume this works for any ISO files. I noticed when using the MCT it places it on the thumb drive extracted (is that the correct term?) to see all the files including the install.esd. Therefore, it's not a true ISO image, correct? It's an install drive?
I found this on TechNet from 6 years ago: How to extract the contents from an .ISO file without burning the .ISO to disc. Office Deployment Support Team Blog
Is there a way to extract ISO files by using Command and/or PS? I'm assuming if PS converts, it must extract as well?
Quote
