Thank you, and I apologize for no answering sooner.

It is interesting to know this, because what we are doing is that we use a special technique to "box" (embed) the C++ runtime libraries with out assemblies, so that the user does not have to install them separately. So, this should work behind the scenes, automatically.

This said, we do not actually support the Community edition of the Visual Studio.

So there are basically three possibilities:

a) We have made mistake somewhere, and are not "boxing" the right libraries with the product (I am particularly interested in the "Update 3" in the link you provided, we need to check the proper update number). But we test our product on fresh Windows systems so it is unlikely we would have missed this.

b) We are "boxing" the right libraries, but the process have failed somewhere (for this there are some diagnostics tools possible, but first I need to verify the "a)" above).

c) Everything is as designed, but the problem is limited to the Community edition, and the Community edition does something differently. In this case we probably won't have any solution for it (unless it is extremely easy to resolve).

Regards