Search results

Why would they be corrupted ? Boot.wim is only used until the first boot of the installation. install.wim/.esd for the following of the installation

That's what I did last year, in May or June, I think, then I modified the boot.wim (I've been using the 24h2 image since then, but it doesn't change much during the installation). What's the bug ? By removing WinRE, an error is normal if you use the new setup (2nd screen) And try with .wim...

Here

Don't you have this component ?

You can only remove WinRE and all components related with 24h2/25h2 if you are using the legacy setup. Option Boot/Setup - Legacy in Settings of NTLite (for boot.wim, index 2) for example

Yes, there are multiple .rtf files which are kept with the Pro versions, for example Enterprise versions use the .rtf files from the Pro versions. Keep this component until a fix is added in a future version of NTLite EDIT : Example of files kept...

Okay, with the same preset, it's fine with the old version of NTLite, but it's an error with the latest version, right ? Strange, nothing has changed in this Custom cleaning option (for updates).

Oh no, I mixed up two posts. What do you call a custom backup ?

Yes, a user reported this problem, nuhi must protect this file also for non-Pro versions (Enterprise among others). When this component is deleted It's in the to-do list

No, I don't have a bug, I still have the command prompt windows that appear very briefly just after installation, and this is normal (option added in NTLite applied to the installation)

I don't remember which packages/files it's anymore, it was a year ago (and I didn't see it on the forum) We test at each release of "real build" (without EP) and we keep the .1 since W10 (but maybe not since the 1st build)

When we tested with nuhi, there was a difference in files between the .1 + CU and the ISO with the CU already integrated (leftovers) We always use the .1 (which is why the "Placeholders" were added). PS: tested before and with the .1742

Which ISO (build version) are you using ? Are you just integrating EP 25h2, nothing else ? It's just an activation package, if the ISO works without the EP, that's weird I haven't seen anyone have a problem with the EP integration, to see if there are any other modifications

You're welcome. It's true that replacing Depend with Missing would probably be more understandable. The uninitiated might think that the checkpoint is already integrated and there's no need to add it again.

When you integrate a LP, you must also reintegrate the checkpoint (KB5043080). This is a new requirement with the 24h2 and the appearance of the checkpoint. There was roughly the same thing with Windows 8.1 (but not really a checkpoint).

Yes, it's the same update for 24h2 and 25h2, and the same for the following ones.

I haven't looked at how it works. With Windows 11 Home/Pro, these updates aren't integrated. That's why I deleted them from the .msu file (from 3.34GB to 1.31GB). EDIT : They would only be installed "online" and the update would detect the "NPU" I saw a registry key to add so that they would be...

Since 24h2, there are 2 French languages for the keyboard (never looked what the difference was), I removed the "French (Standard)" keyboard

Monthly updates have doubled in size because MS "added" the MSIX files. It's for Recall and other AI components, not for regular apps. It gets installed for NPU PCs only MS could have distinguished these updates, it would have avoided for those like us (without NPU PC) having to download...

Yes, there have been traces of "Copilot" in Windows for quite some time now. 2 components "linked" to Copilot in Windows