bmp999
-
Posts
11 -
Joined
-
Last visited
Posts posted by bmp999
-
-
We have tested during the day using a manual run and it NEVER fails. Only fails at night.
-
On 8/28/2020 at 12:09 PM, itman said:
In any case, try the following Eset file exclusions instead and see if that resolves the issue:
E:\WindowsImageBackup\EFI\Microsoft\Boot\BCD
E:\WindowsImageBackup\EFI\Microsoft\Boot\BCD.LOG
E:\WindowsImageBackup\EFI\Microsoft\Boot\bootmgfw.efi
E:\WindowsImageBackup\%WINDIR%\system32\winload.efi
There is no such files on E drive. Backup is stored in a special folder where there are huge .vhd files and small .xml files. If you right click WindowsImageBackup, you can enter the folder with the OPEN option.
-
I am away today and the weekend, so will try this next week. However I’m skeptical because there is no actual path E:\EFI... on the E drive. windows 7 backup creates a special folder where files are stored. Opening the folder spawns a program. Also the disk image (which is where the EFI would be backed up, is what’s failing. System image goes into a different file on E:\.
something to ponder and try for sure.
Thx,
Brian
-
You can see by the list vol above that there is no drive letter assigned.
Thanks for your help.
-
And this is the only system that has this problem at the moment. I have Eset Smart Security on my office w10 system with an internal secondary drive and it does not fail on the EFI partition. Runs exactly same time 11pm. Also it never fails when we run a manual backup on the customer system. Its only the at night for the SCHEDULED backup.
We really need the source of the issue addressed, not a work around with scripts and the like. Since this is a customer system, I could be dragged back every time there is a hiccup.
We have established that REGISTRY Hivelist points to HarddiskVolume3 and that is what we have used for every exception. But there are a lot more files in there than just these 3 (listed above). Adding them all one by one is arduous. Need wild card to perhaps SKIP them all and then work our way down.
Only way to see EFI files I have found that works (and only accessible via Powershell not File Explorer) for W10 is to:
Powershell (ADMIN)
mountvol P: /s
dir P: -s or switch to P: then CD down the paths.
mountvol P: /DAttached a full W10 EFI Directory listing.
SO back to the first question, what other files can be locked and how do we see which files ESET has its fingers on when backup runs that cause it to fail? -
OK, any more suggestions why using HarddiskVolume3 is not working in our case?
We have been making backup work by stopping ESET for 4 hrs ever day at 10pm so that backup will run at 11pm. We will STOP this so it fails again. Also we found the location of more detailed backup logs in C:\windows\Logs\WindowsBackup, will post the next failure. It only keeps 5 copies of the logs, so we don't have a failure log until it happens again.
Thx,
Brian
-
Here is more information... had to visit client to get this.
EFI is on HarddiskVolume3 as we have added to the exception list for the BCD, BDC.log and many other files, including the one in the windows folder on C that was suggested.
Thx,
Brian
-
Yes there is a C drive and an additional internal Drive (not bootable - No OS). Will ask client to send me a SNIP of the Disk Management. Its a new Lenovo (6 months old), C should be a Port 0, but not sure. Will post when I get it.
PS: Its Eset version 13.2.15.0
-
In Windows 10 Pro, using Windows 7 backup on Windows 10 to make daily backups - has worked for 6 months, we get the same error as outlined in KB6121
https://support.eset.com/en/kb6121-windows-backup-failing-error-message
However adding these exclusions do not work. I have added all the EFI files in that same folder with no luck. The EFI partition has a lot of files in it, so hoping to get a way to see which file exactly is locked.
To prove it is ESET causing the issue not another program, We have disabled ESET for 4 hours every day for a week 1 hr before backup and backup works every time, but it fails almost every time (1 or 2 rare exceptions) in the past 2 weeks if we leave ESET running (not paused) and Daily Backup runs at 11pm.Ideas anyone?
Thx,
Brian
-
Just installed NOD32 V8 (latest version off the website) on a freshly reloaded HP laptop (windows 8.1 Home, Office 2013 Home and Business, Quicken 2012) yesterday and today the client called and said OUTLOOK crashed and offered the user to enable or disable the ESET Add-on. We tried to Enable and Outlook Crashed again so the only way to make it work is to disable it. This client needs email protection. So 8 months after the last post, the issue is still present. I've been using ESET on all clients systems for 6+ years and it is overall very dependable. It did work for 1 day error free, but then started crashing OUTLOOK today (next day). I did notice that the Outlook .PST file was ~6GB+ in size. I compacted .PST yesterday. And I recommended the user purge many of the 30K+ emails in the sent folder from 2004 to 2013.
Hoping that there is a quick fix for this. Any suggestions?
Backup Failed EFI locked
in ESET Internet Security & ESET Smart Security Premium
Posted
We might have to consider another backup software. Thx for the suggestion. I will try and change the time the backup is done. I'm wondering if its when the computer comes out of sleep that the problem occurs (remember its not every day, but most days at 11pm). Maybe Eset starts a scan when its wakes from sleep.