Hi folks, new to the forum and to the industry.
Just encountered an issue attempting to install KX drivers on a Galaxy Book running Windows 10. Speaking to my superiors I have heard mixed suggestions: including using "samsung cloudprint" or just using "Universal Drivers"
Wondering if anyone has any experience with a similar situation, and how you came to a resolution?
For more background-- I was able to download and launch the KX executable, and itseemed to work fine, however at the final stage of the installation, the "KX Driver" was marked with a red X. After taking this action I could find the device in the control panel, and test prints came through without a problem, but it was using a generic plug-n-play driver.
I did attempt to uninstall the driver, delete the KX files from the C:\KX, re-download, extract and launch again to no avail. Then attempted to "add printer" from the control panel interface using the IP and pointing it to the "oemsetup" file, and it simply would not take-- said that the directory did not contain the correct drivers (it did).
Just encountered an issue attempting to install KX drivers on a Galaxy Book running Windows 10. Speaking to my superiors I have heard mixed suggestions: including using "samsung cloudprint" or just using "Universal Drivers"
Wondering if anyone has any experience with a similar situation, and how you came to a resolution?
For more background-- I was able to download and launch the KX executable, and itseemed to work fine, however at the final stage of the installation, the "KX Driver" was marked with a red X. After taking this action I could find the device in the control panel, and test prints came through without a problem, but it was using a generic plug-n-play driver.
I did attempt to uninstall the driver, delete the KX files from the C:\KX, re-download, extract and launch again to no avail. Then attempted to "add printer" from the control panel interface using the IP and pointing it to the "oemsetup" file, and it simply would not take-- said that the directory did not contain the correct drivers (it did).
Comment