When attempting to capture or create a new disk or partition image using GhostCast Server, the process consistently stalls or terminates between 5% and 20% completion with Error 19945.
While image deployment (restoration) tasks may complete successfully, capturing new images fails across both unicast and multicast session types, regardless of whether older or newly created WinPE USB boot drives are used.
GSS 3.3.13
Component: GhostCast Server (Ghost64.exe / GhostCast executable)
Preboot Environment: WinPE Automation (USB Boot Media)
GhostCast Server Error 19945 represents a communication timeout or session synchronization drop between the Ghost client executing in WinPE and the GhostCast Server host. During heavy inbound data streams (image creation), the client drops TCP/UDP acknowledgments (ACK), causing both endpoints to wait indefinitely on packet arrival until the connection times out.
While software firewalls, antivirus interceptors, or corrupt preboot media frequently trigger this timeout, network infrastructure instability, specifically intermediate switch port packet drops under high-throughput conditions, is a primary root cause when software configurations are validated.
Confirmed Primary Cause: Degradation or buffer exhaustion in the physical network switch, causing severe packet drops during high-speed data uploads from client to server.
Probable Secondary Causes:
Firewall / Security Filtering: Windows Defender Firewall or EDR/Antivirus inspecting dynamic GhostCast communication ports (TCP/UDP 6666–7000 and 20700–20705).
WinPE NIC Driver Instability: Network adapter driver drops connections during sustained send operations.
Storage Access Issues: Target drive write locks or insufficient host storage permissions.
Verify that the destination path on the GhostCast Server (e.g., C:\Users\Administrator\Desktop\Test Image\) has adequate free disk space to store the uncompressed image payload.
Confirm that the directory is not set to Read-Only and that local security software does not block write attempts from GhostCast.exe.
Ensure that required network ports are open on the GhostCast Server host:
Open the Windows Defender Firewall console:
Click Start > Control Panel > Administrative Tools > Windows Defender Firewall with Advanced Security.
On the left navigation pane, select Inbound Rules, then click New Rule... on the right panel.
Configure the inbound rule for the following port specifications:
Rule Type: Port
Protocol & Ports: Select TCP and specify local ports 6666-7000, 20700-20705.
Action: Allow the connection.
Profile: Select Domain, Private, and Public.
Repeat Step 3 for UDP protocol on the same port ranges.
Repeat the entire procedure under Outbound Rules.
Note: Temporarily disabling the Windows Defender Firewall service helps isolate whether security rules are blocking data flow.
If communication drops persist, generate advanced trace logs from the client in WinPE:
Boot the target endpoint into the WinPE preboot environment via USB.
Open the Command Prompt inside WinPE and navigate to the Ghost directory:
cd /d X:\ghost\
Execute ghost64.exe with diagnostic logging enabled:
ghost64.exe -afile=X:\ghost_debug.txt
Reproduce the image creation workflow.
Inspect X:\ghost_debug.txt or ghosterror.txt for packet acknowledgment timeout patterns:
[TCP/IP Diagnostic] Client waiting on ACK from Server...
[GhostCast] Timeout waiting on client payload response (IP: 128.###.###.111)
Review the following matrix when interpreting network session failures:
| Diagnostic Finding | Root Cause | Action Step |
| Symmetrical timeout (Client and Server both waiting for ACK) | Physical switch packet dropping or port flapping | Replace intermediate network switch or connect via direct crossover patch cable |
| Multicast fails immediately; Unicast succeeds | IGMP Snooping or switch multicast filtering | Enable IGMP Snooping on switch or switch session mode to Unicast |
| Stalls immediately at 0% | Port blocking or folder write restriction | Verify inbound/outbound ports 6666–7000 and 20700–20705 |
Disconnect the host and target system from the production network switch.
Connect both machines through a known functional switch or direct ethernet connection.
Re-run the image creation task to verify resolution.
When diagnosing complex deployment issues, check the following system components:
Network Interface Settings: Ensure jumbo frames and energy-efficient ethernet (EEE) are disabled on the server NIC properties.
WinPE Drivers: Verify that the correct Win11 network driver (matching the WinPE kernel version) is imported into the Boot Disk Creator rather than standard desktop drivers.
Ghost Command Line Switches: Test image capture using standard performance switches to bypass potential driver bottlenecks. DOS command:
ghost64.exe -noide -nongui -ffu