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

Shanks

New Member
Environment:
Windows 1909 Pro x64
NTlite Home License 2.3.6.8785 x64

Hello everyone, I have a problem with Unattended.

When I change the computer name field value in unattended settings to [prompt], then apply, and finally I create new ISO file.
When I test the installation on a new computer with a fresh ISO, after I enter the computer name, I get the error: “ntlcompname.vbs Permission denied code 800A0046”

I checked unattended.xml with PE and everything looks fine:
The content looks correct.
Users have read-only permissions, and administrators and systems have read-write permissions.

And I didn't make any other changes to the original ISO.
I used the new ISO in the virtual machine and it didn't work in the virtual machine either. ,

When I don't change the unattended settings and extract only the PRO version, the created ISO works in a virtual machine.

What am I doing wrong?
Can you help me?

Honeyview_error.jpg
 
Last edited:

nuhi

NTLite developer
Staff member
Hi,

tested it now, works fine, attached below is what I see.

I'm assuming you do something extra to cause it.
If not, please attach the preset demonstrating the issue, where only that preset is necessary to replicate it.

If I need a special image, which I welcome, to see the issue with no extra steps except the preset, please upload somewhere and PM only me with the link.

Thanks.

Temp-2022-06-14-15-15-41.png
 

Shanks

New Member
Hi,

tested it now, works fine, attached below is what I see.

I'm assuming you do something extra to cause it.
If not, please attach the preset demonstrating the issue, where only that preset is necessary to replicate it.

If I need a special image, which I welcome, to see the issue with no extra steps except the preset, please upload somewhere and PM only me with the link.

Thanks.

View attachment 7527
Hi, nuhi.
Thanks for your reply.

I'm at home now and can only test with a virtual machine (VMWare 15), and while I can't fully reproduce the previous issue, I still get an error: Windows doesn't seem to load properly.

Below are the relevant documents.
administrator
1.q

The previous problem was after entering the computer name(physical machine).The installation will continue despite the error, but no account has been created.

The new error occurred before entering the computer name(VM).

Thanks.
 

Attachments

  • error1.PNG
    error1.PNG
    21.1 KB
  • info1.PNG
    info1.PNG
    38.7 KB
Last edited:

garlin

Moderator
Staff member
When I tried using '[Prompt]' for computer name, NTLite didn't create a NTLCompName.vbs
But SetupComplete has the line to remove it.

This part of the preset cannot be in Chinese.
<TimeZone>中国标准时间</TimeZone>
 

Shanks

New Member
There are two problems.
When using unattended, Setup cannot ask for the PC's name. "[Prompt]" has "[ ]", which are not allowed.


This part of the preset cannot be in Chinese.


https://docs.microsoft.com/en-us/wi...re/desktop/default-time-zones?view=windows-10
OK, I will try it.

In fact, the above options are not filled in manually by me, but are selected from the options provided by ntlite.
If the verification is successful, it may be a translation problem.

Thank you for your help.
 

Attachments

  • info2.PNG
    info2.PNG
    36 KB

nuhi

NTLite developer
Staff member
Hi, nuhi.
Thanks for your reply.

I'm at home now and can only test with a virtual machine (VMWare 15), and while I can't fully reproduce the previous issue, I still get an error: Windows doesn't seem to load properly.

Below are the relevant documents.
administrator
1.q

The previous problem was after entering the computer name(physical machine).The installation will continue despite the error, but no account has been created.

The new error occurred before entering the computer name(VM).

Thanks.
Thanks, will try your preset tomorrow on cn lang ISO and reply back.
 

Shanks

New Member
Sorry I messed up part of my reply. ^^ Updated.
I have tried it, and it still has this error.

It seems to have nothing to do with the time zone.
Because when the error "Permission denied code 800A0046" appears, the installation will continue until the system installation is completed.
Throughout the installation process, the system does not require any interaction operations; 'Unattended' looks effective..
However, the final computer did not join the working group and caused unable to log in.

I suspect that the prompt of error "Permission denied code 800A0046" is correct.
It is precisely because the input computer name does not replace "[Prompt]" that after the system is installed, the computer name is "[Prompt]" (or wrong), which makes it impossible to join the WORKGROUP?

But there is a strange problem.
The completed system in this way will wait a long time at the "Please wait" interface at each start before entering the login interface.

NTLCompName.vbs is located in install.wim.
Thanks.
 
Last edited:

garlin

Moderator
Staff member
When I tried using '[Prompt]' or '%SERIAL%', NTLite skips the important step of creating install.wim's Windows\Panther\unattend.xml.
Without a Panther\unattend.xml, Setup will search other folders for the answer file.

NTLCompName.vbs:
Code:
'Generated by NTLite - ntlite.com
unattendFile = "C:\Windows\Panther\unattend.xml"
If fso.FileExists(unattendFile) = False Then WScript.Quit

The only other file is \autounattend.xml which has '[Prompt]' or '%SERIAL%', and both names have illegal characters '[ ] %'.
Windows is not happy about that <ComputerName>.

I don't know why it's broken. Maybe nuhi will confirm.
 

Shanks

New Member
When I tried using '[Prompt]' or '%SERIAL%', NTLite skips the important step of creating install.wim's Windows\Panther\unattend.xml.
Without a Panther\unattend.xml, Setup will search other folders for the answer file.

NTLCompName.vbs:
Code:
'Generated by NTLite - ntlite.com
unattendFile = "C:\Windows\Panther\unattend.xml"
If fso.FileExists(unattendFile) = False Then WScript.Quit

The only other file is \autounattend.xml which has '[Prompt]' or '%SERIAL%', and both names have illegal characters '[ ] %'.
Windows is not happy about that <ComputerName>.

I don't know why it's broken. Maybe nuhi will confirm.
The unattend.xml file is also in install.wim (I enabled copying it in wim), you will see it after unzipping.

I think I probably know the reason for the error.

I use "autofill" in "unattended", then modify the computer name to "[Prompt]", and finally create the ISO, then it's working.
It may really be due to an error in some of the "unattended" configuration files, which makes it impossible to continue.

I think it will take a while to test one by one.
After all building wim is too slow.

Thanks for your help.
 

Shanks

New Member
No it fails even if Computer Name is the only edit in Unattend.
From the current point of view, some settings of Unattended need to be filled in.

E.g:
Fill in field 1, you must fill in field 2.
Fill in field 2, you cannot fill in field 3.

Some fields are also associated, but I can't understand the association from NTLite.
NTLite doesn't seem to populate default values for its associated fields when not filled.

If a place is filled incorrectly, the result will be an error, or fail.

I got this error, maybe that's it.
When I adopted, NTlite's Auto-Fill filled in ALL, then changed the computer name to "[Prompt]", and finally created the ISO. The new ISO works fine in virtual machines and PCs.

"Unattended" feels like a certain level of Microsoft expertise is required.
 

nuhi

NTLite developer
Staff member
Used your preset (just had to remove the product key), and 18363.592_amd64_zh-cn_professional
No issues, attached screenshot.
TempBios-2022-06-15-16-32-05.png
Also installed to the end.

Can you think of anything else, any extra steps other than NTLite, maybe upload your exact image?
 
Last edited:

Xiphan

New Member
I hope I can also jump aboard this thread as I'm also having an issue with NTLCompName.vbs albeit in trying to create an up-to-date Windows 8.1 ISO:

NTL.png

If I click OK setup will continue and Windows will eventually boot up but it causes a problem in that it skips the rest of the setup process and does not display the setup stages where I can create a local account. It skips this step even though I didn't have skip local account setup selected in the unattended settings. So while it does eventually come to a login screen I have no way of logging in to the PC.

This is what I had specified for computer name:

Code:
<ComputerName>EE-%SERIAL%</ComputerName>
 

nuhi

NTLite developer
Staff member
I hope I can also jump aboard this thread as I'm also having an issue with NTLCompName.vbs albeit in trying to create an up-to-date Windows 8.1 ISO:
That's a different scenario and error, still thanks for the feedback.

Confirmed, seems like the function used is not available on Win8.1.

Will correct the script to politely skip, not error out, and see alternative option for legacy OS.

Thanks!
 

Shanks

New Member
Used your preset (just had to remove the product key), and 18363.592_amd64_zh-cn_professional
No issues, attached screenshot.
View attachment 7544
Also installed to the end.

Can you think of anything else, any extra steps other than NTLite, maybe upload your exact image?
I did nothing else but populate the unattended fields.

From my current test results(refer to my conversation with Garlin.), it should be that some fields conflict.
There are so many unattended fields, I tested a few variations, but the wait times in loading and building are just too long (my PC isn't bad)...so I'm giving up on testing for now. . .

Only the auto-fill all and change computer name fields are applied.

Thank you very much.
 

nuhi

NTLite developer
Staff member
I did nothing else but populate the unattended fields.

From my current test results(refer to my conversation with Garlin.), it should be that some fields conflict.
There are so many unattended fields, I tested a few variations, but the wait times in loading and building are just too long (my PC isn't bad)...so I'm giving up on testing for now. . .

Only the auto-fill all and change computer name fields are applied.

Thank you very much.
I used your preset directly, on a Chinese ISO. Other than getting your exact image, I'm out of options.
 
Last edited:

Shanks

New Member
I used your preset directly, on a Chinese ISO. Other than getting your exact image, I'm out of options.
:) Thanks.

I'll pack it up and upload it to a web drive later for you to test.

I have a new problem.

When using the unattended partition function. In actual deployment, if there are multiple hard disks, the system installation will be randomly installed on one of the hard disks.

Because when the Windows system recognizes the disk, it is out of order.
E.g:
Possibly: m2 is disk0, hdd is disk1.
Possibly: m2 is disk1, hdd is disk0.

I encountered this problem before when I used Microsoft's MDT. In MDT, I can use a script to select the hard disk that needs to be installed. Does NTlite have a similar function?

There seems to be an additional problem with NTlite, when I use a USB stick to install the system, it may recognize the USB stick as disk0, which causes an error.
 
Last edited:

Hellbovine

Active 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.
 
Last edited:

garlin

Moderator
Staff 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.
 
Top