Different results with same source and preset
- Thread starter mattybi
- Start date
Hi Matt,
I tried now and I don't see any WIM duplication.
- Can you please post a screenshot of the issue?
- Also a %temp%\ntlite.log at that moment would also give me more details.
- And second time you load the preset on the same image, you get just Save image task, no other config as it was already done?
Thanks.
I tried now and I don't see any WIM duplication.
- Can you please post a screenshot of the issue?
- Also a %temp%\ntlite.log at that moment would also give me more details.
- And second time you load the preset on the same image, you get just Save image task, no other config as it was already done?
Thanks.
I am afraid you misunderstood my question. Allow me to explain.
This is my source:
Name: en-gb_windows_10_enterprise_2016_ltsb_x64_dvd_9060114.iso
SHA1: 21D25006B7F0C00D035A200B0FE4CB7DA1C1E2EF
I extract it to some directory and load the install.wim in NTLite. Next, I apply the simple preset which I attached in my first post. Finally, I apply the changes and save the images.
Then I copy the modified install.wim into some other directory, let's say "NTLite_modified" and I rename it to "install_1.wim".
I repeat this process one more time, only in the end I rename the modified image to "install_2.wim"
I see that install_1.wim and install_2.wim are different.
I am interested why are these files different? The source image is the same. The preset is the same.
I allowed myself to compare the differences between them. Here is what I found:
Files install_1/Users/Default/NTUSER.DAT and install_2/Users/Default/NTUSER.DAT differ
Files install_1/Windows/System32/config/COMPONENTS and install_2/Windows/System32/config/COMPONENTS differ
Files install_1/Windows/System32/config/DEFAULT and install_2/Windows/System32/config/DEFAULT differ
Files install_1/Windows/System32/config/DRIVERS and install_2/Windows/System32/config/DRIVERS differ
Files install_1/Windows/System32/config/SOFTWARE and install_2/Windows/System32/config/SOFTWARE differ
Files install_1/Windows/System32/config/SYSTEM and install_2/Windows/System32/config/SYSTEM differ
Files install_1/Windows/System32/SMI/Store/Machine/SCHEMA.DAT and install_2/Windows/System32/SMI/Store/Machine/SCHEMA.DAT differ
These are registry files, apparently.
I do not understand why are the systems different. They should be exactly the same.
Could you help me understand, please?
This is my source:
Name: en-gb_windows_10_enterprise_2016_ltsb_x64_dvd_9060114.iso
SHA1: 21D25006B7F0C00D035A200B0FE4CB7DA1C1E2EF
I extract it to some directory and load the install.wim in NTLite. Next, I apply the simple preset which I attached in my first post. Finally, I apply the changes and save the images.
Then I copy the modified install.wim into some other directory, let's say "NTLite_modified" and I rename it to "install_1.wim".
I repeat this process one more time, only in the end I rename the modified image to "install_2.wim"
I see that install_1.wim and install_2.wim are different.
I am interested why are these files different? The source image is the same. The preset is the same.
I allowed myself to compare the differences between them. Here is what I found:
Files install_1/Users/Default/NTUSER.DAT and install_2/Users/Default/NTUSER.DAT differ
Files install_1/Windows/System32/config/COMPONENTS and install_2/Windows/System32/config/COMPONENTS differ
Files install_1/Windows/System32/config/DEFAULT and install_2/Windows/System32/config/DEFAULT differ
Files install_1/Windows/System32/config/DRIVERS and install_2/Windows/System32/config/DRIVERS differ
Files install_1/Windows/System32/config/SOFTWARE and install_2/Windows/System32/config/SOFTWARE differ
Files install_1/Windows/System32/config/SYSTEM and install_2/Windows/System32/config/SYSTEM differ
Files install_1/Windows/System32/SMI/Store/Machine/SCHEMA.DAT and install_2/Windows/System32/SMI/Store/Machine/SCHEMA.DAT differ
These are registry files, apparently.
I do not understand why are the systems different. They should be exactly the same.
Could you help me understand, please?
Last edited:
All of those are registry hives, and their mounting and editing causes their databases to have different timestamps in the entries (content, not file date).
Also registry is known for all kinds of hashed temporary entries, meaning they are generated in the moment, unique numbers, usually sessions and cache IDs.
More clear comparison on the hives would be to mount them, extract the REG file of the root registry key for each and compare those REG files, not the direct databases.
You can easily mount them with the tool, go to the Integrate - Registry page after loading the image, and on the right side Edit hive. Not all of them are listed, but if you confirm for those 4 or so, should prove the point.
Still you will have to ignore some entries, you can post any that triggers the difference, but not sure of.
Also registry is known for all kinds of hashed temporary entries, meaning they are generated in the moment, unique numbers, usually sessions and cache IDs.
More clear comparison on the hives would be to mount them, extract the REG file of the root registry key for each and compare those REG files, not the direct databases.
You can easily mount them with the tool, go to the Integrate - Registry page after loading the image, and on the right side Edit hive. Not all of them are listed, but if you confirm for those 4 or so, should prove the point.
Still you will have to ignore some entries, you can post any that triggers the difference, but not sure of.