Hi @OSDeploy,

can you please edit https://github.com/OSDeploy/OSDBuilder/blob/master/Catalogs/Windows%2010.xml and add CU KB4489894 (http://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=3479e30e-0cdb-47e6-9eb5-3b3efbe508df). This CU will replace KB4489868 which is currently still in the XML.

Thank you in advance!

Kind regards,
Sven

C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.11.12.0\Public\Initialize-OSDBuilder.ps1: 41 Carácter: 45
JsonLocal = Join-Path $global:GetOSDBuilderHome 'OSDBui
+ CategoryInfo : InvalidData: (:) [Join-Path], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand

When running Update-OSMedia, is there currently a way to include all available optional Windows updates without the need to specify them by name?

The PackageName has additional information following the base name, which also includes version numbers, and can change for each version. When running these scripts via an automated method, it's difficult to remove AppX apps based off of the PackageName.

DisplayName                            PackageName
-----------                            -----------
Microsoft.549981C3F5F10                Microsoft.549981C3F5F10_1.1911.21713.0_neutral_~_8wekyb3d8bbwe
Microsoft.BingWeather                  Microsoft.BingWeather_4.25.20211.0_neutral_~_8wekyb3d8bbwe
Microsoft.DesktopAppInstaller          Microsoft.DesktopAppInstaller_2019.125.2243.0_neutral_~_8wekyb3d8bbwe
Microsoft.GetHelp                      Microsoft.GetHelp_10.1706.13331.0_neutral_~_8wekyb3d8bbwe
Microsoft.Getstarted                   Microsoft.Getstarted_8.2.22942.0_neutral_~_8wekyb3d8bbwe
Microsoft.HEIFImageExtension           Microsoft.HEIFImageExtension_1.0.22742.0_x64__8wekyb3d8bbwe
Microsoft.Microsoft3DViewer            Microsoft.Microsoft3DViewer_6.1908.2042.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftEdge.Stable         Microsoft.MicrosoftEdge.Stable_84.0.522.52_neutral__8wekyb3d8bbwe
Microsoft.MicrosoftOfficeHub           Microsoft.MicrosoftOfficeHub_18.1903.1152.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftSolitaireCollection Microsoft.MicrosoftSolitaireCollection_4.4.8204.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftStickyNotes         Microsoft.MicrosoftStickyNotes_3.6.73.0_neutral_~_8wekyb3d8bbwe
Microsoft.MixedReality.Portal          Microsoft.MixedReality.Portal_2000.19081.1301.0_neutral_~_8wekyb3d8bbwe
Microsoft.MSPaint                      Microsoft.MSPaint_2019.729.2301.0_neutral_~_8wekyb3d8bbwe
Microsoft.Office.OneNote               Microsoft.Office.OneNote_16001.12026.20112.0_neutral_~_8wekyb3d8bbwe
Microsoft.People                       Microsoft.People_2019.305.632.0_neutral_~_8wekyb3d8bbwe
Microsoft.ScreenSketch                 Microsoft.ScreenSketch_2019.904.1644.0_neutral_~_8wekyb3d8bbwe
Microsoft.SkypeApp                     Microsoft.SkypeApp_14.53.77.0_neutral_~_kzf8qxf38zg5c
Microsoft.StorePurchaseApp             Microsoft.StorePurchaseApp_11811.1001.1813.0_neutral_~_8wekyb3d8bbwe
Microsoft.VCLibs.140.00                Microsoft.VCLibs.140.00_14.0.27323.0_x64__8wekyb3d8bbwe
Microsoft.VP9VideoExtensions           Microsoft.VP9VideoExtensions_1.0.22681.0_x64__8wekyb3d8bbwe
Microsoft.Wallet                       Microsoft.Wallet_2.4.18324.0_neutral_~_8wekyb3d8bbwe
Microsoft.WebMediaExtensions           Microsoft.WebMediaExtensions_1.0.20875.0_neutral_~_8wekyb3d8bbwe
Microsoft.WebpImageExtension           Microsoft.WebpImageExtension_1.0.22753.0_x64__8wekyb3d8bbwe
Microsoft.Windows.Photos               Microsoft.Windows.Photos_2019.19071.12548.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsAlarms                Microsoft.WindowsAlarms_2019.807.41.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCalculator            Microsoft.WindowsCalculator_2020.1906.55.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCamera                Microsoft.WindowsCamera_2018.826.98.0_neutral_~_8wekyb3d8bbwe
microsoft.windowscommunicationsapps    microsoft.windowscommunicationsapps_16005.11629.20316.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsFeedbackHub           Microsoft.WindowsFeedbackHub_2019.1111.2029.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsMaps                  Microsoft.WindowsMaps_2019.716.2316.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsSoundRecorder         Microsoft.WindowsSoundRecorder_2019.716.2313.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsStore                 Microsoft.WindowsStore_11910.1002.513.0_neutral_~_8wekyb3d8bbwe
Microsoft.Xbox.TCUI                    Microsoft.Xbox.TCUI_1.23.28002.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxApp                      Microsoft.XboxApp_48.49.31001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxGameOverlay              Microsoft.XboxGameOverlay_1.46.11001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxGamingOverlay            Microsoft.XboxGamingOverlay_2.34.28001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxIdentityProvider         Microsoft.XboxIdentityProvider_12.50.6001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxSpeechToTextOverlay      Microsoft.XboxSpeechToTextOverlay_1.17.29001.0_neutral_~_8wekyb3d8bbwe
Microsoft.YourPhone                    Microsoft.YourPhone_2019.430.2026.0_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneMusic                    Microsoft.ZuneMusic_2019.19071.19011.0_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneVideo                    Microsoft.ZuneVideo_2019.19071.19011.0_neutral_~_8wekyb3d8bbwe

Hello, in latest version OSDBuilder 21.5.27.1
Get-DownOSDBuilder -Download -UpdateArch 'x64' -UpdateBuild '20H2' -UpdateOS 'Windows 10' -WebClient
(Save-OSDBuilderDownload alias)
The .cab files are no longer distributed in the directories by categories 'Windows 10' or 'Windows 10 Dynamic Update', is this the new expected behavior ?
Thank you for your very useful work
Best regards.
Now it's like this : all mixed flat
Transcript started, output file is C:\OSDBuilder\Win10_20H2_x64\Updates\GetUpdates_Win10_20H2_x64_2021-06-14_153103.log
VERBOSE: Downloading OSDUpdates using System.Net.WebClient
VERBOSE: OSDSUS 21.6.8.1 Windows http://osdsus.osdeploy.com/release
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb5003637-x64_54182e037903c3010ff0d56c4f8dbc951cd95a03.cab
http://download.windowsupdate.com/d/msdownload/update/software/secu/2021/06/windows10.0-kb5003637-x64_54182e037903c3010ff0d56c4f8dbc951cd95a03.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb5003254-x64-ndp48_7e71609004f7df68d03bece213a4c1c0078e88ec.cab
http://download.windowsupdate.com/d/msdownload/update/software/updt/2021/04/windows10.0-kb5003254-x64-ndp48_7e71609004f7df68d03bece213a4c1c0078e88ec.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb5003240-x64_cbbbc75ecf4e645236f90788e896705d443091c6.cab
http://download.windowsupdate.com/c/msdownload/update/software/crup/2021/05/windows10.0-kb5003240-x64_cbbbc75ecf4e645236f90788e896705d443091c6.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb5000983-x64_1652e61bb134adeb190a119aa738486e4ac9b462.cab
http://download.windowsupdate.com/d/msdownload/update/software/crup/2021/03/windows10.0-kb5000983-x64_1652e61bb134adeb190a119aa738486e4ac9b462.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb4589212-v2-x64_a2aabdd9d06d57c9275997cab64eb45d6821e934.cab
http://download.windowsupdate.com/c/msdownload/update/software/updt/2021/01/windows10.0-kb4589212-v2-x64_a2aabdd9d06d57c9275997cab64eb45d6821e934.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb4577586-x64_025c603f506481a321d52e47e18fe8374b64a3a5.cab
http://download.windowsupdate.com/c/msdownload/update/software/updt/2020/10/windows10.0-kb4577586-x64_025c603f506481a321d52e47e18fe8374b64a3a5.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb4601050-x64-ndp48_cb09a1198335a24535d73b8ddfa4196ba5edc115.cab
http://download.windowsupdate.com/d/msdownload/update/software/secu/2021/01/windows10.0-kb4601050-x64-ndp48_cb09a1198335a24535d73b8ddfa4196ba5edc115.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\windows10.0-kb4580325-x64_7cdf5f50ee497f6f94bca6be791dcaeecce5e307.cab
http://download.windowsupdate.com/d/msdownload/update/software/secu/2020/10/windows10.0-kb4580325-x64_7cdf5f50ee497f6f94bca6be791dcaeecce5e307.cab
Transcript stopped, output file is C:\OSDBuilder\Win10_20H2_x64\Updates\GetUpdates_Win10_20H2_x64_2021-06-14_153103.log

But before it was like that : well arranged by type of updates
VERBOSE: Downloading OSDUpdates using System.Net.WebClient
VERBOSE: OSDSUS 21.3.9.1 Windows http://osdsus.osdeploy.com/release
C:\OSDBuilder\Win10_20H2_x64\Updates\Windows 10\2021-01 Update for Windows 10 Version 20H2 for x64-based Systems (KB4589212)\Windows10.0-KB4589212-v2-x64.cab
http://download.windowsupdate.com/c/msdownload/update/software/updt/2021/01/windows10.0-kb4589212-v2-x64_a2aabdd9d06d57c9275997cab64eb45d6821e934.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\Windows 10\2021-03 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5000802)\Windows10.0-KB5000802-x64.cab
http://download.windowsupdate.com/c/msdownload/update/software/secu/2021/03/windows10.0-kb5000802-x64_86037aa61b4b202e2ce622605e3cf50d354f4c1c.cab
C:\OSDBuilder\Win10_20H2_x64\Updates\Windows 10 Dynamic Update\2021-03 Dynamic Update for Windows 10 Version 20H2 for x64-based Systems (KB5001263)\Windows10.0-KB5001263-x64.cab
http://download.windowsupdate.com/c/msdownload/update/software/crup/2021/03/windows10.0-kb5001263-x64_78def9e77dc6ca87d30f0585e6c16db0b96ba680.cab

Removed Out-Null from robocopy command and this nis the issue:

Are there any PS-Commands to clean up old OSBuild, OSImport and OSMedia folders?
Or is manually folder delete in explorer the only alternative?

Hi, any chance OSDBuilder can add Azure Stack HCI into the list? The codebase is Windows Server 2019.

Source OSMedia Windows Image Information
-OSMedia Path:              c:\osdbuilder\OSImport\Azure Stack HCI x64 2009 17784.1068
-Image File:                c:\osdbuilder\OSImport\Azure Stack HCI x64 2009 17784.1068\OS\sources\install.wim
-Name:                      Azure Stack HCI
-Description:               This option installs Azure Stack HCI.
-Architecture:              x64
-Edition:                   ServerAzureStackHCICor
-Type:                      Server Core
-Languages:                 en-US
-Major Version:             10
-Build:                     17784
-Version:                   10.0.17784.1068
-SPBuild:                   1068
-SPLevel:                   0
-Created Time:              07/17/2020 00:45:57
-Modified Time:             08/01/2020 08:21:17
========================================================================================
WARNING: OSDBuilder does not currently support this version of Windows ... Check for an updated version

OSDBuilder 19.8.27.0, running under Windows PowerShell on Windows 10 1903 x64.
Did an import-osmedia of a fresh off the ISO Server 2019 Desktop Experience.

Both KB4506990 and KB4511522 failed with 0x8007371b

It would be nice to be able to import media from Windows Update, just as https://uupdump.ml is doing.

WARNING: OSPoshModsSystem is being deprecated in the near future

Is there a planned replacement, or is it being discontinued entirely?

Could you please show me in your documentation where you need OSCDIMG.exe or download the ADKSETUP?

Please add at your convenience.

OSDBuilder 21.10.14.1 | OSD 21.11.9.1

Same Image and same command, one hand you will get an error and updates are installing, where on the other hand, updates are not installed and skipped. WINRE is only mentioned on 7,1.

Powershell 7.1.5:
`2021-11-10-123607 MEDIA: Copy Operating System to I:\Osdbuilder2021\OSMedia\build2111101235
2021-11-10-123612 WinPE: Mount WinPE.wim to I:\Osdbuilder2021\Mount\winpe2111101236
2021-11-10-123618 WinPE: Mount WinRE.wim to I:\Osdbuilder2021\Mount\winre2111101236
2021-11-10-123623 WinPE: Mount WinSE.wim to I:\Osdbuilder2021\Mount\setup2111101236

2021-11-10-123629 WinPE: (SSU) Servicing Stack Update
INSTALLED 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) - windows10.0-kb5005112-x64_99919606d4632b1f4b9bd4bff48a363739776047.cab
2021-11-10-123630 WinRE: (SSU) Servicing Stack Update
INSTALLED 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) - windows10.0-kb5005112-x64_99919606d4632b1f4b9bd4bff48a363739776047.cab
2021-11-10-123630 WinSE: (SSU) Servicing Stack Update
INSTALLED 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) - windows10.0-kb5005112-x64_99919606d4632b1f4b9bd4bff48a363739776047.cab 2021-11-10-123630 WinPE: (LCU) Latest Cumulative Update INSTALLING 2021-09 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5005568) - windows10.0-kb5005568-x64_8bf5f955f8221e5d1df616ffa9a3d6cb28e2fc5d.cab C:\Users\fladmin\AppData\Local\Temp\SSU\SSU-17763.2170-x64.cab Add-WindowsPackage: C:\Users\fladmin\Documents\PowerShell\Modules\OSD\21.9.21.1\Public\DISM\Add-WindowsPackageSSU.ps1:94 Line | 94 | Add-WindowsPackage -PackagePath $_.FullName -Path $Path - …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Fehler: Es wurde kein Vorgang ausgeführt. Stellen Sie sicher, dass DISM ordnungsgemäß im Abbild installiert ist, und wiederholen Sie dann den Vorgang.

2021-11-10-124032 WinRE: (LCU) Latest Cumulative Update
INSTALLING 2021-09 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5005568) - windows10.0-kb5005568-x64_8bf5f955f8221e5d1df616ffa9a3d6cb28e2fc5d.cab
2021-11-10-124434 WinSE: (LCU) Latest Cumulative Update
INSTALLING 2021-09 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5005568) - windows10.0-kb5005568-x64_8bf5f955f8221e5d1df616ffa9a3d6cb28e2fc5d.cab
2021-11-10-124829 MEDIA: Update Media Sources with WinSE.wim
2021-11-10-124829 WinPE: Export WinPE Package Inventory to I:\Osdbuilder2021\OSMedia\build2111101235\WinPE\info
2021-11-10-124838 WinPE: Dismount-WimsPE`

Powershell 5.1:

`2021-11-10-132222 MEDIA: Copy Operating System to I:\Osdbuilder2021\OSMedia\build2111100122

2021-11-10-132228 WinPE: Mount WinPE.wim to I:\Osdbuilder2021\Mount\winpe2111100122

2021-11-10-132234 WinPE: Mount WinRE.wim to I:\Osdbuilder2021\Mount\winre2111100122

2021-11-10-132240 WinPE: Mount WinSE.wim to I:\Osdbuilder2021\Mount\setup2111100122

2021-11-10-132248 WinPE: (SSU) Servicing Stack Update
WARNUNG: Skipping WinPE SSU Update for this version of Windows
2021-11-10-132248 WinPE: (LCU) Latest Cumulative Update
WARNUNG: Skipping WinPE LCU Update for this version of Windows

2021-11-10-132248 MEDIA: Update Media Sources with WinSE.wim

2021-11-10-132248 WinPE: Export WinPE Package Inventory to I:\Osdbuilder2021\OSMedia\build2111100122\WinPE\info

2021-11-10-132256 WinPE: Dismount-WimsPE`

LTSB / LTSC Versions show always open updates

MediaType : OSMedia
ModifiedTime : 17.02.2020 14:53:55
Revision : OK
Updates : Update
Name : Windows 10 Enterprise 2016 LTSB x64 1607 14393.3504
OperatingSystem : Windows 10
Arch : x64
ReleaseId : 1607
RegBuild : 14393
UBR : 14393.3504
Version : 10.0.14393.3504
MajorVersion : 10
MinorVersion : 0
Build : 14393
Languages : {en-US}
EditionId : EnterpriseS
InstallationType : Client
ImageName : Windows 10 Enterprise 2016 LTSB
OSMFamily : Client EnterpriseS x64 14393 en-US
FullName : C:\OSDBuilder\OSMedia\Windows 10 Enterprise 2016 LTSB x64 1607 14393.3504
CreatedTime : 16.07.2016 15:28:45
OSMGuid : d5345596-33d8-4cdc-99d7-9611a0ea193d
OSMFamilyV1 : 20160716152845EnterpriseS

as of today 14393.3504 is the latest version according to
https://docs.microsoft.com/en-us/windows/release-information/

Windows 10 1909 works as expected.
MediaType : OSMedia
ModifiedTime : 19.02.2020 12:39:53
Revision : OK
Updates : OK
Name : Windows 10 Enterprise x64 1909 18363.657
OperatingSystem : Windows 10
Arch : x64
ReleaseId : 1909
RegBuild : 18363
UBR : 18363.657
Version : 10.0.18362.657
MajorVersion : 10
MinorVersion : 0
Build : 18362
Languages : {en-US}
EditionId : Enterprise
InstallationType : Client
ImageName : Windows 10 Enterprise
OSMFamily : Client Enterprise x64 18363 en-US
FullName : C:\OSDBuilder\OSMedia\Windows 10 Enterprise x64 1909 18363.657
CreatedTime : 07.10.2019 04:18:55
OSMGuid : 6bb8cbd0-d9b1-4337-9732-cd9904451592
OSMFamilyV1 : 20191007041855Enterprise

regards

Fabian

Error Code: 0x800F0823 (2148468771)
Error Name: CBS_E_NEW_SERVICING_STACK_REQUIRED
Error Source: CBS
Error Message: Package needs a newer version of the servicing stack.

Add-WindowsPackage : Add-WindowsPackage failed. Error code = 0x80004001

Please help

When running on Server Core (automating image builds), a custom build task cannot be created with New-OSBuildTask as Out-GridView is not available.

I proposed we add an additional -OSMedia parameter to New-OSBuildTask that permits passing a result of Get-OSMedia and bypassing the OGV selection.

If you're happy with this, I'll submit a PR shortly...

Importing media (VLSC Media)

Source Path: D:
-Image File: D:\Sources\install.wim
-Image Index: 1
-Name: Windows Server 2019 Standard
-Architecture: x64
-Edition: ServerStandard
-Type: Server Core
-Languages: en-US
-Build: 17763
-Version: 10.0.17763.107
-SPBuild: 107
-SPLevel: 0
-Bootable: No
-WimBoot: False
-Created Time: 10/30/2018 10:43:41
-Modified Time: 10/30/2018 11:13:56
-UBR: 17763.
-OSMGuid: d334e407-ab40-48ea-8218-35c971657a5f

Imports the media OK
BUT note the UBR is set to 17763. not 17763.0, 17763.1, etc

So when you attempt to update the media with update-osmedia -Download -Execute or update-osmedia -ShowAllOSMedia
your custom properties does this UBR = [version]$OSMUBR (line 343 in Get-OSMedia) and dies a horrible death

I feel like I've done something wrong as ALL the media I've imported (from mounted ISO, win10 1903,win2016, win 2019)

this is a fresh install of OSDBuilder using

Find-Module osdbuilder | Install-Module -Scope CurrentUser -Force
Import-Module OSDBuilder
Get-OSDBuilder -SetPath E:\osdbuilder -Verbose

Import-OSMedia hangs on "Copy Operating System...."

Possible reasons?

Hi,

I am trying to update my osmedia and want to install some optional updates. The problem is that I can't find any log information that they have been installed. One of the updates I am trying to install is KB4535680 (https://www.catalog.update.microsoft.com/Search.aspx?q=KB4535680).

Is there a way to see optional updates that are installed? I can see other updates in the logs without any problems.

Note: I use Get-DownOSDBuilder -GridView -UpdateBuild 1809 -UpdateOS 'Windows Server 2019' to download the updates and then transfer them to an offline computer which are used for building.

Best Regards,
Sebastian Fridell

Hi there,

when using OSDBuilder I encountered an error. When applying the start layout the copy process fails because of a wrong path. The issue is in OSD-OSBuild.ps1 at line 186.

This line currently is:

Copy-Item -Path "$OSDBuilderContent\$StartLayoutXML" -Destination "$MountDirectory\Users\Default\AppData\Local\Microsoft\Windows\Shell\LayoutModification.xml" -Recurse -Force | Out-Null

The error is here that $StartLayoutXML already contains $OSDBuilderContent so this can be left and the new line would be:

Copy-Item -Path "$StartLayoutXML" -Destination "$MountDirectory\Users\Default\AppData\Local\Microsoft\Windows\Shell\LayoutModification.xml" -Recurse -Force | Out-Null

I have the same issue when copying the unattend.xml file. The problem here is also in OSD-OSBuild.ps1 on line 206 and 207, but as far as I can see this also affects the process of adding packages.

If you have any further questions, please feel free to contact me.

OSDBuilder throws an error serializing hashtable variables to JSON:

2019-06-18-203556 OS: Export Image Content to C:\OSDBuilder\OSBuilds\build2355\info\Get-WindowsImageContent.txt
ConvertTo-Json : The type 'System.Collections.Hashtable' is not supported for serialization or deserialization of a
dictionary. Keys must be strings.
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.6.14.0\Private\AllFunctions.ps1:3025 char:58
+ ... riable | Select-Object -Property Name, Value | ConvertTo-Json | Out-F ...
+                                                    ~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Collections.Hashtable:Hashtable) [ConvertTo-Json], InvalidOperationException
    + FullyQualifiedErrorId : NonStringKeyInDictionary,Microsoft.PowerShell.Commands.ConvertToJsonCommand

2019-06-18-203604 Media: Renaming "C:\OSDBuilder\OSBuilds\build2355" to "Windows Server 2019 Datacenter Evaluation Desktop Experience x64 1809 17763.557"

This appears to be an issue when the -match operator has been used and it creates the $Matches automatic variable.

I will submit a PR shortly that fixes this...

Hi! I'm trying to do an OSBuild, using a newly created OSBuildTask. The problem I'm experiencing, is the the path to my Language packs under IsoExtract gets duplicated while running the OSBuild: C:\OSD\Content\C:\OSD\Content\IsoExtract...

Any hints on how to get around this? I've even tried shortening the path in the json file for the OSBuildTask, but that seems to make no impact at all.

i used the tool to create an updated ISO and it says KB4512495 was installed . When i went to deploy a new server 2016 image and ran windows updates it installed this update . whats going on ? am i missing something ?

Hi - I am reviewing module and love it alot, thank you so much. Currently, I use the update feature to speed my deploys.

I see on this page: https://osdbuilder.osdeploy.com/docs/legacy/windows-server-2012-r2

It says that we can update 2012, but so far I can only download updates. Which module will actually apply them?

I keep getting the below issues trying to enable dotnet to the OS (LTSC 2019 64bit) during New-OSBuildTask? All other OS's are adding them fine.
2021-05-05-160917 OS: Enable NetFX 3.5
WARNING: One or several parent features are disabled so current feature can not be enabled.
2021-05-05-155558 OS: Enable Windows Optional Feature
NetFx4Extended-ASPNET45
WARNING: One or several parent features are disabled so current feature can not be enabled.

Keeps getting this error:

VERBOSE: OSDSUS 19.9.26.1 Windows http://osdsus.osdeploy.com/release
Cannot convert value "18362." to type "System.Version". Error: "Inputstrengen var ikke i et korrekt format."
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.9.20.0\Public\Get-OSMedia.ps1:336 char:13

•         $ObjectProperties = @{
  

•         ~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidArgument: (:) [], RuntimeException
  • FullyQualifiedErrorId : InvalidCastParseTargetInvocation

Exception setting "Revision": "The property 'Revision' cannot be found on this object. Verify that the property exists and can be set."
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.9.20.0\Public\Get-OSMedia.ps1:374 char:148

• ... ct {$.Group | Select-Object -First 1} | foreach {$.Revision = 'OK'}

•                                                   ~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
  • FullyQualifiedErrorId : ExceptionWhenSetting

Hi,

I'm having problems applying LCU, after import my vlsc iso with -Update -BuildNetFX, Windows will download and install the KB4524570 again.

ISO: Windows 10 x64 1909 from VLSC.

On Windows 10 releases 1809 and above, the RSAT components are installed via Features on Demand, so it makes sense to include those only if targeting a compatible release.
From Microsoft:

If you have a version of Windows 10 prior to the October 2018 Update (1809), you will not be able to use Features on Demand. You will need to download and install the RSAT package.
Download and install WS_1803 RSAT package, as outlined below: When installing on Windows 10 April 2018 Update (1803) or earlier, for managing Windows Server, version 1803 or Windows Server, version 1709.

The Get-TaskContentAddFeatureOnDemand cmdlet builds the selection list via exclusion (it gets all files in the IsoExtract directory and starts filtering out undesired/incompatible files).

This means that the RSAT-related files should be filtered out for Release IDs below 1809.

Instead,

Changing $OSMedia.ReleaseId -gt 1803 to $OSMedia.ReleaseId -le 1803 (or $OSMedia.ReleaseId -lt 1809 to better fit Microsoft's verbiage) addresses this issue.

I can fork and submit a Pull Request if it'll help get this fixed.

I'm trying to use OSDBuilder to update an original IoT Enterprise LTSB 2016 Image and am running into errors.

First of all I'm not entirely sure if IoT Enterprise LTSB/LTSC Images are supported - the 2019 version works flawlessly however. secondly I'm not sure the Image my Vendor supplied is a "standard" Windows Image or if some customization has already been applied.

Here are some details on the Iso / DVD title:
ISO Name: OPK_Win_10_IoT_Enterprise_2016_LTSB_32Bit_English_X21_12007_Installation_DVD.iso
Disk Drive Name: CES_X86FREP_EN-US-DV5

Adding the 2020-07 LCU (KB4565511), DotNet 4.8 (KB4486129) and Adobe Update (KB4561600)

fails with error code 0x800f0922 in various stages: WinPE, WinRE, WinSE, OS:

Add-WindowsPackage: Add-WindowsPackage failed. Error code = 0x800f0922

The resulting Image does not have a higher build number than the original and fails to install on my test VMs:

WARNING: The Update Build Revision did not change after Windows Updates

When installing the original image manually the following Updates are applied via Windows Update (which takes at least an hour in my testing on a fast Desktop machine with 6 Cores/64GB RAM and NVMe SSD):

Windows10.0-KB4022632-x86-EXPRESS.cab
windows10.0-kb4033631-v2-x86-express.cab
windows10.0-kb4049411-v2-x86-express.cab
windows10.0-kb4103720-x86_0c3ff1b1c91df54b483f6c27b85b64a65b09f28e.msu
windows10.0-kb4103723-x86_827869f9c5e3f47732dd7e0cd6c048b920d573e0.msu
windows10.0-kb4565912-x86_d85141ed58bf80c5556e3c43a7ec491968e3b7e1.msu

most of these are not available via the msupdate catalog but have to be extracted from the test machine after the installation.

I'm not entirely sure if OSPackages would be the way to go to manually add these as I'm not sure what qualifies as "OSPackage".

I have attached the debug logs and am hoping you might be able to reproduce/fix this issue.
logs.zip
Thank you for your great work on this tool which has saved me hundreds of hours already!

There is support for 20H2 but the cmdlet Get-DownOSDBuilder does not.

Cannot validate argument on parameter 'UpdateBuild'. The argument "2009" does not belong to the set
"1909,1903,1809,1803,1709,1703,1607,1511,1507,7601,7603" specified by the ValidateSet attribute. Supply an argument
that is in the set and then try the command again.

regards
Faba

It would be nice if winsxs could be cleaned up with a parameter.

Dism.exe /Cleanup-Image /StartComponentCleanup /ResetBase

Windows Server 2019 (Version 1809 Build 17763.2183)
ADK (Version 10.1.22000.1)
ADK PE Add-ons (Version 10.1.22000.1)
ISO's tried:
SW_DVD9_Win_Pro_10_21H1_64BIT_English_Pro_Ent_EDU_N_MLF_X22-55036.ISO
SW_DVD9_Win_Pro_11_21H2_64BIT_English_Pro_Ent_EDU_N_MLF_-2_X22-82699.ISO
Module OSDBuilder (Version 21.10.12.1)
Module OSD (Version 21.10.12.1)

Special circumstances:
Machine does not have access to internet. Modules are manually imported.
D-Drive has dedup enabled.

C:\Windows\Logs\DISM\Dism.log

`
[28216] Mounting new image.

Wim: [E:\Sources\install.wim]
Image Index: [3]
Mount Path: [D:\OSDBuilder\Mount\os084638]
[28216] [0x80070032] EnableShortnamesOnApplyTarget:(548): The request is not supported.
[28216] [0x80070032] WIMSetFileShortName:(620): The request is not supported.
[28216] [0xd00000bb] WimImageSetInformationFile:(2367)
[28216] [0xc144012e]
Error DISM DISM WIM Provider: PID=28216 [RestoreHardlink:(556) -> setting hardlink failed] D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\Content.xml (HRESULT=0x80070032) - CWimManager::WimProviderMsgLogCallback
[28216] [0xd00000bb] RestoreHardlinks:(735)
[28216] [0xd00000bb] RestoreFileMetadata:(192)
[28216] [0xc144012e]
Error DISM DISM WIM Provider: PID=28216 [RestoreFileMetadata:(196) -> RestoreFileMetadata: RestoreHardlinks failed] D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\Content.xml (HRESULT=0x80070032) - CWimManager::WimProviderMsgLogCallback
[28216] [0xd00000bb] RestoreRefNode:(1722)
[28216] [0xc144012e]
Error DISM DISM WIM Provider: PID=28216 D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\Content.xml (HRESULT=0x80070032) - CWimManager::WimProviderMsgLogCallback
[28216] [0xd00000bb] RestoreRefNodeCallback:(1884)
[28216] [0xd00000bb] ProcessWimQueueNode:(98)
[28216] [0xd00000bb] DequeueWimData:(304)
[28216] [0xd00000bb] ImageWorkerThread:(250)
[28216] [0xd00000bb] GetImageErrorCode:(2837)
[28216] [0xd00000bb] RestoreFileNodeList:(2050)
[28216] [0xd00000bb] RestoreFilesCallback:(3963)
[28216] [0xd00000bb] EnumImageDataEntries:(1052)
[28216] [0xd00000bb] GetImageErrorCode:(2837)
[28216] [0xd00000bb] ImageWorkerThread:(198)
[28216] [0xd00000bb] RestoreAllData:(1101)
[28216] [0xd00000bb] WIMApplyImageInternal:(777)
[28216] [0x80070032] ImageStubMountDirectory:(985): The request is not supported.
[28216] [0x80070032] WIMMountImageHandle:(1275): The request is not supported.
[28216] [0x80004005] DeleteAndRestoreDirectory:(335): Unspecified error
[28216] [0xc1420117] DeleteAndRestoreDirectory:(336)
[28216] [0xc1420117] RestoreMountDirectory:(404)
[28216] [0xc1420117] WIMMountImageHandle:(1328)
Error DISM DISM WIM Provider: PID=28216 TID=40892 "Failed to mount the image." - CWimImageInfo::Mount(hr:0x80070032)
Error DISM API: PID=28216 TID=40892 onecore\base\ntsetup\opktools\dism\api\lib\imagingcommandobject.cpp:215 - CMountCommandObject::InternalExecute(hr:0x80070032)
Error DISM API: PID=28216 TID=40892 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070032)
Error DISM API: PID=28216 TID=36328 CMountCommandObject failed - MountImageInternal(hr:0x80070032)
Error DISM API: PID=28216 TID=36328 onecore\base\ntsetup\opktools\dism\api\lib\dismgeneralapisinternal.cpp:632 - MountImageInternal(hr:0x80070032)
`

A lot of files and directories are left under D:\OSDBuilder\Mount

`
D:\OSDBuilder\Mount\os084638
D:\OSDBuilder\Mount\os105423
D:\OSDBuilder\Mount\os110004
D:\OSDBuilder\Mount\os110641
D:\OSDBuilder\Mount\os114251
D:\OSDBuilder\Mount\os115155
D:\OSDBuilder\Mount\os122912
D:\OSDBuilder\Mount\os125141
D:\OSDBuilder\Mount\os084638\Windows
D:\OSDBuilder\Mount\os084638\Windows\WinSxS
D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d
D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsar.xml
D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipscat.xml
D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipschs.xml
D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipscsy.xml
D:\OSDBuilder\Mount\os084638\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsdan.xml
D:\OSDBuilder\Mount\os105423\Windows
D:\OSDBuilder\Mount\os105423\Windows\WinSxS
D:\OSDBuilder\Mount\os105423\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d
D:\OSDBuilder\Mount\os105423\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsar.xml
D:\OSDBuilder\Mount\os105423\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipscat.xml
D:\OSDBuilder\Mount\os105423\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipschs.xml
D:\OSDBuilder\Mount\os110004\Windows
D:\OSDBuilder\Mount\os110004\Windows\WinSxS
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.19041.746_none_cb918c7159c1f7d9
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nkrecognition.en-ca_31bf3856ad364e35_10.0.19041.1_none_799aed230997c7b3
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..platform-comruntime_31bf3856ad364e35_10.0.19041.746_none_a889d2a595dea698
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.19041.746_none_cb918c7159c1f7d9\hwrcommonlm.dat
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nkrecognition.en-ca_31bf3856ad364e35_10.0.19041.1_none_799aed230997c7b3\hwrenclm.dat
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsar.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipscat.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipschs.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipscht.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipscsy.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsdan.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsdeu.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsel.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsen.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsesp.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.19041.746_none_1da55dc225237a0d\ipsfin.xml
D:\OSDBuilder\Mount\os110004\Windows\WinSxS\amd64_microsoft-windows-t..platform-comruntime_31bf3856ad364e35_10.0.19041.746_none_a889d2a595dea698\InkDiv.dll
D:\OSDBuilder\Mount\os110641\Windows
D:\OSDBuilder\Mount\os110641\Windows\WinSxS
D:\OSDBuilder\Mount\os110641\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684
D:\OSDBuilder\Mount\os110641\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8
D:\OSDBuilder\Mount\os110641\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684\hwrcommonlm.dat
D:\OSDBuilder\Mount\os110641\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipsar.xml
D:\OSDBuilder\Mount\os110641\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipscat.xml
D:\OSDBuilder\Mount\os114251\Windows
D:\OSDBuilder\Mount\os114251\Windows\WinSxS
D:\OSDBuilder\Mount\os114251\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684
D:\OSDBuilder\Mount\os114251\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8
D:\OSDBuilder\Mount\os114251\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684\hwrcommonlm.dat
D:\OSDBuilder\Mount\os114251\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipsar.xml
D:\OSDBuilder\Mount\os114251\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipscat.xml
D:\OSDBuilder\Mount\os115155\Windows
D:\OSDBuilder\Mount\os115155\Windows\WinSxS
D:\OSDBuilder\Mount\os115155\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684
D:\OSDBuilder\Mount\os115155\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8
D:\OSDBuilder\Mount\os115155\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684\hwrcommonlm.dat
D:\OSDBuilder\Mount\os115155\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipsar.xml
D:\OSDBuilder\Mount\os115155\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipscat.xml
D:\OSDBuilder\Mount\os122912\Windows
D:\OSDBuilder\Mount\os122912\Windows\WinSxS
D:\OSDBuilder\Mount\os122912\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684
D:\OSDBuilder\Mount\os122912\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8
D:\OSDBuilder\Mount\os122912\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684\hwrcommonlm.dat
D:\OSDBuilder\Mount\os122912\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipsar.xml
D:\OSDBuilder\Mount\os125141\Windows
D:\OSDBuilder\Mount\os125141\Windows\WinSxS
D:\OSDBuilder\Mount\os125141\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684
D:\OSDBuilder\Mount\os125141\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8
D:\OSDBuilder\Mount\os125141\Windows\WinSxS\amd64_microsoft-windows-t..-coreinkrecognition_31bf3856ad364e35_10.0.22000.1_none_43dbdf4affbbc684\hwrcommonlm.dat
D:\OSDBuilder\Mount\os125141\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipsar.xml
D:\OSDBuilder\Mount\os125141\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.22000.1_none_95efb09bcb1d48b8\ipscat.xml

`

When trying to clean up the files in the folder D:\OSDBuilder\Mount I get the following error message.

I can successfully delete the files if I change owner to administrator.

Hi,

wonder if anyone else is having this problem:

• grabbed latest 1809 iso from VLSC
• ran: update-osmedia -Execute
• completes with WARNING:
  WARNING: The Update Build Revision did not change after Windows Updates
  WARNING: There may have been an issue applying the Latest Cumulative Update if this was not expected
• Get-OSMedia shows:
  NeedsUpdate : True

full log
`$osmedia | Update-OSMedia -Execute
VERBOSE: WSUSXML 21.10.14.1 Windows http://wsusxml.osdeploy.com/release
Operation Running ======================================================================================== Update-OSMedia PROCESS ======================================================================================== Source OSMedia Windows Image Information -OSMedia Path: C:\OSDBuilder\OSMedia\Windows Server 2019 Standard Desktop Experience x64 1809 17763.2237 -Architecture: x64 -Edition: ServerStandard -Type: Server -Languages: en-US -Major Version: 10 -Build: 17763
-Version: 10.0.17763.2237
-SPBuild: 2237
-SPLevel: 0
-Created Time: 08/05/2021 20:49:31
-Modified Time: 10/20/2021 13:39:30

WSUSXML (Microsoft Updates) Downloaded
01/14/2020 18:00:00 - DotNet - Microsoft .NET Framework 4.8 for Windows Server 2019 Version 1809 for x64 (KB4486153)
07/14/2020 17:00:00 - DotNetCU - 2020-07 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516)
07/14/2020 17:00:00 - DotNetCU - 2020-07 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516)
08/11/2020 17:00:00 - DotNetCU - 2020-08 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505)
08/11/2020 17:00:00 - DotNetCU - 2020-08 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505)
02/09/2021 18:00:00 - DotNetCU - 2021-02 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887)
02/09/2021 18:00:00 - DotNetCU - 2021-02 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887)
02/16/2021 22:00:09 - AdobeSU - Update for Removal of Adobe Flash Player for Windows Server 2019 for x64-based systems (KB4577586) 08/10/2021 17:00:06 - SSU - 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) 10/12/2021 17:00:00 - DotNetCU - 2021-10 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5006765) 10/12/2021 17:00:00 - DotNetCU - 2021-10 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5006765) 10/12/2021 17:00:06 - LCU - 2021-10 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5006672) ======================================================================================== ========================================================================================
Working Information
-WorkingName: build2110200414
-WorkingPath: C:\OSDBuilder\OSMedia\build2110200414
-OS: C:\OSDBuilder\OSMedia\build2110200414\OS
-WinPE: C:\OSDBuilder\OSMedia\build2110200414\WinPE
-Info: C:\OSDBuilder\OSMedia\build2110200414\info
-Logs: C:\OSDBuilder\OSMedia\build2110200414\info\logs

2021-10-20-161425 MEDIA: Copy Operating System to C:\OSDBuilder\OSMedia\build2110200414
2021-10-20-161453 WinPE: Mount WinPE.wim to C:\OSDBuilder\Mount\winpe2110200414
2021-10-20-161517 WinPE: Mount WinRE.wim to C:\OSDBuilder\Mount\winre2110200414
2021-10-20-162026 WinPE: Mount WinSE.wim to C:\OSDBuilder\Mount\setup2110200414
2021-10-20-162038 WinPE: (SSU) Servicing Stack Update
WARNING: Skipping WinPE SSU Update for this version of Windows
2021-10-20-162038 WinPE: (LCU) Latest Cumulative Update
WARNING: Skipping WinPE LCU Update for this version of Windows
2021-10-20-162038 MEDIA: Update Media Sources with WinSE.wim
2021-10-20-162038 WinPE: Export WinPE Package Inventory to C:\OSDBuilder\OSMedia\build2110200414\WinPE\info
2021-10-20-162055 WinPE: Dismount-WimsPE
2021-10-20-162206 WinPE: Export WIMs to C:\OSDBuilder\OSMedia\build2110200414\WinPE
2021-10-20-162213 WinPE: Rebuild C:\OSDBuilder\OSMedia\build2110200414\OS\sources\boot.wim
2021-10-20-162217 WinPE: Export WIM Inventory to C:\OSDBuilder\OSMedia\build2110200414\WinPE\info
2021-10-20-162218 OS: Mount to C:\OSDBuilder\Mount\os2110200414
2021-10-20-162403 OS: Replace C:\OSDBuilder\Mount\os2110200414\Windows\System32\Recovery\winre.wim
2021-10-20-162410 OS: Mount Registry for UBR Information
2021-10-20-162413 OS: (SSU) Servicing Stack Update
INSTALLED 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) - windows10.0-kb5005112-x64_99919606d4632b1f4b9bd4bff48a363739776047.cab
2021-10-20-162414 OS: Update Build Revision 17763.2237 (Pre-LCU)
2021-10-20-162414 OS: (LCU) Latest Cumulative Update
INSTALLING 2021-10 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5006672) - windows10.0-kb5006672-x64_45fca68c1624de53a4360ea477a6e6cf3d05f6bd.cab
C:\Users\user\AppData\Local\Temp\SSU\SSU-17763.2170-x64.cab
VERBOSE: Target Image Version 10.0.17763.2237
VERBOSE: Successfully added package C:\Users\user\AppData\Local\Temp\SSU\SSU-17763.2170-x64.cab
2021-10-20-163147 OS: Update Build Revision 17763.2237 (Post-LCU)
2021-10-20-163147 OS: (ASU) Adobe Flash Player Security Update
INSTALLED Update for Removal of Adobe Flash Player for Windows Server 2019 for x64-based systems (KB4577586) - windows10.0-kb4577586-x64_06ebe9335c8e417e086810e04b1ddc89cb427d03.cab
2021-10-20-163148 OS: (NetCU) DotNet Framework Cumulative Update
INSTALLED Microsoft .NET Framework 4.8 for Windows Server 2019 Version 1809 for x64 (KB4486153) - windows10.0-kb4486153-x64_a26355147c0496eb4e6b5493319946c508a15e0d.cab
INSTALLED 2020-07 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516) - windows10.0-kb4565625-x64_0030dee25072b20025ebb9c4f31844a0cd8bb26f.cab
INSTALLED 2020-07 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516) - windows10.0-kb4565632-x64-ndp48_8b481763cf07efc55f729bb1e08dc9fe32d3237a.cab
INSTALLED 2020-08 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505) - windows10.0-kb4569750-x64-ndp48_0dd3093f3f40487ea43b5e4d0016798e6e7d8f7a.cab
INSTALLED 2020-08 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505) - windows10.0-kb4569776-x64_3ea94342674c03a8316ebfe073b8f24816699cc5.cab
INSTALLED 2021-02 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887) - windows10.0-kb4601055-x64-ndp48_2f27cd9b42e020a7dd2abe2f899793fe28d7a93b.cab
INSTALLED 2021-02 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887) - windows10.0-kb4601060-x64_03981619b805af509ae2c728b082c79c41f51216.cab
INSTALLED 2021-10 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5006765) - windows10.0-kb5005540-x64-ndp48_c8735dd8f17d8d1a53a000b62ad96995b17bd490.cab
INSTALLED 2021-10 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5006765) - windows10.0-kb5005543-x64_2fa26eab83f0f1aac86b5598afe5e41fd40da70b.cab
2021-10-20-163204 OS: DISM Cleanup-Image StartComponentCleanup ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.17763.2237

[=========== 20.0% ]
The operation completed successfully.
2021-10-20-163408 OS: Backup Auto Extra Files to C:\OSDBuilder\OSMedia\build2110200414\WinPE\AutoExtraFiles
2021-10-20-163411 OS: Exporting Sessions.xml Patch Inventory
Source: C:\OSDBuilder\Mount\os2110200414\Windows\Servicing\Sessions\Sessions.xml
Destination: C:\OSDBuilder\OSMedia\build2110200414\info\Sessions.xml
Export: C:\OSDBuilder\OSMedia\build2110200414\Sessions.txt
Export: C:\OSDBuilder\OSMedia\build2110200414\info\xml\Sessions.xml
Export: C:\OSDBuilder\OSMedia\build2110200414\info\json\Sessions.json
2021-10-20-163412 OS: Export Inventory to C:\OSDBuilder\OSMedia\build2110200414
2021-10-20-163447 OS: Dismount from C:\OSDBuilder\Mount\os2110200414
2021-10-20-163854 OS: Export to C:\OSDBuilder\OSMedia\build2110200414\OS\sources\install.wim
2021-10-20-163932 OS: Export Configuration to C:\OSDBuilder\OSMedia\build2110200414\WindowsImage.txt

WARNING: The Update Build Revision did not change after Windows Updates
WARNING: There may have been an issue applying the Latest Cumulative Update if this was not expected

WARNING: Trying to rename the Build directory, but it already exists
WARNING: Appending 2110200439 to the directory Name

2021-10-20-163933 OS: Export Image Content to C:\OSDBuilder\OSMedia\build2110200414\info\Get-WindowsImageContent.txt
2021-10-20-163945 Media: Renaming "C:\OSDBuilder\OSMedia\build2110200414" to "Windows Server 2019 Standard Desktop Experience x64 1809 17763.2237 2110200439"

PS C:\WINDOWS\system32>
PS C:\WINDOWS\system32> Get-OSMedia -Newest -Verbose
VERBOSE:
VERBOSE: OSMedia Full Path: C:\OSDBuilder\OSMedia\Windows Server 2019 Standard Desktop Experience x64 1809 17763.2237 2110200439
VERBOSE: MediaType: OSMedia
VERBOSE: ImageName: Windows Server 2019 Standard (Desktop Experience)
VERBOSE: Arch: x64
VERBOSE: EditionId: ServerStandard
VERBOSE: InstallationType: Server
VERBOSE: Version: 10.0.17763.2237
VERBOSE: MajorVersion: 10
VERBOSE: MinorVersion: 0
VERBOSE: Build: 17763
VERBOSE: UBR: 17763.2237
VERBOSE: UpdateOS: Windows Server
VERBOSE: Languages: en-US
VERBOSE: ReleaseId: 1809
VERBOSE: CurrentBuild: 17763
VERBOSE: OSMFamily: Server ServerStandard x64 17763 en-US
VERBOSE: Guid (New): e4e2636d-58a7-4929-86de-88efb440ddb0
VERBOSE: Installed: Microsoft .NET Framework 4.8 for Windows Server 2019 Version 1809 for x64 (KB4486153) Windows10.0-KB4486153-x64.cab
VERBOSE: Installed: 2020-07 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516) windows10.0-kb4565632-x64-ndp48.cab
VERBOSE: Installed: 2020-07 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516) windows10.0-kb4565625-x64.cab
VERBOSE: Installed: 2020-08 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505) windows10.0-kb4569776-x64.cab
VERBOSE: Installed: 2020-08 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4570505) windows10.0-kb4569750-x64-ndp48.cab
VERBOSE: Installed: 2021-02 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887) Windows10.0-KB4601055-x64-NDP48.cab
VERBOSE: Installed: 2021-02 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4601887) Windows10.0-KB4601060-x64.cab
VERBOSE: Installed: Update for Removal of Adobe Flash Player for Windows Server 2019 for x64-based systems (KB4577586) Windows10.0-KB4577586-x64.cab
VERBOSE: Installed: 2021-08 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB5005112) Windows10.0-KB5005112-x64.cab
VERBOSE: Installed: 2021-10 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5006765) Windows10.0-KB5005543-x64.cab
VERBOSE: Installed: 2021-10 Cumulative Update for .NET Framework 3.5 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB5006765) Windows10.0-KB5005540-x64-NDP48.cab
VERBOSE: Not Installed: 2021-10 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5006672) Windows10.0-KB5006672-x64.cab
VERBOSE:

MediaType : OSMedia
ModifiedTime : 20/10/2021 16:39:32
Superseded : False
NeedsUpdate : True
Revision : OK
Updates : Update
Name : Windows Server 2019 Standard Desktop Experience x64 1809 17763.2237 2110200439
OperatingSystem : Windows Server
Arch : x64
ReleaseId : 1809
RegBuild : 17763
UBR : 17763.2237
Version : 10.0.17763.2237
MajorVersion : 10
MinorVersion : 0
Build : 17763
Languages : {en-US}
EditionId : ServerStandard
InstallationType : Server
ImageName : Windows Server 2019 Standard (Desktop Experience)
OSMFamily : Server ServerStandard x64 17763 en-US
FullName : C:\OSDBuilder\OSMedia\Windows Server 2019 Standard Desktop Experience x64 1809 17763.2237 2110200439
CreatedTime : 05/08/2021 20:49:31
OSMGuid : e4e2636d-58a7-4929-86de-88efb440ddb0
OSMFamilyV1 : 20210805204931ServerStandard
`

OSDBuilder 21.10.14.1 | OSD 21.11.9.1

Even if I follow:
WARNUNG: Use the following command before running New-OSBuild WARNUNG: Update-OSMedia -Name 'Windows Server 2019 Datacenter Desktopdarstellung x64 1809 17763.2300 de-DE' -Download -Execute

The WARNING will never disappear.

In these strange times I work from remote on a workstation in the office via RDP.
This workstation is fully installed and up2date with all necessary requirements for OSDbuilder
Windows 10 v2004 x64 Enterprise and ADK 2004 + WiinPe addon

Whenever I execute new-osbuild -execute the RDP session disconnects and the computer is no longer reachable over the network. When trying to login into the the local console every possible user account (user or local admin) gets following error and logon fails:

The Object Invoked Has Disconnected from its Clients

only a restart of the computer fixes rdp and local logons

The path looking for DartConfig8.dat is missing the full path. Line 520 in New-PEBuild.ps1.

} elseif (Test-Path $(Join-Path $(Split-Path $WinPEDart) 'DartConfig8.dat')) {

should be

} elseif (Test-Path $(Join-Path $(Split-Path "$OSDBuilderContent\$WinPEDart") 'DartConfig8.dat')) {

there is also no final else condition to log the condition where DartConfig*.dat does not exist.

else {
    Write-Warning "DartConfig.dat or DartConfig8.dat were not found. Unable to integrate."
}

I am trying to build a windows 20016 update image from the 2016 eval image. I run the following set of commands.

Import-OSMedia Update-OSMedia -Download -Execute New-OSBMediaISO

The ISO is created but when I try and run the windows 2016 install during the windows initial setup at the update check mark the install stops and jumps back to the "Start install screen".

It did take quite a while to update the media , I build the update in a VM and there is no 3rd party AV installed. Original works and no clear error on screen. Looking at logs for any issues but any other trouble shooting I can do please let me know

OS: 2012 R2
OSDSUS: 20.6.9.1

I am only pulling June's patches as of today. I made sure to run OSDBuilder -Update and OSDBuilder -UpdateModule.

I see that July hasn't been released yet at http://osdsus.osdeploy.com/release. Is there a status update on the release date?

Thanks!

Hi,
Would it be possible for Update-OSMedia to update patches from an internal WSUS or SCCM server that has already latest updates downloaded? I don't have direct internet access in the company I work.

version 21.3.9.2
Missing this function and the -superseded -remove options.
https://osdbuilder.osdeploy.com/docs/download-updates#remove-superseded
If there is a new command could you update the above page

Looking at automating ISO builds for a vsphere environment and it would help a lot being able to either set the ISO path and name or return the name of the created ISO for further scripting.

Does someone know why SSU and CU are not applied to wim files wimpe, wimse and wimre ?

The function Update-CumulativePE (AllFunctions.ps1) have exception to skip installation of the latest
cumulative update (LCU) for build greater or equal to 18362 for wimpe, wimse and wimre.

Likewise, servicing stack update (SSU) is skipped for those same wims (function Update-ServicingStackPE).

Also, the media sources are not updated for build greater or equal to 18362 or release greater or
equal to 1903 (function Update-SourcesPE).

I copied the WinPE OC's to the appropriate Release and Architecture folders with the us-en subfolder and yet the OC's are not populating into the final image. I cannot get the Powershell modules to be integrated into my WinPE.

the line in the new-osbuild is as follows 2020-09-15-130117 WinPE: ContentPack PEADK with no file loads.

I know/understand OSDBuilder is not meant for importing custom WIMs.
However I really like the easy ISO creation facility (for use in VMs mostly) and would also like to use it for other images, eg custom boot/repair images for instance. I mean only the ISO creation functionality.
Is this possible, eg could this function be used on any WIM without importing into OSDBuilder proper, or could it work if we do not do anything to the imported image except immediately creating the ISO? Thanks for any useful info regarding this.

I wish WIMwitch would have implemented an ISO creation facility, but I don't think it's a priority ;-(.

Thanks for the great work, much appreciated.

Bavo

When I run Update-OSMedia I get:

Update-OSMedia PROCESS
Get-Date : Cannot bind parameter 'Date' to the target. Exception setting "Date": "Cannot convert null to type
"System.DateTime"."
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.12.10.1\Public\Get-OSMedia.ps1:181 char:45

• ... SMFamilyV1 = $(Get-Date -Date $($XmlWindowsImage.CreatedTime)).ToStri ...

•                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : WriteError: (:) [Get-Date], ParameterBindingException
  • FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.PowerShell.Commands.GetDateCommand

You cannot call a method on a null-valued expression.
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.12.10.1\Public\Get-OSMedia.ps1:181 char:47

• ... OSMFamilyV1 = $(Get-Date -Date $($XmlWindowsImage.CreatedTime)).ToStr ...

•                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidOperation: (:) [], RuntimeException
  • FullyQualifiedErrorId : InvokeMethodOnNull

Cannot convert null to type "System.DateTime".
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\19.12.10.1\Public\Get-OSMedia.ps1:231 char:13

•         $ObjectProperties = @{
  

•         ~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidArgument: (:) [], RuntimeException
  • FullyQualifiedErrorId : nullToObjectInvalidCast

This is on Server 2019 that is fully update to date. This has happened on different versions of OSDBuilder, going back at least several months, probably to this summer. I don't believe there is any issue with the actual update process.

PowerShell version:

Name Value

PSVersion 5.1.17763.771
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.771
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

I am not sure if this is intended but I noticed it today while trying to automate the updates of my Windows 10 1903 vanilla image.

PS L:\Sources\OSD\OSBuilder\OSMedia> get-childitem


    Directory: L:\Sources\OSD\OSBuilder\OSMedia


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        7/27/2019   2:15 PM                   17763.475
d-----        8/17/2019   2:12 PM                   17763.475  1245
d-----        8/10/2019   2:14 PM                   17763.475  1421
d-----       10/12/2019   2:15 PM                   17763.475  1508
d-----         8/3/2019   2:16 PM                   17763.475  1608
d-----        7/27/2019   2:22 PM                   18362.86
d-----        8/17/2019   2:16 PM                   18362.86  1634
d-----       10/12/2019   2:18 PM                   18362.86  1832
d-----         8/3/2019   2:20 PM                   18362.86  2009
d-----        7/20/2019   2:20 PM                  1809 17763.557
d-----        7/20/2019   2:28 PM                  1903 18362.207
d-----       11/16/2019   2:22 PM                build0951
d-----        8/10/2019   2:14 PM                build1423
d-----       11/26/2019   2:28 PM                build2744
d-----         7/6/2019   3:38 PM                Windows 10 Enterprise x64 1809 17763.437
d-----        7/13/2019   3:42 PM                Windows 10 Enterprise x64 1809 17763.557
d-----         9/7/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2201
d-----        8/24/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2208
d-----        9/14/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2219
d-----        8/31/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2225
d-----        9/28/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2233
d-----       10/26/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2235
d-----       11/23/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2246
d-----        9/21/2019   2:22 PM                Windows 10 Enterprise x64 1809 17763.557 2256
d-----        10/5/2019   2:23 PM                Windows 10 Enterprise x64 1809 17763.557 2311
d-----       10/19/2019   2:23 PM                Windows 10 Enterprise x64 1809 17763.557 2320
d-----        11/9/2019   2:23 PM                Windows 10 Enterprise x64 1809 17763.557 2330
d-----        11/2/2019   2:23 PM                Windows 10 Enterprise x64 1809 17763.557 2334
d-----       11/26/2019  12:56 PM                Windows 10 Enterprise x64 1809 17763.557 5626
d-----         7/6/2019   4:58 PM                Windows 10 Enterprise x64 1903 18362.207
d-----       11/26/2019   1:05 PM                Windows 10 Enterprise x64 1903 18362.207 0551
d-----         9/7/2019   2:31 PM                Windows 10 Enterprise x64 1903 18362.207 3132
d-----        8/24/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3204
d-----        8/31/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3213
d-----       10/26/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3217
d-----       11/16/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3220
d-----        9/28/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3225
d-----        9/14/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3226
d-----       11/23/2019   2:32 PM                Windows 10 Enterprise x64 1903 18362.207 3258
d-----        9/21/2019   2:33 PM                Windows 10 Enterprise x64 1903 18362.207 3306
d-----        10/5/2019   2:33 PM                Windows 10 Enterprise x64 1903 18362.207 3323
d-----       10/19/2019   2:33 PM                Windows 10 Enterprise x64 1903 18362.207 3335
d-----        11/2/2019   2:33 PM                Windows 10 Enterprise x64 1903 18362.207 3351
d-----        11/9/2019   2:33 PM                Windows 10 Enterprise x64 1903 18362.207 3359
d-----        7/13/2019   3:51 PM                Windows 10 Enterprise x64 1903 18362.207 5133

After each Update-OSMedia run, a new folder is created. Each folder is 3-5gb so these end up taking up a lot of space. The following code is what I use to run my weekly updates of the image.

$location = "L:\Sources\OSD\OSBuilder"
$logfile = "$location\Logs\$(Get-Date -UFormat %Y%m%d%I%M).log"
Start-Transcript -Path $logfile -Append
Update-Module -Name OSDBuilder -Force
Get-OSBuilder -SetPath $location 
Get-OSMedia | Where-Object { $_.Revision -ne "Superseded" } | Where-Object {$_.Name} | Select-Object -ExpandProperty Name | ForEach-Object {
	Update-OSMedia -Name $_ -Download -Execute -Verbose 
}
Stop-Transcript

I am not sure if this intended or if I am just doing something completely wrong. My goal is to simply have OSDBuilder do a weekly check on the vanilla windows 10 1903 image and ensure it has all the current windows updates applied to it. It does not seem like it would sense to have a new folder be made since SCCM needs to have a source folder for the install.wim.

Any information you have on where I might be going wrong would be greatly appreciated.

Thank you!

There seems to be an issue when using -RemoveAppx during OSBuild process and Windows 11 ISO from Volume Licensing site,

I am able to complete the OSBuild process without issues. However, if I use the resulting WIM file on any of my test machines, there is a problem launching several of the built-in apps - Notepad, Paint, Snip & Sketch, Snipping Tool specifically. I believe these are new versions for Windows 11 so this could be part of the issue.

If I run the OSBuild process with the same media but do not remove any of the Appx apps, all of the built in apps launch without any problems - including the 4 mentioned previously.

Doesn't appear to be any difference in how many Apps are removed. I have tested it with a single app removed and with multiple apps selected to remove. If you do not remove anything then everything tests just fine.

I'm new to OSDBuilder, but I wanted to create a global build template. However, I get a message saying that no build tasks have can be found.

Version Information:

PS > Get-OSDBuilder
OSDBuilder 21.5.27.1 | OSDSUS 21.6.8.1 | OSD 21.6.4.1

Output:

PS > New-OSBuild
VERBOSE: OSDSUS 21.6.8.1 Windows http://osdsus.osdeploy.com/release
========================================================================================
New-OSBuild PROCESS
WARNING: OSBuild Task was not selected or found . . . Exiting!

Templates Directory:

PS > Get-ChildItem -Path $SetOSDBuilderPathTemplates OSBuild*.json

    Directory: C:\OSDBuilder\Templates

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----        6/15/2021   3:15 PM           4420 OSBuild Global 20H2 Customization.json

Command used to create template:

PS > $name = 'Global 20H2 Customization'
PS > New-OSBuildTask -TaskName $name -CustomName $name -ContentScripts -ContentStartLayout -SaveAs Template

Template JSON:

{
    "TaskType":  "OSBuild",
    "TaskVersion":  "21.5.27.1",
    "TaskGuid":  "e8b39d2a-8951-43cf-af8d-df35478e3d2d",
    "TaskName":  "Global 20H2 Customization",
    "CustomName":  "Global 20H2 Customization",
    "OSMFamily":  "Client Enterprise x64 19042 en-US",
    "OSMGuid":  "abe957c1-9a9d-4f44-ae1a-d168493bef91",
    "Name":  "Windows 10 Enterprise x64 20H2 19042.1052",
    "ImageName":  "Windows 10 Enterprise",
    "Arch":  "x64",
    "ReleaseId":  "20H2",
    "UBR":  "19042.1052",
    "Languages":  [
                      "en-US"
                  ],
    "EditionId":  "Enterprise",
    "InstallationType":  "Client",
    "MajorVersion":  "10",
    "Build":  "19041",
    "CreatedTime":  "\/Date(1620254927147)\/",
    "ModifiedTime":  "\/Date(1623781179737)\/",
    "ContentPacks":  null,
    "EnableNetFX3":  "False",
    "WinPEAutoExtraFiles":  "False",
    "WinPEOSDCloud":  "False",
    "WinREWiFi":  "False",
    "RemoveAppxProvisionedPackage":  null,
    "RemoveWindowsCapability":  null,
    "RemoveWindowsPackage":  null,
    "DisableWindowsOptionalFeature":  null,
    "EnableWindowsOptionalFeature":  null,
    "Drivers":  null,
    "ExtraFiles":  null,
    "Scripts":  [
                    "Scripts\\Remove-Windows10Bloat.ps1"
                ],
    "StartLayoutXML":  "StartLayout\\Windows10StartLayout.xml",
    "UnattendXML":  "",
    "AddWindowsPackage":  null,
    "AddFeatureOnDemand":  null,
    "WinPEADKPE":  null,
    "WinPEADKRE":  null,
    "WinPEADKSE":  null,
    "WinPEDaRT":  "",
    "WinPEDrivers":  null,
    "WinPEExtraFilesPE":  null,
    "WinPEExtraFilesRE":  null,
    "WinPEExtraFilesSE":  null,
    "WinPEScriptsPE":  null,
    "WinPEScriptsRE":  null,
    "WinPEScriptsSE":  null,
    "LangSetAllIntl":  "",
    "LangSetInputLocale":  "",
    "LangSetSKUIntlDefaults":  "",
    "LangSetSetupUILang":  "",
    "LangSetSysLocale":  "",
    "LangSetUILang":  "",
    "LangSetUILangFallback":  "",
    "LangSetUserLocale":  "",
    "LanguagePack":  null,
    "LanguageInterfacePack":  null,
    "LocalExperiencePacks":  null,
    "LanguageFeature":  null,
    "LanguageCopySources":  null
}

I've created a new ISO with current OSDBuilder. Then I created a USB-key for installation, but computers SSD drives are not found during setup. winPE seems to be broken in some matter. Or is this a issue on my side?