No longer able to install WSERemoteApp

0

Hi,

I have Windows Server 2022 Datacenter. I have WSEE installed and I had WSERemoteApp. But recently it was telling me it was not supported. I downloaded the latest version and tried installing it but got a message ‘The add-in cannot be installed on the server.”.

I also started getting the error that WSERemote App is no longer supported when trying to start any program.

So naturally I decided to uninstall the add in and try installing it but ended up having the error.

What do you recommend I do?

Screenshots
WSE RemoteApp
  • You must to post comments.
Filter
Sort by: Oldest First
Post Answer
1

Hmm… I’m not exactly sure what’s going on there. Please try the following to see if it resolves the issue for you:

1. Sign in to your Essentials server as an Administrator.

2. Open the following folder on the Essentials server:

C:\ProgramData\Microsoft\Windows Server\Data\addins

NOTE: The ProgramData folder is a hidden system folder, and so you’ll need to enable the viewing of hidden files and folders in order for you to be able to see its contents. That can be done using the “Folder Options” Control Panel applet (via its “View” tab).

3. In the “packages” subfolder, delete the file named “009ef2c9-1a5c-4564-8156-92b85d9d7705.wssx” (if it exists).

4. In the “msi” subfolder, delete the entire subfolder named “009ef2c9-1a5c-4564-8156-92b85d9d7705” (if it exists).

5. Open the following folder on the Essentials server:

C:\ProgramData\Microsoft\Windows Server\Data\settingsproviderdata\WEBSERVICESPLATFORM\ADDINS

6. Look through all of the .xml files that are in that folder until you find the one that corresponds to WSE RemoteApp (just double click on the .xml file to open it in the web browser, or you can open it in any text-based reader app such as Notepad, WordPad, etc. and then search its text contents for “WSE RemoteApp” to know that you’ve located the correct .xml file). Once you’ve located the correct .xml file, go ahead and delete it from your Essentials server (note that you can also delete its corresponding .bak file as well).

NOTE: This simple text-based file contains installation information, etc. about the WSE RemoteApp add-in (such as its version number, etc.). It will be automatically recreated the next time you perform an installation of the add-in.

7. Download the latest release of the WSE RemoteApp Updater from here (as of this writing, the current/minimum release is Version 1.255.2103.0).

8. Run the WSE RemoteApp Updater program from the desktop of the Essentials server.

Does that resolve the issue for you?

  • You must to post comments.
0

Hi Mike,

Thanks for the quick reply. I tried the file deletion then run the latest install and got the same error.

What is interesting is that the files got recreated.

While following your guide I saw a log folder and this is what I see in there after the install:

———————————————————
[44540] 260710.213032.9416: Addins: Parsed command line args for InstallAddin.exe. Path=C:\Users\Administrator.TECHNOBUG\AppData\Local\Temp\n0d5uu0f.wssx,Silent=False,ClientInstall=False
[44540] 260710.213033.1727: General: VerifyPackageResult=OkToInstall
[44540] 260710.213033.1757: General: DoInstall=True
[29272] 260710.213033.2667: Addins: Looking for EULA at: Eula-en-GB.rtf
[29272] 260710.213033.2692: Addins: Looking for EULA at: Eula-en.rtf
[29272] 260710.213033.2692: Addins: Extracting EULA: Eula.rtf
[44540] 260710.213033.5742: General: VerifyPackageResult=OkToInstall
[44540] 260710.213033.5748: General: DoInstall=True
[44540] 260710.213033.7078: InstallAddinWizard: Created wizard with addin of type: Microsoft.WindowsServerSolutions.Console.AddIns.AddinPackages.PackageAddin
[44540] 260710.213052.7363: Addins: Async operation did not complete: Error=Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInException: InstallError
   at Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInManager.PerformAction[T](ProviderConnector`1 connector, Action`1 action, Boolean waitForCallback)
   at Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInManager.<>c__DisplayClass66_0.<InstallAddInAsync>b__0(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
[44540] 260710.213052.7403: Exception:
—————————————
An exception of type ‘Type: Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInException, AddinInfrastructure, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ has occurred.
Timestamp: 07/10/2026 21:30:52
Message: InstallError
Stack:    at Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInManager.PerformAction[T](ProviderConnector`1 connector, Action`1 action, Boolean waitForCallback)
   at Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInManager.<>c__DisplayClass66_0.<InstallAddInAsync>b__0(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
[44540] 260710.213057.0268: Addins: Exiting with return code: -1
  • You must to post comments.
0

Some more logs that might be  helpful

https://1drv.ms/u/c/8162175425df9132/IQCKH_tBbmukQLeRnnxjxVRJAYqFCbR9jqZ3h5gJOiJbhZc?e=BeEtRl

  • You must to post comments.
0

I’m not seeing much in that log blurb that you posted, and I can’t access your one drive logs. So…

Are you running the WSE RemoteApp Updater from the server, or from one of your connected client computer? If the later, then try running it directly from the server instead.

Is the WSEE Installer on your Windows Server 2022 up-to-date? If not, then download the latest WSEE Updater from here.

If the latest release of WSE RemoteApp still won’t install, then you might want to try completely removing it from your Essentials server, rebooting, and then installing it again. To do so… Open the server Dashboard, go to the “APPLICATIONS” page, select the WSE RemoteApp add-in, and then click on the “Remove the add-in” task. Reboot the server afterwards, and then reinstall WSE RemoteApp via the latest full installer that can be downloaded from here.

Other than that… Take a look in the server’s “Logs” folder to see if any of the logs in there give any additional information as to why the installation is failing. You can find the server’s Logs folder here:

C:\ProgramData\Microsoft\Windows Server\Logs

If you sort the folder by date modified, then the most recently written to log files will appear up at the top of the folder.

You might also want to take a look in the Windows Logs -> Application log of the Event Viewer to see if anything of interest shows up in there as well.

  • You must to post comments.
0

Everything is on latest.

I followed the instructions still same issue.

The error is on the WSERA.ServerSetup.log file but it is too big. That is what I had on the onedrive link, not sure why you are not able to open it. I tested it with a private window and it works fine.

Here are the lines that have error:

MSI (s) (3C:28) [22:16:23:394]: PROPERTY CHANGE: Adding WSERARDWebErrorDir property. Its value is ‘C:\Program Files\The Office Maven\WSE RemoteApp\RDWeb\Error\’.

MSI (s) (3C:28) [22:16:23:608]: Dir (target): Key: WSERARDWebErrorDir , Object: C:\Program Files\The Office Maven\WSE RemoteApp\RDWeb\Error\

MSI (s) (3C:D0) [22:16:24:580]: Hello, I’m your 64bit Elevated Non-remapped custom action server.
SchedSecureObjectsRollback: Failed to store ACL rollback information with error 0x80070003 – continuing

MSI (s) (3C!A0) [22:16:24:725]: MSI_LUA : Custom Action ‘ExecSecureObjectsRollback_64’ is running with sufficient privileges.
Action ended 22:16:24: ExecSecureObjectsRollback_64. Return value 1.
SchedSecureObjectsRollback: Failed to store ACL rollback information with error 0x80070002 – continuing

MSI (s) (3C:D8) [22:16:30:345]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI60C8.tmp, Entrypoint: ExecSecureObjects
ExecSecureObjects: Error 0x80070002: failed to get security info for object: CLASSES_ROOT\CLSID\{F02C1A0D-BE21-4350-88B0-7367FC96EF3C}\ShellFolder
CustomAction ExecSecureObjects_64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 22:16:30: InstallFinalize. Return value 3.

MSI (s) (3C:28) [22:16:34:115]: Error in rollback skipped. Return: 5

MSI (s) (3C:28) [22:16:34:175]: Windows Installer installed the product. Product Name: WSE RemoteApp Windows Server Solutions Add-in. Product Version: 1.255.2103.0. Product Language: 1033. Manufacturer: The Office Maven. Installation success or error status: 1603.

MSI (s) (3C:28) [22:16:34:183]: Deferring clean up of packages/files, if any exist
MSI (s) (3C:28) [22:16:34:187]: MainEngineThread is returning 1603
MSI (s) (3C:20) [22:16:34:195]: RESTART MANAGER: Session closed.
MSI (s) (3C:20) [22:16:34:200]: No System Restore sequence number for this installation.
MSI (s) (3C:20) [22:16:34:210]: User policy value ‘DisableRollback’ is 0
MSI (s) (3C:20) [22:16:34:216]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (3C:20) [22:16:34:221]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (3C:20) [22:16:34:225]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (3C:20) [22:16:34:230]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (3C:20) [22:16:34:235]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (3C:20) [22:16:34:240]: Destroying RemoteAPI object.
MSI (s) (3C:40) [22:16:34:245]: Custom Action Manager thread ending.
MSI (c) (60:20) [22:16:34:251]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (60:20) [22:16:34:256]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/07/2026 22:16:34 ===

 

Nothing in C:\Program Files\The Office Maven\WSE RemoteApp\RDWeb\Error\, `WSE RemoteApp` does not even exist.

  • You must to post comments.
Showing 5 results
Your Answer
Post as a guest by filling out the fields below, or you may to post using your existing user account (register to create a user account if you do not already have one). Guest's questions will be moderated before being posted. NOTE: Your email address will not be published, nor will it be used for marketing purposes, etc. (as per our privacy statement).
Name*
E-mail*
Answer Details*
Screenshots
File Name Size
There are currently no files uploaded.
Maximum number of files 4, maximum file size 5MB.
Supported file formats: gif jpeg jpg png

Featured Questions

Recent Questions & Answers

Q&A Toolbox

Log in | Register

Ask a question

View all questions