Skip to content

Troubleshooting

Common issues and how to resolve them. If your problem is not listed, contact support@pvs-forge.com.

Guided self-help (Notification center)

PVS Forge points you to the common problems below directly in the app. When a problem aborts an imaging job, it appears in the Notification center — the Notification entry at the bottom of the sidebar, with a badge for unread notices. Click Possible Solution on an entry to see the cause and the fix. Depending on the problem, the dialog offers a command to copy and run on the master target, a jump to the matching settings page, or a one-click fix (always with a confirmation).

For example, if PowerShell remoting is disabled on the master target, a "WinRM access denied" notice offers the command Enable-PSRemoting -Force to run on the target.

Works offline

The guided self-help is fully offline and needs no API key or internet access.

Imaging will not start

Symptom: The Play button does nothing, or you are told imaging is blocked.

  • License required. Imaging is gated by licensing. If you have no valid license, or your trial has expired, imaging will not start. Activate or renew your license on the License page. The rest of the app (dashboard, compare, vDisk storage, history) stays available.
  • Row belongs to a running batch. A master target that is part of a Start all batch that is still running cannot be started again until its own job finishes; the live log notes this when you click Play. Other rows are not affected — they can be started individually or as a second batch.
  • Reachability check failed. Watch the live log: it shows which step failed (ping, WinRM, or store). Fix that specific item and retry.

Cannot reach the master target (WinRM)

Symptom: The job fails at the WinRM step.

  • WinRM (port 5985) must be enabled on the master target and reachable from the PVS server.
  • Always reach the master target by hostname / FQDN, not by IP — Kerberos needs the hostname.
  • Verify the imaging credentials (Settings → Security) have WinRM rights on the target.

If WinRM has never been set up on the master target, one command is enough — run it on the master target in an elevated PowerShell:

winrm quickconfig -quiet

This enables the WinRM service, creates the HTTP listener on port 5985, and adds the required firewall rule in one step.

Scheduled task fails to register

Symptom: Imaging fails while registering the imaging task on the master target.

The imaging task runs as a batch logon. The most common cause on hardened targets is a missing user right: the imaging account needs Log on as a batch job on the master target. With tiered/Tier hardening this right is often removed — imaging then never starts until it is granted. The logon stores no password, so "Do not allow storage of passwords and credentials for network authentication" is not the problem.

If registration or start still fails, check that:

  • the imaging account holds Log on as a batch job on the target and is not covered by a Deny log on as a batch job policy,
  • the master target credentials have local administrator rights on the target,
  • WinRM (5985) is reachable from the PVS server, and
  • no third-party agent on the target is blocking task registration.

gpresult /H report.html on the target helps confirm which policies are applied.

Sync to another PVS server fails (SMB)

Symptom: Imaging completes but the sync to another PVS server fails, or hangs for ~20 seconds before failing.

  • SMB (port 445) must be reachable on the sync target. Reachability is what matters — a firewall rule existing is not the same as the port being open.
  • PVS Forge checks SMB over IPv4. If a hostname resolves to IPv6 first, you can hit a ~22 second IPv6 timeout before the IPv4 fallback. Ensure IPv4 connectivity to port 445.
  • On multi-NIC targets, make sure SMB is open on the interface the push actually uses (your LAN, not the streaming NIC).

Not enough space on the sync target

Symptom: The job stops before or during sync with a capacity error.

PVS Forge checks free space before pushing and applies a safety margin (a VHDX is typically larger than the file-system "used" figure because imaging captures block-level data plus NTFS metadata). Free up space on the target store, or sync to a target with more capacity.

Imaging waits and retries right after the start

Symptom: Shortly after the imaging phase begins, the live log shows a retry message and the job waits a few minutes before continuing.

Cause & fix: At the moment the image capture is prepared, Windows must briefly freeze and flush all disk writes on the master target. Under heavy disk load (for example parallel imaging jobs, backups, or antivirus scans hitting the same storage), this can time out. PVS Forge treats this as temporary and automatically retries up to three times (waiting 2 and then 5 minutes). Usually no action is needed — the job continues on its own. If it still fails after three attempts, reduce the concurrent disk load on the master target's storage and start the job again.

Imaging fails at the very end ("file in use")

Symptom: The imaging copy runs to 100 %, but the job fails while finalizing the new vDisk — often with a "file in use" / "used by another process" error, and sometimes only intermittently or when several vDisks target the same store.

Cause & fix: Real-time antivirus on the PVS server (for example Windows Defender) scans the store's vDisk files on access and can hold one open into the finalize step. Exclude the vDisk store from real-time scanning on every PVS server — see Antivirus exclusions.

PVS Forge closes when the RDP session times out

Symptom: An administrator starts PVS Forge in an RDP session on the PVS server, disconnects the session, and later finds the run aborted — without any notification.

Cause & fix: The server ends disconnected (or idle) RDP sessions after a time limit, and PVS Forge is terminated together with the session. PVS Forge checks this at startup: if a time limit is active, a notice appears in the notification center. The suggested solution can set the local group policy to never end sessions directly from the notice (with confirmation). Note that a domain group policy overrides the local value — in that case, ask your domain administrator; the notice will reappear at the next start. Until the limit is removed, keep the RDP session connected while a run is active.

PVS Forge starts in demo mode

Symptom: Imaging options are unavailable and the app indicates a limited mode.

The Citrix PVS PowerShell snap-in (Citrix.PVS.Snapin) was not found. PVS Forge must run on a PVS server with the snap-in installed. Demo mode is only for exploring the UI on a machine without PVS.

Only one instance runs

Symptom: Starting PVS Forge shows a message that it is already running.

PVS Forge allows a single instance per host (across all RDP sessions). The message includes who holds it (session, user, start time). Use the existing instance, or close it first.