Known Issues and Workarounds

SPX 8.0

• Installer known Issues:
• Links in the License agreement are not clickable.
• The SPX application size shown in the control panel or Add or Remove Program menu maybe shown as larger that it actually is due to differences in builds or upgrades.
• Clicking the print button in the Installer license agreement, prints “Lorem Ipsum” text instead of the actual EULA.
• For Agent Based (volume based) backups, when the destination of a job is changed and .spf/.spi files are copied to the new location agent/volume-based backups continue as incremental because all chain information (file set ID, PIT ID, generation) is stored inside the file headers, and the system can rebuild its records by scanning the destination. Host/VM-based (Hyper‑V) backups cannot continue as incremental in this scenario because Hyper‑V incrementals require a Change Tracking (RCT) ID that is issued by Hyper‑V per backup and stored only in the product database — it is never written into the backup files.
• Additionally, the VM-side validator does not perform an on-disk fallback scan to rebuild chain records from copied files. As a result, the next host/VM backup is downgraded to a full or differential.
• For host/VM jobs requiring a destination change, expect a new full backup and let subsequent scheduled runs rebuild the incremental chain.
• VirtualBoot, Mount (for File & Folder Recovery) and ImageManager Advanced Verification for Hyper-V Host Based backups are not supported in SPX version 8.0.
• Key Points:
• With Host Based Backup mode enabled, if you also have Agent backup images in the environment, you won’t be able to use Mount or VirtualBoot actions on the Hyper-V host.
• ImageManager 8.1 or newer is required to manage and support Host Based Backup images.
• ShadowControl 4.6 is not yet integrated with Host Based Backup options.
• Host Based Backup currently only protects entire virtual machines hosted in stand-alone Hyper-V servers. SPX 8.0 doesn’t support disk exclusions or Hyper-V clusters.
• For SPX 8.0 Host Based restores, if you attempt to mount a VHD/VHDX by right clicking on it (i.e. using the Windows mount functionality) you may see the error: "You don't have permission to mount the file" (or a similar message).
• If you use the Windows mount functionality you may be able to see the drive in disk manager as being attached but a drive letter won't be assigned.
Common reasons why drive letters may not be assigned.
Disk ID collision (very common with cloned/system VHDX)
• If the VHDX is a clone of another Windows disk, it can have the same disk signature/GPT disk GUID as an existing disk.
• Windows may attach it but keep it offline or partially unusable, and Explorer reports a generic “you don’t have permission to mount.”
Partition attributes block drive-letter assignment
• The NTFS partition may have GPT attributes like Hidden or NoDefaultDriveLetter.
• Result: disk attaches, but NTFS volume never gets a letter automatically.
Automount is disabled or SAN policy is restrictive
• If automount is disabled, new volumes do not get letters.
• SAN policy like OfflineShared can also keep newly attached virtual disks from being brought online as expected.
BitLocker-protected OS/data partition
• If the NTFS partition is BitLocker-encrypted, Windows may attach the disk but not assign a normal letter until unlocked.
Mounted read-only / VHDX file access context.
• If the VHDX file is in a restricted location, has read-only state, or is attached in read-only mode, Explorer can show misleading permission text.
Partition type is wrong
• If the “main” partition was accidentally marked as Recovery or other non-basic data type, Windows won’t treat it as a normal mountable data volume.
Assigning a drive letter with Powershell commands - Temporary Workaround.
To assign drive letters to partitions that need to be exposed the following tools can be used:
• Disk management console Snap-in.
• Powershell command Add-PartitionAccessPath.
• DiskPart command-line utility.
Note: Only the main Basic Data NTFS partition should get (or be assigned) a letter. It is normal for EFI and Recovery partitions to not receive drive letters.
• SPX Agent Based backup jobs fail for all volumes when an exFAT volume is included in the same backup job with other supported volumes (e.g., NTFS, FAT32). The error displayed is: “Not Supported on This Platform – Unable to Take Snapshot of the Volume."
• When installing and configuring remote monitoring on SPX 8.0, make sure that the installation type is the same for the core server and the remote monitor machines. For example, if the core server is Agent based the remote monitor must also be Agent based. If you are using Host Based backup on the server, the remote machine must also be installed with the Host based option. See the Remote Monitor and the Silent Install sections of the User Guide for additional information.

Core Server Installation	SPX Remote Monitor Installation	Allowed?
Agent Based	Agent Based	YES
Agent Based	Host Based	NO
Host Based	Host Based	YES
Host Based	Agent Based	NO