Invalid Boot.ini, loading from C:\Windows

The problem was caused due to a corrupted boot.ini file which is usually located in the C drive. Since I had a copy of XP Home I tried to rebuild the boot.ini as per the instructions below.

1. Insert the Microsoft Windows XP CD into the computer. Note: If you have a system recovery CD or restore CD (not a Microsoft CD) these steps will likely not work for your computer.
2. Reboot the computer with the CD and press any key when prompted to press any key to boot from the CD. If you do not receive this prompt and/or are not able to boot from the CD see document CH000217.
3. Once in the Microsoft Setup menu press R to open the recovery console.
4. Select the operating system you wish to use; if you only have Windows XP on the computer you will only have one prompt.
5. Once prompted for the password enter the Admin password and press enter.
6. Once at the command prompt type bootcfg /rebuild to start the rebuild process.
7. The rebuild process will step you through a number of steps depending upon how many operating systems you have on the computer and how the computer is setup. Below is a listing of the common steps you are likely going to encounter.
• Prompt for the identified versions of Windows installed. When you receive this prompt press Y if the bootcfg command properly identified each of the Windows operating systems installed on the computer. It is important to realize this command will only detect Windows XP, Windows 2000, and Windows NT installations.
• Prompt to enter the load identifier. This is the name of the operating system for the boot.ini. For example, Microsoft Windows XP Home users would enter Microsoft Windows XP Home edition.
• Prompt to Enter OS load options. When this prompt is received type /fastdetect to automatically detect the available options.
8. Once you have completed all the available options in the rebuild and are back at the prompt type exit to reboot the computer.

See Microsoft KB289022 for more info on boot.ini.

Take a look for yourself.

net stop bits
net stop wuauserv
regsvr32 /u wuaueng.dll /s
del /f /s /q %windir%\SoftwareDistribution\*.*
del /f /s /q %windir%\windowsupdate.log
regsvr32 wuaueng.dll /s
net start bits
net start wuauserv
wuauclt.exe /resetauthorization /detectnow

This did not solve the issue for me. I turned out that my WSUS server did not mark the old IMF update as declined. Once the old update’s status was changed to declined the update cycle was stopped dead in its tracks.

Here is what I did to get my clients checking in again.

Check the folder permissions on the SelfUpdate directory, located at C:\Program Files\Update Service\SelfUpdate. Make sure the permissions like this;

In my case the IUSR_ComputerName permission was missing.

After adding the correct permissions I looked for the re-installation msi, Selfupdate.msi. The only problem is that the SelfUpdate re-installation msi was not found on my WSUS server. Turns out in the recent WSUS update to 3.1 this installer can become corrupted and not installed on the server.

To get the Virtual Directory back I would have to install it by hand. Here are the settings you need to create it;

Open Internet Information Services (IIS) Manager. Right click on the “Default Web Site” and choose;

• New
• Virtual Directory…
• It started the VD Creation Wizard
• Alias = SelfUpdate
• Path = C:\Program Files\Update Services\SelfUpdate
• Finish the wizard.
• Right click on the newly SelfUpdate and choose Permissions.
• I added “Authenticated Users” and gave them the default rights:
• Read & Execute
• List Folder Contents
• Read

After completing these steps I ran “wuauclt /detectnow” on each of my servers. I left the workstations to check in on their own.

Within 12 hours the number of missing clients had gone from nearly 200 to less than 50. Once everyone logs in on Monday morning this number should dwindle to nothing.

I tried for most of Friday to get my keys but was unable to get past the green circle of death. Today the process was painless and carefree.

I haven’t had the time to install it yet, but look forward to doing so and seeing if the hype meets expectations.

“Spoolsv.exe – Application Error”

“The instruction at “0×77fcc2c0″ referenced memory at “0×00000000″.

“The memory could not be written.”

I popped out my trusty Troubleshooting Swiss Army Knife (read: Google) and quickly had another tool to fight the tenacious spooler.

It turns out the most common cause of the error is an abundance of .SHD and .SPL files in the spool directory. These files are created by the spooler to save the spooled data of a print job. The .SPL file comprises drawing commands and the .SHD file comprises job settings information of the print job.

To fix spoolsv.exe application error, you will have to remove these files from the system. To do this, perform the following steps on your Windows XP computer:

1. Open Control Panel, select Performance and Maintenance, select Administrative Tools and then select the Services option.
2. In the Services management console, locate the Spooler services, right-click on it and select Stop.
3. Next, open the C:\Windows\System32\Spool\Printers folder. (Here, we are assuming that your Windows is installed in the default C:\Windows folder)
4. Delete all the .SHD and SPL files from this folder.
5. Next, open the TMP folder and delete all old and unused files from this folder.
6. Finally, restart the Spooler service from the Services management console.

Just like that the users printer problems disappeared.

Setting up the connection info is a snap. You just have to enter in the URL of your site, the info of the user you want to post as and you are on your way.

I’m not sure if I will continue using Word 2007 to post as some of the advanced options for images and post layout are a bit finicky, but it is a great way for average users to use an application they are comfortable with to post to their blogs.

In related news, Jim Louderback is leaving PCMag for Revision3 and has some parting shots at Vista.  Jim was a proud supporter of Vista since the launch, but after using it extensively he has changed his tune.

To get Windows 2000 to recognize the changes you make in TZEdit you have to change the timezone you are in to a different one, i.e. from Central to Eastern, apply the change and then change it back again.  After doing this you will see the correct time on the clock.

For those of you running XP or Windows 2003 you can apply a registry edit that will fix the problem for you.  I've created the file for you here.  Save the file to your desktop, then run it accepting all prompts.

Microsoft Knowledge base article 837115 gives you the description of the errors it fixes and a link to the download.