Extract Files from Windows 7 Installation DVD

Thanks for the reply. But if suppose there are critical files missing then that step should be attempted. Is it not?. This forum is for all and this tutorial applies to all.
Even i commented this on that article. Normally person do not know that their windows protected files are removed by trojans.It just removes and the person infected by the trojan gets the trouble in so many ways, some of which could not be easily deciphered and decided upon.
Reinstalling of windows or repairing of windows , i think , is only the last step to be tried. But, the removed files could only be fixed if they know what sfc /scannow does to retrieve those.For anything and everything i only use this forum tutorial which is self explaining with tutorials very easy to understand.
Before writing, i tried the same copied instructions in the other site, and tried the option. Upto the 2nd it says , that successfully owned , and given admin rights also. But the third one could not be executed, as it says the syntax is incorrect or some error. I know the flaw and immediately resorted to system restore point , which i have created, so no problem. But if i had not created, i might have had some other errors for i have to search.
Once again thanks for quick responses

Hello, Been reading through this thread and others here @ sevenforums.com cause I am having issues with files sfc cannot repair. Even after 3 after running it 3 times.

I checked my cbs log and was able to locate 11 files that could not be repaired:

C:\Windows\System32\autochk.exe

C:\Windows\System32\batmeter.dll

C:\Windows\System32\CompMgmtLauncher.exe

C:\Windows\System32\comres.dll

C:\Windows\System32\control.exe

C:\Windows\System32\localsec.dll

C:\Windows\System32\IMJP10.IME

C:\Windows\System32\wpccpl.dll

C:\Windows\System32\logoncli.dll

C:\Windows\SysWOW64\mfreadwrite.dll

C:\Windows\SysWOW64\devmgr.dll

Followed your instructions on using 7zip to extract those files from my Win7 SP1 disk and replace the existing ones. As you mentioned I had to take ownership of each file to do this.

Ran sfc after rebooting and still getting errors on the same files.

This started as a result of a bad HDD. I cloned and replaced the drive with a new one and started noticing issues with the Computer Managment Console and getting lsass.exe crashes that generated the following errors:

Event ID 1015 Wininit.
A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.


Event ID 1000 Application

Faulting application name: lsass.exe, version: 6.1.7601.18443, time stamp: 0x5348920c
Faulting module name: logoncli.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c71e
Exception code: 0xc000001d
Fault offset: 0x000000000000fc70
Faulting process id: 0x380
Faulting application start time: 0x01d0110a0f51db65
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\system32\logoncli.dll
Report Id: dd4fd2b3-7d03-11e4-9bce-74d435754420

Event ID 1005 Application

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Local Security Authority Process because of this error.

Program: Local Security Authority Process
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0


Any advice is greatly appreciated.

Hello Brink,
I ran the System Update Readiness Tool, extracted and copied the files again, and ran sfc.
Still no joy same files cannot be repaired.

No problems since the last lsass.exe crash about 8 hrs ago. That was around the time I found your threads on sfc and tried to copy the files. I have also applied some MS hotfixes for the lsass error. Guess I'll let it go for now and see what I can do for the wifi here.
Thanks for you help.

Hello Brink,

thanks for this tutorial! Windows 8 does not have an installation.wim anymore, instead it has an installation.esd in the same directory ([root-folder]\sources). installation.esd cannot be opened by 7-zip, but there is an easy solution using Windows' built-in tool called DISM (Deployment Image Servicing and Management). DISM is available for Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, according to its MSDN article. Many thanks to this article from deskmodder.de (German site) which explains the usage of DISM in order to extract installation.esd.

The instructions are as follows:

1. Gain access to Windows' installation data using
   a) your Windows 8 installation disc,
   b) a downloaded ISO file, which you can mount by right-clicking in Explorer and selecting Mount, or using
   c) a USB Flash drive on which you have "burnt" the downloaded ISO file.
   
   See Windows 8 and Windows 8.1 ISO - Download or Create if you need help with creating/downloading a legal Windows 8 ISO file.
   
   
2. Run the following commands in a console (cmd.exe or PowerShell) with elevated privileges (have a look at Command Prompt: frequently asked questions if you do not know how):
   
   Code:

   mkdir c:\...\mount
   dism /apply-image /imagefile:d:\sources\install.esd /index:1 /ApplyDir:c:\...\mount

   c:\...\mount is the directory into which you wish the Windows install.esd to be extracted. Command #1 creates this directory. Be sure to replace c:\...\mount by your path in the second command as well!
   d:\sources\install.esd is the path to install.esd of your Windows installation medium. Replace d by the drive letter of your disc, mounted ISO file, or USB Flash drive.
   Please avoid spaces in both paths! If you absolutely require them, then enclose all paths by double quotes (e.g. /ApplyDir:"c:\here is a space\my-directory").
   
   
3. install.esd has been now extracted into the stated directory.

Maybe these instructions could be incorporated into the existing article or into a new one.