Unable to install Windows Server 2008 R1, Windows Vista or Windows 7 on a Dell PowerEdge 2600 – Setup error 0x80070022

System Requirements:

  • Dell PowerEdge 2600
  • Toshiba SD-C2502 DVD-ROM Drive

The Problem:

When you try and install an edition of NT 6 x86 on a Dell PowerEdge 2600 using self-created DVD media (DVD-R, DVD+R, DVD-RW, DVD+RW) the setup program takes a very long time to start and after around 30 minutes of “Expanding files” sitting on 0% setup fails with the error code 0x80070022.

More Info

The problem isn’t an incompatibility with the systems and NT6, it’s most likely the DVD ROM drive itself. You should of course check to make sure that the DVD-R(W) media that you are using is integral and hasn’t failed to burn properly. If the media works fine on other systems then check to see if the machine has a Toshiba SD-C2502 drive.

If it does then it is probably manufactured in or around August 2002 using firmware 1D13 (dates 03/08/2001) before all of the DVD media specifications were standardised. Dell unhelpfully neglected to supply the firmware update for the drive to support improved media compatibility. As you may have guessed, the media can get you into the setup program, but the slow speed is because of an increased number of forced read errors.

The Fix

The good news is that there is firmware available that may resolve this for you. Although Dell neglected to make it available on their PowerEdge support section, the drive is a plain old IDE drive, one that Dell used on a number of other systems. To be precise:

  • Inspiron 2500
  • Inspiron 2100
  • Inspiron 4100
  • Inspiron 8000
  • Inspiron 8100
  • Inspiron 2600
  • Inspiron 8200
  • Inspiron 2650
  • Inspiron 4150
  • Latitude C500
  • Latitude C510
  • Latitude C540
  • Latitude V710
  • Latitude LS
  • Latitude C400
  • Latitude C600
  • Latitude C610
  • Latitude C800
  • Latitude C810
  • Latitude L400
  • Latitude C640
  • Latitude V740
  • OptiPlex GX150
  • OptiPlex GX240
  • OptiPlex GX260
  • OptiPlex GX260N
  • Dell Precision Mobile WorkStation M50

So if you head to the support pages on Dell for one of those you will find the SD-C2502 firmware update which addresses:

This firmware addresses various readability related issues.

The firmware at shipping is 1D13, this updates it to 1D23 and will hopefully get you installing. If you want to search Dell Support for the file name look for br59016.exe

If that doesn’t fix it, it’s a standard IDE drive, simply grab one from any > 2003 laptop and you should be good to go.

How to recover a ‘disassociated’ Windows NT user account’s files and settings into a new profile when the SAM ID is no longer valid on the machine or domain

System Requirements:

  • Windows Vista
  • Windows Server 2008, R2
  • Windows 7

The Problem:

Take the hypothetical situation: Windows 7 fails to boot, you don’t want to lose your user data so you install 7 onto a clean partition. However your old user profile is associated with the random SAM ID from the old installation and the new Windows installation cannot mount the profile. You can copy your data files back over, but you really don’t want to configure the start menu settings for the 1,000,000th time.

Or how about: Your only domain controller failed leaving disassociated roaming profiles on a roaming profile share and you want to recover as much of the user settings and data as possible for use on the newly build AD forest. <– That actually happened to Matt, hence I day dreamed this up.

More Information:

NT user accounts are associated to a Security Account Manager (SAM) ID. The SAM ID is Windows’s SAM or the Active Directory domain user services way of identifying a user, in effect the SAM ID is a super key that identifies a user account on a windows system, acting as a GUID for that profile.

The user name itself is irrelevant and plays no part in identifying the user account apart from being used to performing a reverse lookup to get to the SAM ID, on which Windows bases its logon activities and security token generation in AD.

When you reinstall Windows, the new installation has no awareness of any of the accounts, so if you copy the profiles back into the Windows users directory you will be unable to re-associate that profile with the local SAM database.

The Fix

The simplest way of restoring user data and crucially environment settings (such as desktop wallpaper, window settings and the like) is to follow this process:

  1. Create a new user account for the user you want to migrate onto the new domain/installation
  2. Set the accounts roaming profile settings (if dealing with a roaming profile)
  3. Logon to the machine with Administrator rights
  4. Load Regedit
  5. Click on HKEY_USERS
  6. From the File menu, select Load Hive…
  7. Browse to the NTUser.dat from the previous install/roaming profile for the profile that you are trying to recover and click OK e.g.
  8. When prompted for a name just enter temp and click OK
  9. Expand and click on:
  10. From File select export and save the export file as:
  11. From File, select Unload Hive…
  12. Exit Regedit
  13. Open c:\temp.reg
  14. From the Edit menu select Replace…
  15. In Find What: enter:
    In Replace With: enter:
    Press Replace All
  16. Save the reg file and exit notepad
  17. Log off of Administrator
  18. Log on as the new user
  19. Double click on c:\temp.reg and import the reg file into the new (completely default) user account. If you are using a system with UAC you will need to import the reg file using an administrators account.
  20. Immediately log off
  21. Log back in as Administrator
  22. Go to the recovered profile folder e.g.
  23. Select all files in the folder apart from NTUser.dat, NTUser.ini and NTUser.dat.log and copy them
  24. Paste the data into the new user profile e.g.
  25. The data and the profile settings have now been recovered. Logging back in as the recovered user will restore much of the user profile and all of their data.

Note: It may be necessary to reset folder permissions and ownership on all of the files pasted into the folder to match that of the new user account.

Thanks to Matt Gillard of MGComputing for some testing of my theory.

Remote Desktop Connection (RDP) / Microsoft Terminal Server Client (MSTSC) versions & compatibility

System Requirements:

  • Windows 3.11
  • Windows 95
  • Windows 98, 98 SE
  • Windows Millennium
  • Windows NT 3.51
  • Windows NT 4.0
  • Windows 2000
  • Windows XP
  • Windows Server 2003 / R2
  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2
  • Windows 8
  • Windows Server 2012

The Problem:

Keeping track of RDP release versions. The table below contains the know version and release history for the mstsc / Terminal Services Client / Terminal Server Advanced Client / Remote Desktop Client for Windows. Mac releases are not included.

More Information:

The following table outlines the different versions of the Remote Desktop Client, their file versions and about box versions against their official compatibility between different Windows versions.

Please note that compatibility assumes that a suitable service pack level already exists on the machine to support it. For example 6.1.7600.16385 requires XP SP3.

Version ‘About’ build Encryption CPU RDP Ver 3.11 95 98 ME NT 3.51 NT 4.0 NT 4.0 TSE 2000 XP 2003 XP/2003 x64 Vista 7 2008 2008 R2 8 2012 8.1 2012 R2
4.0.1381.133 4.00.0419 x86 4.0 Y Y Y Y I (SP4)
4.0.1381.259 4.00.0419 x86 4.0 Y Y Y Y
4.0.1381.620 4.00.0419 x86 4.0 Y Y Y Y I (SP6)
4.0.1381.710 4.00.0419 x86 4.0 Y Y Y Y 317636
4.0.1381.32901 4.00.0419 x86, Alpha 4.0 N Y Y I (SP4)
4.0.1381.33027 4.00.0419 x86, Alpha 4.0 N Y Y I (SP5)
4.0.1381.33388 4.00.0419 Alpha 4.0 N N Y I (SP6)
4.0.1381.33478 4.00.0419 x86 4.0 N Y Y 317636
5.0.2195.1620 5.00.2195 56, 128 x86 5.0 Y Y Y Y Y Y Y I (SP1)
5.0.2195.2721 5.00.2195 128 x86 5.0 Y Y Y Y Y Y Y I (SP2)
5.0.2195.3895 5.00.2195 128 x86 5.0 Y Y Y Y Y Y Y I (SP3)
5.0.2195.6674 128 x86 5.0 Y Y I (SP4)
5.0.2221.1 5.00.2221 128 x86 5.0 N Y Y Y N Y Y Y
5.1.2600.0 5.1.2600 128 x86 5.1 N Y Y Y N Y Y Y I (RTM)
5.1.2600.1106 128 x86 5.1 N N Y
5.1.2600.2180 128 x86 5.1 N Y Y Y N Y Y I (SP1)
5.2.3790.0 128 x86 5.2 N Y Y Y N Y I (SP2) I (RTM)
5.2.3790.1830 128 x86 5.2 N N Y Y N Y I (SP1)
5.2.3790.3959 128 x86 5.2 N N Y Y N Y Y Y I (SP2)
5.2.3790.4524 128 x86, x64, IA64 5.2 N N N N N N N 958470 958470 958469 958469
5.2.3790.4807 128 x86 5.2 N N N N N N N N 2483618
6.0.6000.16386 6.0.6000 128 x86, x64 6.0 N N N N N N N N 925876 925876 (SP1)
6.0.6000.16459 6.0.6000 128 x86, x64 6.0 N N N N N N N N 925876 (SP2) 956744
6.0.6001.18000 x86 6.1 N N N N N N N N 952155
6.0.6001.18564 6.0.6001 x86, x64, IA64 6.1 N N N N N N N N 2481109 2481109
6.0.6001.18589 6.0.6001 x86 6.1 N N N N N N N N 2481109
6.0.6001.22840 x86 6.1 N N N N N N N N 2481109±
6.0.6002.18005 x86, x64 6.1 N N N N N N N N I (SP3) I (SP2) I (SP2)
6.0.6002.18356 x86, x64, IA64 6.1 N N N N N N N N 2481109 2481109 2481109
6.1.7600.16385 6.1.7600 x86, x64 7.0 N N N N N N N N 969084 969084 I (RTM) I (RTM)
6.1.7600.16722 6.1.7600 x86, x64, IA64 7.0 N N N N N N N N 2483614 2483614 2483614 2483614 2483614
6.1.7600.20861 6.1.7600 X86 7.00 N N N N N N N N 2483614± 2483614±
6.1.7601.17514 6.1.7601 x86, x64 7.1 N N N N N N N N I (SP1) I (SP1)
6.2.9200.16398 6.2.9200 x86, x64, Arm 8.0 N N N N N N N N N N N N 2592687 N 2592687 I (RTM) I (RTM)
6.3.9600.16415 6.3.9600 x86, x64, Arm 8.1 N N N N N N N N N N N N 2574819
N 2574819
Y Designed for this operating system, just run the installer
N Not designed for this operating system
I Integrated component of this operating system (Release/Service Pack Level)
###### Obtained via this Microsoft update knowledge base number (QFE)
<blank> Untested

± Requires a branch change to QFE or manual extraction

Error: “The procedure entry point UnmapAndCloseFile could not be located in the dynamic link library SETUPAPI.dll” when attempting to run RIPrep.exe on Windows XP or Windows Server 2003

System Requirements:

  • Windows XP Professional, SP2, SP3
  • Windows Server 2003 SP1, SP2

The Problem:

When you attempt to run the Remote Installation Service (RIS) image preparation tool (RiPrep.exe) on a Windows XP or Windows Server 2003 system with the latest service pack you receive the following error message.

riprep.exe – Entry Point Not Found
The procedure entry point UnmapAndCloseFile could not be located in the dynamic link library SETUPAPI.dll

Error: "The procedure entry point UnmapAndCloseFile could not be located in the dynamic link library SETUPAPI.dll"

This error is generated despite having the latest build of RIPrep.exe from Windows 2000 Server SP4 – 5.0.2195.6685 at the time of writing. If you do not have this build of RIPrep you should obtain the current version from Service Pack 4 and update your RIS host to SP4 before continuing.

More Information:

Microsoft’s XP SP2 secure code initiative and several years worth of code development has seen some fundamental changes in the standard setup api used on XP and Server 2003 systems. The problem is caused quite obviously by the lack of the entry point UnmapAndCloseFile in the setupapi.dll.

The Fix

Very simply, you need to give riprep.exe access to a version of the dll with that entry point.

  1. Go to your Windows 2000 Remote Installation Server (ensure that it is SP4)
  2. Navigate to %SystemRoot%\System32
  3. Copy the file setupapi.dll into the <RISPath>\Admin\i386 folder
    e.g. E:\RemoteInstall\Admin\i386
  4. setupapi.dll from Windows 2000 SP4 (version 5.0.2195.6622 as of writing) will now be next to the riprep.exe
    SetupAPI.dll version info
  5. When you run RIPrep from the \\<server>\REMINST\Admin\i386 folder, the version of setupapi.dll in this folder will be used as a higher precedent to the version in the Windows XP or Windows Server 2003 %SystemRoot%\System32 folder, and RIPrep will be able to load correctly.