Scan log thread for malware

[REDACTED]

Here are all the logs the pinned thread adviced to give.

There are some weird things in these logs, lots of system errors and code integrity issues in windows.old folder which is weird because I installed windows10 on fresh ssd. This windows installation is 2 days old.

[DavidR]

Can you also give a brief description of why you feel it necessary to post the logs, e.g. what is going on with your system, constant avast alerts, etc. etc.

It could help the malware removal specialist in their hunt.

[REDACTED]

I used old keyboard from old pc that might have been infected, keyboard model Steelseries 7G.

[Eddy]

No clue at what logs you have looked, but in the ones you have provided there is not a single strange thing to see.

[DavidR]

I used old keyboard from old pc that might have been infected, keyboard model Steelseries 7G.

I like the others highly doubt (like some other respondents in your other topic) that an old keyboard can be infected. First it would have to have a data storage source and some sort of processor to run anything in that data store. If it doesn't have a processor then there would be a requirement for it to be run from your system. It is also most likely that this data storage is volatile, in that it would be cleared when the system is rebooted.

Hopefully as you can see the permutations are massive for a keyboard to be infected and run without attracting AV attention.

I think that your other topic https://forum.avast.com/index.php?topic=193808.0 plus this one should give you some confidence in the unlikelihood you could have an infected keyboard.

[REDACTED]

I used old keyboard from old pc that might have been infected, keyboard model Steelseries 7G.

I like the others highly doubt (like some other respondents in your other topic) that an old keyboard can be infected. First it would have to have a data storage source and some sort of processor to run anything in that data store. If it doesn't have a processor then there would be a requirement for it to be run from your system. It is also most likely that this data storage is volatile, in that it would be cleared when the system is rebooted.

Hopefully as you can see the permutations are massive for a keyboard to be infected and run without attracting AV attention.

I think that your other topic https://forum.avast.com/index.php?topic=193808.0 plus this one should give you some confidence in the unlikelihood you could have an infected keyboard.

Well, it does have micro prosessors, two atleast if not 3.

[REDACTED]

No clue at what logs you have looked, but in the ones you have provided there is not a single strange thing to see.

lots of application errors, system errors, codeIntegrity issues

especially:
 Date: 2016-12-01 13:30:33.095
  Description: Windows is unable to verify the image integrity of the file \Device\HarddiskVolume4\Windows.old\Windows\WinSxS\x86_microsoft-windows-utilman_31bf3856ad364e35_10.0.10586.0_none_3310acc4233710cd\Utilman.exe because file hash could not be found on the system. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.

[Eddy]

That is not a strange thing.

Please stop trying to understand something while you do not even have the basic knowledge on how things are working.
Just use and enjoy your new system.

[Pondus]

Suspicious file(s) can be uploaded and tested here  virustotal.com / metadefender.com / jotti.org
If scanned before, always click rescan for a fresh result
Use the additional tabs for finding additional file info after scan

[DavidR]

I used old keyboard from old pc that might have been infected, keyboard model Steelseries 7G.

I like the others highly doubt (like some other respondents in your other topic) that an old keyboard can be infected. First it would have to have a data storage source and some sort of processor to run anything in that data store. If it doesn't have a processor then there would be a requirement for it to be run from your system. It is also most likely that this data storage is volatile, in that it would be cleared when the system is rebooted.

Hopefully as you can see the permutations are massive for a keyboard to be infected and run without attracting AV attention.

I think that your other topic https://forum.avast.com/index.php?topic=193808.0 plus this one should give you some confidence in the unlikelihood you could have an infected keyboard.

Well, it does have micro prosessors, two at least if not 3.

As I mentioned in your other topic:
I would suggest that you visit the Steelseries forum and see if there is anything there or ask about the possibility. Steelseries keyboards and mice are very popular, especially with gamers and if this happened or could possibly happen, they really should know about it or have come across it before.

They must know if these micro processors could possible run any malware if it were to be in your data storage (buffer) and if that data buffer is cleared on reboot.

[REDACTED]

What about aswMBR.txt, that hasnt been checked yet

[Eddy]

There is no need for it.
Stop worrying, start using the new system.

[dbrisendine]

Your logs look very clean.  What is your issue?  What are you seeing that makes you believe your system is infected?

You have scanned the system with many high level AV / AM tools; what have they found?

Have you considered loading MCShield on the system?  http://www.mcshield.net/

[REDACTED]

If the system is clean, then what are those errors? Especially those flawed signatures on files, also why do I have windows.old if I have new pc?

[Eddy]

You can Google to see what the errors mean, but if I where you I wouldn't do it as they are nothing special and you have a severe lack of knowledge to even start understanding what they mean.

New system doesn't mean Windows 10 is installed by default.
Often Windows 8 (or even 7) is and they just have upgraded the OS to Windows 10.
That is why there is a Windows.old folder