Version of the script
sp_BlitzFirst 2025-07-04 00:00:00.0000000 +00:00

What is the current behavior?
When running in a Docker container, sp_BlitzFirst always reports the CPU as maxed out.

If the current behavior is a bug, please provide the steps to reproduce.
Sure. Mind if I use dbatools?

docker pull mcr.microsoft.com/mssql/server:2022-latest

docker run -e "ACCEPT_EULA=Y" `
-e "MSSQL_SA_PASSWORD=TheNewBreakfast!" `
-p 1433:1433 `
--name BrentForce1 --hostname BrentForce1  `
-d mcr.microsoft.com/mssql/server:2022-latest

$password = ConvertTo-SecureString "TheNewBreakfast!" -AsPlainText;
$cred = [PsCredential]::New("sa", $password);
$ins = Connect-DbaInstance -SqlInstance localhost:1433 -SqlCredential $cred -TrustServerCertificate;
# Add -Force if you have an ancient version cached
Install-DbaFirstResponderKit -SqlInstance $ins -Database master
$ins.query('EXEC sp_BlitzFirst') | ? Finding -like '*CPU*' | Format-Table -Wrap    

To tidy up afterwards, docker stop BrentForce1; docker rm BrentForce1;. Delete the image as well if you don't want it.

What is the expected behavior?
Either report CPU accurately or just don't fire this.

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
This might be related. Maybe it worked in 2019? I used 2022 above.