Microsoft Test Manager error in displaying test steps caused by malware

Microsoft Test Manager error in displaying test steps caused by malware

Sometimes the tool is blamed for errors which are not the fault of the tool – this is one such story.  It was however, not so easy to get to the bottom of it, so I hope sharing this story can help some others.

One of our test developers started to get this message inside the test steps part of a test case in the MTM.

image

saying “Could not load file or assembly ‘0 bytes from System, Version=4.0.0.0,……..”

The same error came up inside Visual Studio when we opened a test case there.

Then we noted a similar error on another piece of software – this error:

image

A System.BadImageFormatException, and same message as above, but just for framework 2.0.

We found this  description which pointed to a malware problem (See bottom of that post), that is a fake anti-spyware program called “Additional Guard”.  We checked the computer in question using Malwarebytes Anti-Malware tool.  It found and cleaned out 753 registry keys!!  After this cleanup operation the error was gone.  This is a great tool ! 

The “Additional Guard” program had been inadvertently installed, and then uninstalled afterwards, but the corrupted keys were of course not removed. 

We also noted that this computer had full corporate virus scanning and malware protection, but still this nasty little thing still slipped through.

This article is part of the GWB Archives. Original Author: terje

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.