How do I scan these "error opening [4] " files

[Ar3a27nm]

Before I buy 5 licenses for the home version I'd like to know how to scan these "error opening [4]" files. I did try Safe Mode too...

:::ESET APPLICATION & OS:::
ESET NOD32 Antivirus 3.0.669.0
Trial Version: 28 Day(s) Left
Virus signature database: 3718 (20081226)
Update module: 1024 (20080514)
Antivirus and antispyware scanner module: 1166 (20081222)
Advanced heuristics module: 1084 (20081202)
Archive support module: 1085 (20081106)
Cleaner module: 1037 (20081209)
Anti-Stealth support module: 1002 (20080723)
Microsoft Windows XP (32-bit)
Version 5.1.2600 Service Pack 3

:::FILES NOT SCANNED:::
C:\pagefile.sys - error opening [4]
C:\Documents and Settings\LocalService\NTUSER.DAT - error opening [4]
C:\Documents and Settings\LocalService\ntuser.dat.LOG - error opening [4]
C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - error opening [4]
C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG - error opening [4]
C:\Documents and Settings\NetworkService\NTUSER.DAT - error opening [4]
C:\Documents and Settings\NetworkService\ntuser.dat.LOG - error opening [4]
C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - error opening [4]
C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG - error opening [4]
C:\Documents and Settings\#####\NTUSER.DAT - error opening [4]
C:\Documents and Settings\#####\NTUSER.DAT.LOG - error opening [4]
C:\Documents and Settings\#####\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - error opening [4]
C:\Documents and Settings\#####\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG - error opening [4]
C:\WINDOWS\system32\config\default - error opening [4]
C:\WINDOWS\system32\config\default.LOG - error opening [4]
C:\WINDOWS\system32\config\SAM - error opening [4]
C:\WINDOWS\system32\config\SAM.LOG - error opening [4]
C:\WINDOWS\system32\config\SECURITY - error opening [4]
C:\WINDOWS\system32\config\SECURITY.LOG - error opening [4]
C:\WINDOWS\system32\config\software - error opening [4]
C:\WINDOWS\system32\config\software.LOG - error opening [4]
C:\WINDOWS\system32\config\system - error opening [4]
C:\WINDOWS\system32\config\system.LOG - error opening [4]

[LowWaterMark]

All those files are open and locked by either the OS or key programs, so, they can not be scanned. That's normal for most all scanners, except that NOD32 happens to report that it can't scan them. Some products simply don't report them.

From the NOD32 FAQ thread (http://www.wilderssecurity.com/showthread.php?t=150856):

{QUOTE-> [4] Locked Files. Answer (http://www.wilderssecurity.com/showthread.php?p=833165#post833165) and Answer (http://www.wilderssecurity.com/showthread.php?p=859496) and Answer (http://www.wilderssecurity.com/showthread.php?t=149942) <-QUOTE}