0

I am having issues booting my windows 7 (service pack 1) laptop and I have been online trying fixes for hours. Based on the evidence it seems I most likely have a corrupt ntdll.dll in my system32 folder. One forum I read said to get the file from a computer with the same installation of windows and replace it using the recovery console. I tried this, but I get the message:

The requested operation cannot be performed on a file with a user-mapped section open.

Is there any way I can replace this file?

(All my restore points failed, startup recovery failed, sfc said it fixed corrupt files, but issue persists, and diskcheck said no problems so I am really out of options)

thanks

Improve this question
3
  • As far as I can tell this error is telling me that the file is being used by another process. Is there some way I can stop it?
    – Matt
    Dec 6, 2013 at 7:09
  • You can try to schedule a file replacement operation with SysInternals tools technet.microsoft.com/en-au/sysinternals/bb897556.aspx
    – MBu
    Dec 6, 2013 at 7:18
  • Tried it out, cant be run without starting windows. Says "The subsystem needed to support the image type is not present." Thanks anyways
    – Matt
    Dec 6, 2013 at 7:21

1 Answer 1

Reset to default
0

boot from the Windows 7 DVD go into the Windows Recovery Environment and run the command prompt and run this:

sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows

Replace C: with the drive letter where you installed Windows. Is sfc able to restore the missing or corrupted ntdll.dll?

Improve this answer
4
  • When I run the WRE it shows my Windows directory is on E: (although it was on C: when booting up normally)> is this typical? And should I use c: or e: in your example?
    – Clay Nichols
    Feb 23, 2015 at 16:50
  • @ClayNichols if Windows is E use E:\ in the commandline
    – magicandre1981
    Feb 23, 2015 at 16:51
  • Yep, did that. It at least ran and finished, but SFC was not able to replace some files. Not sure where to get them and they are all in AMD directories and I am on an Intel processor so hoping I don't need those :)
    – Clay Nichols
    Feb 24, 2015 at 17:30
  • @ClayNichols AMD created the first x64 CPU (Athlon64), so Microsoft used the codename amd64 for their first 64Bit Windows and still uses this for files. this has nothing to do which CPU you use. Can you share the logs, so that we can see which files are damaged?
    – magicandre1981
    Feb 25, 2015 at 5:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .