jems 4 Posted September 1, 2015 Posted September 1, 2015 Just been looking at my scan logs. At the bottom of the scan results it says "[4] Object cannot be opened. It may be in use by another application or operating system." Than, he message "erroe opening{4} is after each item scanned. any help / info would be appreciated.
jems 4 Posted September 1, 2015 Author Posted September 1, 2015 i went to the eset knowledge base - it said files marked in blue (like my scan logs are) indicates MS files, or password protected files. My question - why is the number - 4 at the end of each blue lined error opening in the log? Thanks.
jems 4 Posted September 1, 2015 Author Posted September 1, 2015 Yeah - i liiked at that help above. I went and asked the scan to log everything scanned - at the log of this scan, the lights started turning on. am a bit of a hands on learner, so appreciate people like you. I like your quotes on your posts. I would rebuttle God helps those who help themselves. - with Romans Ch. 5, verse 6.
TomFace 539 Posted September 1, 2015 Posted September 1, 2015 (edited) Why 4 files ? don't know-I have the same amount. MBR sector of the 1. physical disk - error opening [4] MBR sector of the 2. physical disk - error opening [4] MBR sector of the 3. physical disk - error opening [4] MBR sector of the 4. physical disk - error opening [4] Boot sector of disk C: - is OK C:\hiberfil.sys - error opening [4] C:\pagefile.sys - error opening [4] Must be a Windows "system thing". Ignore it and good luck. Edited September 12, 2015 by TomFace
ESET Moderators Aryeh Goretsky 394 Posted September 10, 2015 ESET Moderators Posted September 10, 2015 Hello, The errors on the hibernation file and virtual memory paging file occur because those files are held open exclusively by the operating system kernel and cannot be accessed. The errors on the MBR likely occurred because a card reader was plugged in somewhere (could even be part of a USB printer or scanner) and its card slots were enumerated by the operating system and assigned drive letters. However, without having any kind of media plugged into them, attempting to scan them triggers a "MBR cannot be read" error, which is what is expressed in the scanning log for them. Regards, Aryeh Goretsky
TomFace 539 Posted September 12, 2015 Posted September 12, 2015 Thank you Aryeh for the explaination-I always wondered about that.
Recommended Posts