Recent content by garlin

More specifically, integrating what files? Language Packs, Feature on Demand (FOD), or Appx packages?

There's three options for removing unwanted images: 1. From the Image screen, right-menu select on any unloaded image and Delete. Only one image at a time can be removed this way. 2. From the Apply screen, click on "Remove nonessential editions" and select the unwanted images. All selected...

KERNELBASE.dll is a generic error, it usually means "something went wrong", but Windows can't figure out how to pass the specific crash info back to you. You're also examining OverwolfLauncher.exe, but your crash message is from Overwolf.exe itself.

Check the timestamp on the ISO's install.wim. Sounds like the new WIM wasn't fully created before NTLite bailed.

What's the name of the final image file? install.esd or install.wim? If you opened the NTLite.log, does it confirm you asked for ESD compression?

I have no idea. But the Overwolf site keeps mentioning .NET 4.8 in several places, so forcing the latest CLR might or might not work. You can change it on the live system, and restart Windows. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]...

FYI -- Per nuhi's forum rules, we're not allowed to discuss projects that sideload WMC (or other licensed features) to Windows editions that don't have it. There's plenty of enthusiast sites which already cover that subject. Don't cross the DMCA waters.

Overwolf is built on top of OBS. Other than install issues, no one's opened a thread on a broken OBS. Try disabling OnlyUseLatestCLR.

<c>netframework4wcf 'Windows Communication Foundation (WCF) 4'</c>

For every image, there's a base install language which is used as the system's UI language. You can add extra LP's for your users' benefit when creating their account profiles, but that doesn't change the system's language. So a base English-US image would always install as English-US Windows...

You typically answer "Always deleted this" to reflect your personal modding. But that doesn't provide the correct advice for users who don't follow the same path. OOBE's dependency on CreateObjectTask was discussed as far back as in Clanger's time.

This task is required for OOBE, which we know you always skip in Unattended mode.

When you turn off Recall using only DISM in the offline image, doesn't that also trigger a servicing bug? I proved that last year, by skipping NTLite and using manual DISM commands on a clean image. To be fair, I haven't re-tested what happens using an updated 24H2 image.

I tried the original settings (26100.1742 + preset), and Explorer's broken. Removing <c>microsoftwindows.client.aix</c> put it back to normal. If the original intention was to remove Recall, and NTLite reverted to the old behavior of not fixing WindowsAppRuntime.CBS, then DISM is the only way...

For the most part, this list of disabled services is safe except for: Microsoft\Windows\CloudExperienceHost\CreateObjectTask This task must be enabled during install; and can be safely disabled after your user account has been provisioned (logged on). You really shouldn't disable Time Sync...