A few noob questions?

Zombihands

New Member
Hello I've only been using this for about a week and I'm very happy with it. I've been testing it out on my terrible laptop with the "Gamer OS" preset that one of the awesome locals made but is there's a easier way to find all the dependent components needed to enable a application other than doing repeated searches in NTLite for the disabled component? Also what environment do you guys use ntlite in? I know its is a good software for use with a tato pc but what does it totally ruin? I'm guessing secure boot isn't possible with this is it? not that it matters much in a little while as I heard about something that bypasses secure boot called black lotus. thanks! :)
 
Presets are like personality tests. It depends how you want to use Windows.

When you use another person's preset, you may not understand what's missing -- or why they think those features are unimportant. Some of the GamerOS profiles sacrifice functionality to maximize performance. Don't think of this as a competition with the "best" answer.

The easier question than "what don't I remove?" is ask "I need to run XYZ application, what do I keep?" Because I have no idea what programs you want to run, and neither do "Gaming OS" authors. Asking questions is normal, if you haven't found previous answers in Forum search.

- Most users run NTLite on the same OS they're modding, it's easier. But any version of Windows can mod the same version, or lower.
- Secure Boot is optional. I've heard like one game requiring it, mostly because their devs want to use it as anti-cheat shield.
- Consider running W10 on older systems, most apps don't require 11.
 
I haven't tried messing with the os installed on the computer I'm using with NTLite. how does that work? does it reinstall after a reboot or something or did i misunderstand what you said? I've only messed with the install image on one computer and then used rufus to install the image. also what do you mean secure boot is optional? I know you can turn it off but isn't it a layer of security normally left on unless your operating system doesn't support it? never even heard of a game that needs it.
 
yeah I'm guessing its limited mostly the online stuff related to what garlin said anti-cheating. thanks for the article. :)
 
Secure Boot was created for large enterprises (companies, schools, governments) to improve Windows security by only allowing trusted UEFI configs to boot up. If your PC doesn't have the right specs, or doesn't have signed firmware then it's disabled. Other Windows security features are chained off Secure Boot. Without Secure Boot, then other kernel protections can't be trusted.

For the home user, this doesn't translate to much loss of functionality. The enterprise user does care since they're subject to security audits.

You don't build an image "with" or "without" Secure Boot. It just means at boot-time, Windows figures out if enforcement happens or not.
Some users don't care about security features, and will remove them. Right now, it's low on your list of worries.
 
I haven't really messed with secure boot most of the time I just leave it on in the bios and never modded any setups or even really used software like rufus and nlite to stop secure boot checks. I don't really care about any of that either though. I do like having drivers and updates preinstall though. first thing I'm gana do is make a windows 10 disk without the preset.(*will be looking at it though lol). Do you guys use a vm to test it out before install or do you just install/mod your system? I've just been using/testing it on my laptop and setting up the install disk on my desktop.
 
Some users take advantage of two PC's or dual boot. I use a VM. If you're not testing drivers or HW features, it doesn't matter because you want to first check your image installs and has no obvious errors. When you're removing components, test those features.

Did it remove what you expected? Did it break something else you didn't want? If you gradually remove or tweak features, it's easier to keep track of what worked and didn't. Don't delete the earlier presets, you can rollback to the last version instead of starting over.

If you can switch back and forth to a different image (2nd PC, dual boot, VM), it gives you more time to do a good job.
 
Start off by trimming the fat, stuff that "wont(?)" break setup and install,
3rd party published drivers, not MS drivers for X hardware, uneeded keyboards languages and fonts, winsxs backup, cache and temp files, any .net cache and setup files. Once you have tested those and everything works ok then move on to the meat of the os, apps then the core components.

Test them in small groups, use the Categories in the left hand pane, Drivers, Languages, System for winsxs backup, cache and temp files, any .net cache and setup files.

If a component cannot be removed without something breaking can it be disabled in Features instead?

Tweaks - Remove Scheduled Tasks, Autologgers, Winevt Channels, Disable uneeded services.

I use a laptop to test the full setup/install routine, a dual boot on main pc for tweaks etc - extract install.wim to a partition that has a boot entry.
 
Last edited:
Back
Top