Suggestion Lite'ing image from VHD file

aviv00

Active Member
the way i test thing is going like this

i made a vhd with all the boot files already no need to connect iso to hyper v
and install all from the beginning
im just deploy the image to the right partition of this vhd i made
and open hyper-v , start the vm
if everything is good im making iso from it

edit:
and another thing great about vhd
lets say i made a mistake, i could use difference vhds, make a child vhd so any changes wont save to original vhd
once everything is ok i capture to wim, any error i could just del teh child and make new one clean and ready to lite again
/edit

if im using the wim "method"
its need to be open and saved and deploy [ for other to be create to iso and be installed ]
if im wanna make more changes to this OS
i need to capture it back to wim to be able to use it on NTLite again

Ty nuhi for ur consideration
Great job liting Ms's bloat :)
 
Last edited:
Hi,

thanks, yes, targeting other partitions that are not installed (e.g. D:\Windows), or when booting from recovery image to add driver to C:\Windows, and mounted VHDs with that, is planned.
Long time delayed as not many requests came, and it's kinda a hybrid between image editing and online/live.
Problem is that it's fully deployed, then turned off, so the tool has no access to Windows APIs of that install as it's not live.
Maybe no problem, maybe there will be some limitations like driver uninstalls, will see, maybe even for v2.0.

It competes with direct ISO support, to be able to drop in ISOs to the Source page and use it as a reference to be able to quick-sync changed files back, like full install.wim - not individual files.
 
Just drop mounted Windows folder, like E:\Windows to the Source page and edit normally.
What did you expect to be more clear for new users?
On the Source top banner it states it supports deployed Windows.

It's like Live editing, so non-free... as people would be able to boot another partition/USB and edit C:\Windows directly, then booting to it.
Still thinking about unlocking at least Settings on Live/Deployed, as it would be like a tweaking tool at least... never got the time to separate that.
Install Updates with online list is already separated in Source - Tools - Install Updates.
 
IamlOqS.png


thats what i see
mb in add menu
add deployed image (Mounted vhd) would be clearer
add vhd (deployed image)

edit:
i did drop L:\Windows to source list but i get error msg about iso
invaild windows image path
please select windows installation files

if it would work on older windows version i could test it
 
Last edited:
edit:
i did drop L:\Windows to source list but i get error msg about iso
invaild windows image path
please select windows installation files

if it would work on older windows version i could test it
Don't drop the mounted drive, only the Windows folder from the mounted drive.
Just drop mounted Windows folder, like E:\Windows to the Source page and edit normally.
 
i did drop L:\Windows to source list but i get error msg about iso
invaild windows image path
please select windows installation files

if it would work on older windows version i could test it
Should work on all versions of Win7 -> 10.

Are you maybe using stable version (1.9)?
If so, download 2.0 beta, actually wasn't clear about that.
 
NTLite beta | v2.0.0.7490
works

a small bug i just seeing now
is the name of deployed is not correct
and its the same as my system

and new feature i could suggest is
Task Scheduler / remove disable enable tasks
 
Last edited:
For the name:

The host is seen as deployed (type), once a depoyed, the live runing Windows change the type to 'Host' and the new deployed image shows as Deployed.

Identify by the Drive letter.

I would like Task Scheduler tasks in NTLite but I have some disabled/removed and there are a lot of issues, troubleshooting reports about it would take days am afraid. I don't think it will happen, not soon.
 
You can also differentiate other deployed images by the Type (host) and Status (installed) on the source page list, if C:\Windows is not enough.

Interesting about the task scheduler suggestion, didn't realize there could be that many issues with it, implemented.
Since EventLog and Services are similarly dangerous, maybe we should tackle it some day, it is on the wishlist.
Services have a lot of blocks for offline/images to help with that.

Thanks.
 
few suggests
to boost the deletion of the files
run the deleting task from TrustInstaller account
will save time by no need to take ownership and permissions i think

adding capture or append deployed vhd to wim / esd
 
Last edited:
i have suggest to boost the deletion of the files
run the deleting task from TrustInstaller account
Thanks, but I don't see any slowdown in file deletion, the whole process is very fast.
Maybe Defender is running, check in Task Manager sorted by CPU usage while NTLite is processing.
 
Back
Top