After spending some time researching past cases I would try a fast repair
and if that did not resolve the problem I would go for an inplace upgrade.
You would think an sfc /purgecache and sfc /scannow would fix this
particular issu, but all data from past cases indicates it will not. Its
possible that extracting the specific file its asking for and reregestering
the DLL may resolve the issue, but I could find no concrete proof of this.
Make sure you backup your data first. Here is the article for doing a fast
reapir and pertinent detail has been posted below:
238359 Differences Between Manual and Fast Repair in Windows
http://support.microsoft.com/?id=238359
I have included the steps for an inplace upgrade below the fast repair
instructions.
SUMMARY
=======
Windows includes two repair choices: Manual Repair or Fast Repair.
To see these choices, boot from the Windows installation media, press R to
repair, and then press R to use the Emergency Repair process. When you do
this, you see the following options:
- Manual Repair: To choose from a list of repair options, press M.
- Fast Repair: To perform all repair options, press F.
The two repair choices cause the Repair process to perform different tasks.
MORE INFORMATION
================
IMPORTANT: Please do not perform a manual or fast repair on a domain
controller without specific knowledge of how to back up the Active
directory database. If you do these options on a Windows 2000 Server domain
controller you run the risk of overwriting the Active directory database at
\WINNT\NTDS\ntds.dit.
The Ntds.dit file contains your Active Directory,including user accounts.
Manual Repair
-------------
The Manual Repair option provides the following choices:
[X] Inspect startup environment
[X] Verify Windows system files
[X] Inspect Boot Sector
Continue <perform selected tasks>
Inspect Startup Environment
This option checks the ARC path in the boot.ini file for a path to the
Windows boot partition and %SystemRoot% folder. It does this by using the
Setup.log file on the Emergency Repair disk by reading the following values:
[Paths]
TargetDirectory = "\WINNT"
TargetDevice = "\Device\Harddisk1\Partition1"
SystemPartitionDirectory = "\"
SystemPartition = "\Device\Harddisk1\Partition1"
If the Boot.ini file is missing, a new one is created with a valid ARC
path. If the Boot.ini file is present, the ARC path is checked and updated
if needed.
Verify Windows System Files
This selection verifies that each file in the Windows system/boot partition
is good and matches the files that were originally installed. This includes
the Ntldr, Ntdetect.com, Arcsetup.exe, and Arcldr.exe files that are used
for booting various computers. The optional Ntbootdd.sys file is never
checked. Repair performs this check by using the Setup.log file to compare
cyclical redundancy check (CRC) values for each file. If files are missing
or corrupted, you are prompted to replace or skip the file. If you choose
to replace the file, you need the Windows installation CD-ROM or an OEM
driver disk that contains the correct file(s).
Inspect Boot Sector
This option repairs the active system partition boot sector and reinstalls
the boot loader functionality. If the partition uses the FAT or FAT32 file
system and contains a non-Windows boot sector, this repair option also
creates a new Bootsect.dos file to be used to dual-boot MS-DOS, Microsoft
Windows 95, or Microsoft Windows 98 if these operating systems were
previously available to be booted. If you also select the Inspect Startup
Environment option and a new Bootsect.dos file is created, Repair adds the
following entry to the Boot.ini file:
C:\ = "Microsoft Windows"
Note that the Manual Repair option does not give you a choice to repair the
Windows registry files.
Fast Repair
-----------
The Fast Repair option performs all the repairs as the Manual Repair
option, but you are not prompted for choices. Additionally the Fast Repair
option tries to load each Windows registry file (SAM, SECURITY, SYSTEM, and
SOFTWARE). If a registry file is damaged or cannot be loaded, Repair copies
the missing or corrupted registry file from the <SystemRoot>\Repair folder
to the <SystemRoot>\System32\Config folder.
Because the Fast Repair option can replace registry files with those from
the <SystemRoot>\Repair folder, it may revert parts of your operating
system configuration back to the time when Windows was first installed. If
this occurs, you need to restore your last "system state" backup or
manually copy a more recent version of the registry files from the
<SystemRoot>\Repair\Regback folder to the <SystemRoot>\System32\Config
folder by using Recovery Console. The files that are located in the Regback
folder are from the last time you created an Emergency Repair Disk and
choose the option to also back up the registry files to the repair folder.
**********************INSTRUCTIONS FOR AN INPLACE
UPGRADE***************************************
KB article which is pasted below can be found here:
292175 How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/?id=292175
To perform an in-place upgrade of Windows 2000:
1. Insert the Windows 2000 Setup CD into the CD-ROM drive, start the
computer, and then press a key to start from the CD-ROM.
2. On the Windows 2000 Setup screen, press ENTER to run the "To set up
Windows 2000 now, press Enter" command.
3. Click Accept to accept the License Agreement.
4. Setup should now detect your installation. NOTE: If the Setup
program does not detect a previous installation but just continues to
the partitioning screen, there is a problem. An in-place upgrade may
not be possible.
5. When you are prompted to repair the existing Windows 2000
installation, press R. Windows 2000 Setup performs an in-place upgrade
of the existing installation. Note that you might lose some of your
customized settings for the system files.
Elijah Landreth [MSFT]
Microsoft Server Setup Team
Search our Knowledge Base at
http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at
http://www.microsoft.com/ntserver/
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of
Microsoft.
or opinions of Microsoft.
