A tip on the version of windows 10 to choose

Carlo

Member
A fundamental question to create an optimal installation for an older pc (ddr3, ssd pci, intel socket 1150 etc.): which version of windows 10 is the most suitable? What do you think is the best in terms of lightness and speed? I am currently testing 1709 and it seems quite stable. Can anyone point to an alternative version that is snappy and free of useless features?
 

ege914

Active Member
use latest windows 10 home. remove modern apps, store, security center/defender etc. i don't like older versions too many bugs.
 

Carlo

Member
Thanks ege914, i'll try with 20h2-v2. I remember that i try load with Virtualbox a ISO of 20h2-v2 created sometime ago , but unsuccessfull. I'll create a new iso with different parameters, and try again.
 

nuhi

NTLite developer
Staff member
Simply get the latest from here:

And add all updates in NTLite once loaded (Updates - Add - Latest Updates)

Apply without any other changes, store that patched ISO, then copy it as basis and start trimming as you want.
At first keep Compatibility options at default, only when all works start going deeper.
 

AeonX

Active Member
older pc (ddr3, ssd pci, intel socket 1150 etc.)

This is my setup too. Although a little old I think it is quite decent. Any version of Windows 10 will run fine. Even with hard disk here 1607 runs perfectly. I recently purchased an SSD and will change it but before that I will install 21H1 lited on the hard disk to test how it goes.

But on the topic, in my experience NTLite works best with the latest version of Windows. Which makes sense since it is probably the focus of the development. Even with LTSC 1809 which is the latest LTSC version NTLite has some bugs. Even with 1909, although they are less relevant problems. So my suggestion is to use 21H1 if you intend to use NTLite on this.

Generally speaking, the lightest and best performing version of Windows 10 for weak PCs is the LTSB 1607.

But I believe that 21H1 without all the bloat will run very well and better than 1607 in your setup (and mine too) :)
 

ege914

Active Member
i think ltsc is not light, you feel like its light because it doesnt have moderns apps inside. it has a lot more services when compared to home edition. and 1607 or 1809 etc is just not working for me since because of the bugs they have, for example at 1607 i simply can't play gtav or codwarzone without shutter lag. since they are big games i installed them to my hdd. and anygame working from hdd has shutter lag in 1607 at my tests. it need to be updated to latest. and i prefer the latest windows rather than updating old
 

Clanger

Well-Known Member
ltsc has that damn file association bug. you can get sata ssd's for £22 which make them ideal for testing porpoises and handy when the smelly stuff hits the fan.
 

Clanger

Well-Known Member
why you want to use 10 on hardware that is w7 and 8.1 capable, gamers i suppose. 8.1 is supported until new year, Jan i believe.
oops, tell a lie, end of extended support jan 10th 2023
 

Clanger

Well-Known Member
once amd and intel start with their funky big and little core layouts you are at their mercy.
 

nuhi

NTLite developer
Staff member
But on the topic, in my experience NTLite works best with the latest version of Windows. Which makes sense since it is probably the focus of the development. Even with LTSC 1809 which is the latest LTSC version NTLite has some bugs. Even with 1909, although they are less relevant problems. So my suggestion is to use 21H1 if you intend to use NTLite on this.
I am interested in those potential bugs with LTSC, I'm not aware of them. Start a new topic or send me a PM.
Btw Windows itself has issues with cumulative updates on older versions, it's as if they subtly push us towards the newer ones, when it comes to integration for example - known problem 32-bit 1607, then integration of Windows 10 CUs from Windows 7 as a host etc.
 

Carlo

Member
Simply get the latest from here:

And add all updates in NTLite once loaded (Updates - Add - Latest Updates)

Apply without any other changes, store that patched ISO, then copy it as basis and start trimming as you want.
At first keep Compatibility options at default, only when all works start going deeper.
Hi Nuhi, i have downloaded the latest version (21h1) mounted and installed all updates without remove nothing, but at the end i see this:

datinonvalidi.PNG

What's up?
Thanks.
 

nuhi

NTLite developer
Staff member
Hm, puzzling, will need at least a log to know more.
- please attach %temp%\ntlite.log from that session, since that file is being recreated on new sessions, maybe do it one more time to get the fresh file. ntlite.log should also be on the image folder, together with the preset.
- If that's the latest NTLite version, then please attach that preset (autosaved session xml file), otherwise update and try again.
- If you have Sophos Ransomware turned on, turn it off next time.
 

Carlo

Member
Hi Nuhi,
i've tryed another time but unsuccessful:
Cattura.PNG


This is the file that you have requested:

I don't have any antivirus installed.
Thanks for your reply.
 

Attachments

  • Autosalvataggio {1EDDAF8B-15DB-40A9-ABD6-29C26F9349F6}.xml
    4.1 KB
  • NTLite.log
    12.2 KB

nuhi

NTLite developer
Staff member
Thanks Carlo.
Tried the preset, basically 2 updates integrated, and no errors here.

Few things stick out:
- in the log there is an error right after exporting the image, meaning I would not ignore the error

- your host is really old, unpatched 1709 16299.15
Updating it might fix the issue, it does ring a bell regarding 1709 and WIM issues.
However, since it's your choice and it wasn't un-updated by accident, I may have a workaround:
Edit .\settings.xml in the tool, before starting it.
And change <ForceWimLib>false</ForceWimLib> to
<ForceWimLib>true</ForceWimLib>
Save changes and try then, freshly copying the new image of course.

- image is a custom pre-patched one, not sure if it's valid. If you don't get the same issue with other images integrating updates, and that breaking one installs fine before editing, let me know.
 

Carlo

Member
- image is a custom pre-patched one, not sure if it's valid. If you don't get the same issue with other images integrating updates, and that breaking one installs fine before editing, let me know.
Thanks a lot,Nuhi, for your suggestion.
In effect i have noticed that the with other images integrating updates, when i mount it in Virtualbox or installed directly, the cumulative updates remains in state "Staged" as you can see in the image below (my actual machine live-mounted in NTlite)

staged.PNG

Ok, now i try with the latest ISO (21H1) with a file settings.xml modified as your suggestion, try to integrate the updates and report you the result.

We read later.
 

Carlo

Member
Ok i've mounted the new 21H1 iso and seems all fine, but there is issue after unmountin the image.

after update integration:

OK.PNG
But when i try to reload the image for verify i see this:

annullato.PNG

as described, the image seems open in another apllication.
Now i try with another ISO, a old 1709, and try to integrate the updates.
 

nuhi

NTLite developer
Staff member
Interesting, you don't have to retry if the latest 21H1 had the same issue, then it's definitely something in the host (1709).

In the meantime I found the topic which you reminded me of, here.
Problem now is that means even if I install 1709 cleanly, I probably won't see any issues.

If you are not open to upgrading/fixing the host, the workaround would be to install a virtual machine, like VMWare Player, with any Windows 10 you want inside and prepare an ISO.
Then copy the finished ISO from it to the "real" world.

Let me know if you find anything that could help me replicate this on my side, especially if you see the same in a virtual machine, to send me that specific ISO to make a test host.

Thanks.
 

Carlo

Member
Thanls Nuhi, tonight i'll mount a iso in Virtualbox, and try.
Tomorrow i send you the result.
Bye Carlo
 

Carlo

Member
Ok i have realized a image in another pc, that have a similar host (1709) and the update integration works fine.
Securely the first pc is not ok, for a issue that i don't know.
I have try to build a image with a 21H1 ISO, but i dont' able to load in a Virtualbox, the installation process was aborted for lack some files.
I don't know which one. So i decided to realize a image with a old 1607, temporarly, and when i was able to buil a newer ISO (21H1) i install it.
 
Top