If you haven't yet, take a look at the How Do I Troubleshoot Precision X1 Issues? post by EVGATech_AdamB for some good information there.

Try Revo Uninstaller (Free) in Advanced Mode to remove leftover folders, files and registry entries after Precision's uninstaller runs..Then restart your PC..Then delete the EVGA_Co.,_Ltd folder in the (hidden) AppData\Local folder and install 0.3.17 again, or see if 0.3.16 works better.
 
Be sure to only checkmark to delete registry items shown in bold text in Revo.
 
Win10 Pro seems to have the most problems running Precision, don't know exactly why..Maybe the .cfg files or PX18.exe permissions need elevated for the user (right-click -> Properties -> Security)..Security is pretty tight in that version.
 
When I enable Start with OS, Precision gets put in Task Scheduler..Maybe Conditions or Permissions need changed or elevated there.
 
Could try a putting PX18 (in Program Files\EVGA\Precision X1) shortcut in the shell:startup or shell:common startup folder.
 
I don't know what else to tell you right now, just throwing darts, but I hope that helps in some way.

Cool GTX
Make sure MS Windows .NET Framework is up to date 
 
Microsoft .NET Framework 4.7.2 offline installer for Windows

Yep, good add..Although that should have been part of a Windows Update (was for me), we know that Windows doesn't always do the things it should do 
 

luidiva
After "updating" (removing and installing) 0.3.16 to 0.3.17 when select to start with OS (windows 10 pro) and pressing Apply button Precision X1 just crashes. Even when I set manually to start with windows via Task Manager the software does not start.
Already removed all folders (program files and user appdata) after uninstalling and reinstalling as administrator but no luck.

 
Also, if you can't get it fixed, there may be some clue in Event Viewer as to what might be causing it..If there's a bunch of clutter in it, you can clean it up using a .bat file or other methods described here so it's like new again.

(Thanks, Sajin)
 
 

luidiva
 
Installing version .16 fixed the problem. There's something in .17.
 

 
Thank You for the Update - glad to see .16 is working for you