Search results

The Service Stack compatibility is disabled, that is needed for Windows component configuration for removals not to break anything update-wise. So keeping the entire preset the same, if you see any issues with that kept enabled, let me know. I do share the concern about "Delivery Optimization"...

Not available directly, but you can: - search online by the preset line and title what it does - compare two image hives where it was set and not set

I never noticed an issue removing Defender or VBS regarding game protections, or got a report as such. But, if it ever happens, we'll separate those components into a clear Compatibility option.

Let's go over the basics, when you loaded your preset, corrected what you wanted, did you save and overwritten the same preset? If you did and it didn't remember it, give me one example that I can test with your preset here.

Hi, you want me to check the SFC scan, is that all now or?

That error I would saw only when Windows Recovery winre.wim is removed on Win11 24H2+. That said, you should check the logs: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep-process-overview?view=windows-11#sysprep-log-files But first use NTLite's templates like...

NTLite can create ISOs and supports reading from them, even shows the editions before unpacking. Full support for Edit cache and reverting changes on the fly. Also free functionality for personal use. I'm suspecting your account got stolen and this is spam, or you didn't know of NTLite's...

Fix released, thank you.

OK, if you're asking how to remake the ISO with Features working: take the original ISO before editing, load the edition you want. Load the same preset. Go to Components - toolbar Compatibilty - enable Servicing stack and Host Refresh. Apply saving changes. Then in Image - Tools - Host Refresh...

I have renamed the title. Yes, WinSxS is needed for configuring features. Best is to enable Servicing Stack compatibility in Components - toolbar Compatibility next time before any removals.

Crash is still in libwim, it wasn't changed nor anything around it, then it is most likely your machine. I'll return latest wimlib. Somehow it either runs out of memory or overheats or lacks voltage, can be anything when it comes to so high utilization. New idea: edit NTLite shortcut, and add...

Thanks, on it.

Thanks garlin, I missed the point, it is listed in NTLite as mounted, not that NTLite mounted it. In that case it's simple, just right-click and Unload on the blue-iconed mounted entry. It is actually not recommended to manually delete that reg entry as it removes any mounted image references...

Thanks guys.

Thanks, fixed.

I don't have that dir, nor NTLite uses it directly. Common Windows triggers that create this folder: Installing major Windows updates or feature upgrades Running recovery or repair options Preparing to reset your PC Using the Windows Update Assistant Cannot be tied to NTLite starting. But if...

Thank you, fixed. It is part of new drawing optimizations being done in the background, it's worth a bit of growing pain, should be more responsive compared to a version month ago - especially during searching and filtering.

Fix uploaded, let me know if you see anything else.

Thank you, on it.

That one is: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "Start_TrackDocs"=dword:00000000 It already existed, "Let Windows track opened documents to populate Jump Lists" will rename it, thanks. So the new one remains a mistery.