OSDeploy
Server OS Supported?
OSDBuilder 24.10.8.1 seems to only support client OS, is this intended?
Import-OSMedia BEGIN 2024-11-19-094222 Get-OSDBuilder: Validating OSDBuilder Content 2024-11-19-094222 WARNING: This version of OSDBuilder supports: 2024-11-19-094222 WARNING: Windows 10 1607 - 21H2 x64 2024-11-19-094222 WARNING: Windows 11 21H2 - 24H2 x64
The command Save-OSDBuilderDownload -Download -GridView -UpdateArch x64 seems to show some Server updates for 21H2 and above but are not categorised as Windows 10 and 11 are, the fields are empty.
Update-Media also no longer shows any imported server OS for me.
Some thoughts. At this point, OSDBuilder isn't really supported at all. It's a Project that I don't have time to maintain by myself. One of the issues was the updates were coming from WSUS, but gathering these updates and testing them required more time per Patch Tuesday than I could maintain. Last month I tried porting over from WSUS to Microsoft Update Catalog. This took much less time, but some bugs. I thought this was going well, but Microsoft being Microsoft changed the way updates are applied again and I'm not able to get the LCU to install to a mounted WIM. Finally, I've always been a Client person, not Server. So Server working in OSDBuilder was always because Client was working.
So at this time, I can keep adding monthly Patch Tuesday updates, but no point if the LCU won't apply, but unless there are people that want to contribute their own time to OSDBuilder to keep it running, then I'm probably out too.
@OSDeploy I'm confused. There are and have been so many people that are open to helping. But don't get me wrong. It seems we never get replies to our opening to help maintaining the code.
Pull requests never get looked at. There is people that are maintaining the code for you. But only you can verify and process them.
@OSDeploy I'm confused. There are and have been so many people that are open to helping. But don't get me wrong. It seems we never get replies to our opening to help maintaining the code.
Pull requests never get looked at. There is people that are maintaining the code for you. But only you can verify and process them.
Then let's clear the confusion. There have been people offering to help which is updating the catalogs, but this is not the current problem. The current problem is applying an MSU Update to a mounted WIM, offline. I can do this with Windows 10, even Server 2019, but not Windows 11. If you have a solution for this, I'm all ears, but if that's no longer possible, since Microsoft made the change to LCU, what is the ask? Windows 10 and Windows Server 2019 only? I worked on this earlier this month, and Server 2019 seems to work by adding proper Catalogs (see screenshot), but not Windows 11. That is what I need help with. As for Pull Requests, again, those are mostly for catalogs, which I have updated, with only currently open in the last 12 months.
Mmm that is strange. I've been updating LCU's on Server 2019 and 2022 perfectly fine. Are you running in Powershell Core or Windows Powershell?
I've noticed that Powershell Core seems to be more stable.
If there's a PR you need me to review, let me know, but I only have maybe 1-2 hours a month that I can add to OSDBuilder (I've spent 8+ hours this month already). So while it may take a few minutes to approve a PR, etc, that does not include any testing, which as you know can take at least 30 minutes minimum. If you're good with no testing on my end, make a note of that and I'll approve.
Mmm that is strange. I've been updating LCU's on Server 2019 and 2022 perfectly fine. Are you running in Powershell Core or Windows Powershell?
I've noticed that Powershell Core seems to be more stable.
I'll ask again, since you seem to be ignoring my previous reply where I need help with Windows 11. Please show me the "so many people that are open to helping" to get Windows 11 working and I'll gladly release the new Updates in the new format.
I'm unsure what the screenshot is I'm looking at. Form my side I've created a script that reads WSUS and pulls all update data for all OS'. Also for Windows 11 24H2. That delivers me just an LCU and DotNetCU as I'm used to.
With OSDBuilder and OSD I've always pushed these catalog files myself and then using Powershell Core, I've been able many times to updates the images.
What might be important here is the OS you use to run the offline servicing from. What are the issues you specifically encounter? As the screenshot earlier shows Server 2019 which is confusing me as you pointed out you need some help with W11.
I'm unsure what the screenshot is I'm looking at. Form my side I've created a script that reads WSUS and pulls all update data for all OS'. Also for Windows 11 24H2. That delivers me just an LCU and DotNetCU as I'm used to.
With OSDBuilder and OSD I've always pushed these catalog files myself and then using Powershell Core, I've been able many times to updates the images.
What might be important here is the OS you use to run the offline servicing from. What are the issues you specifically encounter? As the screenshot earlier shows Server 2019 which is confusing me as you pointed out you need some help with W11. Ignore the screenshots. Windows 11 is not working. Please test on your end.
Hi David,
The new update mechanism is working fine for me and i'm glad it's causing you less manual work. I can confirm the Update issues with W11 when using my regular (Windows Server 2022) machine to apply the updates.
I did some testing with a W11 VM and OSDBuilder is able to patch new W11 Images when running on a W11 24H2 Machine. I assume this would also work for Windows Server 2025 once the Updates are there.
Testing W11 is actually able to install updates using Add-Windowspackage -online
Pre-Update
PS C:\WINDOWS\system32> get-hotfix Source Description HotFixID InstalledBy InstalledOn
------ ----------- -------- ----------- -----------
DESKTOP-OO... Update KB5045934 11/14/2024 12:00:00 AM
DESKTOP-OO... Update KB5048779 NT AUTHORITY\SYSTEM 11/26/2024 12:00:00 AM
DESKTOP-OO... Security Update KB5043080 9/6/2024 12:00:00 AM
DESKTOP-OO... Security Update KB5043113 9/6/2024 12:00:00 AM
Update Installation
Add-WindowsPackage -Online -PackagePath 'C:\Users\myuser\Downloads\windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu'
Add-WindowsPackage -Online -PackagePath 'C:\Users\myuser\Downloads\windows11.0-kb5046617-x64_1e5d7b716c0747592ae80c218f1d81bbb7b0c7ab.msu'
Post Update. Notice that KB5043080 is not showing
PS C:\WINDOWS\system32> Get-HotFix | Sort-Object InstalledOn
Source Description HotFixID InstalledBy InstalledOn
------ ----------- -------- ----------- -----------
DESKTOP-OO... Security Update KB5043113 9/6/2024 12:00:00 AM
DESKTOP-OO... Update KB5045934 11/14/2024 12:00:00 AM
DESKTOP-OO... Security Update KB5047621 NT AUTHORITY\SYSTEM 11/26/2024 12:00:00 AM
DESKTOP-OO... Update KB5048779 NT AUTHORITY\SYSTEM 11/26/2024 12:00:00 AM
DESKTOP-OO... Security Update KB5046617 DESKTOP-OO6GS4Q\myus 11/26/2024 12:00:00 AM
After installing the latest Updates on the VM I installed OSDBuilder (my Fork to be precise).
Set-ExecutionPolicy RemoteSigned
Install-Module OSD
Import-Module C:\dev\OSDBuilder
Get-OSDBuilder -CreatePaths
copied an existing W11 IoT Enterprise LTSC 24H2 Image to W11 VM OSMedia im working with:
PS C:\WINDOWS\system32> Get-OSMedia
MediaType : OSMedia
ModifiedTime : 11/14/2024 10:44:01 AM
Superseded : False
NeedsUpdate : True
Revision : OK
Updates : Update
Name : Windows 11 IoT Enterprise LTSC x64 24H2 26100.1742
OperatingSystem : Windows 11
Arch : x64
ReleaseId : 24H2
RegBuild : 26100
UBR : 26100.1742
Version : 10.0.26100.1742
MajorVersion : 10
MinorVersion : 0
Build : 26100
Languages : {en-US}
EditionId : IoTEnterpriseS
InstallationType : Client
ImageName : Windows 11 IoT Enterprise LTSC
OSMFamily : Client IoTEnterpriseS x64 26100 en-US
FullName : C:\OSDBuilder\OSMedia\Windows 11 IoT Enterprise LTSC x64 24H2 26100.1742
CreatedTime : 9/6/2024 5:22:28 AM
OSMGuid : 8db4211a-44b5-426f-833b-2fab13e6b547
OSMFamilyV1 : 20240906052228IoTEnterpriseS
Running the regular Update command works on the windows 11 VM on the second attempt.
Update-OSMedia -Download -Execute -ShowHiddenOSMedia
Results after Updating:
- Updates take forever to apply (which has been my overall experience with Windows 11)
- Dynamic Updates fail (Though I think that might just be the LTSC Image)
- LCU Update works!
OSMedia after Update:
PS C:\WINDOWS\system32> Get-OSMedia
MediaType : OSMedia
ModifiedTime : 11/26/2024 5:40:50 PM
Superseded : False
NeedsUpdate : True
Revision : OK
Updates : Update
Name : Windows 11 IoT Enterprise LTSC x64 24H2 26100.2314
OperatingSystem : Windows 11
Arch : x64
ReleaseId : 24H2
RegBuild : 26100
UBR : 26100.2314
Version : 10.0.26100.2314
MajorVersion : 10
MinorVersion : 0
Build : 26100
Languages : {en-US}
EditionId : IoTEnterpriseS
InstallationType : Client
ImageName : Windows 11 IoT Enterprise LTSC
OSMFamily : Client IoTEnterpriseS x64 26100 en-US
FullName : C:\OSDBuilder\OSMedia\Windows 11 IoT Enterprise LTSC x64 24H2 26100.2314
CreatedTime : 9/6/2024 5:22:28 AM
OSMGuid : 8e53fd03-5482-471d-b404-b14caa8e5f21
OSMFamilyV1 : 20240906052228IoTEnterpriseS
So I'm assuming Microsoft added some new DISM functions to W11 only. I do not think it will be easy or even possible to add that new functionality to W10/Windows Server <2025 Machines.
One might add a warning to stop users from complaining (though I doubt it will change much in terms of issues created)...
Given all the negative Feedback in this repo I just want to say: I'm using 2016/2019 LTSB/LTSC Images for work and much appreciate you keeping the Updates working and everything else you have done and are still doing for the community!
Cheers
@burnacid reach out to me about WSUS Windows 11 24H2 that you have so I can test those updates
@zottelbeyer Thanks for the update. Yes it was the LCU that fails Windows 11 and doesn't change the Build
@burnacid reach out to me about WSUS Windows 11 24H2 that you have so I can test those updates
This is what my script has created Windows 11 24H2.zip
@burnacid - are you able to share the script you used to generate those (or point in right direction, happy to write myself)? Cheers 🍻
@zottelbeyer - nice troubleshooting!
Re: DISM - might be handy to add optional support to use the Dism.exe provided with Windows ADK (if you have it installed on the same box you build media).
Dism.exe included with Server 2025 and Windows 11 24H2 (as of 2024-12) - Version: 10.0.26100.1150 Dism.exe included with ADK 10.1.26100.2454 (2024-12) - Version: 10.0.26100.2454
Snippet I use in some of my scripts:
# Set Arch
$WinPEArchitecture = "amd64"
# Get ADK folders
$InstalledRoots = 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots'
$KitsRoot10 = Get-ItemPropertyValue -Path $InstalledRoots -Name 'KitsRoot10'
$AdkRoot = Join-Path $KitsRoot10 'Assessment and Deployment Kit'
$WinPERoot = Join-Path $AdkRoot 'Windows Preinstallation Environment'
$WinPEOCsRoot = Join-Path $WinPERoot\$WinPEArchitecture 'WinPE_OCs'
$DeploymentToolsRoot = Join-Path $AdkRoot (Join-Path 'Deployment Tools' $WinPEArchitecture)
$WinPERoot = Join-Path $WinPERoot $WinPEArchitecture
# Set path to dism.exe
$DISMFile = Join-Path $DeploymentToolsRoot 'DISM\Dism.exe'
@OSDeploy - might be worth installing the latest ADK on your dev box and test scripts using the provided dism? 🤷♂️
FYI - https://support.microsoft.com/en-us/topic/-operation-is-not-supported-error-installing-a-post-checkpoint-update-by-double-clicking-the-msu-package-86b89ef4-d5d3-4a2d-b471-3d67c8ea4f0e
This could explain the problem...
FYI - https://support.microsoft.com/en-us/topic/-operation-is-not-supported-error-installing-a-post-checkpoint-update-by-double-clicking-the-msu-package-86b89ef4-d5d3-4a2d-b471-3d67c8ea4f0e
This could explain the problem...
It doesn't. Updates still won't apply after re-applying KB5043080. It might be related to this issue: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2#issues-might-occur-with-media-which-installs-the-october-or-november-update but we'll just have to wait and see.
In the meantime just spin up a W11 Machine if you need to patch W11 24H2.