-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
executable present but hash not seen by Eclipsium #6
Comments
Wondering the same here. My board is on the list but not detected by the script. I already updated my BIOS to version F65. I should have run GigaTest.ps1 before installing the fixed bios version F65 so I could compare the output.
|
Help! Running this script results in a pause and then these errors: \GigaTest.ps1:33 char:60
Unexpected token ':"en"' in expression or statement.
Missing argument in parameter list.
The '<' operator is reserved for future use.
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
The '<' operator is reserved for future use.
Missing file specification after redirection operator.
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
Missing file specification after redirection operator.
Missing file specification after redirection operator.
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double |
@MichaelinoX i don't think your issues is related to what i describe. i think i would be better to open a new issue |
Hi,
i just run the script for windows and i got this output
Does that mean my PC is infected with a modified version of the Gigabyte Assistant executable ?
also it say that my motherboard is not infected but it's on the list of affected models. I have updated my BIOS so maybe it's that but maybe it will be more clear to say if the model is affected but not this mobo ? or that the BIOS is already up to date (i can see the BIOS version in the System Information app)
The text was updated successfully, but these errors were encountered: