Unattended error "NTLCompName.vbs Permission denied code 0x800A0046"

Shanks

New Member
This last post might be a Microsoft and/or bios issue, that I too am experiencing on W10. Ever since the rise of UEFI this issue seems to be more prevalent. I've spent the last many days trying to resolve this same frustration. Windows keeps trying to boot to my USB sticks or my backup SSD drive, even though my bios has the boot order set properly, I tried changing around the sata cables, reformatting every drive, resetting the bios, clearing cmos, etc. Nothing is really solving it, and Google has a ton of people experiencing the same problems with no universal solution (people that aren't even using NTLite). The worst part is some of the issues are intermittent which makes it harder to troubleshoot.

However, I will say that the issues became more prominent after I moved to the latest NTLite version from June 11. Could be coincidence, but also maybe not. I just recently got the "Windows could not update the computer's boot configuration." after Windows Setup was finished, which is something I never saw before, and my NTLite stuff shouldn't be the cause of it. Now all of a sudden I have to physically remove my USB drive from the device or hit F10 and manually boot to my primary SSD after Windows Setup is done.
I am sorry that my english is not good.
I didn't quite understand what you meant.
I understand you seem to mean the boot is missing or corrupted.

If the error you said was about MDT, I've solved it by writing an extra script.
The following is my MDT solution (Chinese).
The relevant files are in github.

However, this time I want to implement an unattended installation system that is not based on internet.

Thanks.
 

Shanks

New Member
You've used MDT, the exact reason for doing so is fixing inconsistent BIOS setups or device order problems. NTLite doesn't compete in this space. What you can do is use NTLite to customize images, and export install.wim to MDT.
:) OK.

I want to implement an unattended installation system that is not based on internet.
I will try other ways.

Thanks.
 

garlin

Moderator
Staff member
Every ISO image has two different boot.wim's: WinPE and WinPE (Setup). The difference is Setup only runs setup.exe, instead of executing a set of pre-install scripts. You can use WSIM (from the free Windows ADK) to configure WinPE to run your custom scripts before Setup.exe.

MDT is the newer cloud replacement for WSIM, which is the same idea without a domain.
 

Shanks

New Member
Every ISO image has two different boot.wim's: WinPE and WinPE (Setup). The difference is Setup only runs setup.exe, instead of executing a set of pre-install scripts. You can use WSIM (from the free Windows ADK) to configure WinPE to run your custom scripts before Setup.exe.

MDT is the newer cloud replacement for WSIM, which is the same idea without a domain.
OK

I've read about WSIM before, maybe not enough. I will go back and check the information.

Thank you very much.
 
Top