Windows xp не найден файл windows system32 config system

Junior Member

Это файл реестра. Скорее всего был заблокирован. Прогони chkdsk, может поможет.

Цитата:

А разве это не repair режим?

Silver Member

А если раздел под FAT32, то может прокатить scandisk из под 98-го. Загрузится с сист.дискеты и т.д.

BANNED

How to recover from a corrupted registry that prevents Windows XP from starting
View products that this article applies to.
This article was previously published under Q307545
SUMMARY
This article describes how to recover a Windows XP system that does not start because of corruption in the registry. This procedure does not guarantee full recovery of the system to a previous state; however, you should be able to recover data when you use this procedure.

Warning Do not use the procedure that is described in this article if your computer has an OEM-installed operating system. The system hive on OEM installations creates passwords and user accounts that did not exist previously. If you use the procedure that is described in this article, you may not be able to log back into the recovery console to restore the original registry hives.

You can repair a corrupted registry in Windows XP. Corrupted registry files can cause a variety of different error messages. See the Microsoft Knowledge Base for articles about error messages that are related to registry issues.

This article assumes that typical recovery methods have failed and access to the system is not available except by using Recovery Console. If an Automatic System Recovery (ASR) backup exists, it is the preferred method for recovery. Microsoft recommends that you use the ASR backup before you try the procedure described in this article.

Note Make sure to replace all five of the registry hives. If you only replace a single hive or two, this can cause potential issues because software and hardware may have settings in multiple locations in the registry.

If you experience a repetitive occurrence of registry corruption related issues, Microsoft recommends that you obtain and install the hotfix in the following article:
318159 Damaged Registry repair and recovery in Windows XP

This update is also included in Windows XP Service Pack 1.
MORE INFORMATION
When you try to start or restart your Windows XP-based computer, you may receive one of the following error messages:

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE

Stop: c0000218 The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate
The procedure that this article describes uses Recovery Console and System Restore. This article also lists all the required steps in specific order to make sure that the process is fully completed. When you finish this procedure, the system returns to a state very close to the state before the problem occurred. If you have ever run NTBackup and completed a system state backup, you do not have to follow the procedures in parts two and three. You can go to part four.
Part one
In part one, you start the Recovery Console, create a temporary folder, back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. When you have finished this procedure, a registry is created that you can use to start Windows XP. This registry was created and saved during the initial setup of Windows XP. Therefore any changes and settings that occurred after the Setup program was finished are lost.

To complete part one, follow these steps:
Insert the Windows XP startup disk into the floppy disk drive, or insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer.
Click to select any options that are required to start the computer from the CD-ROM drive if you are prompted to do so.
When the «Welcome to Setup» screen appears, press R to start the Recovery Console.
If you have a dual-boot or multiple-boot computer, select the installation that you want to access from the Recovery Console.
When you are prompted to do so, type the Administrator password. If the administrator password is blank, just press ENTER.
At the Recovery Console command prompt, type the following lines, pressing ENTER after you type each line:
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default

Type exit to quit Recovery Console. Your computer will restart.
Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location.

If you have access to another computer, to save time, you can copy the text in step two, and then create a text file called «Regcopy1.txt» (for example). To create this file, run the following command when you start in Recovery Console:
batch regcopy1.txt

With the batch command in Recovery Console, you can process all the commands in a text file sequentially. When you use the batch command, you do not have to manually type as many commands.
Part two
To complete the procedure described in this section, you must be logged on as an administrator, or an administrative user (a user who has an account in the Administrators group). If you are using Windows XP Home Edition, you can log on as an administrative user. If you log on as an administrator, you must first start Windows XP Home Edition in Safe mode. To start the Windows XP Home Edition computer in Safe mode, follow these steps.

Note Print these instructions before you continue. You cannot view these instructions after you restart the computer in Safe Mode. If you use the NTFS file system, also print the instructions from Knowledge Base article KB309531. Step 7 contains a reference to the article.
Click Start, click Shut Down (or click Turn Off Computer), click Restart, and then click OK (or click Restart).
Press the F8 key.

On a computer that is configured to start to multiple operating systems, you can press F8 when you see the Startup menu.
Use the arrow keys to select the appropriate Safe mode option, and then press ENTER.
If you have a dual-boot or multiple-boot system, use the arrow keys to select the installation that you want to access, and then press ENTER.
In part two, you copy the registry files from their backed up location by using System Restore. This folder is not available in Recovery Console and is generally not visible during typical usage. Before you start this procedure, you must change several settings to make the folder visible:
Start Windows Explorer.
On the Tools menu, click Folder options.
Click the View tab.
Under Hidden files and folders, click to select Show hidden files and folders, and then click to clear the Hide protected operating system files (Recommended) check box.
Click Yes when the dialog box that confirms that you want to display these files appears.
Double-click the drive where you installed Windows XP to display a list of the folders. If is important to click the correct drive.
Open the System Volume Information folder. This folder is unavailable and appears dimmed because it is set as a super-hidden folder.

Note This folder contains one or more _restore folders such as «_restore<87BD3667-3246-476B-923F-F86E30B3E7F8>«.

Note You may receive the following error message:

C:\System Volume Information is not accessible. Access is denied.
If you receive this message, see the following Microsoft Knowledge Base article to gain access to this folder and continue with the procedure:
309531 How to gain access to the System Volume Information folder

Open a folder that was not created at the current time. You may have to click Details on the View menu to see when these folders were created. There may be one or more folders starting with «RPx under this folder. These are restore points.
Open one of these folders to locate a Snapshot subfolder. The following path is an example of a folder path to the Snapshot folder:
C:\System Volume Information\_restore\RP1\Snapshot

From the Snapshot folder, copy the following files to the C:\Windows\Tmp folder:
_REGISTRY_USER_.DEFAULT
_REGISTRY_MACHINE_SECURITY
_REGISTRY_MACHINE_SOFTWARE
_REGISTRY_MACHINE_SYSTEM
_REGISTRY_MACHINE_SAM
Rename the files in the C:\Windows\Tmp folder as follows:
Rename _REGISTRY_USER_.DEFAULT to DEFAULT
Rename _REGISTRY_MACHINE_SECURITY to SECURITY
Rename _REGISTRY_MACHINE_SOFTWARE to SOFTWARE
Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
Rename _REGISTRY_MACHINE_SAM to SAM
These files are the backed up registry files from System Restore. Because you used the registry file that the Setup program created, this registry does not know that these restore points exist and are available. A new folder is created with a new GUID under System Volume Information and a restore point is created that includes a copy of the registry files that were copied during part one. Therefore, it is important not to use the most current folder, especially if the time stamp on the folder is the same as the current time.

The current system configuration is not aware of the previous restore points. You must have a previous copy of the registry from a previous restore point to make the previous restore points available again.

The registry files that were copied to the Tmp folder in the C:\Windows folder are moved to make sure that the files are available under Recovery Console. You must use these files to replace the registry files currently in the C:\Windows\System32\Config folder. By default, Recovery Console has limited folder access and cannot copy files from the System Volume folder.

Note The procedure described in this section assumes that you are running your computer with the FAT32 file system.

For additional information about how to access the System Volume Information Folder with the NTFS file system, click the following article number to view the article in the Microsoft Knowledge Base:
309531 How to gain access to the System Volume Information folder

Part Three
In part three, you delete the existing registry files, and then copy the System Restore Registry files to the C:\Windows\System32\Config folder:
Start Recovery Console (or by using a Windows 98 Boot Disk).
At the command prompt, type the following lines, pressing ENTER after you type each line:
del c:\windows\system32\config\sam

copy c:\windows\tmp\software c:\windows\system32\config\software

copy c:\windows\tmp\system c:\windows\system32\config\system

copy c:\windows\tmp\sam c:\windows\system32\config\sam

copy c:\windows\tmp\security c:\windows\system32\config\security

copy c:\windows\tmp\default c:\windows\system32\config\default

Note Some of these command lines may be wrapped for readability.
Type exit to quit Recovery Console. Your computer restarts.
Note This procedure assumes that Windows XP is installed to the C:\Windows folder. Make sure to change C:\Windows to the appropriate windows_folder if it is a different location.

If you have access to another computer, to save time, you can copy the text in step two, and then create a text file called «Regcopy1.txt» (for example).
Part Four
Click Start, and then click All Programs.
Click Accessories, and then click System Tools.
Click System Restore, and then click Restore to a previous RestorePoint.

Junior Member

Загрузка с ДРР.
Тупо скопировал system (после 4—6-й попытки Total Comanderom) в другую папку и в другом разделе. Это тот который не работающий был .
Потому что в папку на этом же разделе system никак копироваться не хотел.
ЗАтем system переименовал в system1 , чтоб не мешал пока.
Потом system скопировал назад в Windows\syystem32\config\

Запустил-перезагрузил винду и все пошло без ошибок .
Другие файлы НЕ ТРОГАЛ . Вот так все решилось .

Тем не менее всем спасибо .
Еще инфа по этой же теме . Mожет кому пригодится.
_hххp://forum.ixbt.com/topic.cgi?id=4:67549#16

Silver Member

Цитата:

непонятно — какой файл скопировал — если тот что был переименовали.
откуда?

у меня то же.. проблем.

запустил чекдиск — кажись попробовал он их восстановить — что получиться поглянем.

Newbie

А чекдиск запусти на проверку с исправлением ошибок — может еще что нибудь найдет

Junior Member

По отдельности работают! А вот чтобы или одну или другую без восстановления запустить — НИКАК! Уже неделю мучаюсь.

HELP. Как решить и в чем тут собака порылась.

Newbie

Волнует 2 вопроса:
1) Из-за чего это могло случиться (никаких установок софта или удаления не было, только обычные «офисные» действия)?
2) Как лучшим образом восстанавливать систему? Чтобы программы остались работоспособными и не испытывать проблем со сбившимися настройками?

Full Member

у меня эта проблема решилась сбросом биоса по умолчанию

был разогнан проц и память система проработала с месяц нормал потом вылезла эта ошибка
проц 8200
память corsair 800 2×1024
мать Asus P5 KC
винт Samsung 640

Silver Member

Цитата:

совет хороший. это первое что я делаю.
второе это chkdsk c: /f/r
третье — это копирование ветки реестра из Windows\repair\- при этом слетят все дрова — но все же это не так смертельно. и не так геморно как переустановка системы.

Newbie

попробовал всё это ничего не помогло( при копировании ветки реестра ком начинает грузится и виснет чёрным экраном и всё происходит это и в безопасном режиме!! что делать посоветуйте так не хочется всю винду перестанавливать!

Newbie

Junior Member

Цитата:

Может уже и поздно советовать, но делать это нужно было не в безопасном режиме, а загрузившись с LiveCD

Цитата:

Цитата:

Время не вылечит.
Если ничего не помогает, нужно установить винду «поверх». При этом сохраняются и дрова и софт. Нужно выбрать пункт меню «чтобы попытаться восстановть выделенную копию. » Чтобы этот пункт был доступен, дистрибутив не должен содержать файл winnt.sif , который часто есть на самосборных дисках.

P/s/ вот еще информация
__хттp://mswin.nm.ru/nastroik/reg3.html

Newbie

Newbie

Из-за чего она появляется? В интернете есть гипотизы о влиянии Касперского на \system.
Что скажете? Как избавится раз и навсегда от этой проблемы? Ибо очень часто она у меня. Пару раз в месяц.

Silver Member

Newbie

У меня при быстром форматировании ничего не получилось чего уж говорить.

Newbie

Кстати где-то 3-4 месяца назад мучал свой HDD всякими тестами, проверками, низкоуровневое форматирование, и т.д. После этого все норм работало. И вот через 3-4 месяц переустанавливаю винду и на следующий день такая байда.
Непомню уже какими прогами мучал винч, но как видите помагло.

Мб, необходимо низкоуровневое форматирование? Типа с обычным форматированием, которое предлагается при установки винды. такая трабла?

Junior Member

1. Не правельное завершение работы Windows
2. Установка игр со своими встроенными дровами для unlock
3. Вирусы
4. Нарушение в работе файловой системе
5. Если винчестер SATA — провода

Источник