09-12-2019 12:00 PM - edited 09-12-2019 12:01 PM
The e: drive is where all my projects, source code, and sequences are.
I found versions of api-ms-win-core dlls in:
c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
and in
c:\Windows\system32\downlevel\
But they are not the versions I need. These are older versions. The Microsoft forum indicates that these DLLs are placeholders and redirect to the real DLLs for the OS. Don't obtain these DLLs from elsewhere, which would be violating the EUA.
However, I had just rebuilt all my code using CVI 2017 on this PC with an NI Windows 10 load. How can it not work?
I am currently downloading CVI 2019. I just looked up and I saw it was installing Windows 8.1 and 10 SDKs. So hopefully it will work when that is installed and I rebuild again.
10-11-2019 02:05 AM
Has anyone found a solution for this issue yet?
My problem is that on my windows 10 development system i installed 2014 SP1 and CVI 2015 i created a CVI DLL which uses the windows SDK but only for using Serial Comms and to find serial comms, and on the development system it work as expected. I then created a deployment of teststand 2014 sp1 with all the runtimes to deploy on different windows 10 PC but when i try to run the sequence i get the following error
On the deployment system i do see the files in c:\Windows\system32\downlevel\ and c:\Windows\sysWow64\downlevel\ but i still get this error.
Can any one please tell why this is happening?
or how i can solve this?
10-14-2019 11:32 AM
Hi Shako,
Have you tried this?
01-02-2020 05:47 AM