7021788: Error “Internal Error Unable to Load or Call External DLL” Occurs when Uninstalling EXTRA! or RALLY! 6.5

In order to uninstall EXTRA! Personal Client 6.5 or RALLY! 6.5, you can do one of the following:

Install EXTRA!/RALLY! 6.5 Service Pack 2

EXTRA!/RALLY! 6.5 Service Pack 2 includes a fix for the error message, “Internal error, unable to load or call external DLL,” when attempting to uninstall from Add/Remove Programs.

Follow these steps to download and install Service Pack 2.

  1. Close all other applications on your desktop to ensure that no system-wide shared files are in use by the operating system during setup.

Note: If you have Windows NT 4.0, ensure that all Control Panel programs are closed or the installation may fail. Setup will not install if any EXTRA!-related programs are running.

  1. Download the file, ESP2.EXE, from the Attachmate Download Library to a temporary directory.

Note: Make sure that the environment variable TEMP is assigned to a directory with read/write access and that there is at least 1.5 MB of available space.

  1. Run the executable to unpack files.
  2. After the files are unpacked, run SETUP.EXE.

Important: If you have EXTRA!/RALLY! 6.5 Server and Client installed to the same machine, the Service Pack installation must be run twice, once to update the Server, and once to update the Client.

The Service Pack updates the Server installation (by default). To update the Client installation (when both the Server and Client installations reside on the same machine) run SETUP.EXE from the command line using the CLIENT parameter (SETUP.EXE CLIENT) which updates the client files for that system.

Note: When the Service Pack is installed, Setup makes backup copies of the original EXTRA! files that are updated. These backup files are copied to a directory called 65BACKUP, located in the directory where EXTRA! is installed.

  1. After Service Pack 2 is installed, you can uninstall EXTRA! Personal Client 6.5 and then you can also uninstall EXTRA! Personal Client 6.5 Service Pack 2.

Replace the Missing File and Modify the Registry

Follow these steps to download and replace the missing uninstall file.

Warning: Proceed with extreme caution when editing the Windows Registry. It is critical to back up the Registry before you proceed. For full details and warnings regarding editing the Windows Registry, see Microsoft Article 256986: http://support.microsoft.com/default.aspx?scid=kb;en-us;256986. Use Registry Editor at your own risk.

  1. Download the file, UNINSTNT.zip, from the Attachmate Download Library. Unzip the file. (It contains the UNINSTNT.dll file.)
  2. Copy the file, UNINSTNT.DLL, into the EXTRA! directory. By default, this is located in C:Program FilesE!PC.
  3. Open Regedit.exe to edit the Registry. Go to the following key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstallEXTRA! Personal Client 32-bit.
  4. Find the key named UninstallString.
  5. Open the key to edit the Value data to reflect the file, UNINSTNT.DLL, rather than UNINST95.DLL.
  6. Click OK and refresh the screen.
  7. Copy the updated string and go to Start > Run and paste the string into the Open: field; by default the string should be: C:WINDOWSIsUninst.exe -f”C:Program FilesE!PCDeIsL1.isu” -C”C:Program FilesE!PCuninstnt.dll” -m”Attachmate_Uninstall”.
  8. Click OK and the Uninstall will start.

Or, Manually Remove the Product(s)

Alternately, you can manually remove EXTRA! Personal Client 6.5 or RALLY! 6.5 by following these steps.

Warning: Proceed with extreme caution when editing the Windows Registry. It is critical to back up the Registry before you proceed. For full details and warnings regarding editing the Windows Registry, see Microsoft Article 256986: http://support.microsoft.com/default.aspx?scid=kb;en-us;256986. Use Registry Editor at your own risk.

  1. From Control Panel, click Add or Remove Programs.
  2. Select RALLY! or EXTRA! and click Change to open the package and change which components or features are installed.
  3. The “Run Installation Program” dialog box opens prompting for the path of the uninstall program.

Note: Do not enter anything on the command line, just click OK.

  1. Another dialog box opens, “Uninstaller Error.” There is an option to remove RALLY! or EXTRA! from the Add / Remove programs list. Click Yes.

Note: This will not uninstall the program.

  1. Remove the program group RALLY! or EXTRA! from the Program Files directory.
  2. Open Regedit.exe to edit the Registry. Remove the following keys:
My ComputerHKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionUninstallXXXXXXXXX (XXXXXXXXXX)

My ComputerHKEY_CURRENT_USERSoftwareAttachmate

My ComputerHKEY_LOCAL_MACHINESoftwareAttachmate.

Note: XXXXXXXXX (XXXXXXXXXX) represents the installed Attachmate software entry.

  1. Exit the Registry. Your edits are automatically saved.


  • No Related Posts

Meltdown – Windows Update

I need a solution

Hi, any idea when Symantec will support the Windows Update for this?

As per the links below, Symantec needs to update a registry key for Microsoft to make the update available.



Contact your Anti-Virus AV to confirm that their software is compatible and have set the following  REGKEY on the machine
Value Name=”cadca5fe-87d3-4b96-b7fb-a231484277cc”




  • No Related Posts

Citrix App Layering – User Layer Error “We were unable to attach your User Layer”

App Layering uses the file share path configured in the ELM management console to set registry keys in published images, which tell those images where to look for their user layers and elastic assignments. These registry keys are set at the time of publishing, so if the path has changed since the last time the image was published, the values will no longer align.

First, check in the ELM Management console to confirm the current file share location. Go to System->Storage Locations

User-added image

Now, make sure the highlighted file share location is the same as the registry key set on the published image where we saw the error. Open RegEdit, and navigate to HKLMSoftwareUnideskULayer and check the “RepositoryPath” key

User-added image

Finally, make sure that you are able to navigate to that directory on your virtual machine. Open up file explorer and check. If you do not have the correct share permissions, please refer to this article for additional configuration assistance: https://www.unidesk.com/support/learn/4.3.0/ms_hyper-v/itoc_2_layer_hv4/layer_user_enable_co_hv

User-added image


  • No Related Posts

Re: Windows Cluster File Server – NTFS Permissions

You can try clearing the cache and backing up again

To correctly back up Windows access control list (ACL) changes, you must leave the NTFS Last Access Time feature enabled. The NTFS Last Access Time feature is enabled by default, but is sometimes disabled for performance purposes. If you disable the NTFS Last Access Time feature on a Windows backup client and you have already performed backups, then the Avamar Client for Windows software cannot detect any further ACL changes. This means that the ACL setting for the file during the original file backup is the ACL setting that applies on all future restores. Complete the following steps to reestablish proper ACL backup behavior. Procedure 1. Enable the NTFS Last Access Time feature by using one of the following methods: l Specify a value of 0 in the following registry entry: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl FileSystemNtfsDisableLastAccessUpdate. A value of 0 enables Last Access Time, while a value of 1 disables Last Access Time. l On Windows 7, Windows Storage Server 2008, Windows Server 2008 R2, Windows Storage Server 2008 R2, Windows Server 2008, and Vista platforms, type the following command from a command prompt: fsutil behavior set disablelastaccess 0 2. Delete the following local Avamar Client for Windows cache files: l C:Program Filesavsvarf_cache.dat l C:Program Filesavsvarp_cache.dat The next backup process for the client re-creates the files.


  • No Related Posts

Missing Information Panes in Citrix Director Activity Manager For Users with High Active Directory Group Membership

Create the following reg keys on each DDC in the environment, following which each DDC must be rebooted.

If the below does not work, increase the first value to 65535 as suggested, and reboot each DDC again.


Name: MaxTokenSize


Data: 48000

(in the event of failure to resolve, increase to 65535)


Name: MaxFieldLength


Data: 65534


Name: MaxRequestBytes


Data: 16777216

The registry keys above are listed elsewhere, but have slightly higher values in this article. There is no known ill-effect of these higher values.


  • No Related Posts

All Changes Revert Back After Reboot/Shutdown And BSOD (CtxMcsWbc.sys) in XenApp 7.11

Cause 1:

“PvsVmBoot” is missing from below mentioned registry location

Path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager

Name: BootExecute


Solution 1:

  1. Shutdown the VM.
  2. Boot the VM with Hiren’s Boot ISO (http://www.hirensbootcd.org/download/)
  3. Launch Mini XP
  4. Edit registry with Registry Editor PE (Step 3: https://www.wintips.org/how-to-edit-and-modify-registry-offline/)
  5. Expand below mentioned registry location and edit “BootExecute” registry string HKEY_LOCAL_MACHINEREMOTE_SYSTEMControlSet001ControlSession Manager

User-added image

  1. Verify the same under HKEY_LOCAL_MACHINEREMOTE_SYSTEMControlSet002ControlSession Manager
  2. Close Registry Editor
  3. Remove Hiren’s Boot CD from boot order and reboot the VM.

Cause 2:

CtxMcsWbc.sys Driver is not behaving as expected

NOTE: The workaround provided below with effectively disable this driver and leave the VDA in a state that is inconsistent.

This workaround may be used for troubleshooting, but will leave the VDA in an inconsistent state. This driver controls the MCS I/O Optimization feature The full effect of disabling this driver is not clear at this point.


  1. Shutdown the VM.
  2. Boot the VM with Hiren’s Boot ISO (http://www.hirensbootcd.org/download/)
  3. Edit registry with Registry Editor PE
  4. Disable the Citrix MCS cache service by changing the Start value from 0 to 4 from the following sub key:

  5. Delete the “CtxMcsWbc” entry in the “UpperFilters” value in the following sub key:

  6. Unload the System hive from the mounted VHD.
  7. Detach the mounted VHD.
  8. Start the VM normally.


Upgrade to XenDekstop 7.15


  • No Related Posts

7.16 Unicode Keyboard Mapping and iPad and Server Keyboard Layout Mismatch

The use of 7.16 VDA, with the Unicode Keyboard Mapping feature activated, is intended to better handle this kind of keyboard layout preference issues, and has been shown to resolve cases where previous fixes for this issue did not.

To use, install 7.16 VDA – ideally, this will be part of an environment-wide upgrade, but is not strictly necessary as VDAs are generally backwards-compatible with earlier DDCs without negative impact – newer VDA features that rely on the DDC however will not be available.

Once installed, activate the feature (disabled by default) with the following registry keys:

Enable or disable Unicode keyboard layout mapping

By default, the feature is disabled on the VDA side. To enable the feature, toggle on the feature by using registry editor regedit on the VDA.

Under HKEY_LOCAL_MACHINE/SOFTWARE/Citrix, create the CtxKlMap key.

Set the DWORD value of EnableKlMap = 1

To disable this feature, set the DWORD value EnableKlMap = 0 or delete the CtxKlMap key.

Enable Unicode keyboard layout mapping compatible mode

By default, Unicode keyboard layout mapping automatically hooks some windows API to reload the new Unicode keyboard layout map when you change the keyboard layout on the server side. A few applications cannot be hooked. To keep compatibility, you can change the feature to compatible mode to support these non-hooked applications.

  1. Under the HKEY_LOCAL_MACHINE/SOFTWARE/Citrix/CtxKlMap key, set the DWORD value DisableWindowHook =1.
  2. To use normal Unicode keyboard layout mapping, set DWORD value DisableWindowHook = 0.


  • No Related Posts

How to Configure Browser Content Redirection

Browser Content Redirection controls and optimizes the way XenApp and XenDesktop deliver any web browser content (like HTML5) to users. Only the visible area of the browser where content is displayed (a.k.a viewport) will be redirected.

The following policy settings are available for Browser Content Redirection feature in Citrix Studio:

1. Browser Content Redirection

By default, Client Fetch Client Rendering is attempted unless the policy “Browser Content Redirection Proxy Configuration” is enabled too, in which case only Server Fetch Client Rendering is attempted.

If Client Fetch Client Rendering fails, server side rendering is attempted.

By default, this setting is Allowed.

Registry Override options for policy settings (Registry path varies depending on VDA architecture):




Name: WebBrowserRedirection


1 = Browser Content Redirection is Allowed.

0 = Browser Content Redirection is Prohibited.

2. Browser Content Redirection ACL Configuration

This setting allows you to configure an Access Control List (ACL) of URLs that can use Browser Content Redirection.

Authorized URLs: Specifies the whitelisted URLs whose content will be redirected to the client.

Wildcard ‘*’ is permitted, however wildcard ‘*’ is not permitted within the protocol or the domain address part of the URL.

For example, http://www.xyz.com/index.html, https://www.xyz.com/*, http://www.xyz.com/*videos* are allowed.

However, http://*.xyz.com/ is not allowed.

Better granularity can be achieved by specifying paths in the URL, for example https://www.xyz.com/sports/index.html. In this case, only index.html page will be redirected.

By default, this setting is set to https://www.youtube.com/*

Registry Override options for policy settings (Registry path varies depending on VDA architecture):




Name: WebBrowserRedirectionACL


3. Browser Content Redirection Proxy Configuration

This setting provides configuration options for proxy settings on the VDA for Browser Content Redirection feature.

If enabled with a valid proxy address and port number, only Server Fetch Client Rendering is attempted.

If disabled or left unconfigured with default value, Client Fetch Client Rendering is attempted.

Allowed pattern: http://<hostname/ip address>:<port>

For example, http://proxy.example.citrix.com:80

By default, this setting is prohibited.

Registry Override options for policy settings (Registry path varies depending on VDA architecture):




Name: WebBrowserRedirectionProxyAddress

Type: REG_SZ

4. Client Side Optimization

The following registry key can be set on the Client in order to enable HdxBrowser.exe (the overlay browser on the endpoint responsible for Client-side rendering) to use the GPU resources on the Client, hence reducing CPU utilization.




Internet Explorer



FEATURE_GPU_RENDERING (create if not present)

HdxBrowser.exe = (DWORD) 00000001


  • No Related Posts

Deployment with multiple commands on one line

I need a solution

We have a package that requires some registry keys to be injected after the install to skip a registration phase.

The following command line works when run manually:

TrackVis_setup_v0.6.1.exe /S & reg.exe IMPORT trackvis_HKLM.reg /reg:64

However, if I use this as part of a software deployment task, in the command line box, one of two things will happen:

1. If the EXE installer is run fine the application installs correctly but the registry keys are not imported.

2. If you swap them around the registry key fails to import, error code 1, and the application install is not even attempted.

For now I have added an “install.bat” to the software package and called this instead, with the installation type set to “Windows Batch Installation file”, which is not ideal and causes the batch file to appear on screen but it does work.

Does Altiris not cope well with multiple commands like this or am I doing something wrong? Suggestions would be most welcome.




  • No Related Posts