(For AWS) Crash-consistent snapshot created instead of filesystem-consistent snapshot

Snapshots taken through AWS Systems Manager (SSM) on Windows Server 2025 are resulting in crash-consistent images instead of filesystem-consistent snapshots. This occurs even though the Provider Managed Consistency and Filesystem consistent are set to true in the Web UI.

The following error message is displayed:

485}    Writer Instance Id: {6d67b7e3-a3f1-43e0-b46d-3e91a65550b7}    State: [1] Stable    Last error: No error  \\r\\nec2-vss-agent is not running.
\\r\\nRunning tasklist /m ec2vssprovider.dll \\r\\nINFO: No tasks are running which match the specified criteria. \\r\\nEC2 VSS Agent Version: 2.3.2.21
\\r\\nPowerShell version: \\r\\n5.1.26100.6584 \\r\\nActive AWSPowerShell version: \\r\\n\r\nAWS Tools for PowerShell\r\nVersion 4.1.892\r\nCopyright
Amazon.com, Inc. or its affiliates. All Rights Reserved.\r\n\r\nAmazon Web Services SDK for .NET\r\nCore Runtime Version 3.7.500.13\r\nCopyright Amazon.com,
Inc. or its affiliates. All Rights Reserved.\r\n\r\nRelease notes:

This issue occurs when the AWS VSS components have been upgraded to the latest versions (2.5.x) along with the AWS VSS SSM document.

The updated VSS Agent does not correctly register or start on Windows Server 2025, resulting in crash-consistent snapshots even when filesystem consistency indicators appear as true.

Workaround:

Use NetBackupSnapshot Manager (host agent-based or agentless) to create filesystem-consistent snapshots for Windows Server 2025.