Google already released a new version, and because they always replace the binary at the download URL with the latest version, the thing we’re downloading now is already higher than 120.0.6099.63 and the hashes don’t match our expected version.
You’ll either need to wait on our next Fixlet publish (and then quickly get the download cached before Google replaces it again), or, if you’re willing to “just install whatever version is available” and not verify the hash, you could use the task I posted at https://bigfix.me/fixlet/details/27003 to download & install whatever version of Chrome is currently hosted.
If you do want to continue verifying hashes on the download (which I’d recommend; my version without the hash verification could be vulnerable to man-in-the-middle attacks that replace the download), then you have to get each given version of Chrome downloads cached before Google replaces them. We discussed one method of doing that at How to handle Google Chrome? where I proved out using the BESDownloadCacher to precache the Chrome installation onto the root server; this could be run through the Task Scheduler to check for Chrome updates several times a day, if needed. That way, whatever version of Chrome fixlet you try to deploy, the download should already be cached on the root server and it won’t matter if Google replaces it with a higher version.