Recent content by olivered

i have no problem editing images on win64 that are in aarch64. but for live edits, host refresh cleanup, etc- it’s helpful to be able to host on arm. If you want me to help you with this i have a Lenovo Yoga C630 13’ arriving today i will be testing ntlite built images out for. The issue i have...

Microsoft windows now issues builds of windows 10 for ARM64. NTLite also works to edit ISO's for ARM64. However, NTLite does not currently run on ARM64.

HKCU keys are seamlessly integrated into the defaultuser ntuser.dat file by ntlite whenever you add them using the built in add to registry key. Those keys are then automatically duplicated to all users during setup and account creation. With regards to manually adding them, what you do is- you...

we're talking about NTLite licenses, not windows licenses. Some of us dont have to deal with windows licenses.

https://www.tenforums.com/tutorials/2570-esd-iso-create-bootable-iso-windows-10-esd-file-43.html Apparently there are some people using boot.esd file with custom BCD store changes

Add WindowsDefenderAppGuard.wim too :P

?? You can just right click and remove them from the task bar? Or remove components: cortana, search, store?

another way this can be used is to port on-demand features between windows editions that are capable but don’t include them, like games from desktop to server. for the sysadmin in all of us. files and edits could be extracted as featureset.buildnumber.deltax(5mb) along with a depends.xml that...

Sometimes i want to make edits to virtual machines or from a separate OS but i can’t. I can’t install windows to a machine, then mount that disk for NTlite to make changes to it- NtLite only works with either wims or the system install it is booted on. Additionally spending activations on...

This is a bit of an odd feature idea- It’s more of a total overhaul of the way something is done rather than a suggestion. let’s say instead of writing edits to the original WIM via the temporary folder, somehow you worked some serious voodoo out and made it so that those edits are instead...

There is a small tweak i would make to the existing process- let’s say you have extracted an ISO, and you want a specific pair of editions, let’s say it’s 7 pro and setup 64. ordinarily you have to manually click on each esd or wim and extract the edition to a wim in a different folder, then...

*make iso would require automatically taking wim out of edit mode or warning user(this wim is uncompressed, you could save a lot of space by taking it out of edit mode).

I have a highly customized win10 laptop with no antivirus or filters that would delay loading of image. But it does have a weak CPU. Boot.WIM if fully customized and with future optimizations to cut SYSWOW64 and other cruft can get quite small. WINDOWS 7 Embedded IBW X64 boot.wim is only...

Not read-only. Toggle influences how runs are processed and applied. A run is everything you do from load -> save. Edit mode is for quick multiple runs- run 1, feature reconfiguration. run 2, component removal. run 3, add files manually to temp dir. If necessary, changes are committed to wim...

A toggle switch on the main application ribbon: "Remastering(slow)/ Edit(fast) toggle Mode" In edit mode, compression on wim is disabled/reduced and certain options like make ESD are disabled. Additionally each run of edits is saved to the temporary directory, but not the WIM. In remastering...