PowerShell Scripting - Update Windows 10 USB install media  

@Kari, I'm curious to know if you have any thoughts on this...

I've been using the tutorials here on TenForums to create unattended install packages and inject updates into my Windows images.

Today, I came across this table from Microsoft:


Up until now, when I update my Windows images, I have only been updating the items shown outlined in red. What I am trying to understand is the impact of not updating the WinRE and WinPE components (item numbers 1-17 in the chart). Do you know if this only effects the running of WinRE from the install media and WinPE for installation of Windows or would this actually effect the final installation of Windows made from this media?

If not certain, that's perfectly fine. I had simply thought that if anyone would know about this, you were the most likely person.

Note: This is not a critical issue, it's mainly just for my own understanding.

Reference:

https://docs.microsoft.com/en-us/win...dynamic-update

https://techcommunity.microsoft.com/...es/ba-p/982477

I wanted to make everyone reading this aware of a bug in Windows 10 2004 related to injecting updates into Windows images.

If you like to roll your own Windows images and you inject Windows updates into your images, be aware of a bug that you may encounter.

When injecting the LCU (Latest Cumulative Update) for Windows, if you log your operations, you will find errors in the DISM log file that appear similar to this:

Code:

2020-06-10 09:48:27, Error                 CSI    00000042 (F) Matching binary srv.sys missing for component Microsoft-Windows-SMBServer-v1, version 10.0.19041.329, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}[gle=0x80004005]

2020-06-10 09:48:27, Error                 CSI    00000043@2020/6/10:14:48:27.073 (F) onecore\base\wcp\componentstore\storelayout.cpp(1682): Error 800f0984 [Warning,Facility=15 (0x000f),Code=2436 (0x0984)] originated in function ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x984))) )
[gle=0x80004005]

These messages always appear in pairs. The first message references a binary file that is missing and that message is followed by a message such as the second message that you see above. These messages appear multiple times in the log, referencing different files. I didn't count but I'd guess I saw about 30 sets of these messages for each edition of Windows that I updated.

I've checked with a Microsoft contact on this and the official word is that this is a known issue. The good news is that these messages are safe to ignore and they are considering for possible servicing in the future.

So, for now, if you get these specific errors, simply ignore them.

i want to export single index using get windows image via output as grid view using powershell but unable to do so . please help where i am wrong.

Powershell -Command "Get-WindowsImage -ImagePath '%UserProfile%\Desktop\Win10\sources\install.wim' | Out-GridView -Title 'Select Image Index to Export into Single Index Image' | Export-WindowsImage -SourceImagePath 'Win10\sources\install.wim' -SourceName $_Index -DestinationImagePath 'install.wim'"

Disk2019 said:

i want to export single index using get windows image via output as grid view using powershell but unable to do so . please help where i am wrong.

Powershell -Command "Get-WindowsImage -ImagePath '%UserProfile%\Desktop\Win10\sources\install.wim' | Out-GridView -Title 'Select Image Index to Export into Single Index Image' | Export-WindowsImage -SourceImagePath 'Win10\sources\install.wim' -SourceName $_Index -DestinationImagePath 'install.wim'"

taking snippits from Kari's original script, I would try the following in a new script window in Powershell ISE

$ISOFolder = Read-Host -Prompt ' Enter source, press Enter'
$WimFolder = $ISOFolder

if (Test-Path $WimFolder\Sources\install.wim)
{
$WimCount = 1
if (($WIMFolder -match "x86") -or ($WIMFolder -match "x64"))
{
$ISOFolder = $ISOFolder -replace "....$"
}
}
elseif (Test-Path $WimFolder)
{
$WimCount = 0
cls
Write-Host
Write-Host ' No Windows image (install.wim file) found'
Write-Host ' Please check path and try again.'
Write-Host
Pause
}
else
{
$FileCount = 0
cls
Write-Host
Write-Host ' Path'$ISOFolder 'does not exist.'
Write-Host
Write-Host ' ' -NoNewline
Pause
}
}

$WimFile = Join-Path $WimFolder '\Sources\install.wim'

cls
Get-WindowsImage -ImagePath $WimFile | Format-Table ImageIndex, ImageName
Write-Host
Write-Host ' The install.wim file contains above listed Windows editions.'
Write-Host ' Which edition should be updated?'
Write-Host
Write-Host ' Enter the ImageIndex number of correct edition and press Enter.'
Write-Host ' If this is a single edition Windows image, enter 1.'
Write-Host
$Index = Read-Host -Prompt ' Select edition'

Get-WindowsImage -ImagePath $ISOFolder -Index $Index | Out-GridView -PassThru | Export-WindowsImage @Kari does this look like it would help or fix @Disk2019 issue?
@Kari - a few pages back on this post, remember the drivers script I uploaded? Well, I'm busy rolling integrating updates, drivers, add/remove features both manual and automated into one script - obviously crediting you with the code, where needed. :)

@Kari - Using the Integrate drivers script i modded, (and referenced in these comments,)after the update script you posted in this tutorial, and I didnt change any code, yet I'm noticing that powershell is not outputting and writing the Success or Fail.log files to C:\. Don't know if that is something to do with an update for Windows 10 or what.

So, I can't update version with this script, right? I mean, let's say I made a unnattended Windows installation for version 2004 of Windows. Can I use this script to update to the 21H2 version? If not, there is any way to do that?