Search results

Yes, most of the AI is in the cloud, but some (some traces) is on the OS. I haven't seen the update for this, or maybe it's in Insider, I haven't looked yet.

Most (perhaps not all) could be removed from Windows For now, the "real" AI components are installed on NPU machines.

More info here : https://www.intel.com/content/www/us/en/architecture-and-technology/vpro/what-is-vpro.html

The main technology of vPro is AMT (Active Management Technology) and there are drivers for that For RAID/VMD drivers, it all depends on how the assembler configured the BIOS for the controller. Generally, Dell/Lenovo sets the VMD in the bios (but not an obligation, depends on the series/models...

Some info here https://www.ntlite.com/community/index.php?threads/ntlite-multiple-images.5749/#post-54064

Nuhi has removed everything that was applied by default and saved in presets since a few versions ago (to make it look cleaner). These commands should be part of it. nuhi will confirm if this is it or not

Indeed, I skipped the "across editions" part. I thought it was simply missing for integration.

MSIX/APPS are to be integrated from the Updates page If it's the MSIX contained in the LCUs, only available for NPU machines

In the latest Insider builds, for now

Strange, I didn't have any problems installing 26200.6899 But the local account is created with unattended and I use SkipMachineOOBE compared to you

Oh yes, my bad, I meant the mcu I was modding a BIOS for a user, and he was asking me for the MEI and I typed MEI here :D I told him that the MEI is separate from the BIOS

If the mcupdate_genuineintel.dll file isn't up to date, then Windows will use the Management Engine Interface firmware version (if it's up to date, of course). Easy to check under Windows which version is "in use" Yes, for those who don't play or benchmark, the difference won't be noticeable...

I have no trace of Copilot file in WinSxS or the files have different names

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).