DISM/NTLite records work directory in registry... How to clean?

[OpenSource Ghost]

If your work directory for NTLite is something like "X:\Y" and you performed offline updates from there, then that directory information is saved and preserved in registry in offline images, which you can find by searching for work directory entries (X:\Y). Official images do not have such records. It doesn't appear that removing those entries manually corrupts file integrity and/or component store, but I am not sure.

 

[garlin]

What registry keys are we talking about?

 

[nuhi]

If your work directory for NTLite is something like "X:\Y" and you performed offline updates from there, then that directory information is saved and preserved in registry in offline images, which you can find by searching for work directory entries (X:\Y). Official images do not have such records. It doesn't appear that removing those entries manually corrupts file integrity and/or component store, but I am not sure.

DISM saves those, you can change the NTLite directories in the Menu - Settings if you need to hide something, like %UserProfile%\AppData\Local\Temp can have your user name.

Btw it is not true that official images don't have such records, at least where I'm looking, so do tell us where is yours.

Windows default ones at:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Client-License-Platform-Upgrade-Subscription-Package~31bf3856ad364e35~amd64~~10.0.22621.1
InstallLocation
\\?\D:\wd\in\BuildChunkArtifact\a27c54f7-1ef4-05c9-ac1c-73c75acbdcba\amd64fre\NEUTRAL_STAGED_CLIENT_CATALOGS\

Other examples have:
\\?\D:\wd\compilerTemp\BMT.ijbjbjy2.cay\Windows\Temp\F83731C0-204B-4AEB-85B1-95209744013A\

Windows Update has:
\\?\C:\Windows\SoftwareDistribution\Download\3fd91fbdc737fa629c32c1f92876eed1\metadata\Windows11.0-KB5032288-x64\

etc.

I could add an option to delete all those InstallLocations, just not sure if MS uses it for anything other than debugging.
We could try as a Settings extra option with a warning?
Let me know if you find it anywhere else, so that we do all at once.

 

[Clanger]

We could try as a Settings extra option with a warning?

Put it in a Beta and see what happens

 

[garlin]

The simplest fix is don't use AppData\Local\Temp as your NTLite temp folder. There's nothing special about that path, other than it always exists on everyone's PC.

 

[OpenSource Ghost]

The latest NTLite alpha has the setting to delete them! Does it also include removal of all .log1, .log2, .blf, and .regtrans files from all WIM images files?

There are container WIM image files that are locked as read-only. They can only be unlocked by exporting them in NTLite and then exporting the exported image again, but there is no way to re-lock them with NTLite. Forcing read-only flag on WIM files can be a good feature for NTLite.

 

[OpenSource Ghost]

New alpha version setting 'Remove registry logs of package install locations' doesn't remove all the entries. It leaves "Microsoft\Windows NT\CurrentVersion\Print\PackagesToAdd" behind.

 

[nuhi]

New alpha version setting 'Remove registry logs of package install locations' doesn't remove all the entries. It leaves "Microsoft\Windows NT\CurrentVersion\Print\PackagesToAdd" behind.

Thanks, can you please export and send it to me, I have nothing at that location. Full Windows included.