Disabling Smart App Control
Procedure for blockages of RetailVista POS components by Windows Security
Background
Windows Security blocks a component of RetailVista POS because Smart App Control cannot verify the publisher of a loaded file. This can, for example, be the NedFox.RetailVistaPos.UI.Touch task, which tries to load NedFox.EFT.dll:
"Part of this app is blocked. Some features of NedFox.RetailVistaPos.UI.Touch may not work because we can't verify who published NedFox.EFT.dll that the app tried to load."
This type of notification typically occurs right after an update of the POS software, at the point when Windows does not yet recognize the new file (or its new version/signature) as trusted.
Disabling Smart App Control
Via the Start menu
- Open Smart App Control via the Start menu (Start > search for "Smart")
- Open Smart App Control
- Set the toggle to "Off"
- Confirm the UAC prompt if it appears (administrator rights required)
Via the Settings app
- Settings > Privacy & security > Windows Security > App & browser control
- Under "Smart App Control settings," set it to "Off"
Note
Smart App Control has three states: Off, Evaluation, and On. Once it is fully set to "On" outside the evaluation period, some versions of Windows no longer offer a toggle to turn it off again through Settings; the only way back is then a clean installation of Windows. If the "Off" option is greyed out or missing, this indicates that situation. Don't rule this out before scheduling an update that depends on this procedure. After disabling it, a restart may be needed before the change fully takes effect.
Procedure around RetailVista updates
Follow the steps below to let an update proceed without a blockage:
- Turn off Smart App Control
- Start RetailVista POS
- Let the application update
- Turn Smart App Control back on
- The application starts normally again and remains usable
Additional notes
With Smart App Control disabled, RetailVista POS can be started again and the update can be allowed to complete. As long as Smart App Control is off, Windows no longer checks newly loaded files for publisher identity, allowing NedFox.EFT.dll and similar components to load normally. Once the update is finished, Smart App Control can be re-enabled via the same route. RetailVista POS remains usable in practice, since the updated files have by then already been loaded as known.
At the time of writing this guide, work is also underway on a permanent solution so that the steps above will no longer be necessary.