SlimJim LTSC 2021 Preset (free)

tted

Member
Messages
38
Reaction score
8
So my particular deployment of Ntlite is anal and complicated as can be; sometimes you have to make yourself your own tools case and point SlimJim.
So what is the point of SlimJim preset. It is an ideal image for virtualization, includes .net 3.5, you can install the old run times like VC++ 2005 and 2008 and run those basically largely compromised runtimes in a virtual environment as well as most 3D games. But I had two purposes for myself which were provide the ideal and minimal drivers and hardware support (vis-a-vis) a real pc. You can further trim the drivers and hardware, but this baseline is hard to beat for real systems. You can download that just to see how you did and improve your own preset. But in my case, I have 6 machines, and NTlite comes with 5 activations, so I downloaded an old beta NTlite (1.8....) and I load this perfect SlimJim, import host drivers and export for my real and production ready live image which focuses on security, privacy, functionality and performance. This combined with driver booster 12 made it easy to compile a master light driver package for my systems and one that was up to date.

I'm usually not one to share presets, but as I said my releases are complicated such that this comprises maybe 1/10th of the final ISO. This is just a component removal and unattended. You should probably add the NTlite settings for a more comfortable experience. You use SlimJim with any Windows 10 ISO really, but it was designed for LTSC 2021 IoT Enterprise. With this preset, I assure you, you'll come close to driver/hardware mastery which if you don't have deep knowledge of windows is truly arbitrary. Obviously, this preset is better than any automated preset in NTlite. The Wim size is 1.6GB. And though I can get a Wim size of 1.05 GB, it's a flaky problematic image. SlimJim is ironclad and virgin. I always recommend against modding boot.wim especially if you are releasing to public.
 

Attachments

NTlite has a gaming preset, best you stick to that. But for hardware and drivers, you can look at my preset and merge it with the gaming preset of NTlite. To answer your question, probably yes, but if you want to make sure...

Regards,
 
So my particular deployment of Ntlite is anal and complicated as can be; sometimes you have to make yourself your own tools case and point SlimJim.
So what is the point of SlimJim preset. It is an ideal image for virtualization, includes .net 3.5, you can install the old run times like VC++ 2005 and 2008 and run those basically largely compromised runtimes in a virtual environment as well as most 3D games. But I had two purposes for myself which were provide the ideal and minimal drivers and hardware support (vis-a-vis) a real pc. You can further trim the drivers and hardware, but this baseline is hard to beat for real systems. You can download that just to see how you did and improve your own preset. But in my case, I have 6 machines, and NTlite comes with 5 activations, so I downloaded an old beta NTlite (1.8....) and I load this perfect SlimJim, import host drivers and export for my real and production ready live image which focuses on security, privacy, functionality and performance. This combined with driver booster 12 made it easy to compile a master light driver package for my systems and one that was up to date.

I'm usually not one to share presets, but as I said my releases are complicated such that this comprises maybe 1/10th of the final ISO. This is just a component removal and unattended. You should probably add the NTlite settings for a more comfortable experience. You use SlimJim with any Windows 10 ISO really, but it was designed for LTSC 2021 IoT Enterprise. With this preset, I assure you, you'll come close to driver/hardware mastery which if you don't have deep knowledge of windows is truly arbitrary. Obviously, this preset is better than any automated preset in NTlite. The Wim size is 1.6GB. And though I can get a Wim size of 1.05 GB, it's a flaky problematic image. SlimJim is ironclad and virgin. I always recommend against modding boot.wim especially if you are releasing to public.

Why not use LTSC 2024 ?
 
Thanks for sharing the preset. Will this work on a free (non paid) version of ntlite?
 
When using a free edition, any licensed Component removals will be silently ignored. Most of the advanced presets take advantage of the premium features to greatly reduce the image size.
 
On this preset (applied to a Windows 10 LTSC 2021 image), it seems to be impossible to install MSI packages like the QEMU guest agent MSI — it errors out almost immediately. Could you please advise / look into what might be the problem?
 
QEMU needs the Hyper-V component, so the feature can be enabled.
 
QEMU needs the Hyper-V component, so the feature can be enabled.
I'm afraid you misunderstood. I'm talking about the QEMU guest agent. Obviously I have no desire to run QEMU hypervisor under Windows (this is not actually possible, it does not have a Hyper-V backend).
 
This preset doesn't do any customizations other than removals. If other MSI's install fine, then it's a dependency on a missing device driver or the Hyper-V feature (which includes other virtual device support).
 
This preset doesn't do any customizations other than removals. If other MSI's install fine, then it's a dependency on a missing device driver or the Hyper-V feature (which includes other virtual device support).
I cannot test other MSIs because, well, I need the guest agent to drop files into the VM (and this image also has nonfunctional SMB, so I cannot reach my lab server either). If you can suggest any diagnostics I can run (except msiexec /log which does not say anything useful), I'd be happy to dig deeper.

Like I said, QEMU guest agent is not QEMU. It does not depend on or use Hyper-V in any way. Think of it as VirtualBox guest additions (except that VBox GA package contains both drivers and background services, while the virtio-win project provides them separately — I have no problems with installing drivers, only the agent). I might be asking for help with this specific image, but please don't treat me like I'm clueless even after I said that I'm not.
 
Last edited:
No one's treating you as clueless. If you read the preset's list of removals (open it in a text editor), those are the only logical culprits unless the MSI's looking for some other dependency like a missing UI library. Knowing the QEMU folks, they're more likely to stick to the basics and not demand any exotic things with WPF or whatever to run.

This preset (which isn't mine) also removes a lot of native network drivers, network discovery, and SMB1. While it's built on LTSC, it's probably intended for gaming and strips out features than are normally taken for granted on LTSC platforms.
 
I tried the file and this awful message appeared. I tried to get a Windows installation disc from Microsoft, but when I tried the file, this message appeared. I tried several other files, and I keep getting problems, as shown in the picture. I don't understand what the solution is anymore.Screenshot 2026-04-27 171717.pngScreenshot 2026-04-25 181110.pngScreenshot 2026-04-25 180854.png
 
These are the most annoying messages I receive, even though I want to edit a CD that hasn't been edited before.
 
Back
Top