Jump to content

Unable to open files on a lot of files when scanning


Recommended Posts

Unable to open files on a lot of files when scanning drive with OS installed. This is my 1st time using ESET product, and I am on 30 days trial. A lot of files on the drive with OS installed scan unable to open files. 

Link to comment
Share on other sites

  • Administrators

Please refer to https://support.eset.com/kb2155/ for clarification.

The files are either inaccessible in your account (e.g. if you do not run a scan as an administrator) or they are exclusively used by the operating system and are unavailable to other applications.

Link to comment
Share on other sites

7 hours ago, Marcos said:

Please refer to https://support.eset.com/kb2155/ for clarification.

The files are either inaccessible in your account (e.g. if you do not run a scan as an administrator) or they are exclusively used by the operating system and are unavailable to other applications.

I ran the scan as the admin, and I am still getting " Unable to open files " on over 100 files on my C drive, and you are telling me ESET has no idea whether these files are safe or not?! I feels like 75% of my C drive only got scan and the other 25% ESET has no idea. 

Link to comment
Share on other sites

  • Most Valued Members

Can you please post the logs of the scan? , a screenshot of the scan log from the logs , or copy and paste some of the 'cannot open' lines

Edited by Rami
Link to comment
Share on other sites

  • Most Valued Members

Sadly I don't have access to Attachments , so I can't see the log, If you could just copy and paste some of the examples from the scan log.

Edited by Rami
Link to comment
Share on other sites

14 minutes ago, Rami said:

Sadly I don't have access to Attachments , so I can't see the log, If you could just copy and paste some of the examples from the scan log.

Mate, it will be a very long paste.What you mean you can't access it when I can? 

Edited by WutDaPhuc
Link to comment
Share on other sites

  • Most Valued Members

Attachments can be accessed only by Moderators/Admins , I didn't mean that you post the whole log , just an example of the 'cannot open' , or just wait for an admin to reply.

Edited by Rami
Link to comment
Share on other sites

  • Administrators

Scan Log
Version of detection engine: 18166 (20181005)
Date: 10/5/2018  Time: 12:33:59 PM
Scanned disks, folders and files: C:\Boot sectors/UEFI;C:\
C:\Documents and Settings\All Users\Microsoft\Crypto\RSA\MachineKeys\0ed42f57fd974675eb6d09ea3ce7b9c5_e60bb0d3-c763-4f6a-91c7-15c664ea4473 - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\TELEMETRY.ASM-WINDOWSSQ.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\telemetry.P-ARIA-194626ba46434f9ab441dd7ebda2aa64-5f64bebb-ac28-4cc7-bd52-570c8fe077c9-7717.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\telemetry.P-ARIA-5476d0c4a7a347909c4b8a13078d4390-f8bdcecf-243f-40f8-b7c3-b9c44a57dead-7230.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.app.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.cert.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.cert.json.bk - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.privacy.json - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\ETLLogs\ShutdownLogger\AutoLogger-Diagtrack-Listener.etl - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\EventStore.db - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\TenantStorage\P-ARIA\EventStore.db - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\VortexSchemaRequests.dat - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\osver.txt - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Diagnosis\parse.dat - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Search\Data\Applications\Windows\Windows.edb - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Search\Data\Applications\Windows\Windows.jfm - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Search\Data\Applications\Windows\edb.jtx - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_Z\LockScreen___1920_1080_notdimmed.jpg - unable to open [4]
C:\Documents and Settings\All Users\Microsoft\Windows Defender\Scans\History\CacheManager\4D3D3BFB-F0B2-45CC-A9BC-A30CF4D9A4FD-0.bin - unable to open [4]
C:\Documents and Settings\All Users\NVIDIA Corporation\NvFBCPlugin\logError.txt - unable to open [4]
C:\Documents and Settings\All Users\NVIDIA Corporation\NvFBCPlugin\logNvFBCPlugin.txt - unable to open [4]
C:\Documents and Settings\All Users\NVIDIA Corporation\NvTelemetry\events.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Google\Chrome\User Data\Default\Current Session - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Google\Chrome\User Data\Default\Current Tabs - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\INetCache\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\INetCache\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\UsrClass.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\WebCache\V01.log - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\Windows\WebCacheLock.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\WindowsApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Microsoft\WindowsApps\MicrosoftEdge.exe - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Documents and Settings\User\AppData\Local\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Documents and Settings\User\Local Settings\Google\Chrome\User Data\Default\Current Session - unable to open [4]
C:\Documents and Settings\User\Local Settings\Google\Chrome\User Data\Default\Current Tabs - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\INetCache\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\INetCache\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\UsrClass.dat - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\UsrClass.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\UsrClass.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\WebCache\V01.log - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\WebCache\WebCacheV01.dat - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\WebCache\WebCacheV01.jfm - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\Windows\WebCacheLock.dat - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\WindowsApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe - unable to open [4]
C:\Documents and Settings\User\Local Settings\Microsoft\WindowsApps\MicrosoftEdge.exe - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Documents and Settings\User\Local Settings\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Documents and Settings\User\Local Settings\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Documents and Settings\User\NTUSER.DAT - unable to open [4]
C:\Documents and Settings\User\ntuser.dat.LOG1 - unable to open [4]
C:\Documents and Settings\User\ntuser.dat.LOG2 - unable to open [4]
C:\Program Files\WindowsApps\Microsoft.MicrosoftSolitaireCollection_4.1.3290.0_x86__8wekyb3d8bbwe\archives\data-30e19a8e53aa3bb4cd8490fe5335e47f35bac111.archive » ZIP » all.bpackages - archive damaged - the file could not be extracted.
C:\Program Files\WindowsApps\Microsoft.MicrosoftSolitaireCollection_4.1.3290.0_x86__8wekyb3d8bbwe\archives\data-30e19a8e53aa3bb4cd8490fe5335e47f35bac111.archive » ZIP » adconfigs/msstaticadsconfigoriginal.js - archive damaged - the file could not be extracted.
C:\Program Files\WindowsApps\Microsoft.MicrosoftSolitaireCollection_4.1.3290.0_x86__8wekyb3d8bbwe\archives\data-30e19a8e53aa3bb4cd8490fe5335e47f35bac111.archive » ZIP » adconfigs/msvideoadsconfig.js - archive damaged - the file could not be extracted.
C:\Program Files\WindowsApps\Microsoft.MicrosoftSolitaireCollection_4.1.3290.0_x86__8wekyb3d8bbwe\archives\data-30e19a8e53aa3bb4cd8490fe5335e47f35bac111.archive » ZIP » tuning/ui_layouts.tuningdata - archive damaged - the file could not be extracted.
C:\Program Files (x86)\IObit\IObit Uninstaller\IObitDownloader.exe - a variant of Win32/IObit.L potentially unwanted application - action selection postponed until scan completion
C:\Program Files (x86)\IObit\IObit Uninstaller\UninstallPromote.exe - a variant of Win32/IObit.J potentially unwanted application - action selection postponed until scan completion
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\0ed42f57fd974675eb6d09ea3ce7b9c5_e60bb0d3-c763-4f6a-91c7-15c664ea4473 - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\TELEMETRY.ASM-WINDOWSSQ.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.P-ARIA-194626ba46434f9ab441dd7ebda2aa64-5f64bebb-ac28-4cc7-bd52-570c8fe077c9-7717.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.P-ARIA-5476d0c4a7a347909c4b8a13078d4390-f8bdcecf-243f-40f8-b7c3-b9c44a57dead-7230.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.app.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.cert.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.cert.json.bk - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.privacy.json - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\ETLLogs\ShutdownLogger\AutoLogger-Diagtrack-Listener.etl - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\EventStore.db - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\TenantStorage\P-ARIA\EventStore.db - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\VortexSchemaRequests.dat - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\osver.txt - unable to open [4]
C:\ProgramData\Microsoft\Diagnosis\parse.dat - unable to open [4]
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb - unable to open [4]
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.jfm - unable to open [4]
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.jtx - unable to open [4]
C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_Z\LockScreen___1920_1080_notdimmed.jpg - unable to open [4]
C:\ProgramData\Microsoft\Windows Defender\Scans\History\CacheManager\4D3D3BFB-F0B2-45CC-A9BC-A30CF4D9A4FD-0.bin - unable to open [4]
C:\ProgramData\NVIDIA Corporation\NvFBCPlugin\logError.txt - unable to open [4]
C:\ProgramData\NVIDIA Corporation\NvFBCPlugin\logNvFBCPlugin.txt - unable to open [4]
C:\ProgramData\NVIDIA Corporation\NvTelemetry\events.dat - unable to open [4]
C:\System Volume Information\IndexerVolumeGuid - unable to open [4]
C:\System Volume Information\MountPointManagerRemoteDatabase - unable to open [4]
C:\System Volume Information\WPSettings.dat - unable to open [4]
C:\System Volume Information\Wcifs.md - unable to open [4]
C:\System Volume Information\klBackupDepository.dat - unable to open [4]
C:\System Volume Information\{052e9757-c41b-11e8-931f-0862664c1ba6}{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\System Volume Information\{052e9cda-c41b-11e8-931f-0862664c1ba6}{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\System Volume Information\{1b7e0d2c-c584-11e8-9324-0862664c1ba6}{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\System Volume Information\{1b7e0d39-c584-11e8-9324-0862664c1ba6}{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\System Volume Information\{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\System Volume Information\{3ab5a556-bccb-11e8-92f4-0862664c1ba6}{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\System Volume Information\{6fe0abd8-c29d-11e8-9318-0862664c1ba6}{3808876b-c176-4e48-b7ae-04046e6cc752} - unable to open [4]
C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys\0ed42f57fd974675eb6d09ea3ce7b9c5_e60bb0d3-c763-4f6a-91c7-15c664ea4473 - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\TELEMETRY.ASM-WINDOWSSQ.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\telemetry.P-ARIA-194626ba46434f9ab441dd7ebda2aa64-5f64bebb-ac28-4cc7-bd52-570c8fe077c9-7717.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\telemetry.P-ARIA-5476d0c4a7a347909c4b8a13078d4390-f8bdcecf-243f-40f8-b7c3-b9c44a57dead-7230.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.app.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.cert.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.cert.json.bk - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\DownloadedSettings\utc.privacy.json - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\ETLLogs\ShutdownLogger\AutoLogger-Diagtrack-Listener.etl - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\EventStore.db - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\TenantStorage\P-ARIA\EventStore.db - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\VortexSchemaRequests.dat - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\osver.txt - unable to open [4]
C:\Users\All Users\Microsoft\Diagnosis\parse.dat - unable to open [4]
C:\Users\All Users\Microsoft\Search\Data\Applications\Windows\Windows.edb - unable to open [4]
C:\Users\All Users\Microsoft\Search\Data\Applications\Windows\Windows.jfm - unable to open [4]
C:\Users\All Users\Microsoft\Search\Data\Applications\Windows\edb.jtx - unable to open [4]
C:\Users\All Users\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_Z\LockScreen___1920_1080_notdimmed.jpg - unable to open [4]
C:\Users\All Users\Microsoft\Windows Defender\Scans\History\CacheManager\4D3D3BFB-F0B2-45CC-A9BC-A30CF4D9A4FD-0.bin - unable to open [4]
C:\Users\All Users\NVIDIA Corporation\NvFBCPlugin\logError.txt - unable to open [4]
C:\Users\All Users\NVIDIA Corporation\NvFBCPlugin\logNvFBCPlugin.txt - unable to open [4]
C:\Users\All Users\NVIDIA Corporation\NvTelemetry\events.dat - unable to open [4]
C:\Users\User\AppData\Local\Google\Chrome\User Data\Default\Current Session - unable to open [4]
C:\Users\User\AppData\Local\Google\Chrome\User Data\Default\Current Tabs - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\INetCache\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\INetCache\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\UsrClass.dat - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG1 - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG2 - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\WebCache\V01.log - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.jfm - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\Windows\WebCacheLock.dat - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\WindowsApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe - unable to open [4]
C:\Users\User\AppData\Local\Microsoft\WindowsApps\MicrosoftEdge.exe - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Users\User\AppData\Local\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Users\User\AppData\Local\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Users\User\Local Settings\Google\Chrome\User Data\Default\Current Session - unable to open [4]
C:\Users\User\Local Settings\Google\Chrome\User Data\Default\Current Tabs - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\INetCache\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\INetCache\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\UsrClass.dat - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\UsrClass.dat.LOG1 - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\UsrClass.dat.LOG2 - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\WebCache\V01.log - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\WebCache\WebCacheV01.dat - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\WebCache\WebCacheV01.jfm - unable to open [4]
C:\Users\User\Local Settings\Microsoft\Windows\WebCacheLock.dat - unable to open [4]
C:\Users\User\Local Settings\Microsoft\WindowsApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe - unable to open [4]
C:\Users\User\Local Settings\Microsoft\WindowsApps\MicrosoftEdge.exe - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG1 - unable to open [4]
C:\Users\User\Local Settings\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat.LOG2 - unable to open [4]
C:\Users\User\Local Settings\Temporary Internet Files\Content.Word\~WRS{68425FC4-862A-4F55-8AEE-65B057FE3E71}.tmp - unable to open [4]
C:\Users\User\Local Settings\Temporary Internet Files\Content.Word\~WRS{EF4C856D-444A-4D64-8D4A-5CF0026D84D0}.tmp - unable to open [4]
C:\Users\User\NTUSER.DAT - unable to open [4]
C:\Users\User\ntuser.dat.LOG1 - unable to open [4]
C:\Users\User\ntuser.dat.LOG2 - unable to open [4]
C:\Windows\InfusedApps\Packages\Microsoft.MicrosoftSolitaireCollection_4.0.1301.0_x86__8wekyb3d8bbwe\archives\data-84580d8cee4b84f391ccd24f3d770d5b1418cddd.archive » ZIP » all.bpackages - archive damaged - the file could not be extracted.
C:\Windows\InfusedApps\Packages\Microsoft.MicrosoftSolitaireCollection_4.0.1301.0_x86__8wekyb3d8bbwe\archives\data-84580d8cee4b84f391ccd24f3d770d5b1418cddd.archive » ZIP » audio/init.bnk - archive damaged - the file could not be extracted.

C:\Windows\InfusedApps\Packages\Microsoft.MicrosoftSolitaireCollection_4.0.1301.0_x86__8wekyb3d8bbwe\loc_archives\en-gb\loc.archive » ZIP » localization/en-gb/fontmapping.fontmapping - archive damaged - the file could not be extracted.
C:\Windows\InfusedApps\Packages\Microsoft.MicrosoftSolitaireCollection_4.0.1301.0_x86__8wekyb3d8bbwe\loc_archives\en-gb\loc.archive » ZIP » localization/en-gb/import.binloc - archive damaged - the file could not be extracted.
C:\Windows\Resources\Themes\aero\VSCache\Aero.msstyles_1033_96_01.mss - unable to open [4]
C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT - unable to open [4]
C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT.LOG1 - unable to open [4]
C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT.LOG2 - unable to open [4]
C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT - unable to open [4]
C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT.LOG1 - unable to open [4]
C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT.LOG2 - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTDefenderAuditLogger.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTDiagLog.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventLog-Application.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventLog-System.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTEventlog-Security.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTNT Kernel Logger.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTUBPM.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRTWFP-IPsec Diagnostics.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{0265876E-8129-42E8-BF9D-AF6BC06C8BA6}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{06F7002A-7CBE-4DCA-A8C7-28F0B922C62B}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{1B49F38B-681B-40D9-A182-938CE139BDF8}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{23337D18-2FED-48D7-8E10-72D4771EAD39}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{30BE55B3-D1B0-49C0-AD89-E2E1E8D3FC06}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{4281EE65-C857-409E-A3F2-C7C141985FB2}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{5966D78A-E707-49D5-A7DB-85933E1689F3}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{5C58E330-F3EA-4830-8763-6FA1230D11AA}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{5E86640D-FC35-474B-B365-7561772EB3CC}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{66E7923F-1F06-4696-8F54-1B28C67B28C0}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{6B578F65-D1AC-4566-90D1-46A4DE795E90}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{A917146B-7CE7-4DAB-B605-751B46C16C6C}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{AD9AA779-DC20-4D11-B54D-4F8E28CD54F9}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{BF077333-C787-4B19-A082-89476EBA9A19}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{C0E64C84-42CF-4FC0-9BCD-844B4750B174}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{EF6BD318-AB29-443F-AD62-4666325D7CD4}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{F46E2347-B3DE-4B71-AC25-75ACC8CFD4A1}.etl - unable to open [4]
C:\Windows\System32\LogFiles\WMI\RtBackup\EtwRT{FDC58D0D-1236-4987-8DE1-3DCB07C2D07A}.etl - unable to open [4]
C:\Windows\System32\config\BBI - unable to open [4]
C:\Windows\System32\config\BBI.LOG1 - unable to open [4]
C:\Windows\System32\config\BBI.LOG2 - unable to open [4]
C:\Windows\System32\config\DEFAULT - unable to open [4]
C:\Windows\System32\config\DEFAULT.LOG1 - unable to open [4]
C:\Windows\System32\config\DEFAULT.LOG2 - unable to open [4]
C:\Windows\System32\config\RegBack\DEFAULT - unable to open [4]
C:\Windows\System32\config\RegBack\SAM - unable to open [4]
C:\Windows\System32\config\RegBack\SECURITY - unable to open [4]
C:\Windows\System32\config\RegBack\SOFTWARE - unable to open [4]
C:\Windows\System32\config\RegBack\SYSTEM - unable to open [4]
C:\Windows\System32\config\SAM - unable to open [4]
C:\Windows\System32\config\SAM.LOG1 - unable to open [4]
C:\Windows\System32\config\SAM.LOG2 - unable to open [4]
C:\Windows\System32\config\SECURITY - unable to open [4]
C:\Windows\System32\config\SECURITY.LOG1 - unable to open [4]
C:\Windows\System32\config\SECURITY.LOG2 - unable to open [4]
C:\Windows\System32\config\SOFTWARE - unable to open [4]
C:\Windows\System32\config\SOFTWARE.LOG1 - unable to open [4]
C:\Windows\System32\config\SOFTWARE.LOG2 - unable to open [4]
C:\Windows\System32\config\SYSTEM - unable to open [4]
C:\Windows\System32\config\SYSTEM.LOG1 - unable to open [4]
C:\Windows\System32\config\SYSTEM.LOG2 - unable to open [4]
C:\hiberfil.sys - unable to open [4]
C:\pagefile.sys - unable to open [4]
C:\swapfile.sys - unable to open [4]
Number of scanned objects: 332794
Number of threats found: 0
Number of cleaned objects: 0
Time of completion: 12:36:44 PM  Total scanning time: 165 sec (00:02:45)
Notes:
[4] Object cannot be opened. It may be in use by another application or operating system.

 

Link to comment
Share on other sites

1 hour ago, TomFace said:

There is nothing to fix. Read the KB Marcos posted.

So ESET only scan like 95% of my drive and the rest 5% don't know if it safe or not? What? 

Link to comment
Share on other sites

I'm having the same problem but I purchased the version.  Makes no sense that all I see is "unable to open". 

 

 ex:  Log
C:\Program Files (x86)\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\AppvIsvStream64.dll - unable to open [4]

Log
C:\Program Files (x86)\Microsoft Office\root\Client\AppvIsvStream32.dll - unable to open [4]
 

 

Link to comment
Share on other sites

The simple answer to this scanning issue is certain files; OS based, certain Microsoft applications, etc.. are preventing read access to those files. The only way Eset could scan these files is if it changed file access permissions so it could access those files. This is something Eset and no other security vendor for that matter is going to do. Nor is it something they should do since the possibility of a "bork" in doing so is high not to say the impact on overall scanning times which would be considerable. 

Edited by itman
Link to comment
Share on other sites

50 minutes ago, itman said:

The simple answer to this scanning issue is certain files; OS based, certain Microsoft applications, etc.. are preventing read access to those files. The only way Eset could scan these files is if it changed file access permissions so it could access those files. This is something Eset and no other security vendor for that matter is going to do. Nor is it something they should do since the possibility of a "bork" in doing so is high not to say the impact on overall scanning times which would be considerable. 

 

2 hours ago, Marcos said:

If ESET cannot scan certain files, then any possible malware would not be able to modify them either,

I can't tell if my system is safe or not if I see more than 100 files that ESET skipped because it can't be open than there is something wrong with it. Kaspersky and Bitdefender scan them fine with no problem. 

Link to comment
Share on other sites

  • Most Valued Members
7 hours ago, WutDaPhuc said:

 

I can't tell if my system is safe or not if I see more than 100 files that ESET skipped because it can't be open than there is something wrong with it. Kaspersky and Bitdefender scan them fine with no problem. 

Are you sure that you have scanned as Administrator?

Link to comment
Share on other sites

  • Administrators

A Procmon log created during a scan might shed more light. Start logging at least a couple of seconds before you run a scan.

Link to comment
Share on other sites

14 hours ago, WutDaPhuc said:

Kaspersky and Bitdefender scan them fine with no problem. 

Do they?

I believe a number of AV vendors do not display files in their log file's they cannot scan due to OS file locking. This would give one the impression that the files Eset shows as non-scannable were indeed scanned.  Personally, I don't know why Eset does not do likewise since this issue keeps appearing in the forum with regular frequency.

Edited by itman
Link to comment
Share on other sites

  • Most Valued Members
15 minutes ago, itman said:

Do they?

I believe a number of AV vendors do not display files in their log file's they cannot scan due to OS file locking. This would give one the impression that the files Eset shows as non-scannable were indeed scanned.  Personally, I don't know why Eset does not do likewise since this issue keeps appearing the forum with regular frequency.

I think it's better in terms of monitoring the scan , what was scanned and what was not , whether it was locked or something else, maybe adding a feature to hide them from the scanlog by default might help.

Link to comment
Share on other sites

6 hours ago, Marcos said:

A Procmon log created during a scan might shed more light. Start logging at least a couple of seconds before you run a scan.

How to do that? 

1 hour ago, itman said:

Do they?

I believe a number of AV vendors do not display files in their log file's they cannot scan due to OS file locking. This would give one the impression that the files Eset shows as non-scannable were indeed scanned.  Personally, I don't know why Eset does not do likewise since this issue keeps appearing in the forum with regular frequency.

They scanned fine. 

 

1 hour ago, Rami said:

I think it's better in terms of monitoring the scan , what was scanned and what was not , whether it was locked or something else, maybe adding a feature to hide them from the scanlog by default might help.

Yeah....

Link to comment
Share on other sites

6 minutes ago, Mr.Wong said:

How to do that? 

In @Marcos's previous reply, click on the FAQ: link "Using Process Monitor to create log files."

Edited by itman
Link to comment
Share on other sites

I will state this in regard to this issue. The number of files Eset cannot scan at any given time will vary depending on current system status.

When I did my last Eset install on 9/4, Eset's full system scan bypassed 76 files. My last scan Smart scan a couple of days ago yielded over 400 files being bypassed. Why?

Well since 9/4 a number of system updates have occurred on my system; most notably two failed attempts to upgrade to Win 10 1809. Most of the files bypassed in the last Smart scan are in this directory, C:\WINDOWS\System32\winevt\Logs, which is logically assuming the above failed upgrade attempts.

Bottom line - manually try to access the one or more of the files Eset's scanning bypassed. If you cannot access those files due to the following message:

Access_Violation.png.9798d76ed7feea7f2e50ec60555b7e71.png

Neither can Eset access the file.

Link to comment
Share on other sites

7 minutes ago, Rami said:

@itman, Even though that you are the Administrator you still receive that message?

I run as a limited admin.

As I posted previously, these files can't be read nor can even ownership be established:

No_Read_Permissions.thumb.png.8f9f3e87243780167f982220942ba9a6.png

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...