Unable to unstall CU22 on SQL 2019

[vitalic023]

He there,
When installing CU22(KB5027702) using dbatools, I get the warning:
[Get-SqlInstanceUpdate] 15.0.4312 on computer [computername] is already the
latest available.
The 15.0.4312 is CU20(kb5024276), its current installed version and its not the latest, obviously.
Code used:
$splatUpdateInst = @{
ComputerName = "computername"
Path = 'C:\temp\SQLServer2019-KB5027702-x64.exe'
}
Update-DbaInstance @splatUpdateInst

Any help suggestion will be greatly appreciated.

VJ

[niphlod]

hi @vitalic023 , do you have an updated index ? run Update-DbaBuildReference , then retry the Update-DbaInstance.

long story: every dbatools ships with a file which has the sql server builds AT THE TIME that dbatools release is shipped. Via Update-DbaBuildReference that file is fetched from internet with the sql server builds AT THE TIME that you run the command.
Update-DbaInstance reason on the "applyability" of a CU on the same reference info, so, if it's not updated, it doesn't know there is, in fact, a newer CU to install.

[vitalic023]

Thanks Simone, that fixed it 😊 Kindest regards, Vitali From: Simone Bizzotto ***@***.***> Sent: Tuesday, October 10, 2023 5:06 PM To: dataplat/dbatools ***@***.***> Cc: Vitali Jokst ***@***.***>; Mention ***@***.***> Subject: Re: [dataplat/dbatools] Unable to unstall CU22 on SQL 2019 (Discussion #9123) hi @vitalic023 , do you have an updated index ? run Update-DbaBuildReference , then retry the Update-DbaInstance. long story: every dbatools ships with a file which has the sql server builds AT THE TIME that dbatools release is shipped. Via ZjQcmQRYFpfptBannerStart This Message Is From an External Sender If in doubt, throw it out. Report Suspicious <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/KtHZpw!IZDOnfruw84dXQYOdqqOrEGgY_ZOryOFcw0Cr_yICBPv-hYgAyjjQqEDDFktzLXo30HLCutDHyaOSpMMvPNLoFyUOuv9On-pPeu7MWRQ39yQ234AP2ba3RE1b1v9oSF5OH-a4hE$> ‌ ZjQcmQRYFpfptBannerEnd hi @vitalic023<https://urldefense.com/v3/__https:/github.com/vitalic023__;!!KtHZpw!AL7p4yE-gRk1PpEqKIfP91w8erDO6rGX5uJCWqYBTyNkqhagY7h7HTY6kMcI71cs9t7SIsflS7poPIoaQh0bZUv8pbYKNwPVdQ$> , do you have an updated index ? run Update-DbaBuildReference , then retry the Update-DbaInstance. long story: every dbatools ships with a file which has the sql server builds AT THE TIME that dbatools release is shipped. Via Update-DbaBuildReference that file is fetched from internet with the sql server builds AT THE TIME that you run the command. Update-DbaInstance reason on the "applyability" of a CU on the same reference info, so, if it's not updated, it doesn't know there is, in fact, a newer CU to install. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/dataplat/dbatools/discussions/9123*discussioncomment-7242985__;Iw!!KtHZpw!AL7p4yE-gRk1PpEqKIfP91w8erDO6rGX5uJCWqYBTyNkqhagY7h7HTY6kMcI71cs9t7SIsflS7poPIoaQh0bZUv8pbbr3_cAHg$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BDFPRTNBGAOUZMBMVHUCMX3X6VW7JAVCNFSM6AAAAAA52OHFKKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TENBSHE4DK__;!!KtHZpw!AL7p4yE-gRk1PpEqKIfP91w8erDO6rGX5uJCWqYBTyNkqhagY7h7HTY6kMcI71cs9t7SIsflS7poPIoaQh0bZUv8pbbFbhZYzg$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>