OsInfo.dll is not part of .NET framework, so the cause is not in it. I also think that the bad is somewhere else, most probably the OsInfo.dll rely on other component, which is not installed, or corrupted. What about try to use Dependency Walker (depends.exe) to check out what does the OsInfo.dll require?

Also, there may be a bug in class constructor, e.g. attempt to write to forbiden path. Such a kind of errors is hard to recognize, because they are "consumed" by class loader and are propagated strange.