Hi Hua Li,
The problem resides locally on Computer A. Following the feature update on Computer B, its security negotiation parameters refreshed, but Computer A is still silently passing an outdated, cached authentication token. Windows prioritizes this hidden token over what you type, which is why it constantly returns an incorrect password error despite your accurate input.
To resolve this, you must flush the corrupted cache on Computer A. Open the Start menu on Computer A, search for Credential Manager, and open the Windows Credentials tab. Look through the list for any saved passwords that reference Computer B's hostname or IP address, expand them, and click Remove. This action destroys the stale secure channel.
When you attempt to reconnect and the login prompt appears, you must explicitly define the authentication target to prevent Windows from mistakenly passing a Microsoft Account PIN or local credential. You do this by typing Computer B's exact device name, followed by a backslash, and then the username. For example, type TargetComputerName\Username into the login field. This exact syntax forces the system to authenticate directly against the upgraded server's local database, ensuring your password is processed correctly.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN