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
To resolve this problem update to SQL Backup V10.2.0.3898
Execute the SQLBackup_10.2.0.3898.exe and run it on the machine where your SQL Back Pro GUI is installed. This action will update the SQL Backup GUI only. On reopening the GUI, you will be informed that that the SQL Backup Server Components need to be installed.
To install the SQL Backup Server components. Right click the registred server and select the option to install or upgrade components.
If this fails, install the SQL Backup Server Components manually.
Locate a file called SQBServerSetup.exe which will be located in the GUI installation folder, which by default will C:\Program files (x86)\Red Gate\SQL Backup 10\.
Locate the SQBServerSetup.exe copy it to the server hosting your SQL Instance and run it.
Follow the on-screen instructions.
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
Thank you for the article. Standing by for a fix. I'm affected :(
Got the same issue on SQL 2019 across 4 environments, so waiting for a fix with bated breath.
Also waiting on the fix for two of our SQL 2022 servers. Thanks.
FYI, the common suggestion of restarting the SQL Server instance service and Redgate SQL Backup Agent following the MS Security Update does not help.
Confirming the fix is working, all my databases backing up again, thanks!
Also, encountered same issue on SQL 2019 after applying Microsoft SQL Server 2019 update KB5128494. Can you please update this article to state that V10.2.0.3893 also fixes the same issue in Red Gate SQL Backup on SQL 2019, if the SQL Server instance has Microsoft SQL Server 2019 security update KB5128494 applied?
I was getting the errors but the backup file was being created, anyhow can confirm the fix works
Need HELP with Red Gate (RG) SQL Backup GUI not working now.
Upgrading server to V.10.2.0.3893 on the SQL Server appears to be fine. But when I updated the RG SQL Backup GUI on my machine to V.10.2.0.3893, now the RG SQL Backup GUI is NOT able to connect to any of the SQL Server instances in the GUI.
However, when I use the previous version [V.10.1.34.3119] of RG SQL Backup GUI on a different machine, and it connects to all of the SQL Server instances fine: the 2 SQL Servers with RG SQL Backup V.10.2.0.3893 and the other 2 SQL Servers with previous version [V.10.1.34.3119] of RG SQL Backup.
***Disregard: Red Gate just came out with a new minor upgrade [V.10.2.0.3898] to address this issue. Applied the new upgrade, and the GUI is able to connect to all the SQL Server instances now.