Why does Remote Desktop work only with the deprecated Microsoft app?

For a domain account, try entering the identity directly in the credential prompt as DOMAINuser or user@domain, then remove any cached credentials for the notebook from Windows Credential Manager before trying again. A previously saved password or an incorrectly scoped credential can make mstsc fail immediately even though another client works.

The Store app is only a client; the actual RDP service is part of Windows, so you normally should not need that app specifically. Confirm that the notebook is running a server-capable edition such as Windows 11 Pro, that your account is allowed to use Remote Desktop, and that the Remote Desktop firewall rules are enabled. Also try connecting with the notebook’s hostname or IP address rather than a saved connection profile.

Since disabling NLA did not change anything, check the authentication and authorization settings on the work notebook rather than focusing only on the client. Make sure the account or its domain group is listed under Remote Desktop Users, the Remote Desktop Services service is running, and local or corporate policy is not restricting interactive RDP logons. The fact that the old client reaches the Windows sign-in screen suggests the network path and RDP listener are probably working.

The old app may be handling the sign-in sequence differently, but its installer is not required for a fresh setup. The standard mstsc client is included with supported Windows editions. If it still fails after clearing stored credentials, test with the exact computer name and check the Remote Desktop event logs on the notebook; those should reveal whether the failure is an invalid password, a denied logon right, or an authentication-policy problem.