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