Windows SteadyState version 2.5 succeeds Windows SteadyState version 2.0 while the Shared Computer Toolkit for Windows XP is an earlier version of Windows SteadyState. You must uninstall any previous versions before you can install Windows SteadyState version 2.5. Follow the steps below to uninstall the Shared Computer Toolkit. Step 1: Turn off Windows Disk Protection On the Start menu click Programs, then click Microsoft Shared Computer Toolkit to open the Shared Computer Toolkit. Click Windows Disk Protection. Click Keep Off. Restart the computer when prompted.
Step 2: Remove user accounts created by the Shared Computer Toolkit From the Windows Control Panel, open User Accounts. Select the user to be deleted. Click Remove, then click Yes.
Step 3: Uninstall Shared Computer Toolkit On the Start menu, click Programs, click Microsoft Shared Computer Toolkit, then click Uninstall the Shared Computer Toolkit. A message appears stating: "Removing the Toolkit will automatically restart the computer." Click Remove to begin the uninstall. Click Finish to restart your computer.
Step 4: Remove the User Profile Hive Cleanup Service (UPHClean) On the Start menu, click Settings, click Control Panel, click Add or Remove Programs, then click Remove Program. Select User Profile Hive Cleanup Service, then click Remove. When prompted to confirm that you want to uninstall the program, Click Yes to begin uninstalling UPHClean. The uninstall takes approximately five seconds to complete.
| | Remove the partition used for Windows Disk Protection | When you first set up Shared Computer Toolkit, you were required to create a separate partition for Windows Disk Protection. This partition is not required by Windows SteadyState, so you can now remove this partition and reclaim the hard disk space. |
|
| | What's Next | After you have uninstalled the Shared Computer Toolkit, your next steps are:
|
|
|  | |  | Learn more and download Windows SteadyState. Watch the demonstrations for a quick overview. Refer to the handbook for further information. The Technical FAQ may have the answers you need. Others in the Windows SteadyState Community may have experiences you can learn from. |