NTLite build 6146

I don't know what causes this but I always have a folder called Documentos ("Documents", in Portuguese) created (I suppose by some program), alongside the original "Documentos" folder which has that original icon. I also had a folder called "Documents" created somehow, which led to some problems. Also, I had a default0 folder under the Users folder.
 
Last edited:

nuhi

NTLite developer
Staff member
@VladD, can you tell me the details how to provoke that crash, what to set the Temp and Scratch to and which preset do you apply and it reliably crashes?

@Windows 10 User, compare to full unedited Windows (Documentos and default0), then if those are not there, send me the preset demonstrating the issue.

Thanks.
 
@Windows 10 User, compare to full unedited Windows (Documentos and default0), then if those are not there, send me the preset demonstrating the issue.

Thanks.
In the unedited Windows I don't have the default0 folder but I don't remember if I had the Documentos folder since I don't install the unedited version for a long time. Maybe this problem regarding the Documents folder is caused by some program whose path folder is set to the Documents folder and for some reason it creates another Documents folder but without the former icon (it has the icon of a regular folder). Here's my preset.
 

Attachments

Last edited:

rambolcm

New Member
Under component removal section, I cannot find the item "windows defender" which I appears in previous version.
As a result, "windows defender" will be removed in final outcome but I would like to keep. Please help!
 

Kasual

Well-Known Member
Under component removal section, I cannot find the item "windows defender" which I appears in previous version.
As a result, "windows defender" will be removed in final outcome but I would like to keep. Please help!
have you typed defender in the search box?
 

rambolcm

New Member
yes, of course. I have used NTLITE for several years and I am not a new user. Once there is new version of NTLITE with new Windows 10 updates, I will do exactly the same step to integrate update and trim windows. Thus I notice to discover such problem.
 

Kasual

Well-Known Member
I have used NTLITE for several years and I am not a new user.
I don't but i know how it works and still sometimes i screw it up.
Sometimes i forgot to load a clean source, check if you had loaded a clean source.

This is clean, not updated:
Defender.PNG
 

MC_MuHyeon

New Member
Hi. I have a problem with the build 6105. I didn't have this problem in the build 6080, but when I try to load a fresh clean OS installer folder, an error message pops up and says that the NTLite has detected an unknown OS. The OS I tried to tweak was Win 10 LTSB 2016 Korean (1607). The message looks like the following:

Picture.PNG
Picture_2.PNG
 

Velocet

New Member
Unbenannt.png

I have a bug in 1.6.0.6080. Steps to reproduce:
- Integrate updates into LTSB 2016 ISO and process everything
- Load WIM again, change something (i did not delete any editions)
- Export to ISO

Dunno if it's corrected in the newest build but it only seems to be a UI bug since the WIM/ISO loads just fine.

[EDIT]
Ha, just read the newest changelog:
UI: Export progress bar could show incorrect values when multiple images were processed in sequence
So i think this bug report is obsolete...
 
Last edited:

nuhi

NTLite developer
Staff member
@rambolcm, let me know exactly which Windows ISO is that (original filename if possible) that is not detecting Defender, and that it's actually there after installation.

@MC_MuHyeon, I have tried just now and no issues. Did you try rebooting, cleaning the image (right-click unload before loading it), and recopy fresh ISO?
If so, please attach %temp%\ntlite.log at the moment of the error.
Also see about any antiviruses and suspend them while retrying, to exclude any external blocks.

@Velocet, yeah :), fixed in 6105, thanks for reporting anyway.
 

MC_MuHyeon

New Member
@MC_MuHyeon, I have tried just now and no issues. Did you try rebooting, cleaning the image (right-click unload before loading it), and recopy fresh ISO?
If so, please attach %temp%\ntlite.log at the moment of the error.
Also see about any antiviruses and suspend them while retrying, to exclude any external blocks.
Hi. I did as what you've said and the problem is solved. Thank you very much!
 
I have an error (something of a crucial package not being detected) when I try to load the extracted content of the likely Windows 10 RS4 (Version 1803 Build 17133.1) Enterprise pt-pt x64 version but I can successfully load the files after I click "OK".

EDIT: I also have a defaultuser0 folder inside the Users folder.
 
Last edited:

nuhi

NTLite developer
Staff member
@rambolcm, try to get the official 16299.15+, .0 was not the final build.
I would still recommend to get the new 17133.1 as it will be RS4.
Let me know if you still don't see Defender then, that would be truly unexpected.

@Windows 10 User, you really are a bug magnet :)
Enterprise package message is confirmed, working on it.
defaultuser0 first confirm that you don't have it without removals as well, I saw it using the full ISO as well sometimes.
Do you rename Administrator account, is it English or other language ISO?

Thanks.
 
@rambolcm, try to get the official 16299.15+, .0 was not the final build.
I would still recommend to get the new 17133.1 as it will be RS4.
Let me know if you still don't see Defender then, that would be truly unexpected.

@Windows 10 User, you really are a bug magnet :)
Enterprise package message is confirmed, working on it.
defaultuser0 first confirm that you don't have it without removals as well, I saw it using the full ISO as well sometimes.
Do you rename Administrator account, is it English or other language ISO?

Thanks.
No, I didn't rename it. It's the Portuguese (Portugal) version.
 
@Windows 10 User, then it's normal, I've seen defaultuser0 on non-English non-edited Windows as well.
Let me know if you don't see the same.
I've yet to see if I have it in an untouched ISO but I didn't have it in non-English non-edited and non-English edited Windows installs before RS4.

EDIT: The 1803 RS4 Enterprise edition crucial package not detected error message no longer shows up in the latest NTLite version.
 
Last edited:
Top