Discussion and Poll, Which OS do you use.

What OS do you use?

  • Windows 7

    Votes: 5 29.4%

  • Windows 8.1

    Votes: 3 17.6%

  • Windows 10

    Votes: 9 52.9%
  • Total voters
    17
  • Poll closed .
My preset, always my own work. :) 8.1 has about the same telemetry as w7.
 
7

I have trialled 10 on several occasions - but there`s always something that just makes me so annoyed, I just wipe it :)
 
Hello all!
I have recently discovered this utility, and am seeing that some of you have mentioned "cleaning up" Windows 10. I was wondering if y'all would be willing to share any recommendations or suggestions for doing so? Biggest Q: is it possible to kill their telemetry with this utility?
 
Since you're new here, might I respectfully suggest spending a little time perusing the forum and using the Search feature first to find the answers you're looking for? You'll find that, yes, NTLite will remove telemetry. And many people - particularly Clanger - have posted their Presets for cleaning up Windows.
 
I keep thinking about trying Win8. But 1) I really should be doing work and trying Win8.1 would consume a couple of days, and 2) After updating Win7 with the latest KB's using WSUS Offline Updater, Win7 is working REALLY well. (Turns out that I needed .NETFramework 4.7.2 for some things (like Handbrake Portable) to work.) So, if it ain't broke, don't fix it, I guess. Maybe I'll try 8.1 after the December holidays.
 
Dot Nets are an abomination, along with RGB except i can do without RGB. :mad:

And glass cases, what state will they arrive in when the dhl loading bay johhny on minimum wage and a bad mood has had his mitts on them.
 
Last edited:
Yeah, the .NETs are just more vectors for attack and I hate having to install them. I disabled 2.0 in Services.

When I checked the log file in the netframework cleanup tool, it said that only 3.5 was installed. After I installed 4.7.2, it says that all the Nets are active. So I guess I have CLR enabled.
 
Fat bloated os which they then bloat out even more, makes me facepalm.
 
pmikep said:
Since you're new here, might I respectfully suggest spending a little time perusing the forum and using the Search feature first to find the answers you're looking for? You'll find that, yes, NTLite will remove telemetry. And many people - particularly Clanger - have posted their Presets for cleaning up Windows.
Click to expand...

I do not know why my initial reply did not post, but here goes attempt 2!

Of course, pmikep! I have been perusing as well, just thought that in the spirit of working smarter not harder, some may have saved links readily available as reference to a cleanup "guide" and cut down on the search time.
 
The definition of clean will vary on each user. What i call clean(from my nlite days) is removing 3rd party drivers, uneeded keyboards and languages, many fonts(i compiled my own keep fonts list for en-gb), cache/temp/.net cache files and stripping out winsxs. Its leaner than standard but still fairly large. I actualy get the performance gains(offline workstation) from bareboning services and disabling scheduled tasks, custom power plan and a few ui speed up tweaks. I will do a few component removals, defender, system restore and any bloody awfull wallpapers.
 
Last edited:
DomAnf said:
I use Win 10 x64 Pro but I am getting very annoyed with it breaking my Intel Ethernet Connection (2) I219-V Device Manager [DM] tabs, such as Advanced, VLans, Teaming and Link Speed tabs missing since the April update. Intel engineers keep posting at their forum how they are working on the issue. I have 2 desktops PCs both with the same ethernet chipset on board, with the same version of Windows, the older desktop with a Z170 intel chipset has all tabs in place in the network DM, but the newer desktop with a Z370 chipset has been broken in the sense of the above DM mess up? go figure?!
Click to expand...
Looking back it is easy to understand why: It seems Intel had planned to Sunset PROSet utility ; it is not available for Windows 11 and Windows 11 has no native or 3rd party NIC Teaming support (as of 2025-Q2, maybe that will change). Ultimately, architecturally, it seems that physical NIC Teaming should be done at the Hypervisor (or Cisco UCS vNIC) level.
 
You must log in or register to reply here.
Back
Top