Hmm.. That is interesting. It seems that there is a problem with the System.IO library. I've uploaded it here:https://1drv.ms/u/s!AtgYyPhhrKrMnKouasc3qSMPGyO2NAAs you are running Dynamo for Revit, please copy/paste the following line into the address bar of the Windows explorer (not internet explorer, the file manager)

A common issue is that libraries sometimes may get blocked when they are downloaded from the web.You could try to go to %AppData%\Dynamo\Dynamo Revit\1.3\packages\KUKAprcDynamo\bin and right-click each of the DLL files. Choose Properties and then if there is a button called "Unblock" click it and confirm with OK. I would see this as a likely reason for the total disappearance of KUKA|prc after you copied the extra libraries that it were missing before.

How have you guys been finding KUKAprc for Dynamo? My pc is up there in terms of power, but when working on a simple milling/drawing tutorial I quickly lost my patience with how long it took Dynamo/Revit to compute simple changes. The same actions in GH would have taken milliseconds.. ?

It is quite a lot slower on Dynamo because the Dynamo 3D engine is rather basic (WPF / Helix). That being said it did not feel super slow to me, unless you import a huge NC file. Can you give me some performance numbers (e.g. how long a solution takes) for me to compare with?

However I have been working on bringing PRC for Grasshopper and Dynamo on a common codebase over the holidays, so that they use exactly the same libraries and thus implement new features and robots in parallel- until now it was basically a branch. It also improved the speed and added several new features, and it will make support for new platforms like Grasshopper 2 a matter of hours.I don't know how quickly it will be possible to push out the new release for both GH and Dynamo - probably there will be an early beta in 2-3 weeks.We also saw some people having issues with Dynamo complaining about missing libraries. We haven't quite figured out the exact reason why it works on most Win7/8/10 PCs but not all of them, but the new versions seems to have reduced - and ideally solved, but we'll only know this after more external feedback - these issues.