Search results

Your ISO (or image directory) is on a disk / USB drive formatted in FAT32 ? Which would explain the 4GB limit

It's DDR4 (F4-3200C16D-16GTZSK)

For STIBP, I had found how to disable it only under Linux, but nothing for Windows. I'll check if it's present in the old microcodes (before the famous patches) or not.

Thanks for info I tried it once at the very beginning of the 24h2, with an Intel CPU. From what I remember, it was good... Or maybe not. But I haven't tried it since, I always use the AMD file renamed to Intel.

Delete it in the Cache directory if you no longer use it or delete it from the Update page before launching the process, it will not be applied but will still be present (well, not sure, never tried it) Otherwise, NTLite applies everything in the preset (if present) EDIT : You can remove all...

To back up your WinRAR configuration, export the .REG file from WinRAR and integrate it using NTLite (Registry page). In WinRAR, Options => Import and Export => Export configuration.... Me, I no longer install WinRAR, I copy the WinRAR directory into the image and integrate the .REG file

I know these values for FeatureSettings "FeatureSettingsOverride"=dword:2000003 "FeatureSettingsOverrideMask"=dword:00000003 I hadn't looked for xxxx, I'll look

Answered here : https://ntlite.com/community/threads/do-you-guys-know-how-to-disable-all-cpu-mitigations-in-windows.5910/post-56604

Since Windows 11 24h2, for an Intel CPU, you delete (or rename as you wish) the mcupdate_GenuineIntel.dll file and rename the mcupdate_AuthenticAMD.dll file to mcupdate_GenuineIntel.dll Do the opposite with an AMD CPU. Alternatively, you can also use a empty .txt file, eg, that you rename to...

This is the one appxsupport32 'Modern App support - 32 bit'

I remove efsfeature (feature) in the image and never had any installation problems efssvc (service) must be kept for installation and is "marked" in red (not recommended) The solution is to keep "Telemetry Client" for now then, with Windows 10 (no problem with Windows 11) To see with Nuhi to...

fclip and clipsvc are 2 different components Yes Windows Update can be removed in the image, but Windows Update service can only be removed in Live

Service ClipSVC and Microsoft Account It's best to keep "KMS Connection Broker" as well, this prevents the sppsvc service from remaining constantly running. By checking the Activation box in the Compatibility (Components) menu of NTLite, the associated components should be protected.

The few times it happens to me, I restart the PC and it's fine

If it's 1, 11, 12, .. 20, 21, 3, 30, etc. then that's normal as mentioned above

For nuhi

medizin It should be fine with the latest version

NTLite does not have this type of log

The taskbar works, I don't know about the Start Menu, I don't use the Windows one. nuhi will look into those components.

Okay, you're keeping WFE Core (MicrosoftWindows.Client.Core) for "Live captions" it seems And for "Voice access" you're keeping WFE - Voice ? Have you tried removing it ? In an 26100.1 image, "Live captions" is separated if I remember correctly, but not in Live it seems. Or the components are...