Surely you could just wipe the embedded install, and install a full version of windows?
I'd guess that if it's capable of running windows embedded, it'll run the full version provided you're sensible about what options you install, and use a reasonably specced unit. A basic Win10 install doesn't need that much space, and performs well even low power machines.


Kit, provided you're using an external motion control, timing issues in windows are very unlikely to be a problem. As soon as you use an external motion controller, all motion is buffered, so provided the computer is capable of keeping the buffer topped up, it's not a problem. Those who do experience problems are normally pushing things to the limit, like a computer that meets the absolute bare minimum of specs, or using the same computer to do something processor intensive. There is also the potential issue of windows updates if you leave the computer connected to the outside world (I'd actually suggest win 10 pro, as it gives you much better control over updates if you do plan to have the computer online)

It's also worth mentioning that even in generic LinuxCNC there is a motion buffer, much to the chagrin of the zealots who brandish the whole 'real time' nugget without actually understanding what it means, or how it applies to the whole control process. Every CNC has buffers, it's just that some implementations are not exactly that robust or reactive (Mach3 with an external motion controller is probably one of the worst examples!).