Integrate updates, drivers, automate Windows and application setup

NTLite (64-bit)

NTLite 2.3.4.8658 (64-bit)

  -  22.72 MB  -  Demo

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of NTLite 2.3.4.8658 (64-bit).


For those interested in downloading the most recent release of NTLite (64-bit) or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • NTLite 2.3.4.8658 (64-bit) Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    NTLite 2.3.4.8658 (64-bit) Screenshot 1
  • NTLite 2.3.4.8658 (64-bit) Screenshot 2
  • NTLite 2.3.4.8658 (64-bit) Screenshot 3
  • NTLite 2.3.4.8658 (64-bit) Screenshot 4

What's new in this version:

New:
- Components: ‘YubiKey’ compatibility option

Upgrade:
- Settings: ‘Enable Local User support’ listed for Win11 Home as well
- Components: ‘Setting Sync’ component detection on Win11
- Components: ‘Biometric Service’ split from ‘Biometric’ (needed for Settings Sign-in options delay), and both moved under their dependencies
- Components: ‘Cloud Files’ split from ‘Setting Sync’, needed for iCloud
- Components: ‘Runtime Broker’ added to ‘OOBE’ compatibility, needed for Windows Setup

Fixed:
- Components: ‘Xbox App’ renamed to ‘Xbox Core’ and moved to Media, contains support for all things Xbox
- Components: ‘GamingApp’ renamed to ‘Xbox App’
- Components: ‘Phone Service’ was breaking Roblox App, Lively Wallpaper
- Components: ‘Ease of Access’ removal would break Lock-screen On-Screen keyboard shortcut
- Settings: Telemetry Policy values would not be reflected on reloading the target (actual settings were applied)