Windows Defender May Cause Elliott Start-Up Difficulties
It has come to our attention that Windows Defender may conflict with Elliott. Even though we can't duplicate this in-house, in a few Elliott installations with Windows Defender, users experience strange behavior during Elliott start-up, such as the following:
Normally, this configuration window only pops up automatically when you use Elliott for the first time and the system needs some basic information in order to run Elliott. We know that this clearly is not the case for our users who are reporting the Elliott start-up issue. The start-up screen problem may happen to both Elliott V7 and V8 users. Users typically can just click "OK" or "Cancel" to continue.
(1) Elliott Configuration Screen Appears
When starting up Elliott, the Elliott configuration screen appears automatically. See sample screen below.
Normally, this configuration window only pops up automatically when you use Elliott for the first time and the system needs some basic information in order to run Elliott. We know that this clearly is not the case for our users who are reporting the Elliott start-up issue. The start-up screen problem may happen to both Elliott V7 and V8 users. Users typically can just click "OK" or "Cancel" to continue.
(2) Exceed User License Count
The second symptom occurs when users receive exceeding user license count messages like the following: "Licensed Number of Concurrent Users (...) Has Been Exceeded. Pls. Contact NETCELLENT Inc. Or Your Authorized Dealer To License Additional Users." See sample screen below:
Users may receive this message even though there are no other users in Elliott, or very few users in Elliott. This message applies to V7 only. If the same user uses Elliott V8 to start up, then he/she will not receive this message. When this message shows up for Elliott V7 users, those users can't proceed any further.
Stop Windows Defender
To determine whether Windows Defender is the cause of your Elliott start-up problem, please start up your Window Services and find out if you have "Windows Defender" installed. If you do and it is "started," then right click on "Windows Defender" and choose "Stop." Test Elliott to see if the start-up problem goes away.
If you have proven that "Windows Defender" is the cause of the Elliott start-up problem, then you should go to Windows Services, right click on "Windows Defender," and choose "Properties." Change the start-up type to "Disabled" so Windows Defender will not run in the future.
Since we can't duplicate this Elliott start-up problem in-house with Windows Defender, it is quite possible that you may be able to run Windows Defender without any issue. However, most of the support incidents we have identified so far with this Elliott start-up problem are related to Windows Defender. Disabling the Windows Defender fixes the problem. In many cases, these users are running on virtualized Windows 7 machines. However, we can't say the virtualized Windows 7 + Windows Defender combination will cause the Elliott start-up problem since we tested that scenario in-house without problems.
If your organization requires anti-virus software on each workstation, you can run other anti-virus software. As far as we are aware, we have not found any commercially available anti-virus software that is incompatible with Elliott. Windows defender is a free anti-virus software from Microsoft. It comes with a service pack update automatically.
In most cases, if you run another anti-virus software, Windows Defender will be disabled automatically. However, we have also seen situations where another anti-virus software is running side-by-side with Windows Defender. Don't assume Windows Defender is not running because you have another anti-virus software installed. Check your Windows Services to see if it is running when you are having Elliott start-up problems as described in this Knowledge Base.
Related Articles
Does Elliott Support Windows 10?
Q - Does Elliott support Windows 10? A - With the latest Elliott version, we do support Windows OS 10. We suggest that you first update to the latest relevant Elliott version. There are a few issues you should pay attention to when upgrading to ...IPV6 May Cause Problem for PSQL 11 Relational Query
Release Date: 01/20/19 IPV6 (Internet Protocol Version 6) is designed to eventually replace IPV4. IPV4 has an IP address like 192.168.1.1. Each segment can have a value from 0 - 255, so the theoretical maximum number of IPV4 addresses is a little ...Your File System May Lack 8.3 Filename Support
Release Date: 4/3/2019 Revised: 09/23/2023 Version: 8.x & up Q - We get this error on a random basis. Elliott SM Error from P2LVEFCT Unable to create temp file: C:\Users\202-CAP\AppData\Local\Temp\8\P2LVEFCT.501 You file system may lack 8.3 filename ...How the Windows Scheme You Choose May Affect the Elliott Screen Display
Q - In some areas of Elliott, the message that displays on the bottom line is often unreadable because of the window placement. See example below. How can we see the message? A - This is often due to the Windows scheme you choose. For example, if ...I Receive Error 114 When I Start Up Elliott on the Server
Q: I receive error 114 (shown in the window below) when I start up Elliott on the server. How do I resolve this problem? A: Most likely your system is impacted by DEP (Data Execution Prevention) if you start Elliott and immediately see the above ...