Recent upgrade to 9.2.12.4 Not using correct Oracle home

Installed Oracle 19c on server and it is listed first in %path%.
Have to remove older Oracle 12.1 home from server due to vulnerabilities.
When i rename old ORACLE_HOME\product\12.1 to "z_12.1", all the scheduled jobs queue up unable to run.
Soon as i rename folder back to "12.1" the jobs startup and complete.

Is the Oracle driver being used in a config file or in Win OS registry?
Update 0833....
Searched Registy for ETL-Tools, and Visual Importer, nothing found.

 

0851, Not fixed.
Soon as i rename WinOS \oracle_home\12.1 folder to \oracle_home\z_12.1, jobs started queuing up and not running.
Somewhere VI scheduler is setup to use old Oracle home, not newest Oracle home in Win %path%.
Manual run of jobs complete, no issue, so seems to be Scheduler issue... 

 

0847, Believe found solution.
Had to rename 12.1 reg key first to force VI to use 19.2 Ora home.
Added "z_" to old 12.1 regkey. HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\z_KEY_OraClient12Home1.
Jobs stopped queuing up and now run.
 

Any further thoughts on where previous install of Visual Importer would be storing old Oracle home?
Would it take hiding old Oracle 12 home from registry, and windows, and Path and then reinstalling Visual Importer?