I do have the license. I have removed apps but it's hit or miss with me with that start menu bloat. Sometimes it's gone, other times it's not. I don't know what the correct setting is to prevent it. I have had luck removing all the apps I want gone but that start menu bloat is a thumb in my eye after a successful clean install. I only have 3 requirements for my NT lite install no crap in the start menu, crap apps gone and office and spotlight need to work. I do not like turning anything off that cant be turned on in windows. I never broke office, but half the time I break spotlight on the lock screen and spotlight for the desktop background.
Guide: Optimized Image
Removing Content Delivery Manager does block all 3rd-party app suggestions, but it will break Spotlight. The alternative is enabling a series of reg keys, which sometimes doesn't always work.
I believe Spotlight is SubscribedContent-338387.
Code:
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "ContentDeliveryAllowed" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "FeatureManagementEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "OemPreInstalledAppsEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "PreInstalledAppsEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "PreInstalledAppsEverEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SilentInstalledAppsEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SoftLandingEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContentEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContent-310093Enabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContent-338388Enabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContent-338389Enabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContent-338393Enabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContent-353694Enabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContent-353696Enabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SubscribedContentEnabled" /t REG_DWORD /d "0" /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "SystemPaneSuggestionsEnabled" /t REG_DWORD /d "0" /f
reg add "HKLM\Software\Policies\Microsoft\PushToInstall" /v "DisablePushToInstall" /t REG_DWORD /d "1" /f
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager\Subscriptions" /f
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager\SuggestedApps" /fI believe Spotlight is SubscribedContent-338387.
Hellbovine
Well-Known Member
This guide is intended for W10, and although many of the tweaks will work on W11, not all of them will. The start menu is an aspect that needs new tweaks on W11, so using this guide as-is won't tweak that effectively, which is why the FAQ tells people to adapt the tweaks to their needs if they go off course, such as by using W11, otherwise things won't work as intended.
Is there a policy I could have accidentally enabled with NTLite that would prevent me from changing settings within windows with 3rd party apps?
Last edited:
Hellbovine
Well-Known Member
Everything Windows 11 as well as third party tools is unrelated to this guide and needs to be posted elsewhere. The point of threads like these is to troubleshoot or discuss things relevant to the first post, which in this case is purely about using NTLite as the only tool to specifically tweak Windows 10. Most people's issues on this forum are really due to an overuse of tools and scripts, which are all overwriting each other and creating bugs.
Last edited:
hi Hellbovine, thanks for such an effort to teach us some more stuff! will this guide work with win10pro 22h2 or should i consider more actions to be done?
Hellbovine
Well-Known Member
I've thoroughly answered questions about Windows (W10/W11), editions (Home/Pro), versions (21H2/22H2), and builds (19044.1288/etcetera), dozens of times now. I mean no insensitivity, but it's exhausting to rehash this every week, so now I'm directing people to carefully read through the guide, because maybe an answer isn't where it's expected to be found, but it's there. I'm well over 1,000 hours into this guide, so it's not unreasonable that I ask people to spend 20 minutes reading in return for a huge, transparent, polished image, that's free of charge.
If there are specific questions that someone is still confused about and it doesn't have an almost verbatim answer already sitting in the guide, then please ask and I or someone else will assist, but most of the questions in this thread is tweaking 101 information that applies to all custom images, meaning it's stuff that everyone landing on an advanced computer website like NTLite.com should already be at least a tiny bit familiar with.
Inexperienced users aren't discouraged from asking questions, but they need to get their feet wet first by following some guides and actually making a few images, because there's no substitution for hands-on experience. When I have a question like, "Will this tweak work" I answer it myself by installing a default Windows, installing the tweak, then reboot and test it. Newbies can do that too, but if they aren't interested in that kind of learning then they need to use guides as-is and accept things as they are.
If there are specific questions that someone is still confused about and it doesn't have an almost verbatim answer already sitting in the guide, then please ask and I or someone else will assist, but most of the questions in this thread is tweaking 101 information that applies to all custom images, meaning it's stuff that everyone landing on an advanced computer website like NTLite.com should already be at least a tiny bit familiar with.
Inexperienced users aren't discouraged from asking questions, but they need to get their feet wet first by following some guides and actually making a few images, because there's no substitution for hands-on experience. When I have a question like, "Will this tweak work" I answer it myself by installing a default Windows, installing the tweak, then reboot and test it. Newbies can do that too, but if they aren't interested in that kind of learning then they need to use guides as-is and accept things as they are.
Last edited:
Studied all the registry tweaks of this build line by line and did not find anything about disabling naggles algorithm. I disabled it manually after installing the build. I am primarily playing PUBG and disabling naggles reduces stuttering issue (at least for me). I am trying to learn like everyone else on this forum and would like to hear some opinions on disabling naggles algorithm and is there any reason why it wasn't included in this build cause I think it is a worth doing it.
Nagle’s Algorithm, like all tweaks, is an optimization based on a particular workload. What problem is the most important one to solve, since it’s impossible to solve ALL problems at the same time. Nagle was interested in the problem where small network transactions become inefficient, because the ratio of actual payload data is low vs. the TCP overhead.
Thus if your most important problem is the transfer of large data blocks, ie. copying files, then you try to wait and consolidate data by topping off each network packet. This also has the side effect of reducing CPU overhead from servicing less network buffer interrupts.
Nagle wasn’t a FPS gamer, and so his optimization is terrible for keeping low latency, and better response times while playing online games. So you should understand what problem his RFC was trying to fix.
Another factor is some of this might be moot. Some network performance might improve for local traffic (inside your home or office LAN), but ultimately you don’t manage the upstream routers past your own network. Those might have a stronger impact that any perf optimizations you do locally.
Like everything, you need to test performance based on your specific network setup, apps, and your ISP. What works for you may not benefit my situation. The real problem is you can’t switch TCP settings like Nagle’s on the fly.
So make a smart choice.
Thus if your most important problem is the transfer of large data blocks, ie. copying files, then you try to wait and consolidate data by topping off each network packet. This also has the side effect of reducing CPU overhead from servicing less network buffer interrupts.
Nagle wasn’t a FPS gamer, and so his optimization is terrible for keeping low latency, and better response times while playing online games. So you should understand what problem his RFC was trying to fix.
Another factor is some of this might be moot. Some network performance might improve for local traffic (inside your home or office LAN), but ultimately you don’t manage the upstream routers past your own network. Those might have a stronger impact that any perf optimizations you do locally.
Like everything, you need to test performance based on your specific network setup, apps, and your ISP. What works for you may not benefit my situation. The real problem is you can’t switch TCP settings like Nagle’s on the fly.
So make a smart choice.
Hellbovine
Well-Known Member
Yeah, pretty much what Garlin said. I didn't include any network tweaks in the first release, because I wanted to be certain about the stability of the configuration I settle on. There's a huge difference in modern Windows versus older operating systems in the sheer number of tweaks that can be toggled in the adapter properties as well as in the operating system through tools like TCP Optimizer, meaning it's very easy to make a mistake and actually harm performance, since network settings are extremely fickle.
We saw this issue (link) on the GamerOS thread, where the new PowerShell script crippled network performance, even though those tweaks were meant to improve it. I should have focused more on network a long time ago, and it was one of the very first things I was asked about when I started making guides. I began writing up a network guide back then, but part of the delay in its release is because there's three major aspects that have to be addressed for networks to come together properly (adapter, Windows, router), so it's a lot to manage and try to get right.
Nagle is a tweak that should improve performance if disabled, since it was designed to intentionally slow down how often packets are sent, which has the side effect of increasing latency. In other words, network data is carpooling instead of driving solo, so there's fewer cars on the road, but it's a longer trip overall with Nagle's algorithm enabled. Many network settings have scenarios where the opposite results can happen too, so keep that in mind while benchmarking and troubleshooting, because something odd will inevitably come up while experimenting.
We saw this issue (link) on the GamerOS thread, where the new PowerShell script crippled network performance, even though those tweaks were meant to improve it. I should have focused more on network a long time ago, and it was one of the very first things I was asked about when I started making guides. I began writing up a network guide back then, but part of the delay in its release is because there's three major aspects that have to be addressed for networks to come together properly (adapter, Windows, router), so it's a lot to manage and try to get right.
Nagle is a tweak that should improve performance if disabled, since it was designed to intentionally slow down how often packets are sent, which has the side effect of increasing latency. In other words, network data is carpooling instead of driving solo, so there's fewer cars on the road, but it's a longer trip overall with Nagle's algorithm enabled. Many network settings have scenarios where the opposite results can happen too, so keep that in mind while benchmarking and troubleshooting, because something odd will inevitably come up while experimenting.
Last edited: