Still if anyone has any idea what could go wrong in 1709, please let me know. Therefore, variable names, attributes names, variable values, and attribute values must have 7-bit ASCII encoding. I took the 1703 build and this one seems to work fine. Also, CDF files do not support non-ASCII encoded inputs. Why does this not work on windows 10, anyone else tried installing this on windows 10?Įdit2: It seems to be an issue in the latest Windows 10 release, 1709 build 16299.19. On Windows 8 it seems to install CDF without any issues. Thanks in advance for any help and information!Įdit: We do not use Windows 8 any more, but I installed a VM with it anyway just to try the same thing there. I checked the location, the file is there, and permissions are on full access for the logged in administrator account I use. I tried starting the service manually, it says the file cannot be found. I have tried googling the error and related issues, but have not found a working solution yet. The installation process stops when it cannot start the service. However when I want to run the Target Device Installation on this machine, it requires me to install 'CDF 64-bit'. I am building a lab environment in an attempt to show the potential of Xendesktop and Provisioning services (to replace the current unmanaged Virtual Desktops) to my manager.Įverything is set up and I have a clean install of Windows 10 to capture.

Cdf files not loading