Mine keeps saying:

FAILED in STEP 13 (Line 21)

And then my 3 custom fields are saying "Audit Required" and "Audit Pending" for the details one.

There is a possibility that you may need to make #meltdownscores# global.  I've seen some issues where local variables are not behaving as expected depending on the build of VSA you're on.

I don't know what that means or how to make it global. I'm on kaseya's hosted cloud VSA.

To make a variable global it needs to be changed: edit the procedure and change "meltdownscores" to "global:meltdownscores" and #meltdownscores# to #global:meltdownscores#

Also make sure that you are launching the procedure as a master admin.

Thanks for your help, but it's still saying "Script Summary: Failed THEN in step 13 (Line 21)". I wish I could be more descriptive, but that's all the error says. Do you have any other suggestions? I'm a top level admin in our cloud VSA.

Following along with the script, I have these in my agent temp directory:

SpeculationControl.zip
SpeculationControl folder and its files
meltdowncheck-working.ps1
meltdown.txt

Looks like I'm missing meltdown-scores.txt file.

And I also don't have meltdown-KVA.txt or meltdown-BTI.txt in the agent temp directory either.

I tried changing the meltdowncheck-working.ps1 file to reflect to same type of write file as the MDFile varible was using, but it didn't work. Got any ideas?

Am I the only person having problems with this?

It would appear that there is a problem in the extraction process that is used to expand the contents of the zip file for use