This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
You can use one of following ways to work around this issue:
- Disable Query store feature before applying the cumulative update and failover.
- Enable Trace Flag (TF) 9109 to skip startup sweep.