Same updates Loop

[Swelidingo]

Hi,
For the past two months, I've been receiving only those same five updates repeatedly. I've already updated OSDBuilder and even removed and reinstalled it from scratch, but those five updates keep showing up over and over again.

My OSD media already includes the latest updates and is based on the build as i had to use DISM manually to install march updates.

Windows 11 Enterprise x64 24H2 26100.3624

Any help would be greatly appreciated!

Microsoft Update Manifests Downloaded
2025-01-14 - DotNetCU - 2025-01 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 for x64 (KB5049622) - windows11.0-kb5049622-x64-ndp481_afb8c71d1958d98de4082ff732762242e9460fad.msu
2025-02-11 - ComponentDU SafeOS - 2025-02 Safe OS Dynamic Update for Windows 11 Version 24H2 for x64-based Systems (KB5053426) - windows11.0-kb5053426-x64_c81b1c234490a57c701ded095d5e2955c1240bdc.cab
2025-02-11 - LCU - 2025-02 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5051987) - windows11.0-kb5051987-x64_199ed7806a74fe78e3b0ef4f2073760000f71972.msu
2025-02-11 - LCU - 2025-02 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5051987) - windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu
2025-02-11 - SetupDU - 2025-02 Setup Dynamic Update for Windows 11 Version 24H2 for x64-based Systems (KB5053424) - windows11.0-kb5053424-x64_239f32c3df18b44c30912c429368813a49e27fb9.cab

KR to all

[darkmuncan-git]

I believe the updates need to be added to the manifest manually by the maintainers, this hasn't happened recently, so more recent updates are not found when scanned.

I imported the March 05 MS media, and also offering 2025-02 as "latest" updates.

[OSDeploy]

This is accurate. I am no longer updating OSDBuilder regularly due to lack of available time. This will not change anytime soon, unfortunately. Please seek alternatives.

David

[OSDeploy]

I just updated the readme on https://github.com/OSDeploy/OSDBuilder to reflect no ETA. My apologies.

[Swelidingo]

we appreciate the time you invested so far. am sure 100s if not 1000s of technicians are greatful for this nice product.

[OSDeploy]

we appreciate the time you invested so far. am sure 100s if not 1000s of technicians are greatful for this nice product.

Thx. To be honest, the main issue is testing. It would probably take me a few hours to update source updates, but Microsoft keeps changing the format on the updates, and testing with so many versions out there (Server, Windows 10, Windows 11, ARM64) takes a while. I know one of the more recent updates I did a few months back I finished up and pushed it about 3:00 when I was done, only to find a bug and stay up for another few hours.

At some point, OSDBuilder will be merged with OSDWorkspace, but there will not be any updates, you will need to source them and do testing, this way no more issues with updates not being up to date, but that won't be for a few more months when I find time.

[alayac]

This is accurate. I am no longer updating OSDBuilder regularly due to lack of available time. This will not change anytime soon, unfortunately. Please seek alternatives.

David

I'd like to use this opportunity to reach out and thank you for OSDBuilder and its predecessor, OSBuilder. These solutions helped my team to stop using reference images at a time that Microsoft made it harder and harder to use their own tools and solutions to get things done efficiently. As part of our current transition to Windows 11, we are now downloading fresh media each month directly from the admin portal and making customizations / updates on the fly during OS installation.

I'm sure I'm not alone in saying that your efforts over the years are greatly appreciated.

[OSDeploy]

This is accurate. I am no longer updating OSDBuilder regularly due to lack of available time. This will not change anytime soon, unfortunately. Please seek alternatives.
David

I'd like to use this opportunity to reach out and thank you for OSDBuilder and its predecessor, OSBuilder. These solutions helped my team to stop using reference images at a time that Microsoft made it harder and harder to use their own tools and solutions to get things done efficiently. As part of our current transition to Windows 11, we are now downloading fresh media each month directly from the admin portal and making customizations / updates on the fly during OS installation.

I'm sure I'm not alone in saying that your efforts over the years are greatly appreciated.

Much appreciated. I apologize I have not had time to keep this project updated. Besides the lack of time, another reason I have not updated this is Microsoft is changing much of the WIM, and I have a concern that editing a WIM may prevent the OS from getting updates or working properly. Because I this, I no longer recommend editing the WIM, do this in post. No matter what you think about how it images faster with the updates baked in, breaking your OS and deploying to tens or hundreds of computers will cost you considerably more time. I don't want that responsibility or liability.
If you work with customers and are doing this as a service, make sure you're covered if/when you blow things up editing the WIM.

David

[squorf]

Does anyone know where you would manually update the manifest to see the manually added Windows updates to install?

[Swelidingo]

i thought of asking the same question actually. Only the developers can update the manifests as they are downloaded when updating the module.
they are downloaded to this folder
C:\Program Files\WindowsPowerShell\Modules\OSD\25.4.6.1\Catalogs\osd-manifests\mscatalog
i even tried to update them manually but there is alot to edit and add.

[OSDeploy]

i thought of asking the same question actually. Only the developers can update the manifests as they are downloaded when updating the module. they are downloaded to this folder C:\Program Files\WindowsPowerShell\Modules\OSD\25.4.6.1\Catalogs\osd-manifests\mscatalog i even tried to update them manually but there is alot to edit and add.

Correct. I started doing this in 2019 with Windows 10, and there were not that many versions. Over the years, adding Windows 11, the different Server flavors ... now, its too much time and effort. Back then I did this because I used these tools for my job, which gave me time during the day at work to do things like this. Unfortunately, that's not what I do now, and I don't have the personal time to commit to OSDBuilder anymore.
I still spend time on OSDCloud, which is used by considerably more people, but I don't have enough free time to spend on both tools.

[xe0n11]

Are you able to provide the bits to generate manifests? It would be good to branch this off and keep the project alive...

FYI - my work around has been to download the latest install media from VS, add the new media, apply it to existing sequence, run.

[OSDeploy]

Yes, but time is limited. As I have been recently laid off, most of my time is focused on returning to the land of the employed. It may be weeks before I can allocate some time.

[xe0n11]

Sounds good, dude.

Take your time.