Search results

Hi, did you reboot and clean the ISO files to the fresh ones? Also there are 5 presets in this zip, please pick one demonstrating the issue, and ntlite.log is better than ntlite_dism.log if the issue repeats with clean ISO files.

Hi, do you have a preset demonstrating that? I have now tested it, loaded install.wim edition, applied CU + SafeOS update, there were no hangups. But I did get a similar report on the email today, if it wasn't you, would be important to replicate this so it can be fixed fast. Thank you.

Thank you. Downloaded your files, placed them and tried to trigger the crash, but no luck. Could it be that your machine is unstable? e.g. memory XMP or CPU overclock? Or some antivirus in the background which I would need to replicate this.

Hi, thank you for the report. I downloaded all the files from your log, and opened Latest online updates, they got parsed, but no crash. Maybe one of the files was corrupted/incomplete. Please next time if this happens, preserve the entire cache directory for me (e.g...

Continuing this over email, got the preset.

That can happen if product key type does not fit any of the kept editions on the image. Try without a product key (leave it empty), all else the same.

Hi, can you please attach %temp%\ntlite.log at that moment, as it does not sound familiar to error out about the download that was finished. Thanks.

That seems to be a heavily custom trimmed image. Anyway, downloaded their example ISO, removed a few components, there was no errors during processing. It's not recommended to download custom ISOs, not just because of potentially unexpected editing, but also security. Best is to use NTLite on an...

If you started the cached image as a "New edit" from a source, be it ISO or another folder, then yes. Select it and use the Revert function. You can also change to which source it is being connected to (revert reference) on a right-click menu.

That's fine, if optional. Problem comes when it's being forced for no reason other than tagging a user.

Isn't that weird, that's the first time I see UUP behaving different than an official version. I believe UUP updated OOBE to a newer one from the previews - or explicitly enabled a newer feature. Thank you as well. Anyway, fix/workaround uploaded, let me know if all good now.

Thank you, confirmed with that image and enabled Internet. Testing.

someonenotyou, cannot replicate, to me it works fine. Please state the exact Windows version (e.g. 26200.?) and where did you download it, so I can test the same. Also make sure you're testing the correct ISO, confirm in a VM for example.

Hm, please attach %temp%\ntlite.log at that moment, never seen that before. Translated to english, cannot find a file - but which, it gave no context, maybe log will.

Let's agree to disagree

Thank you, removed all those catalog-only (not on Windows Update) Intel Memory Mapped I/O updates. They are for old non-patched CPUs, more info here (only for older than Intel Platform Update (IPU) 2022.1 that is dated June 2022).

Yes, start one NTLite, load any of them, then start another and load another.

Feel free to report a bug, I don't see it still.

Yes, in two ways: - if it's the editions of the same WIM/ESD file, then on the Apply page after loading any of the editions, go to Reapply options. - if it's a different WIM, then start another NTLite process, it will ask you to run another. The first one will be auto-locked. Let me know if...

Please try the latest version and let me know if this is resolved.