Search results

Part of magic of NTLite is its Integrate - Registry page. Just drop a REG file with the tweak into it, it will directly write it to the registry hives on Apply, same effect as the tweak being listed. That said, new version with this baked in, tomorrow evening. Or you meant the script to spoof...

"Start layout" is already there, will add HideRecommendedSection next, thanks.

With the new law about age verification on the OS-level, they will just be encouraged to make the MSAccount even more mandatory.

Load one, then go to the Apply page and choose in Reapply section which pages pending operations to propagate to the other one. Then apply to see how it does it automatically.

NTLite has 2 modes or removal, active removals are the same in both modes: Mode 1: Servicing stack compatibility enabled, preserves Windows Update compatibility, keeps most of files in WinSxS for that (WinSxS files are passive - with exception of some runtimes but we do not talk about those...

Hi, yes, you can test it with the free version, it will just have a popup between sessions. It's on the Apply page - Reapply tasks across editions. Also in the licensed version you can run a second NTLite instance and independently operate on another image. Just avoid loading the same image...

Got another mail about the crash with this newer version of wimlib. Shipped a new version using old one, and reserved one more thread for your 20 core situation (10% reserved now instead of 1 core), should reduce the load a bit. Let me know how the new tool version goes, without changing libwim...

The other crashes are also in libwim-15.dll Please read both of my last messages above. My bet is on the PC instability as it sometimes works - it also could be a wimlib bug, but not sure how we catch that - I could build a debug version and send you that, then a DMP file might reveal more...

Thanks, will fix those.

Thank you, please try the new version.

xhisp, it loaded fine here, what is the issue you're having? Screenshot or paste of the error.

Thank you, testing.

Thank you. Crash is in libwim-15.dll (wimlib), it was updated though, please try the older working version NTLite\Tools\wimlib\x64\libwim-15.dll If replacing it from the older version into the new makes the new not crash, I'll revert, don't have control over it other than that and changelog...

I just noticed you use ESD compression, that is very resource heavy, if you PC is in any way unstable it will show. Try rebooting and without running anything else, try again please, from a fresh ISO. Make sure to track your memory, it fills fast, do not start other programs while it's doing...

Hi, do you have a %temp%\ntlite.dmp file? Thank you.

Depends what was done to the system. Do you still have a preset which was used to configure that image for me to test the same thing?

We need to be careful about our future overlords, these are their kids in development now. Also it is a bit confusing even to a human, as part of RPC Locator name is RPC - and locator doesn't sound so legacy. It's a better question why would Microsoft still ship it... maybe a big enterprise...

RPC core service is not RPC Locator, that is a completely different component. The RPC Locator has provided no actual functionality since Windows Vista.

What is its important function? The RPC Locator is a legacy Windows service that acts as a directory for RPC servers on a network - clients can query it to find servers by name instead of needing their exact addresses. It's essentially obsolete now, as modern Windows uses other discovery...

Fix uploaded, it now takes into account Windows settings, hopefully everyone is happy now :)