Skip to content

CapaInstaller 6.7.109 Known Issues and Fixes

This article describes known issues identified in CapaInstaller 6.7.109 and explains how to resolve them.

Applies to: CapaInstaller 6.7.109, build 6.7.294.109 — the initial release, which introduced both issues below.

Download the newest CapaInstaller release

On that page, select Download here.

Issue 1 — Distribution Server rejects incoming file requests

Section titled “Issue 1 — Distribution Server rejects incoming file requests”
Fixed in 6.7.300.109

Symptoms: The Distribution Server rejects incoming file requests. On the client, packages never install. The package log shows the download completing, but the downloaded CapaInstaller.kit file doesn’t exist. The package then starts the same download again with a new transfer ID, and this repeats:

BaseAgent_CopyFile : File successfully downloaded
BITS_A_CopyFile : Completed
File_ExistFile : File '...\CapaInstaller.kit' does not exist.
BaseAgent_CopyFile : Starting download
BaseAgent_CopyFile : TransferID: '79'
BaseAgent_CopyFile : Transfer queued

Resolution: Install build 6.7.300.109 or later, then promote the update and run Update now on every Distribution Server. Until the servers are updated, package jobs can keep downloading in a loop and never reach installation. (First fixed in build 6.7.295.109.)

Issue 2 — OsdClient and CiBaseAgent communication is rejected

Section titled “Issue 2 — OsdClient and CiBaseAgent communication is rejected”
Fixed in 6.7.300.109

Symptoms: Communication between OsdClient and CiBaseAgent is rejected.

Resolution: Install build 6.7.300.109 or later.

Issue 3 — OS deployment fails at CopyWindowsRE

Section titled “Issue 3 — OS deployment fails at CopyWindowsRE”
Not fixed by upgrading — manual fix required

Symptoms: OS deployment fails partway through with:

Failed to copy Windows RE Tools!

Cause: The OSD point still has a legacy DiskPart.txt workaround for EFI partitions that were too small. CapaInstaller 6.7.109 creates the Recovery partition itself, so the old workaround now interferes with deployment.

Resolution: Remove the legacy DiskPart.txt workaround and rebuild the boot image.