Live edit some components not removing

francis11

francis11

Well-Known Member
Messages
1,164
Reaction score
235
Why am i still waiting in a offline rip off from update to 26200.7922 from .7840 with newest update of NTL 2026.03.10854 beside restart twice to get here‍? It don't make sense.
1772643758208.png
 
It seems NTL get stocked when have to do changes on a live image as All changes are direclly saved dosn't seem to work!
 
The problem is, that NTL dosn't finish the job on live removal after update with restart announced - thanks.
 
Forgot to say i have total 834 removals for an update image - the 5 shown is some leftovers NTL isn't capable to remove after first run of removals and 2 restarts Windows come up with, not NTL.
 
Will be checking this today and report back when done, thank you.
 
Cannot confirm, it's removed in my tests.
Which means it's the placeholder.
Some components exist only on certain Windows versions due to being added by a cumulative update.
In this case it's for example Sysmon added in 26200.7922.

Tool lists these placeholders (in this case if 26100 or 26200 < .7922) so a user can add a cumulative update and queue removal of those to-be-added components, otherwise you would need to load the target twice.

If you have any idea how to better present this to the user, currently it's just a [Placeholder] tag on the right in its description.
 
nuhi said:
Cannot confirm, it's removed in my tests.
Which means it's the placeholder.
Some components exist only on certain Windows versions due to being added by a cumulative update.
In this case it's for example Sysmon added in 26200.7922.

Tool lists these placeholders (in this case if 26100 or 26200 < .7922) so a user can add a cumulative update and queue removal of those to-be-added components, otherwise you would need to load the target twice.

If you have any idea how to better present this to the user, currently it's just a [Placeholder] tag on the right in its description.
Click to expand...
The best would be if you couldn’t see them at all, meaning you could only see what exists in the version you loaded. If that doesnt work they could be greyed out or marked as [Not in this version]. :)
 
wurrtrak said:
The best would be if you couldn’t see them at all, meaning you could only see what exists in the version you loaded. If that doesnt work they could be greyed out or marked as [Not in this version]. :)
Click to expand...
It is marked with Placeholder on the right, will see about making it more visible.

wurrtrak said:
But "Microsoft Engagement Framework" doesnt remove even in 7922 build.
Click to expand...
Btw that component is not in the image, seems like Windows installs it Live only.

In my test it removes fine live with DISM method selected in the toolbar App removal mode.
Could be your DISM or app is stuck, potentially we could see what it is by running only that operation and attach %temp%\ntlite.log and ntlite_dism.log
 
nuhi said:
Cannot confirm, it's removed in my tests.
Which means it's the placeholder.
Some components exist only on certain Windows versions due to being added by a cumulative update.
In this case it's for example Sysmon added in 26200.7922.

Tool lists these placeholders (in this case if 26100 or 26200 < .7922) so a user can add a cumulative update and queue removal of those to-be-added components, otherwise you would need to load the target twice.

If you have any idea how to better present this to the user, currently it's just a [Placeholder] tag on the right in its description.
Click to expand...
You're right - it dosn't change size of installed image and all seem to work now as expected, thanks.
 
You must log in or register to reply here.
Back
Top