XP Startup Issues - The Recovery Console

The Windows Recovery Console is a fantastically useful tool if you find yourself with a PC that will not boot Windows.

There are many useful Windows startup tools such as Last Known Good Configuration and the many different flavours of Safe Mode but all of these rely on a bootable Windows system. System Restore is completely useless in this scenario since it relies on one being in Windows to use it.

The kinds of things that could couse an unbootable Windows system could be:

Corrupted boot files - e.g. NTLDR, NTDETECT.COM

Corrputed Windows system files - NTOSKRNL.EXE, HAL.DLL

The Recovery Console allows you to boot into an environment "underneath" that of your Windows installation (by using the Windows CD or by choosing it at boot time if you pre-installed it) and so you can perform major low level repairs to your Windows installation.

Follow the link below to find out how to use the Recovery Console:

http://support.microsoft.com/kb/314058/

Comments

steve said…

Thanks Muhammad. That's a good tip indeed. Only problem is you have to have already done that before a problem appears - i.e. you need to be able to boot into XP in order to set this up. But this is well worth doing. Thanks.

24 November 2010 at 09:08

http://www.arx.com/resources/white-papers/pki-solution-for-electronic-signatures.htm said…

Thanks Muhammad ! This is great link for me. This is what you need to be able to boot into XP in order to set. You did well done job..Well done man !

17 May 2011 at 11:23

Public Key Infrastructure said…

Thanks Muhammad ! This is great link for me. This is what you need to be able to boot into XP in order to set. You did well done job..Well done man !

17 May 2011 at 11:24

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

WSUS Issues

Was configuring WSUS on a Server 2016 VM for a customer recently and found the performance to be very sluggish and most of the time the client PCs would time-out and throw an error message when trying to check for updates. After much digging on different forums I came across a fix that worked nicely: Open Internet Information Services (IIS) Manager and click on Application Pools Then Right-Click on your WsusPool instance and choose Advanced Settings Scroll down to Private Memory Limit (KB) and change it from the default of 1843200 to 0 which means unlimited. Then right-click and stop the WsusPool and then start it again. Hope this works for you.

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition. However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition. This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell: reagentc /disable If you get the error message "REAGENTC.EXE: Operati...

Artifact Weblog

Search This Blog