BeyondDimension/SteamTools · error · FileNotFoundException

${filePath}

Error message

${filePath}

What it means

Error "${filePath}" thrown in BeyondDimension/SteamTools.

Source

Thrown at src/BD.WTTS.Client.Tools.Publish/PowerShell/System.Management.Automation/security/SecuritySupport.cs:598

        //        else
        //        {
        //            throw new System.ComponentModel.Win32Exception(lastError);
        //        }
        //    }

        //    return status;
        //}

        /// <summary>
        /// Throw if file does not exist.
        /// </summary>
        /// <param name="filePath">Path to file.</param>
        /// <returns>Does not return a value.</returns>
        internal static void CheckIfFileExists(string filePath)
        {
            if (!File.Exists(filePath))
            {
                throw new FileNotFoundException(filePath);
            }
        }

        /// <summary>
        /// Check to see if the specified cert is suitable to be
        /// used as a code signing cert.
        /// </summary>
        /// <param name="c">Certificate object.</param>
        /// <returns>True on success, false otherwise.</returns>
        internal static bool CertIsGoodForSigning(X509Certificate2 c)
        {
            if (!c.HasPrivateKey)
            {
                return false;
            }

            return CertHasOid(c, CertificateFilterInfo.CodeSigningOid);
        }

View on GitHub (pinned to c16ffa08e0)

Solutions

1. Verify the file path passed to the signing operation exists on disk.
2. Fix typos or wrong directory segments in the filePath argument.
3. If the file is produced by a previous build step, ensure that step completed successfully before signing.

Example fix

Check the reported path, generate or locate the file (e.g. rerun the build that outputs it), then rerun the signing command.

When it happens

Trigger: Thrown when a file required by a PowerShell security-support operation (e.g. reading or validating a certificate/script file) does not exist at the supplied path.

Common situations: The file path is wrong, the file was moved or deleted, or a relative path resolved against an unexpected working directory. Verify the path exists and is absolute, or correct the working directory before invoking the operation.

AI-assisted analysis of BeyondDimension/SteamTools@c16ffa08e0 (2026-08-13). Data as JSON: /api/errors/d192706412fcd478. Report an issue: GitHub.