Zen11t 2 Posted December 10, 2020 Share Posted December 10, 2020 (edited) After upgraded to ESET Protect I made Agent upgrade task to 3 test PC (Win 7 32 bit, Win 10 64 bit), task finished with error but Agent upgraded on the machines successfully. trace.log last line show: ReadUpgradeStatus: Upgrade of Agent from version '7.2.1266.0' to '8.0.1238.0' failed. Unexpected updater service Win32ExitCode 0x42b Edited December 10, 2020 by Zen11t Quote Link to post Share on other sites
Administrators Marcos 3,596 Posted December 10, 2020 Administrators Share Posted December 10, 2020 I've seen one such report already. Allegedly upgrading Endpoint to v8 first prevented the error from being reported, however, the person claimed that agent was upgraded despite the error. The issue will be investigated further when more info from users is available. Quote Link to post Share on other sites
Zen11t 2 Posted December 10, 2020 Author Share Posted December 10, 2020 I tested it now with another PC: upgraded Endpoint 7 to v8, reboot and send agent upgrade task. It's show task failed message too, but the new V8 agent installed and working good on the machine. trace.log show the same line. Quote Link to post Share on other sites
GRT 0 Posted December 11, 2020 Share Posted December 11, 2020 After upgrade SMC 7.2.12.78 to Protect 8.0.1238 I made upgrade task from Agent 7.2.1266 to 8.0.12.38. ReadUpgradeStatus: Upgrade of Agent from version '7.2.1266.0' to '8.0.1238.0' failed. Unexpected updater service Win32ExitCode 0x42b Client: Win10, ver: 10.0.18363.1198 (64bit) Server: ESET PROTECT (Server), verze 8.0 (8.0.1238.0) ESET PROTECT (Web Console), verze 8.0 (8.0.170.0) Microsoft Windows Server 2012 R2 Standard (64-bit) Quote Link to post Share on other sites
ESET Support tomasS 3 Posted December 11, 2020 ESET Support Share Posted December 11, 2020 is there any chance to provide "ra-upgrade-agent.log"(It should be located at "C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs") or even better if someone can provide the ESET Log Collector log from the affected machine. Quote Link to post Share on other sites
GRT 0 Posted December 11, 2020 Share Posted December 11, 2020 I suspect... Is there anyone, who configure Software Restriction Policies on user account folders? tomasS: How can I send you Eset log collector? Quote Link to post Share on other sites
Administrators Marcos 3,596 Posted December 11, 2020 Administrators Share Posted December 11, 2020 You can upload the archive generated by ELC here. Only ESET staff has access to attachments. Quote Link to post Share on other sites
GRT 0 Posted December 11, 2020 Share Posted December 11, 2020 ees_logs.zip Quote Link to post Share on other sites
ESET Support tomasS 3 Posted December 11, 2020 ESET Support Share Posted December 11, 2020 thanks for the provided log files, we are going to investigate what is happening there. We will keep you posted... Quote Link to post Share on other sites
ESET Staff MartinK 332 Posted December 11, 2020 ESET Staff Share Posted December 11, 2020 Thanks for logs. As we suspected, upgrade of AGENT itself went fine, but there is some unknown problem with helper service shutdown (service that executed upgrade itself). Unfortunatelly it seems that this service is crashing during shutdown: could you please check directory: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\ on client machine for entries related to UpdaterService.exe? There are references in system logs from client device. Quote Link to post Share on other sites
GRT 0 Posted December 11, 2020 Share Posted December 11, 2020 AppCrash_UpdaterService.e_3f7dba9e679cb17fdebaec64c5ce9b7dfecabb_3076b009_c9e58383-e622-4fb9-8d0c-aef0f75ee25a.zip Quote Link to post Share on other sites
VorteX28 0 Posted December 15, 2020 Share Posted December 15, 2020 The same problem. Packed trace.log and Updaterservice from WER. Around 25% of computers failed with Agent update D.zip Quote Link to post Share on other sites
ESET Staff MartinK 332 Posted December 15, 2020 ESET Staff Share Posted December 15, 2020 Thanks. From provided crash dumps it seems there is some problem with processing "unicode" paths at the final stage, i.e. after AGENT is successfully upgrade. Just for confirmation, but upgrade is performed on Windows operating systems with localized environment, i.e. paths like "Program Files" or "ProgramData" are localized and possibly using non-asci characters? Quote Link to post Share on other sites
VorteX28 0 Posted December 16, 2020 Share Posted December 16, 2020 15 hours ago, MartinK said: Just for confirmation, but upgrade is performed on Windows operating systems with localized environment, i.e. paths like "Program Files" or "ProgramData" are localized and possibly using non-asci characters? They are exactly with names "Program Files" and "ProgramData" without any other non-ascii characters. BTW after reboot Agent shows updated version. So they are actually updated. Aaaaand now 172/173 agents updated. 1 - is a mystical PC that fails everything. Quote Link to post Share on other sites
Zen11t 2 Posted December 17, 2020 Author Share Posted December 17, 2020 For me it's Programfájlok (x86) and ProgramData, but Antivirus is installed to Program Files directory. Quote Link to post Share on other sites
robg 0 Posted December 21, 2020 Share Posted December 21, 2020 On 12/16/2020 at 9:57 AM, VorteX28 said: They are exactly with names "Program Files" and "ProgramData" without any other non-ascii characters. BTW after reboot Agent shows updated version. So they are actually updated. Aaaaand now 172/173 agents updated. 1 - is a mystical PC that fails everything. Had the same setup and error (apart from0x435 at the end) but also cleared on a reboot ReadUpgradeStatus: Upgrade of Agent from version '7.2.1266.0' to '8.0.1238.0' failed. Unexpected updater service Win32ExitCode 0x435 Quote Link to post Share on other sites
Zen11t 2 Posted December 30, 2020 Author Share Posted December 30, 2020 Any news about it? Will be fixed? Quote Link to post Share on other sites
Administrators Marcos 3,596 Posted December 30, 2020 Administrators Share Posted December 30, 2020 So far all users have confirmed that despite the error agent is upgraded to v8. Yours remain at version 7 after getting the error? Quote Link to post Share on other sites
Zen11t 2 Posted January 8 Author Share Posted January 8 Yes, the agent is upgraded to v8, but with a big upgrade (250+ client) I don't want to check every PC it was successfully or not. Quote Link to post Share on other sites
Administrators Marcos 3,596 Posted January 8 Administrators Share Posted January 8 It's UpdaterService.exe from ESMC v7 which is affected. From what I understood, the file from ESET PROTECT is not affected so upgrade to any future version should work alright. Quote Link to post Share on other sites
ESET Staff MartinK 332 Posted January 11 ESET Staff Share Posted January 11 Just to let you know, problem was indeed triggered by localized Windows operating system, i.e. operating systems where certain status messages provided by system itself contained non-ASCII characters. Unfortunately problematic helper tool UpdaterService.exe is part of already installed version 7.2.1266.0 and therefore proper solution was not possible and upgrade from this specific version to any new version will report this kind of failure even when upgrade will be successfully. Also it has been confirmed that upgrade from version 8.0 is not affected, so there should be no such problem with future upgrades. Peter Randziak 1 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.