Reports

Whitelisted phrase (-1): Hope this helps
Long answer (-0.5):
Has code block (-0.5):
Me too answer (2.5): Seeing the same issue
Low reputation (1):

Seeing the same issue as user1967479, We are able to repeat this behaviour on dbatools v2.1.30 with sql server 2022. Separating to bak and trn restore has resolved the issue.

We used the below code to restore the bak and trn files leaving the db in norecovery ready for adding to an availability group. Hope this helps someone else.

# Full backup first
Restore-DbaDatabase -SqlInstance "$TargetServerInstance" `
    -Path (Get-ChildItem "$TargetCopyFolder\$($RefreshDatabase.name)\*.bak" | Sort-Object LastWriteTime).FullName -DatabaseName "$($RefreshDatabase.name)" -WithReplace -NoRecovery -ErrorAction Stop
# Apply transaction logs
Restore-DbaDatabase -SqlInstance "$TargetServerInstance" -Path (Get-ChildItem "$TargetCopyFolder\$($RefreshDatabase.name)\*.trn" | Sort-Object LastWriteTime).FullName -DatabaseName "$($RefreshDatabase.name)" -Recovery -ErrorAction Stop

79740573