ReadyAPI takes 450 seconds to start under Applocker
My company has implemented AppLocker. This means no files can be executed from the user profile, ie. from %APPDATA%.
%OSDRIVE%\USERS\<user>\APPDATA\LOCAL\JXBROWSER\7.1\BROWSERCORE64.EXE was prevented from running.
Starting from ReadyAPI v3.2.0 it takes the program 450 seconds to start up, during which I can only see a white screen. Then another 450 seconds of freezing after start-up if I hit the "wrong" element, eg. if I click 'Endpoint Explorer'.
After start-up the dashboard reads: Browser component disabled.
The issue persists in the latest version 3.3.2.
I can live w/o the browser, but waiting 450 seconds every time I start ReadyAPI is not good.
Can the browsercore sub-process be noved or started from another location (eg. under program files)?
Or can the browser component be disabled alltogether?