Windows Forum / Windows Me / System Tools / March 2005
System Restore is continually writing hundreds of small files
|
|
Thread rating:  |
Zdenek - 05 Jan 2005 12:13 GMT I (or rather Trend Micro scanner) found a virus in the _RESTORE folder. I disabled System restore, cleaned the virus and re-enabled it. Wanting to make a fresh start, I also renamed and deleted (booting from a diskette) the _RESTORE folder.
However, whatever I have tried, System restore has been permanently writing hundreds of small files (A0000xxx.cpy) into the _RESTORE/TEMP folder. There are about ten of them created every minute, each about 100 bytes big.
Is this normal? It definitely did not happen before. Apart from the annoying permanent disk activity, I suspect this process for being responsible for the malfunctioning of the Steganos encrypted drive: I can open it, but not close it, although there is no visible process using it.
Can you suggest how to stop this?
Mike M - 05 Jan 2005 13:32 GMT No, not normal at all. The problem you describe can be caused by your having installed some application or other that for some reason or other is continually modifying, or at least opening if not altering, a file of a type monitored by system restore. For example the application is continually opening and possibly modifying a file with an INI or CFG extension.
That the file concerned is small is both useful and a problem. Useful in that it means the C:\_RESTORE\TEMP folder isn't growing in size too quickly, a nuisance in that its small size probably makes it more difficult to determine the file involved as there are so many small files on a system. Once you have identified the exact name of the file that is being archived I will try and help you in setting up system restore, or rather Win Me's state manager, to ignore changes to this file.
If you open one of the archived CPY files with say Notepad (or perhaps another hex editor) does this give you a clue as to the origin and more importantly the original name and file extension of the file concerned. If so post back details and I will explain how you need to proceed.
 Signature Mike Maltby MS-MVP mike.maltby@gmail.com
> I (or rather Trend Micro scanner) found a virus in the _RESTORE > folder. I disabled System restore, cleaned the virus and re-enabled [quoted text clipped - 13 lines] > > Can you suggest how to stop this? Zdenek - 05 Jan 2005 19:05 GMT Mike,
there are already about 12 000 files created in the past 7 hours. They are all the same: two lines, saying Info and name of the file scanned. I copied some of them:
[Info] LastScan=C:\WINDOWS\FAVORITES\LINKS\WINDGURU.URL
[Info] LastScan=C:\WINDOWS\FAVORITES\LINKS\WINDGURU.URL
[Info] LastScan=C:\WINDOWS\FAVORITES\LINKS\WINDGURU.URL
[Info] LastScan=C:\WINDOWS\EXPLORER.EXE
[Info] LastScan=C:\WINDOWS\HISTORY\DESKTOP.INI
[Info] LastScan=C:\WINDOWS\FAVORITES\LINKS\SKIAREÁL ŠPIND.URL
[Info] LastScan=C:\PROGRAM FILES\TREND MICRO\INTERNET SECURITY\LASTSCAN.INI
[Info] LastScan=C:\WINDOWS\HISTORY\HISTORY.IE5\MSHIST012005010520050106\INDEX.DAT
[Info] LastScan=C:\Program Files\mozilla.org\Mozilla\mozilla.exe
[Info] LastScan=C:\PROGRAM FILES\TREND MICRO\INTERNET SECURITY\LASTSCAN.INI
[Info] LastScan=C:\WINDOWS\INCD\INCDERR.LOG
[Info] LastScan=C:\PROGRAM FILES\TREND MICRO\INTERNET SECURITY\LASTSCAN.INI
[Info] LastScan=C:\WINDOWS\INCD\INCDERR.LOG
[Info] LastScan=C:\PROGRAM FILES\TREND MICRO\INTERNET SECURITY\LASTSCAN.INI
Apart from this, everything else seems to be working.
Zdenek
> No, not normal at all. The problem you describe can be caused by your > having installed some application or other that for some reason or other [quoted text clipped - 33 lines] > > > > Can you suggest how to stop this? Mike M - 05 Jan 2005 19:19 GMT Zdenek,
Now see if you can locate the original file. Since the file contains the line "LastScan" I would start by looking at your antivirus application which might just be, based on past experience, McAfee. Use Windows Explorer's search and look for a file in either your Program Files or Windows folder containing the string/text LastScan.
Once we know the name of the file that is being archived I will explain how to remove the file from system restore's embrace. If it is a file associated with your antivirus application please post details of the AV app you are using including its version.
 Signature Mike Maltby MS-MVP mike.maltby@gmail.com
> Mike, > [quoted text clipped - 45 lines] > > Apart from this, everything else seems to be working. Zdenek - 06 Jan 2005 08:31 GMT Mike,
I think I found the culprit. There is a file called C:\Program files\Trend Micro\Internet Security\lastscan.ini. It seems to contain the last file the anti-virus SW scanned and its modification date and time is being updated continually. The version of TM Internet Security is 11.41, the engine number is 7.100. I am on a broadband connection and the patterns are updated automatically every three hours.
Zdenek
Mike M píše:
> Zdenek, > [quoted text clipped - 58 lines] > > > > Apart from this, everything else seems to be working. Mike M - 06 Jan 2005 12:15 GMT Zdenek,
Great! All that remains is to remove the file LASTSCAN.INI from the scope of Win Me's state manager. The instructions that follow on how to do this might seem long but should solve the problem and once done it will be much easier to then remove any other files or folders from the scope. I am ASSuming in what follows that you know how to work from DOS, if not please post back any specific queries you might have and I will try and help.
a) System Restore monitors and will thus restore (and remove if newer) files with some 550 odd different extensions however it totally ignores changes to the contents of certain folders including My Documents (and any sub folders), and the Temporary and Temporary Internet Files objects wherever located or however named and certain specified files such as McAfee's aviconsol.ini.
Have a look at the file FileList.xml in the windows\system\restore folder with Notepad and you will see the list of monitored file extensions in the section <EXTENSIONS> <Include> and the list of ignored files and folders in the sections <FILES> <Exclude> and <DIRECTORIES> <Exclude>
b) We therefore need to exclude the file C:\Program files\Trend Micro\Internet Security\LASTSCAN.INI from the state manager's scope.
c) Two points to note before we move on. 1) FileList.xml is protected from amendment by Win Me's System File Protection, and, b) Win Me's state manager doesn't actually use FileList.xml but rather the file vxdmon.dat and vxdmon.cfg which are located in the _RESTORE folder on the drive containing the windows folder.
d) The trick here is that FileList.xml contains a reference to itself in the SFP section and thus cannot be replaced whilst Win Me is running without Win Me's System File Protection immediately restoring the original. So make a copy of FileList.xml in your Windows\system\restore folder and name it FileList.new. Now, using Notepad (or your preferred plain text/hex editor), open FileList.new and a) delete the reference to itself (Line: 829), and b) add the line <REC>%ProgramFiles%\Trend Micro\Internet Security\LASTSCAN.INI </REC> immediately after the line <REC>%ProgramFiles%\MCAFEE\AVCONSOL.INI</REC>
Now disable System Restore using the GUI (System | Performance | File System | Troubleshooting and check "Disable System Restore") and immediately reboot the system but instead of rebooting back into Win Me boot to DOS from a floppy. Browse to the Windows\System\Restore folder and rename FileList.xml to FileList.old and FileList.new to FileList.xml. Remove the floppy and reboot back into Win Me, re-enable System Restore and again immediately reboot. The SFP & SR control file vxdmon.dat will now be rebuilt using the modified FileList.xml and the file C:\Program files\Trend Micro\Internet Security\LASTSCAN.INI removed from the state manager's scope.
e) Note that now you have removed the reference to itself in FileList.xml this means that in future this file can be edited as required without SFP butting in and rearing its ugly head <g>. Therefore changes to FileList.xml can now be implemented by simply resetting SR so as to incorporate the changes into a newly built vxdmon.dat without the need to rename files from DOS. Also, if you get the syntax wrong in FileList.xml, statemgr.exe (or is it stmgr.exe - I forget which) will balk when building vxdmon.dat on booting the system and quit and sulk until you correct the error in FileList.xml.
In conclusion if you feel the need for further help feel free to contact me on mikem@mvps.org (rather than the address that follows my sig.).
Best of luck and I hope that enough of what I have written makes sense.
 Signature Mike Maltby MS-MVP mike.maltby@gmail.com
> I think I found the culprit. There is a file called C:\Program > files\Trend Micro\Internet Security\lastscan.ini. It seems to contain [quoted text clipped - 3 lines] > connection and the patterns are updated automatically every three > hours. Zdenek - 06 Jan 2005 17:39 GMT Mike,
many thanks, you are a real pro! The instructions were crystal clear and it worked perfectly, the files are not created anymore.
Best regards, Zdenek
> Zdenek, > [quoted text clipped - 71 lines] > > connection and the patterns are updated automatically every three > > hours. Mike M - 06 Jan 2005 17:59 GMT Zdenek.
Thanks for the feedback. That's the sort of message that any poster is pleased to read - a success! With the details I posted and what you have now learned about the state manager you can now easily add or remove files from the state manager's scope - either as system file protected (SFP) files (that is cannot be deleted) or from being backed up by system restore. In future any changes are as easy as editing FileList.xml and then cycling the state manager (system restore) off and then back on again to rebuild the control files and implement the changes since FileList.xml is no longer protected against deletion by SFP.
Cheers and glad to have been able to help,
 Signature Mike Maltby MS-MVP mike.maltby@gmail.com
> Mike, > > many thanks, you are a real pro! The instructions were crystal clear > and it worked perfectly, the files are not created anymore. Paul Killick - 25 Mar 2005 21:05 GMT Hi Mike
I was reading your discussion about the above . I've got the same problem as mentioned in you discussion. I've got down to creating a filelist.new. I'm not great with DOS and am picking odd bit up by reading the sorts of articles. Could you instruct me how to do the following bit Browse to the Windows\System\Restore folder and rename FileList.xml to FileList.old and FileList.new to FileList.xml.
I would be deeply in your debt. Thanks for your help
> Zdenek, > [quoted text clipped - 71 lines] > > connection and the patterns are updated automatically every three > > hours. Mike M - 25 Mar 2005 21:20 GMT Paul,
Boot to DOS with a floppy. At the A:\> prompt type, all on the same line,
REN C:\WINDOWS\SYSTEM\RESTORE\FILELIST.XML FILELIST.OLD
and then click Enter, now type, again all on the same line,
REN C:\WINDOWS\SYSTEM\RESTORE\FILELIST.NEW FILELIST.XML
and then click Enter. Remove the floppy, boot back into Win Me, re-enable System Restore and once again immediately reboot. Finally adjust the space allocated to the restore archive to meet your preferences.
 Signature Mike Maltby MS-MVP mike.maltby@gmail.com
> Hi Mike > [quoted text clipped - 13 lines] > > I would be deeply in your debt. Paul Killick - 26 Mar 2005 20:21 GMT Mike
Thanks for the help on this one, worked a treat.
Fantastic instructions,even for novices like me.
> Paul, > [quoted text clipped - 30 lines] > > > > I would be deeply in your debt. Mike M - 26 Mar 2005 20:44 GMT Paul,
Thanks for the feedback. Next time I see a similar question with system restore unnecessarily archiving the same file over and over I'll try to remember to include the two DOS REName instructions rather than simply saying boot to DOS and rename, etc. It's so easy to forget that not everyone, and not necessarily novices (such as you were <g>) is particularly comfortable or familiar with working at a DOS (Command) prompt. So thanks for that reminder.
Regards,
 Signature Mike Maltby MS-MVP mike.maltby@gmail.com
> Mike > > Thanks for the help on this one, worked a treat. > > Fantastic instructions,even for novices like me.
|
|
|