Below is the recipe to resize the virtual hard disk:

Part 1:

The first part is to resize the container of the partition, which is done by means of a sector copy. After the resize completed,  the container will have increased but the partition will not be fully extended yet.

1. Download VHD Resizer from VMToolkit.
2. Install and run VHD Resizer.
3. In the file open dialog select the VHD that you want to resize.
4. Type in the new filename to use for the extended VHD.
5. Type in the size of the new container to create.
6. Click on Resize. The process takes a few minutes…

Part 2:

Now that the container is resized, we must now extend the partition to make use of the full container size.

1. Attach the new extended VHD as a non-primary drive to another virtual machine. Do not extend the partition using the virtual machine that will make use of it.
2. Start the virtual machine to which the extended VHD was attached as the non-primary drive and open a command prompt.
3. Type in diskpart and press Enter.
4. Type in list disk.
5. Ensure that disk 1 or greater is the extended disk.
6. Type in select disk 1.
7. Type in list partition.
8. Ensure that the partition sizes matches the old size.
9. Type in extend.
10. Wait for the process to complete and type exit.

Remember to change the disk on the original virtual machine to now use the extended disk. The disk is now resized and ready to be used from the original virtual machine.

Although the error is rather annoying, there is a simple fix for it. I have replicated the steps here for your convenience:

Step 1: Start Registry Editor

Start Registry Editor.

Step 2: Delete the UpperFilters registry entry

1. In Registry Editor, expand My Computer, and then expand HKEY_LOCAL_MACHINE.
2. Expand SYSTEM, and then expand CurrentControlSet.
3. Expand Control, and then expand Class.
4. Under Class, click {4D36E965-E325-11CE-BFC1-08002BE10318}.
5. In the details pane of Registry Editor, on the right side, click UpperFilters.Note You may also see an UpperFilters.bak registry entry. You do not have to remove that entry. Click UpperFilters only.
   • If you see the UpperFilters registry entry in the details pane of Registry Editor, go to step 6.
   • If you do not see the UpperFilters registry entry, you still might have to remove the LowerFilters registry entry. To do this, go to “Step 3: Delete the LowerFilters registry entry.”
6. On the Edit menu, click Delete.
7. Click Yes when you receive the following message:

   Are you sure you want to delete this value?

The UpperFilters registry entry is removed.

Step 3: Delete the LowerFilters registry entry

1. In the details pane of Registry Editor, on the right side, click LowerFilters.Note You might see a LowerFilters.bak registry entry. You do not have to remove that entry. Click LowerFilters only.

   If you do not see the LowerFilters registry entry, unfortunately this content is unable to help you any more. Go to the “Next Steps” section for information about how you can find more solutions or more help on the Microsoft Web site.

2. On the Edit menu, click Delete.
3. Click Yes when you receive the following message:

   Are you sure you want to delete this value?

   The LowerFilters registry entry is removed.

4. Exit Registry Editor.

The article recomends restarting the computer after deleting the two registry entries, but I have found that it works fine without restarting.

This article by Microsoft describes the process to follow when rebuilding the COM+ Catalog. I’ve duplicated the steps here for ease of reference:

1. Rename the %WinDir%\System32\Clbcatq.dll file to %WinDir%\System32\~Clbcatq.dll. Make sure that you include the tilde (~) at the start of the file name.
2. Restart the computer.
3. Start Registry Editor (Regedt32.exe).
4. Locate and delete the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3
5. At a command prompt, type cd %windir%, and then press ENTER.
6. At a command prompt, type rmdir /s Registration, and then press ENTER. This is the location folder of the registration database. Note: If you have MS04-012 installed, you must now re-install MS04-012. For more information about security update MS04-012, click the following article number to view the article in the Microsoft Knowledge Base: 828741
7. Click the Start button, point to Settings, and then click Control Panel.
8. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
9. Click Next to go through the reinstallation process, to reinstall COM+.
10. If IIS is installed on the computer, IIS creates several COM+ applications. These applications will now be missing. To re-create these applications, run the following command at a command prompt: rundll32 %windir%\system32\inetsrv\wamreg.dll, CreateIISPackage

Trying to look into this issue, I opened the SQL Server Configuration Manager and then received the following error:

“Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.
Initialization failure [0x80041014]“

This is not pretty. I went to Google the issue and discovered this post. It seems like the WMI repository corrupted when I did the restore. Nice. So, I followed the instructions detailed in the post, but no luck. It still returned with the same error that I received in the beginning.

The WMI Repository was corrupt in its entirety. How do you rebuild the WMI Repository? Not so easy it seems. Lukcily there is post describing the whole process with a neat little batch file that will rebuild the WMI Repository for you, came in very handy.

Note: Execute the following commands from this directory: C:\Program Files\Microsoft SQL Server\90\Shared

Here is the batch file duplicated for convenience:

net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository

regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll

mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl

for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s

echo DONE
pause

mofcomp sqlmgmproviderxpsp2up.mof

After performing the above steps, I rebooted the server and Team Foundation Server upgraded successfully.