Search results

Yes, I can confirm, it's exactly the way you described. If I extract the SSU cab and queue all of 1) the SSU cab, 2) the SafeOS dynamic update, and 3) the remaining cab from the CU (or even the entire CU *.msu again), integration finishes correctly in this exact order. (I did not try to diff...

I just wanted to note that this topic was about Windows 10 22H2, and on this build right now it's exactly the opposite: current SafeOS update refuses to integrate before the CU. So whatever the solution is, it should take into account that it can go both ways.

nuhi Additionally, I noticed that when editing Winre.wim in "Save the image" saving mode, both Winre.wim and the containing install.wim are saved and unloaded. This is most likely a bug, or at least unwanted behavior. If I'm editing Winre.wim, then I'm expecting that only Winre.wim is saved and...

nuhi Okay, so I've found this article: https://learn.microsoft.com/en-us/windows/deployment/update/media-dynamic-update At a first glance, it says that one should not apply the LCU to the WinRE image (the "Add latest cumulative image" row is empty in the first column). However, there is this...

As I just said, I *don't* want it to be strictly offline, on the opposite, I want it to be *strictly online* and that's why I want to follow the best practice in applying all applicable updates to it. No idea. So for now, I'm trying to process Winre.wim in a separate session, applying "Latest...

Sorry, I'm confused now :D Should I disregard the original advice of applying CUs to Winre.wim via the Reapply menu? w.r.t. not updating, I'm trying to build a customized Macrium recovery image (+ personal rescue toolkit) on top of that WinRE environment, and it's going to be network-enabled...

Oh, thanks, I missed the "N.1" WinRE image in the list (indeed, it only appears after install.wim is mounted, which makes total sense. So then the question is, how do cumulative updates work? Does a cumulative update only apply on top of "its own" edition (like 22H2), or on top of any edition...

How often (or at all) is the WinRE recovery image (Winre.wim) updated over the lifetime of a Windows major version? And if yes, then how do I query the actual version/build of a Windows environment within a WIM image?

How is that even possible? What exactly happens when the enforcement is enabled, on a technical level?

That question was directed to Clanger (who wrote about using sysprep), not you.

Is there a particular reason to do the install + modify + sysprep + capture dance rather than just two NTLite passes as garlin above had suggested?

Hi. Let's say I need to build lots of customized Windows images. Consequently, to reduce the time of each individual image build, I want to integrate upgrades into an intermediate image and then use that as a base for further customization. So, instead of doing this: Unmodified ISO -> NTLite...

I still do not see what is "not possible" about my feature request. The behavior that I need is achievable manually, thus it should be possible programmatically.

That's not the situation I was talking about. In my case, the only condition that's blocking the unmount of the topmost image is the presence of nested mounted images. It is already possible to unmount them all, but I have to click "Unload" twice. Speaking plainly, what I want is to make NTLite...

Yeah, I'm not experienced in Windows' inner workings by any means. Actually, my goal here is still the same: to forward-port MT's preset to LTSC 2021. Any guides you would advise me to follow?

Hi, What exactly are the "Event Viewer channels" that can be configured on the Settings tab of NTLite? What am I gaining/losing by disabling them and what am I risking (in terms of lost functionality) by doing so? Or, to put it another way: why exactly I should not just disable all of them, or...

If processing of an image is interrupted when nested WIMs are mounted (example: install.wim, boot.wim and winre.wim), then clicking "Unload" on the image directory in the Image tab will only unmount winre.wim and boot.wim, skipping install.wim (presumably because it is impossible to unmount a...

There might have been a misunderstanding. What I said is that simply running ntlite.exe /forcelistcomponents /saveallstates and then saving the clean preset (as suggested above) is not enough to get the list of all detected components — this way you get the list of components that should have...

Thanks, I see your minimal services thread. I'll use that as a baseline and then just try to comb through the newly appeared services and scheduled tasks. Yup, there's a few LTSC threads around, but none of those answer my questions definitively (: So yeah, apologies for piling up yet another...

Thanks — it does work for services, tasks and tweaks, but there seems to be an inaccuracy with regards to components. When you run ntlite.exe /forcelistcomponents /saveallstates and then just save the clean preset, you do not get a listing of all components — you only get a listing of components...