Im not sure does developers understand the problem, in this case windows platforms, but here it goes…
I had experience with some rendering engines (vray, arnold, mr, etc), so the general problem is in windows, some smart guy made a stupid solution for cpus above 64 threads, and it looks like this:
if you have cpus with more than 64 threads, windows will make 2 cpu groups, so 1st group is group0 and it will have max 64threads and group1 the rest of it. Unfortunately only solution is developers to rebuild the application so it could read not only cpu group0 but to read all cpu groups… If you check the processes of some application under affinity
you should see something like this, i guess it might take some time for your cpus, my friend, thats why i took e5-2683 v4 = 64 threads in total 
btw, in linux there are no cpu groups, so linux doesnt have this kind of problem
cheers