/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Feature Update Windows 10 build 2004 fails and retries immediately

08/19/2020 432 views

We have been able to get the 1903 and 1909 feature updates to deploy successfully, but we are having an issue with Feature Update 2004.  We cloned the same settings for 1903 and 1909 update for a Detect and Deploy and all the same prompts to the 2004 settings, but the deployment keeps failing.  We have been able to run the update manually by downloading from MS so it does not appear to be a compatibility issue.

When we look inside the C:\ProgramData\Quest\KACE\kpd folder, we clearly see the 3+ GB .ESD file download, but it never installs.  After about a minute the ESD file disappears and our Kace prompt box give our completed message even though it did nothing.  Then about a minute later it tried the same thing 2 more times.  After the 3 tries the computer inventory shows:

  • Deploy Status: Failed
  • Exit Code: 3247440417,0xC1900221
  • Deploy Tries: 3

I can't seem to find any logs to tell me why this is failing.

1 Comment   [ + ] Show comment

Comments

  • Wish I could answer this for you. We blocked it due to risk. Too many potential driver issues. We have a team testing it but havent heard anything.

All Answers

0

Hi,

that  Exit Code: 3247440417,0xC1900221 , comes from the O.S., the KACE agent is just passing the error generated by Windows.

The Kagent.log  could give you some insights...

After the payload is downloaded, WindowsUpdateBox.exe should kick off the process.

Go to:
C:\ProgramData\Quest\KACE\user\KAgent.log

Around the time you started the process search for this line:

KLaunchClientImpl::LaunchInSession    cmd=[C:\ProgramData\Quest\KACE\kpd\WindowsUpdateBo x.exe /Update /Install /quiet /noreboot

If you see that line, the payload was downloaded, and the Windows 10 Setup exe was started.

At this point it's time to review Windows Logs to attempt to determine what went wrong, those are:

setupact

setuperr

diagwrn

diagerr

These are all log files from this folder C:\$WINDOWS.~BT\Sources\Panther.

You might want to target a vanilla 1903 or 1909 virgin VM or device.

I would also do an sfc /scannow in those devices.


Answered 08/20/2020 by: Channeler
Red Belt

  • Something failed, but I am not able to interpret what it means. Here is the KAgent.log below. The other logs never get created:

    * Connection #0 to host mykboxhost.com left intact
    [2020-08-22.14:48:12][KacePatch:KWeb::UploadUsingCurl ] UPLOADFILE: CURL DEBUG INFO --->>> END <<<---
    [2020-08-22.14:48:12][KacePatch:KWeb::UploadUsingCurl ] UploadFile: Uploaded to https://mykboxhost.com/service/kbot_upload.php?checksum=ce409836eff4938357effcc311c041e347f170d071a95d0502e2f7d4cf8e302a1bd3d80ba9319d176c5653e72377c149114a17b2396272f44e985136d944dba5 Upload speed: 1109.000000 bytes/second
    [2020-08-22.14:48:12][KacePatch:KWeb::UploadUsingCurl ] UploadFile: Server gzip compression cleanup.
    [2020-08-22.14:48:12][KacePatch:KacePatch::Execute ] KacePatch::DoPlugin: Command finished
    [2020-08-22.14:48:12][KacePatch:main ] KacePatch::Main: Sending final status 0 back to SMA
    [2020-08-22.14:48:12][KSWMeter:EventSink::Indicate ] EventSink::Indicate, process id 1520 name C:\Program Files (x86)\Quest\KACE\KacePatch.exe size 3666432 created, stored in the hash
    [2020-08-22.14:48:13][KSWMeterSvc_:ProcessMeter::AddPr] Checking mobile attribute ~|~| against blacklist
    [2020-08-22.14:48:13][KSWMeterSvc_:ProcessMeter::AddPr] APP_LAUNCHED event occured, process 1520 name kacepatch.exe with original name KacePatch.exe s-time 2020-08-22 18:48:12
    [2020-08-22.14:48:13][KSWMeterSvc_:ProcessMeter::AddPr] inserted 1 rows into process DB: Process ID 1520 Name kacepatch.exe
    FileVersion 10.2.110 ProductVersion 10.2.110
    Description KacePatch Publisher Quest Software Inc.
    Modified Date 2020-08-21 Language Code 0409 user ##NOTUSER##
    Start Time 2020-08-22 18:48:12

    [2020-08-22.14:48:13][KSWMeter:EventSink::Indicate ] EventSink::Indicate, failed to open and get a valid handle for process 8256
    [2020-08-22.14:48:13][KSWMeterSvc_:ProcessMeter::AddPr] updated 1 rows in process DB
    [2020-08-22.14:48:13][KSWMeterSvc_:ProcessMeter::AddPr] APP_TERMINATED event occured, process 1520 s-time 2020-08-22 18:48:12 e-time 2020-08-22 18:48:13
    [2020-08-22.14:48:26][KSWMeterSvc_:ProcessMeter::AddPr] updated 1 rows in process DB
    [2020-08-22.14:48:26][KSWMeterSvc_:ProcessMeter::AddPr] APP_TERMINATED event occured, process 7920 s-time 2020-08-22 18:46:27 e-time 2020-08-22 18:48:26
    [2020-08-22.14:48:42][KSWMeterSvc_:ProcessMeter::AddPr] updated 1 rows in process DB
    [2020-08-22.14:48:42][KSWMeterSvc_:ProcessMeter::AddPr] APP_TERMINATED event occured, process 9108 s-time 2020-08-22 18:47:27 e-time 2020-08-22 18:48:42
    [2020-08-22.14:49:14][KSWMeterSvc_:ProcessMeter::AddPr] updated 1 rows in process DB
    [2020-08-22.14:49:14][KSWMeterSvc_:ProcessMeter::AddPr] APP_TERMINATED event occured, process 3780 s-time 2020-08-22 18:47:52 e-time 2020-08-22 18:49:14
    [2020-08-22.14:49:14][KSWMeterSvc_:ProcessMeter::AddPr] updated 1 rows in process DB
    [2020-08-22.14:49:14][KSWMeterSvc_:ProcessMeter::AddPr] APP_TERMINATED event occured, process 6176 s-time 2020-08-22 18:47:52 e-time 2020-08-22 18:49:14
    [2020-08-22.14:49:38][KSWMeterSvc_:ProcessMeter::AddPr] updated 1 rows in process DB
    [2020-08-22.14:49:38][KSWMeterSvc_:ProcessMeter::AddPr] APP_TERMINATED event occured, process 1936 s-time 2020-08-22 18:48:06 e-time 2020-08-22 18:49:38
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ