serbiede 0 Posted January 31 Share Posted January 31 I am trying to update several Windows Server 2016 / 2019 / 2022 servers in Spanish, from version 9.0.12013.0 to version 9.0.12017.0. I have tried to do it from ESET Protect Console 10.0, and the task failed. Later I tried to do it manually, but it gave me an error during the installation. Finally, I tried to uninstall the product, to later install the new version, and I get an error when trying to uninstall. Does not allow me. I was looking at several KBs, and really the manual uninstall option (entering Safe Mode) is not an option, since they are production servers. Please if you can give me some suggestions, on how I could fix it. Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted January 31 Administrators Share Posted January 31 Please provide logs collected with ESET Log Collector. If standard uninstallation fails, you can run the ESET Uninstall tool in safe mode. Link to comment Share on other sites More sharing options...
serbiede 0 Posted January 31 Author Share Posted January 31 Logs collected attached. The problem with "run the ESET Uninstall tool in safe mode." that it is not possible, because the Servers are in production. Thanks. Attached file 1 of 2 efsw_logs.zip Link to comment Share on other sites More sharing options...
serbiede 0 Posted January 31 Author Share Posted January 31 Attached file 2 of 2 efsw_logs(1).zip Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted February 1 Administrators Share Posted February 1 No installation log was generated. Please follow the instructions at https://support.eset.com/en/kb406 to generate and install log and provide it for perusal. Link to comment Share on other sites More sharing options...
serbiede 0 Posted February 1 Author Share Posted February 1 The Logs are attached. The file setupapi.app.log was no present in the C:\Windows\INF\ folder. efsw_install_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 4,919 Posted February 1 Administrators Share Posted February 1 Error: Failed to access database: C:\ProgramData\ESET\ESET Security\Installer\fix_norepair.mst Please create also a Procmon log from a failed upgrade. Did you try to reboot the server? A restart will be needed after upgrade anyways. You said you can't boot to safe mode because it's a production server. However, software upgrades should be performed during maintenance windows. Link to comment Share on other sites More sharing options...
serbiede 0 Posted February 1 Author Share Posted February 1 Marcos, file procmon.log attached. I have this same issue in 8 Servers, there are all in production. The server wich I'm working right now to extract the Logs is our Windows Storage Server 2016, that we use for Backup retention. And, yes, I restart the server before posting here. efsw_install_procmon_logs.zip Link to comment Share on other sites More sharing options...
serbiede 0 Posted February 1 Author Share Posted February 1 Here are the Procmon boot Logs. efsw_install_procmon_boot_logs.zip Link to comment Share on other sites More sharing options...
serbiede 0 Posted February 3 Author Share Posted February 3 Any update? It is not critical right now, but... Link to comment Share on other sites More sharing options...
Administrators Solution Marcos 4,919 Posted February 3 Administrators Solution Share Posted February 3 For some reason C:\ProgramData\ESET\ESET Security\Installer\fix_norepair.mst is missing. Please delete HKCR\Installer\Products\6C04EBCFB22F95A4D9FCFB61648B9B1A\Transforms and try again. Link to comment Share on other sites More sharing options...
serbiede 0 Posted February 3 Author Share Posted February 3 Great! Problem solved, thank you very much! Link to comment Share on other sites More sharing options...
Recommended Posts