Most likely your VI Support/systempower2.vi contains a Call Library Node which calls this function.
MSDN doesn't say that this function would be missing in a Windows 10 Home installation but that seems to be the case here. You could change this Call Library Node to specify the kernel32.dll name on the diagram instead so it will not be required for loading the application and then handle the error returned by the Call Library Node as it can't find the function.
Rolf Kalbermatter
My Blog 
DEMO, Electronic and Mechanical Support department, room 36.LB00.390