Feature Request: Allow Users to Lock Components from Removal

[slownumb]

Hi nuhi, I’d like to suggest adding a user-defined component lock/protection feature to NTLite. It would be very useful to manually mark specific components as “Do not remove,” regardless of the current compatibility settings or presets.

For example, I recently identified three components whose removal caused real application compatibility issues:

• AF_UNIX (afunix): Docker Desktop
• WinINet 32-bit (wininet32): Adobe applications (not total breaking, but keeps poping up messages) and Microsoft Office installer
• RichEdit 32-bit (msftedit32): third-party Win32 applications (in my case Razer Firmware Updater)

A simple “Lock/Protect component” option would allow users to maintain their own known-good dependency list while still aggressively debloating the rest of Windows. This could be especially useful for advanced users who iteratively test and refine their images.

 

[francis11]

Already protected if you use NTL Compatibility tab wisely and don't unclick your prefered keepings still removable - use Type here to filter option in Components section according to your preferred Preset/ Template:

 

[tistou77]

For RichEdit 32-bit (msftedit32) I needed it too, for a soft, but it's just the DLL, so I'm protecting the DLL,
And there's no problem if the component is deleted.
Same for WinINet 32-bit (wininet32)