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

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more... but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box: \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in: UPDATE tbSingletonData SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Convert Ruckus AP from Unleashed to ZoneDirector-managed

Here is the method to convert a Ruckus Unleashed AP to one which can be managed by a Ruckus ZoneDirector controller: - Login to https://support.ruckuswireless.com/ - Click "Downloads" - Choose the correct product, e.g. Ruckus R550 - Choose a "standalone" version along the lines of 118.2.0.0.875.bl7 or something similar - Agree to terms and download the software - Connect to the AP's IP address - It should open the setup wizard, showing "Unleashed Installation" - Click "Local Upgrade" - Choose the firmware image file you just downloaded - It will upload, process, and then be ready for upgrade when you click "Yes" - After this, the ZD should detect the new AP - The new AP will then need to be approved - The new AP will then be upgraded to the correct software by the ZD - The new AP will then reboot and should be ready to use - Don't forget that, for the ZD to even detect, let alone manage the new AP, it must have enough licenses

DNS Dynamic Updates & DNS Scavenging

I was encountering an issue at a customer's site where the DNS records of their client PCs often would be behind or out of sync with the records in DHCP. Usually the IP address would be older in DNS and this was causing issues with scripts executing and network tools correctly resolving client PC hostnames to their correct IP addresses. I realised I needed to make some changes to their dynamic DNS updating configuration. After a lot of reading through Microsoft's documentation and various online forums, this is what I ended up configuring. Hopefully this may help someone, some day: - Make the DHCP server a member of the "DnsUpdateProxy" group - Create a new user account, in the "Users" OU, called "dnsdynamicupdates" - This new user only needs to be a member of the "Domain Users" group - no special privileges - Make the password strong and set it to never expire - Set this new user as the credentials used by the DCHP server in IPv4...

Artifact Weblog

Search This Blog