When loading a KBE, the Script Error "Could not complete the operation due to error 8004100c" shows before opening the KACE Boot Environment.
Answers (6)
There’s a way to bypass this. When you get this error and it fails, it typically gives you options to edit with CMD, notepad, etc. Choose to edit with notepad and your computer's file explorer will appear. Look for the device you are imaging with and look for a folder named KACE, it may be called something different for you. Regardless, find the "network" and "storage" folders. If you have any files inside that are named any of these:
6621F_A00-00
99KJH_A00-00
904JJ_A00-00
HF3RM_A00-00
T6VND_A00-00
YK00J_A00-00
Please remove them and restart the computer to begin the image process again. The PC should pass the step it was failing at before.
Correction. It didn't work. It looked like it was. I got to pick my KBE and it started loading, I got the windows splash screen then it started loading the script again and threw the same error.
I am getting this error when using WinPE 11 version A04 but not using WinPE11 is there a huge difference in this?
Try clearing out your driver share, reload the driver package from support and recreate a fresh KBE, that’s always the first step I take when I have KBE issues
Comments:
-
Still have this problem, I followed these instructions to no avail:
(1, downgrade Windows-ADK)
https://support.quest.com/kace-systems-deployment-appliance/kb/4374054/vbgetmac-script-error-loading-kbe
and
(2, delete Drivers in K2000 KBE-Share)
https://support.quest.com/kace-systems-deployment-appliance/kb/4371486/receiving-script-error-8004100c-when-loading-kbe
Very frustrating, as there's no appropriate driver Support for new devices from Quest at the moment. The Driver Pack on the SDA Software download page STILL refers to the Driver Pack A29 from March 2023(!).
I already opened a ticket at Quest to update the drivers on the Quest software download page; the support is nice and the download page for SDA 9.2 was updated soon (sadly with a link to the old drivers, A29). They say that another team responsible for up-to-date driver Packs is investigating it, we can just hope now.
Additionally, I got a link from the Quest support Team for a direct driver Pack download from DELL Version A33, which is to find here, maybe it helps others, for me, it doesn't work when following the steps above:
https://www.dell.com/support/kbdoc/en-us/000107478/dell-command-deploy-winpe-driver-packs?lwp=rt - ChristianMRZ 7 months ago
Same here, the line 279 in the kacelib.js tries to do this:
inv_data.MAC_Address = VBGetMAC();
which obviously fails.
This could be, according to other articles here:
- missing VBScript support (Link:the suggested solution is to downgrade to Windows ADK 22H2)
- it could be caused by some drivers, which musn't be in the KBE-image (Link: the suggested solution is to delete the related drivers).
Tried both solutions, but it still doesn't work. Opening a new ticket at Quest now.
I was getting this on a Lenovo X1 Carbon. We have 2 DC running DHCP and it turns out scope options 66&67 were only set up on one of them. Once I set it up on the second mine booted and imaged without any issues.