SQL Backup fails with errors 790, 3013 and 3271 after SQL Server security update KB5128493.
Applies to
SQL Backup 10.1.34.3119 and earlier
SQL Server 2019, 2022 and 2025
Summary
Microsoft released a security update for SQL Server on 13 October 2026. It includes two security fixes for the SQL Server Virtual Device Interface (VDI). After installing it, SQL Backup 10.1.34.3119 and earlier can’t back up or restore databases.
The VDI changes in KB5128493 are incompatible with SQL Backup 10.1.34.3119 and earlier.
Microsoft’s release notes are here: KB5128493 for SQL Server 2022
Symptoms
SQL Backup creates a VDI whenever it backs up or restores a database. With KB5128493 installed, the Windows host of the SQL Server instance returns operating system errors 13 and 955, and the operation fails.
You may see:
- SQL Backup exit code 790: A nonrecoverable I/O error occurred on file “[GUID of the VDI]:” 13 (The data is invalid.)
- SQL Server error 3013: a generic error showing the backup or restore is ending abnormally
- SQL Server error 3271: an error raised when the operating system reports a problem
Status
We’re investigating a fix as a priority and will update this article when one is available. Until a fix is released, either reverse/remove the KB5128493 SQL Server security update. Or if the update cannot be reversed, use native SQL Server backup and restore for your backup and restore operations.
Was this article helpful?
Articles in this section
- SQL Backup errors 790, 3013 and 3271 after installing KB5128493
- Resolving Error 507 and SQL Error 18456 in PCC Backup Restores
- SQL Backup error 605
- SQL Backup Error: Cannot access resource
- SQL Error 3203
- Error - Cannot load the DLL xp_sqlbackup.dll, or one of the DLLs it references
- Failed to obtain the list of cluster nodes
- Log Copy Queue is stuck in SQL Backup
- SQL Backup Network Share Permissions Test
- SQL Backup troubleshooting
Add comment
Please sign in to leave a comment.