Unsolved
6 Posts
0
4237
Precision 3630 - Command Configure 4.2.1.568 - Couldn't get WMI-ACPI Buffer Size
I am unable to set BIOS options on this machine using Command Configure 4.2.1.568.
During install I get told the machine is not compatible (although it is listed under Compatible Systems on the download page), but I am offered the chance to continue with install.
After instal, if I try to use the cctk command line, I get the error message "Couldn't get WMI-ACPI Buffer Size". I did not try the GUI.
Machine is on BIOS 2.4.2. Latest BIOS 2.5 would not install via Windows - I received the "Failed to read manifest on current system" as reported elsewhere on this site and I do not have physical access to install from USB.
How do I resolve this?
Has anyone else had this issue? I see there is a newer version of Command Configure available, 4.3.0.83, perhaps that will work? Or do I just need to wait for the BIOS 2.5 Windows package to be fixed?
I won't be able to test anything on the machine until next week but if anyone else has ideas that would be helpful.
rsm080
6 Posts
0
April 17th, 2020 00:00
I assume from the lack of responses no-one else has had this problem (or even better, solved it...)
I've tried updating to the latest Command Configure, 4.3.0.83, and it gives the same error message.
I assume (although didn't have time to try again today) that the Windows EXE to update from BIOS 2.4.2 to BIOS 2.5 is still broken with "Failed to read manifest on current system".
Due to Covid-19 lockdown I can't get physical access to the machine to update the BIOS via F12 and USB key.
Perhaps BIOS 2.4.2 is the issue here? Nothing can read values from BIOS 2.4.2, not even the Windows EXE package to update to 2.5..?
rsm080
6 Posts
0
April 17th, 2020 09:00
So... after a frustrating afternoon during which I discovered a second 3630 with the exact same problem I was eventually able to find a workaround.
BIOS 2.5.0 doesn't fix this problem, I managed to talk a user through doing the update from a USB stick but it made no difference to whatever was blocking me from using Command Configure.
However I did notice once change. After the update to BIOS 2.5.0, although Command Configure 4.3.0.83 still gave the "Couldn't get WMI-ACPI buffer" error, trying again with Command Configure 4.2.1.568 I got a different error - "SYSTEMSMANAGEMENT: The current user does not have elevated administrator privileges" (which is nonsense, the user was a local admin). Perhaps a hint at what is going wrong on an underlying level though.
What eventually allowed me to update BIOS settings was to go right back to an ancient version of Dell CCTK, v 2.0.1 in fact, released 2011(!). With this I was able to successfully enable Wake-On-Lan on BIOS 2.5.0.
Slightly worried it might have some ill effects but not noticed anything so far other than WOL working so fingers crossed all good and I imagine that one day the current software will be updated so that it actually works on this machine.
thierryd83
2 Posts
0
April 20th, 2021 01:00
Hi i have Precision 3630 bios 2.5 and i using Command Configure 4.4.0.86 for unified bios settings and bios update but don't work
Have you resolve this problem ? it's very stange because precision buying dated 2020 ...
First problem is Couldn't get WMI-ACPI Buffer Size on installation Command Configure software
And second problem is Failure to update bios result : Couldn't get WMI-ACPI Buffer Size!! and FAILURE
Thanks !
rsm080
6 Posts
0
May 27th, 2021 07:00
Hi, I'm afraid not, in fact I'm encountering the exact same problem on a new Precision 3640, can't update the BIOS, can't use Command Configure.
The software quality is an absolute joke and this time the Dell CCTK v 2.0.1 workaround is no joy.
Thanks Dell.
speedstep
8 Wizard
8 Wizard
•
47K Posts
0
May 27th, 2021 08:00
"Are you telling me these machines don't have WMIC-ACPI BIOS"
No I did not say that. Those are your words.
There is Pro support for this.
Said support for Command and SCCM is not free.
This software does not support all models all years all os versions etc.
See Supported Platforms for more information.
https://www.dell.com/support/article/SLN312336/
ACPI is processor specific.
I said nothing about the age of the machine.
The support you are asking for has a per incident cost from DELL or Microsoft unless you have a support contract. They will also provide an onsite engineer but this too is not free.
https://www.dell.com/support/kbdoc/en-us/000178049/
https://support.microsoft.com/en-us/topic/microsoft-professional-support-pay-per-incident-faq-575821bc-17bb-7484-4935-334c5437639f
https://www.delltechnologies.com/en-us/collaterals/unauth/quick-reference-guides/services/dell-prosupport-suite-for-pcs-comparison-chart-commercial.pdf
rsm080
6 Posts
0
May 27th, 2021 08:00
Both are Core i7 machines.
BIOS update should just work. Especially a critical BIOS update.
I shouldn't need support for Command Configure, I don't want to do anything special with it, I just want it it to connect to the BIOS in the first place so I can issue a couple of commands.
speedstep
8 Wizard
8 Wizard
•
47K Posts
0
May 27th, 2021 08:00
There is Pro support for this.
Said support for Command and SCCM is not free.
ACPI is processor specific.
https://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/processor-vendor-specific-acpi-specification.pdf
[05/27/21 08:30:56] Vendor Software Return Code: 141
[05/27/21 08:30:56] Name of Exit Code: Couldn't get WMI-ACPI Buffer Size!!
[05/27/21 08:30:56] Exit Code set to: 0 (0x0)
[05/27/21 08:30:56] Result: FAILURE
[05/27/21 08:30:56] Name of Exit Code: Couldn't get WMI-ACPI Buffer Size!!
[05/27/21 08:30:56] Execution terminated at date-time 05/27/21 08:30:56
[05/27/21 08:30:56] ######
CCTK is now Dell Command | Configure and is a part of the Dell Client Command Suite. Click HERE to go to the new page.
Dell Command | Configure 4.0 or later requires platforms supporting WMI-ACPI BIOS.
The error is VERY specific.
Previous Releases
Dell Command | Configure 4.0
Dell Command | Configure 3.3
Dell Command | Configure 3.2
Dell Command | Configure 3.1.2
Dell Command | Configure 3.1
Dell Command | Configure 3.0
rsm080
6 Posts
0
May 27th, 2021 08:00
In both cases we are talking about a brand new machine, (last year - a 3630, this year, a 3640) with Dell's own build of Windows installed, where Dell's own software update tool is are unable to see the BIOS from Windows to perform an update described as critical and where Dell's own Command Configure tool - the very latest one - also can't talk to it.
Are you telling me these machines don't have WMIC-ACPI BIOS? Of course they do. Brand new machines. Fool me twice shame on me I guess.
thierryd83
2 Posts
0
May 27th, 2021 23:00
The error is VERY specific ???
yes, perhaps but what is the solution ?
I have 200 new Dell precision 3630 (buying 2020) with this problem not resolve by bios update
Trooper Smith
4 Posts
0
November 5th, 2021 12:00
I just tested this (see below) and if you install DCC v3.0 -> v3.3 and then (re)create the EXE Package again for your machines, which I use the 'multiple machine type' BIOS config in DCC for our four different Precision models, I hope it works for you like it did for me.
From my old Dell Precisions T5810, it proved that you cannot create an EXE package in 4.x of the DCC for the older/legacy BIOS Precisions as WMI queries that DCC CCTK.exe component within the EXE package is v4.x and fails with the error.
Now I know all your PCs are new, but give the DCC v3.3 a try, which I assume it will still install on a brand new Dell.
If it fails from the DCC v3.x EXE package, I would try changing the bios back to Legacy mode (if still available on new Dells) and try with the v3.3 EXE package, just on one PC to check. Then I would try to change the bios mode back to UEFI and run the same v3.3. EXE package it again and review the EXE log file to see.
Anyway, I see this thread it a little old and you have it sorted by now, or I hope this helps out in some way.
Cheers!
Version 4.x EXE package log:
[Sat Nov 6 04:54:41 2021]
--- End of Vendor Software Log ---
[Sat Nov 6 04:54:41 2021] Get name of the Folder file: C:\temp
[Sat Nov 6 04:54:41 2021] Vendor Software Return Code: 141
[Sat Nov 6 04:54:41 2021] Name of Exit Code: Couldn't get WMI-ACPI Buffer Size!!
[Sat Nov 6 04:54:41 2021] Exit Code set to: 0 (0x0)
[Sat Nov 6 04:54:41 2021] Result: FAILURE
[Sat Nov 6 04:54:41 2021] Name of Exit Code: Couldn't get WMI-ACPI Buffer Size!!
[Sat Nov 6 04:54:41 2021] Execution terminated at date-time Sat Nov 6 04:54:41 2021
[Sat Nov 6 04:54:41 2021] ######
Version 3.3 EXE package log:
CCTK STATUS CODE : SUCCESS
[11/06/21 05:21:49]
--- End of Vendor Software Log ---
[11/06/21 05:21:49] Get name of the Folder file: C:\temp
[11/06/21 05:21:49] Vendor Software Return Code: 0
[11/06/21 05:21:49] Name of Exit Code: SUCCESS
[11/06/21 05:21:49] Exit Code set to: 0 (0x0)
[11/06/21 05:21:49] Result: SUCCESS
[11/06/21 05:21:49] Name of Exit Code: SUCCESS
[11/06/21 05:21:49] Execution terminated at date-time 11/06/21 05:21:49
[11/06/21 05:21:49] ######
jsiii2010
14 Posts
0
February 1st, 2023 08:00
I don't get it. Some models just randomly don't work. It doesn't matter how old they are. If I try to use cctk 3, it says "There was an error setting the option 'wakeonlan'".
jsiii2010
14 Posts
0
May 31st, 2023 11:00
This is quite intractable. It seems to resolve itself in win10 22h2 or win11 22h2. Maybe it's a weird driver issue.
DELL-Cares
Moderator
Moderator
•
25K Posts
0
June 16th, 2023 05:00
Thank you for the confirmation. We’re glad the issue is resolved.
jsiii2010
14 Posts
0
June 16th, 2023 05:00
Uninstalling two of the system devices in device manager, 'Microsoft System Management BIOS Driver' and 'Microsoft Windows Management Interface for ACPI', and rebooting fixed it for me (the devices come back). It fixes bios updates and powershell as well.