Jump to content

streeterg

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by streeterg

  1. BTW any thief with a touch of common sense is not going to connect a stolen device to a network as they will be aware it's going to call home to Google location etc. They'll usually wipe it and sell it with a bare Windows installation in place of your setup. The ESET anti-theft is a limited form of protection against an amateur opportunist as part of a defence-in-depth policy.

    Use full disk encryption (e.g. BitLocker) and strong user passwords on a laptop to protect your data.

    If you don't want to encrypt the entire disk then at least use the Windows encrypting file system (EFS) for sensitive data.

    If your version of Windows (e.g. Home) does not support Bitlocker or EFS then store sensitive data in an encrypted virtual file volume using 3rd party tools such as VeraCrypt for example. You can also upgrade to ESET Smart Security Premium which includes encryption functionality.

  2. 14 minutes ago, hrgajek said:

    After ESET 13.0.24.0 Update i looked at lusermgr.msc and found a funny user named "ydffggrr" (or so).

    But this User was not visible in the normal Windows 10 User-Interface ? 😞

    I did like described above started "my eset.com" --> "Anti Theft Procedure".

    I was asked to install the Phantom user "Alexander".  I did.

    Nothing happened after this. Computer Reboot. Nothing. Computer shut down again and went to sleep.

    This morning restarted the Computer and Alexander is there 🙂

    I entered the "Alexander" User works like usual "Hello, please wait while we install…." , but Harddrive "D" is blocked (no Access). (Windows is on  Drive "C")

    I started lusrmgr.msc again, the funny user "ydffggrr" is gone :-) Alexander is there and in the Windows 10 user interface, too.

    Just for the records:

    Should Alexander be used one time, to Setup the complete account or is this not necessary?

    I think, the Thief would be suspicious, if entering into an account, which never had been started before..

     

     

    As I said above it seems the temporary random user is part of the phantom account creation process.

    You should read the user guide for the product so you understand what the phantom account does and the consequences of logging into it:

    https://help.eset.com/antitheft/en-US/issue_no_fakeuseraccount.html

     

     

  3. 1 hour ago, BrianE said:

    Still no sign of the phantom account appearing on my Windows 10 laptop. I thought that problem had been fixed with the latest release.

    I removed the device on the anti-theft site, removed the old phantom account from Windows manually and then re-ran the anti-theft setup including the optimization step that creates the phantom account. So far it's all behaving correctly.

    Note that phantom account takes a while to appear after you click the "optimize" button on the Anti-Theft web site. It seems to create an account with a random set of characters as the "name" and after a while this is modified to the real name you entered for the account.

    When something gets screwed up in IT due to a bug it's usually best to reset to a known state from what is probably an unknown condition, That's why the stock answer from M$ support is to reinstall windows 😉

  4. Have to agree with the need for a priority patch. My personal laptop moves between two locations on a weekly basis. Anti-theft is one of the significant features of the product which has been rendered inoperable by the v13 upgrade. As a 30+ year veteran professional IT developer (include a period as a licenced IT security evaluator for GCHQ) I find it remarkable that such an obvious defect was missed during testing.

  5. UPDATE: I have received a standard proforma reply to my support ticket on this issue instructing me to completely remove ESET IS in safe mode and re-install. Both PCs are in constant use and I'm not going to do this for now as all other ESET functionality is unaffected and it's not clear whether such a drastic "solution" will address the issue as it seems to be a defect in the software. I await an update to ESET to fix the defect before I attempt to re-initialise the Anti-Theft component.

  6. Marcos  - the Windows "work" account was still present and could be seen under the Computer Management tool on Windows even though the local Internet Security app reported a problem (optimization) and the web site said the phantom account was not present. I deleted it both on the laptop in windows and at the my.eset.com web site. When I ran the command to recreate the phantom account on the web site it said it was successfully created but it did not appear on the laptop under the management app listing. The eset site and the laptop seem to no longer be communicating properly? Nothing has changed apart from the ESET update from v12 to v13

  7. I upgraded my Windows 10 laptop to v13 of ESET Internet Security yesterday. It now repeatedly displays a warning that the anti-theft component is not optimized as the phantom account is missing. The account is present (the default "work") and has been present for several years. I ran the anti-theft web site option to create the account but it made no difference. I manually deleted the "work" account on the laptop and also deleted it from the anti-theft web site, then ran the option to create it again. Although the web site said the account had been created there was no "work" account on the laptop.

    The laptop is fully up to date with all Windows 10 updates including the cumulative updates to v1903 and the .NET framework released this week

    The anti-theft component worked fine with ESET v12

    I've disabled the anti-theft for this device until this issue is resolved.

  8. I have experienced this issue repeatedly since the middle of 2016 with the latest instance today.

     

    It occurs when Windows 10 itself installs a significant update and NOT when ESET Internet Security itself is updated. It causes my laptop to become unusable due to slow responses until the registry delete fix is applied. This is a work-around and not a solution. This problem was reported in August. I am running out of patience with the product and will have to look for alternatives if this issue is not addressed.

     

    Please investigate and correct this issue,

     

    ESET IS 10.0.369.0

    Windows 10 Home

    Version    10.0.14393 Build 14393

     

    Windows 10 updated today. Issue with ESET started occurring immediately after successful Windows update session and reboot. Fixed with Registry key deletion.
     

×
×
  • Create New...