Missing "System" file

  • Thread starter Thread starter Alberto
  • Start date Start date
A

Alberto

I have read and used the procedures outlined here to save my sanity when
encoiuntering this problem of the missing "System" file. I appreciate
everyone's posts.
My question now is: Why this would happen so frequently (every 2 or 3
months)? My kids use it for iTunes and we all use it for digital cameras, I
was wondering if the way we remove the devices from the USB ports is a
problem, or is there a virus I am not aware of that could do this? I have
scanned using two programs and I run an anti-spyware program which have come
up with nothing. What should I be looking for?

Thanks
 
Without more information as to the file that's going missing, you're
probably not going to get much help.
 
*Bonjour Alberto * !
I have read and used the procedures outlined here to save my sanity when
encoiuntering this problem of the missing "System" file. I appreciate
everyone's posts.

I hope you use ERUNT !
http://www.larshederer.homepage.t-online.de/erunt/
http://www.google.com/search?q=ERUNT+~tip
My question now is: Why this would happen so frequently (every 2 or 3
months)? My kids use it for iTunes and we all use it for digital cameras, I
was wondering if the way we remove the devices from the USB ports is a
problem, or is there a virus I am not aware of that could do this? I have
scanned using two programs and I run an anti-spyware program which have come
up with nothing. What should I be looking for?

SYSTEM is a Registry file
http://support.microsoft.com/kb/307545

For information, the sentence :
"By default, Recovery Console has limited folder access
and cannot copy files from the System Volume folder"
*is false*
http://fspsa.free.fr/images/cdr-svi/cdr-svi-dir.png

With Erunt you dont need to do all these.

Did you make a CHKDSK /R recently ?
So do it :
Start>Execute>chkdsk /r
Accept ... and restart.
Wait ... wait ... wait ... can be 1/2 to few hours.

Active SMART into the BIOS and watch that disk
http://crystalmark.info/?lang=en
 
Alberto said:
Sorry - by "System" I meant Windows\system32\Config\System

That's a very bad sign...

run the manufacturer's harddrive diagnostic
and also run a RAM test.

Additionally, you may want to check the harddrive for excess temperature
 
JF said:
*Bonjour Alberto * !



I hope you use ERUNT !
http://www.larshederer.homepage.t-online.de/erunt/
http://www.google.com/search?q=ERUNT+~tip



SYSTEM is a Registry file
http://support.microsoft.com/kb/307545

For information, the sentence :
"By default, Recovery Console has limited folder access
and cannot copy files from the System Volume folder"
*is false*
http://fspsa.free.fr/images/cdr-svi/cdr-svi-dir.png

That is not false, it is true. For security reasons file access in the
Recovery Console is limited to the root folders and to the %Systemroot%
folder and its subfolders. This behaviour can be changed by a registry
edit or via Group Policies, if the changes were not made the Recovery
Console will not have access to the System Volume folder.

John
 
Alberto said:
Sorry - by "System" I meant Windows\system32\Config\System


How to Troubleshoot Registry Corruption Issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;822705


--

Bruce Chambers

Help us help you:


http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot
 
*Bonjour John John (MVP) * !
JF wrote:
That is not false, it is true. For security reasons file access in the
Recovery Console is limited to the root folders and to the %Systemroot%
folder and its subfolders. This behaviour can be changed by a registry edit
or via Group Policies, if the changes were not made the Recovery Console will
not have access to the System Volume folder.

Sorry, you're wrong. I know all that. Look :
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole
SecurityLevel=0
SetCommand=0

And now try this from the Recovery Console ==>
(you *dont need* to type SET AllowAllPaths = TRUE)

CD \
CD "SYSTEM VOLUME INFORMATION"
DIR

==>
http://fspsa.free.fr/images/cdr-svi/cdr-svi-dir.png

*Why dont you try* ?

We proved that SVI is accessible since SP1 for the Recovery Console ==>
http://fspsa.free.fr/cdr-svi-accessible.htm
Microsoft has been noticed to modify KB307545
http://support.microsoft.com/kb/307545

Confirmation by Mark Russinovich :
Microsoft Windows Internals: Microsoft Windows Server 2003, Windows XP,
and Windows 2000, Fourth Edition by Mark E. Russinovich and David A.
Solomon Microsoft Press © 2005
http://microsofteref.books24x7.com/viewer.asp?bookid=10479&chunkid=936576450
"If you're running Windows XP and System Restore is enabled (System
Restore is discussed in Chapter 12) , you can often obtain a more
recent backup of the registry hives, including the System hive, from
the most recent restore point. However, you may not be able to access
the directory in which restores points are stored, \System Volume
Information, from within the Recovery Console. *Windows XP Service Pack
1 Versions of the Recovery Console allow access to that directory*, but
older versions do not unless the system's local security policy allows
it."

So for a long time now we use this method to help people with Registry
problems : http://fspsa.free.fr/cdr-svi.htm

Easier of course with a BARTPE, which
doesn't know restrictions about SVI
http://www.ubcd4win.com
 
Thanks, I will see what diagnostics eMachines has to offer on the disk. How
would I run a check on the RAM? I've never tried it before, but it could be
an issue.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top