IW 14 on Win11 - Install und Uninstall Problems/Errors

[berni123]

Hi,

recently installed RAD Studio XE4 and upgraded to IW 14 with bundled key on new Windows 11.
Problem: after cleaning up the bundled with removal tool as usual and installed iw14.2.13.exe
in RAD Studio there are no IW-Tool. No Paths are set. No Modules available. So something must be wrong.
The file Registration.log showed successfull messages but no IW in RAD at all.

Code:

- Validating license
License validated
License written to registry
Checking if Gtk2Hs\bin dir is already on the %PATH%
HKCU\Environment\PATH = %USERPROFILE%\AppData\Local\Microsoft\WindowsApps;
Looking for application\bin dir in %PATH%: C:\dev\IntraWeb XIV\bin in %USERPROFILE%\AppData\Local\Microsoft\WindowsApps;
Did not find application\bin dir in %PATH% so will add it
- UpdateSearchPathOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\Library\Win32
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W32 to Search Path
- UpdateSearchPathOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\Library\Win64
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W64 to Search Path
- UpdateGlobalsOnRegistry
SOFTWARE\Embarcadero\BDS\11.0\Globals - ForceEnvOptionsUpdate
- UpdateCPPPathsOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\C++\Paths\Win32
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W32 to Search Path
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W32 to Search Path
- UpdateCPPPathsOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\C++\Paths\Win64
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W64 to Search Path
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W64 to Search Path
- RegisterDesignTimePackage
Removing old IntraWeb Design Packages registration on: HKCU Software\Embarcadero\BDS\11.0
Updating registry: Software\Embarcadero\BDS\11.0\Known Packages adding C:\dev\IntraWeb XIV\Bin\dclIntraweb_14_DXE4.bpl
- RegisterDesignTimePackage OK
- CreateWin32LicenseFile in C:\dev\IntraWeb XIV\LiXE4W32
- CreateBCBBatchFile in C:\dev\IntraWeb XIV\LiXE4W32
- CreateWin64LicenseFile in C:\dev\IntraWeb XIV\LiXE4W64
- CreateBCBBatchFile x64 in C:\dev\IntraWeb XIV\LibXE4W64

When using the IW uninstaller unins000.exe, Windows shows error:
Runtime Error (at: 91:259): Could not call proc.

Seems that IW 14 is unable to run unter Windows 11 (23H2 used wirh all updates).

Under Windows 10 there are no problems.

Any hints whot to do and how to remove the broken install?

Regards,
Bernd

[berni123]

I found a solution to get IW14 running.
Log:
Looking for application\bin dir in %PATH%: C:\dev\IntraWeb XIV\bin in %USERPROFILE%\AppData\Local\Microsoft\WindowsApps;
Did not find application\bin dir in %PATH% so will add it

but PATH was not set.
Fixing that, I could install the component via dclIntrawebXIVXE4.bpl and it is running.

Not clear, why that went wrong ...

[harriettedkwzjq]

Hi,

recently installed RAD Studio XE4 and upgraded to IW 14 with bundled key on new Windows 11.
Problem: after cleaning up the bundled with removal tool as usual and installed iw14.2.13.exe
in RAD Studio there are no IW-Tool. No Paths are set. No Modules available. So something must be wrong.
The file Registration.log showed successfull messages but no IW in RAD at all.

Code:

- Validating license
License validated
License written to registry
Checking if Gtk2Hs\bin dir is already on the %PATH%
HKCU\Environment\PATH = %USERPROFILE%\AppData\Local\Microsoft\WindowsApps;
Looking for application\bin dir in %PATH%: C:\dev\IntraWeb XIV\bin in %USERPROFILE%\AppData\Local\Microsoft\WindowsApps;
Did not find application\bin dir in %PATH% so will add it
- UpdateSearchPathOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\Library\Win32
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W32 to Search Path
- UpdateSearchPathOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\Library\Win64
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W64 to Search Path
- UpdateGlobalsOnRegistry
SOFTWARE\Embarcadero\BDS\11.0\Globals - ForceEnvOptionsUpdate
- UpdateCPPPathsOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\C++\Paths\Win32
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W32 to Search Path
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W32 to Search Path
- UpdateCPPPathsOnRegistry
Reading registry: Software\Embarcadero\BDS\11.0\C++\Paths\Win64
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W64 to Search Path
Updating registry: adding C:\dev\IntraWeb XIV\Libxe4W64 to Search Path
- RegisterDesignTimePackage
Removing old IntraWeb Design Packages registration on: HKCU Software\Embarcadero\BDS\11.0
Updating registry: Software\Embarcadero\BDS\11.0\Known Packages adding C:\dev\IntraWeb XIV\Bin\dclIntraweb_14_DXE4.bpl
- RegisterDesignTimePackage OK
- CreateWin32LicenseFile in C:\dev\IntraWeb XIV\LiXE4W32
- CreateBCBBatchFile in C:\dev\IntraWeb XIV\LiXE4W32
- CreateWin64LicenseFile in C:\dev\IntraWeb XIV\LiXE4W64
- CreateBCBBatchFile x64 in C:\dev\IntraWeb XIV\LibXE4W64

When using the IW uninstaller unins000.exe, Windows shows error:
Runtime Error (at: 91:259): Could not call proc.

Seems that IW 14 is unable to run unter Windows 11 (23H2 used wirh all updates).

Under Windows 10 there are no problems.

Any hints whot to do and how to remove the broken install?

Regards,
Bernd

Registry Issues: The registration log shows IntraWeb is attempting to update the registry with paths and package information. However, Windows 11's security and registry handling can sometimes interfere with this process, especially with older installers.
Path Issues: The log shows it's adding paths, but it's possible these aren't being correctly recognized by RAD Studio. The %USERPROFILE%\AppData\Local\Microsoft\WindowsApps path is a common culprit, as it's often restricted.
BPL Loading: The core issue is that the dclIntraweb_14_DXE4.bpl package isn't being loaded by RAD Studio. This is why you don't see the IntraWeb components.
Uninstaller Error: The runtime error in the uninstaller suggests a problem with the uninstaller's ability to execute certain procedures, likely due to compatibility issues with Windows 11.