Applies to: Microsoft Windows NT, Windows 2000, Windows XP When you start your computer, you receive the error message "NTLDR is missing. Press any key to restart." The error message "NTLDR is missing" means that the Windows boot loader (NT Loader, NTLDR) cannot be found. This often occurs when the computer tries to boot from a drive other than the one Windows is installed on, due to a change in the drive configuration or because you left a bootable disk in a removable drive. But it may also be because the NTLDR file has been corrupted or deleted. First, check the boot drives to make sure that the computer is not trying to boot from a different drive to the one that contains Windows. If this does not resolve the problem, you will have to repair the NT boot loader. The easiest way to fix the "NTLDR is missing" error is to use Spotmau PowerSuite. However, if your computer is using Windows XP and you have a Windows XP installation CD you may be able to boot from this and use the Recovery Console to fix NTLDR manually instead. The tool will repair the file and report "NTLDR and NTDETECT have been recovered successfully." The Windows 2000 and Windows XP CDs supplied by Microsoft has a tool called the Recovery Console which can be used to repair errors that prevent Windows XP from starting using the command line. OEM versions of Windows XP, including computers that were supplied with Windows XP preinstalled, may not have this utility.How To: Fix "NTLDR is missing"
Symptoms
Cause
Solution
Check the boot drives
Fix NTLDR
Using the Windows Recovery Console
COPY D:\I386\NTLDR C:\
COPY D:\I386\NTDETECT.COM C:\
Last week Microsoft announced that MSE 2.0 was available for public beta testing. The cool thing is the new version of MSE installs on Windows Home Server. Here we’ll take a look at running it on WHS “Vail”.
Last week we showed you a screenshot tour of the new Microsoft Security Essentials 2.0 Beta running on Windows 7 and the current version of Windows Home Server. Since the current version of Windows Home Server is built on Server 2003, it doesn’t support the new feature of Network Protection. The feature is available in WHS Vail though, as it is built on top of Server 2008 R2. Let’s take a look at installing and running it on WHS Vail.
MSE 2.0 Beta on Vail
First put the MSE 64-bit install package into one of your Vail Server Shared Folders. You will need to use the 64-bit version because that is the only version Vail comes on.
Now on a computer connected to your network Remote Desktop into Vail and install MSE 2.0.
Run through the install wizard just like you would if you were installing it on a Windows computer.
It also includes Windows Firewall Integration so you’ll want to decide if you want to enable it or not.
A restart of the server will be required.
After the server restarts, remote back into it and you’ll see that MSE 2.0 is updating its malware definition files.
After that it will kick off the first Quick Scan but it can take several minutes to complete.
After the scan is complete, you can go into Settings \ Real-time Protection and notice the Network protection feature is supported by Vail.
Like on your desktop, the MSE icon lives in the Taskbar and will run during system startup so you don’t need to install it as a Service.
We ran a couple test viruses from eicar.com (which is a great way to make sure your Antivirus software is working) on Vail and MSE 2.0 detected and removed them successfully.
Conclusion
If you have Windows Home Server, either version 1 or are testing the beta code named “Vail”, you’ll be happy to know that MSE 2.0 will work on both versions. Although the Network Protection feature isn’t available on version 1, it’s nice to have a solid, lightweight, and easy to use Antimalware utility to protect your server. In our week of testing it, we had no issues and it seems to be working perfectly. Make sure to check out our screenshot tour of MSE 2.0 where we show it running on Windows 7 and the current version of WHS.