Not able to launch RemoteApp connections on Windows 10 machine

Are you seeing any errors in the event logs on either side?

Do you have a test server?

I am presuming the win10 box is the client.  When you say you disabled the firewall, I presume you turned the firewall off in control panel and did not stop the service.

Do you have anti malware with an integrated network security module?

Yes, this is an end user machine (Dell XPS 15 9550 with Windows 10 Pro 64-bit).

I have tried stopping the Windows FW service, as well as disabling the AV software; issue remained. I also tried again uninstalling and re-installing the RemoteApp Work Resources but issue remains. The event logs show no errors or information regarding the issue.

Realize, for the most part, you NEVER want to stop the Windows firewall service.  Use the Windows Firewall control in Control Panel to turn the firewall off.

Can you check the Windows Security Event Log on the server for event 4625?
If you see these sourced from the machine in question, check the local security policy on that workstation
Computer Configuration->Windows Settings->Security Settings – Network security:LAN Manager authentication level.
It needs to be set to NTLMv2 Only.

I checked the Security Event log on the server and did see the 4625 event logged when trying to connect to the Work Resources on the machine having issues. However, when trying to set the "Network security:LAN Manager authentication level to NTLMv2 response Only, the issue remained." I have also tried removing and re-adding the machine to the domain and setting up the WorkResources; but issue remains. Below is the event 4625 logged on the server:


An account failed to log on.

Subject:
      Security ID:            NULL SID
      Account Name:            -
      Account Domain:            -
      Logon ID:            0x0

Logon Type:                  3

Account For Which Logon Failed:
      Security ID:            NULL SID
      Account Name:            HARDCORE
      Account Domain:            

Failure Information:
      Failure Reason:            Unknown user name or bad password.
      Status:                  0xC000006D
      Sub Status:            0xC0000064

Process Information:
      Caller Process ID:      0x0
      Caller Process Name:      -

Network Information:
      Workstation Name:      
      Source Network Address:      -
      Source Port:            -

Detailed Authentication Information:
      Logon Process:            NtLmSsp
      Authentication Package:      NTLM
      Transited Services:      -
      Package Name (NTLM only):      -
      Key Length:            0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
      - Transited services indicate which intermediate services have participated in this logon request.
      - Package name indicates which sub-protocol was used among the NTLM protocols.
      - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

I am glad your issue was resolved and wish we could have been more helpful, but it looks as if the recent updates may have rewritten registry or WMI settings which likely resolved the issue.

Since some recent Windows Updates installed, the issue is no longer occurring.