when i do a scan boot,avast tells me" error in winstart.bat "
is it important?
xp pro sp2 full updated
ms antispy
kerio 2.1.5
thanks Lee.Only avast tells me about this problem
no problem pointed by windows or others av;so I think it’s not very important,or rather I hope!
Well its kinda hard to help without more specific infomation them, please provide:
Your OS
Your Avast Version
Exact error message
Also have you tried running a scandisk/chkdisk
–lee
Wait a second 
When exactly is the problem reported? I’m not aware of any checks of winstart.bat in avast!..
2 weeks ago.avast 4.6.623
yes i did scan disk/chkdisk
I would like to know when is the error displayed…
when scan on demand only
report tells"c:/windows/winstart.bat error 42006
You mean, when you run a scan from the Simple User Interface, the final report shows error 42006 for that file?
boot scan “error42006”
scan with interface “cannot open winstart.bat”
Well, the error 42006 means “file is offline”, which is rather strange… (unless somebody set the “offline” attribute to this file). Can you check the content of the file? (can you open it in Notepad, for example)?
no ,I can’t find c:/windows/winstart.bat anywhere
Are you sure this file is not hidden?
Windows Explorer > Tools > Folder options > Show… (2nd tab) > Show hidden and system files
Search…
If it’s really not there, I’d try the RootKit Revealer… I believe winstart.bat shouldn’t normally be present in WinXP system.
It’s really not there! and it’s not hidden technical I’ll try your util Igor and tell you after.thanks
here is what i see
HKLM\softwate\microsoft\windows\current version\system
time: 04/02/2005
size:0 bytes
description: key name contains embedded nulls
If somebody can help me .Thanks!
Key name contains embedded nulls.
The Windows API treats key names as null-terminated strings whereas the kernel treats them as counted strings. Thus, it is possible to create Registry keys that are visible to the operating system, yet only partially visible to Registry tools like Regedit. The Reghide sample code at Sysinternals demonstrates this technique, which is used by both malware and rootkits to hide Registry data.
This is from its help file… My system scan reveals the same… I haven’t too much time to interpret it but it seems to be normal and not a problem really…
Thank you Technical !It’s reassuring!