Usage: RDACUninstUtil.exe                         v. 09.01.35.12

 RDACUninstUtil removes RDAC registry entries. If a RDAC
 install or uninstall does not complete successfully, a
 blue screen might occur during the install/uninstall or
 on system reboot. Removing the RDAC registry entries should
 resolve this problem. If RDACUninstUtil.exe is run after a
 failed install, you may need to also rerun the RDAC uninstaller
 (accessed via Windows "Add or Remove Programs"), to prepare the
 system for the next install.

 RDACUninstUtil can be run before or after performing an
 uninstall using the "Add or Remove Programs" RDAC uninstaller.

 WARNING: For RDAC v8.4 uninstall, RDACUninstUtil must be run
 prior to the "Add or Remove Programs" RDAC uninstaller, to avoid
 accidental system reboot on the last screen of the RDAC uninstaller.

 In the situation where another system is experiencing
 blue screens on boot, either copy that system's SYSTEM
 Hive to a system with the same Windows OS or attach the
 failing system disk to a bootable system (again with the
 same Windows OS). Then, run RDACUninstUtil against the
 failing SYSTEM Hive.

 If you are not sure that a RDAC uninstall completed
 successfully on the local system, you can run RDACUninstUtil
 against the current local registry. To do this, do not enter
 a hive name on the command line.

 Command Line Syntax:
 At a command prompt enter
 > RDACUninstUtil [-l logname] [-f hivename]
  or
 > RDACUninstUtil [-l:logname] [-f:hivename]

 Options / Parameters:
 -l logname = the file path and name where you would like the
              RDACUninstUtil log saved.
              If this option is not entered, a log will not be
              written.
              The directory path and directory where the log is to be
              saved, must exist prior to running RDACUninstUtil.

 -f hivename = the file path and name of the SYSTEM Hive to be
               repaired. The SYSTEM Hive, in this case, is not
               the local system's hive but is a hive copied from
               a different system or located in an attached
               system disk.
               The location of a SYSTEM Hive can be found at:
               drive:(WINDOWS or WINNT)\system32\config\system.

               ex: C:\WINDOWS\system32\config\system
                   C:\WINNT\system32\config\system

               If this option is not entered, the local system's
               HKEY_LOCAL_MACHINE SYSTEM key will be the target of
               the repair.

 Examples:

  RDACUninstUtil -l C:\regrepair.txt -f E:\WINDOWS\system32\config\system
  > The above command will repair the SYSTEM Hive located at
    E:\WINDOWS\system32\config\system and log status/errors to
    C:\regrepair.txt.

  RDACUninstUtil -f D:\Temp\badsystem
  > The above command will repair the SYSTEM Hive that was copied
    from a different system and renamed 'badsystem'.
    No status/errors will be logged.

  RDACUninstUtil -l A:\statusfile\repoutput.log
  > The above command will repair the HKEY_LOCAL_MACHINE SYSTEM key
    and log status/errors to A:\statusfile\repoutput.log.

  RDACUninstUtil
  > The above command will repair the HKEY_LOCAL_MACHINE SYSTEM key.
    No status/errors will be logged.

  Notes:
  - You MUST be logged on as local Administrator to run RDACUninstUtil.
  - If a Root-Boot system does not boot after repair, check the controllers
    preferred path status.