Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile
-
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?
If you just want the contents of the ISO, perhaps to copy them or look at them, just mount the ISO (open with Explorer if Mount command not available). The system will assign a drive letter. Treat it as any other drive. When done, eject it.
-
If you just want the contents of the ISO, perhaps to copy them or look at them, just mount the ISO (open with Explorer if Mount command not available). The system will assign a drive letter. Treat it as any other drive. When done, eject it.
Thanks, TC. :)
-
Very similar concept to the Hosts file.
The hash is used by quite a number of scripting languages (PHP, Bash, Python etc.) for remarks. In PowerShell you can also use start tag <# and end tag #>, placing any amount of text in between these tags as a comment that will be ignored when script is run. See this example:
Code:
<#
Following loop reads each update .cab and .msu file
from given folder and writes it to Windows image.
If OK, update name including KB number will be
added to 'WUSuccess.log' file, if failed to 'WUFail.log'
#>
ForEach ($File in $WUFiles)
{
Write-Host ' Applying'$File
Add-WindowsPackage -Path $Mount -PackagePath $File.FullName | Out-Null
if ($? -eq $TRUE)
{$File.Name | Out-File -FilePath C:\WUSuccess.log -Append}
else
{$File.Name | Out-File -FilePath C:\WUFail.log -Append}
}
The part in red, everything between the remark / comment tags (including the tags themselves) will be taken as a comment and ignored when script is run.
Since Windows 8 it has been possible to mount ISO and IMG files simply by opening (double click) them, making about all third party programs which "extract" them almost useless. A Windows 10 ISO image is extracted when you mount it and copy its content to a folder.
If you just want the contents of the ISO, perhaps to copy them or look at them, just mount the ISO (open with Explorer if Mount command not available). The system will assign a drive letter. Treat it as any other drive. When done, eject it.
Exactly.
Kari
-
-
Just an odd habit of mine. After creating an ISO (UUPtoISO), I always sanity check the setup.exe properties/details for the build number. By mounting it. Not that it ever would be wrong, just habit.
-
Since Windows 8 it has been possible to mount ISO and IMG files simply by opening (double click) them, making about all third party programs which "extract" them almost useless. A Windows 10 ISO image is extracted when you mount it and copy its content to a folder.
Kari
Thanks. Yes, I remember mounting them in 8/8.1 to perform an in-house upgrade. Never realized the files could be copied.
I have ISOs starting with Insider build 16179 that I'll run through your script.
BTW, I saved your script to a file to use again. That's ok to use that way, yes?
-
-
Thanks. Yes, I remember mounting them in 8/8.1 to perform an in-house upgrade. Never realized the files could be copied.
I have ISOs starting with Insider build 16179 that I'll run through your script.
BTW, I saved your script to a file to use again. That's ok to use that way, yes?
Yes. of course. In fact, anyone interested can download it from my OneDrive: W10ImageUpdate.ps1.
Save the script, rename it as you wish. In an elevated PowerShell with script execution enabled, run it with following command, replacing the path and filename as needed:
.\'W:\PS Scripts\W10ImageUpdate.ps1'
-
Continuing this "We are officially off topic to fill the void while waiting next build", here's some beast of a server:
-
Yes. of course. In fact, anyone interested can download it from my OneDrive:
W10ImageUpdate.ps1.
Save the script, rename it as you wish. In an elevated PowerShell with script execution enabled, run it with following command, replacing the path and filename as needed:
.\'W:\PS Scripts\W10ImageUpdate.ps1'
Thanks. Download says "Publisher of this program couldn't be verified". You are a verified real person, yes? 
Originally I copied and pasted the script into PS editor and ran it. It asked if I wanted to save while closing it out in which I did.
-
You are a verified real person, yes?

Ask any of my exes, I'm just a bag of s**t. Ask any of people knowing me and my current real life situation well, I'm surreal rather than real :)
Personally, I'm not so sure about that verification part... Feeling not valid, not licenced, expired.
-
Ask any of my exes, I'm just a bag of s**t. Ask any of people knowing me and my current real life situation well, I'm surreal rather than real :)
Personally, I'm not so sure about that verification part... Feeling not valid, not licenced, expired.
Even as a native Brit, I cannot work out what the plural of an ex is. Exes is most logical - fox, foxes, but of course ex is a prefix which you cannot pluralise. So @Kari, I think you have invented a new word
. That is the beauty of English - it changes faster than any other language, and has more words than any other Roman letter based language.
Eye love spell chequers as ewe khan knot bee sure if ewe are write.