Mit Hilfe von Powershell lassen sich die Built-in Apps in Windows 10 aus der install.wim entfernen. Auf seinem System Center Configuration Manager Blog hat André Picker ein super Powershell Script veröffentlicht. Das Script muss auf einem Windows 10 Rechner ausgeführt werden.

 Download Script

 Syntax: Example: .\removeapps.ps1 -pathtowim c:\10\install.wim -selectapps $true

 Man kann natürlich auch mit den DISM- Befehlen manuell arbeiten, aber das Script erledigt die Aufgabe perfekt.

 Quelle: http://www.clientmgmt.de

Andere Variante, die ich auch gerne benutze:

mkdir C:\WimMount

Get-WindowsImage -ImagePath C:\temp\install.wim

Mount-WindowsImage -path C:\WimMount -ImagePath C:\temp\install.wim -Index 3

Get-AppxProvisionedPackage -path c:\WimMount | out-gridview -PassThru | Export-Clixml c:\temp\ProvisionedApps.xml

Import-Clixml -Path C:\temp\ProvisionedApps.xml | Remove-AppxProvisionedPackage -Path c:\WimMount

Dismount-WindowsImage -Save

weitere Ideen:

Removing Windows 10 Built-in Apps Offline WinPE Quick Guide

Windows System Image Manager known issue

When using Window System Image Manager (SIM), you might encounter errors if the ADK is installed on a device running a 64-bit version of Windows. To create unattended Windows Setup answer files on a 64-bit version of Windows, download the WSIM 1903 update, and follow the included installation instructions.

Updating Windows System Image Manager for Windows 10, Version 1903

Checking to see if your system is affected:
=================================================================================
1. If the host system that is running the ADK is 32-bit, you are not affected and do not need to update anything.
2. If the host system that is running the ADK is 64-bit, you are affected need to follow the steps below.

For Install Instructions read the readme.txt File in Download Folder

Quelle: docs.microsoft

OSDBuilder is a PowerShell module to help you perform Offline Servicing to a Windows Operating System Image. By using an Offline method of configuring an Operating System, it can then be imported in MDT or SCCM and used like any other OS Deployment. This includes being able to use in an Upgrade Task Sequence, which you cannot do with a Captured Image.

The main difference between OSDBuilder and other scripted methods for Servicing a Windows Image Offline is that OSDBuilder creates an answer file called a Task (think Task Sequence). Since the Task has all the information it needs to update the Windows Image, there is no interaction necessary, and as long as the content (updates) are updated regularly, the Task can be repeated as needed.

Since the configuration is also saved in a Task, it is possible to select multiple tasks to run, and they will execute one right after another. This makes performing a monthly update take a few minutes to kick off. After a few hours, everything will be complete!

Website

Brain Dumps and basic commands for me:

Install OSDBuilder &  Import the Operating System

Install-Module -Name OSDBuilder -Force
Import-Module -Name OSDBuilder -Force

Import-OSMedia

Update-OSMedia -Download -Execute 

New-OSBuildTask -TaskName Build-060419 -EnableNetFX3

New-OSBuild -ByTaskName Build-060419-Execute

Anleitungen:

Quick Start Guide Windows 10 WaaS Servicing Updates via OSDBuilder

Download Evaluierungsversionen von Windows 10 1903 Enterprise x64

Download Evaluierungsversionen von Windows 10 1903 Enterprise x86

Evaluation to Full

Dism /online /Get-TargetEditions
DISM /online /Set-Edition: /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula
https://docs.microsoft.com/en-us/windows-server/get-started/supported-upgrade-paths

KMS client setup keys