A few users are experiencing this problem.

Event ID: 5973

Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

And event ID: 1000

Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.2125, time stamp: 0x5a990817
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.2125, time stamp: 0x5a9909e5
Exception code: 0xc000027b
Fault offset: 0x00000000006d710b
Faulting process id: 0x6b78
Faulting application start time: 0x01d3c1fbf1890ced
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 7c1dae0b-eec7-416c-b5c9-5148b1bc7ba6
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.2068_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App

When this happens the start menu will not work. This corresponds with me enabling the roaming of C:\Users\user\AppData\Local

I'm wondering if there is a folder I should exclude from roaming.

If it's not being caused by roaming the local folder then it may be caused by some GPO settings I also changed. I did this because windows search was out of control and consuming too many resources. Unfortunately I cannot disable search completely because of Outlook. My discussion on Outlook and search I had to re enable indexing outlook.

Any guidance on this is appreciated.

So far the only fix I've come up with is temporary, which is to delete the local profile and on the next login the start menu works. After a day or 2 it stops working again. I haven't totally recreated the user profile and I'm hoping this is not the ultimate fix because that would be a PITA to have to do that for all the users that have this happen.

Hi everyone,

We have customer that has a strange issue. Only few users have this issue and not everyone. Scenario is like this, customer have roaming profiles with folder redirection. They have application that is installed on all rds servers. That application calls another program and to make this work they had to change registry entry for every users under HKCU\software\software name

Now issue here is that when some users log in path to the program changes from S (which is manually configured in registry and it is giving path to the files of program) to C: where the program is installed. My question is, is this windows error of is this the application error. I think that windows registry should not change this automatically or am I wrong? I am not sure what to do because application vendor told us that this is windows issue not application?

Hello everyone,

I've been trawling around and cannot find any info on my problem.

Server 2008 std R2 SP1 >> fully updated

Running in vmWare workstation, to test in readiness for production vSphere environment (not sure if that's relevant, it crossed my mind as I had a gotcha in RD farms in that area and uni/multicast settings)

I've worked around it by using the exact same config on Server 2008 - which is nice and stable, and in our production environment.

The TSgateway service stops with 'The following exception code "3221225477" occured in the RD Gateway server', and no other detail - this can be reproduced at will by causing a RAP to fail (which is part of my testing). It stays running reliably when authentication requests are correct and RAP is satisfied, ie: u/n + p/w are correct and the remote host being requested is allowed.

I'm keen to avoid being stuck on Server 2008 to workaround, any help appreciated !

Thanks in advance,

BP

We have Symantec End Point Installed in Servers. We found Event 4625 Which has NULL Event Logs Information found in the Logs 4625.

Can can anyone explains, How do we do the Investigation cause receiving many logs for same with Justification. 

We are in Mid of the Conclusion, and Why is this Event Generated by Whom and How?

Good afternoon all;

I have an issue and not sure how to complete this.

2012 R2 for all servers
2 connection brokers in HA, 1 license server, 1 web access server, and 5 session hosts

There are 2 session collections on there. One of them is very old and was setup by someone else. this one works fine and when people click on the RDP full desktop icon ( Not a published Remote Desktop MSTSC Remoteapp). They get all settings prefilled correctly, RDP to the connection Broker farm name, with the RD gateway...it all works.

Put in a new session collection to 2 new session hosts that were put up for this purpose.

Everything works EXCEPT the prefilling of RDP settings, as of right now they come in blank.
How do I get this to be prefilled like the old session collection?

Every time I try to modify the deployment using

Set-RDsessionCollectionConfiguration -CollectionName XXXXX -CustomRdpProperty "full address:s:broker.example.com gatewayhostname:s:rdp.example.com" -ConnectionBroker ZZZZZZ

Whenever I try to apply this it looks like its going to apply but gives
You cannot call a method on a null-valued expression 
"At line:1 char:1"

Can anyone help me get through this? or some other way to apply those settings? I was poking at this for hours today and can't find a reason why this is not applying.

I even tried copying the custom RDP session deployment configuration reg keys for the old one into the new session but that didn't work.

Goofball

Hello Expertz,

I have 1 (one) session host server and 10 users are connecting to that server using mstsc. 

The problem here is printer redirection is not happening on the server from past 3 days. I have installed the new drivers but the issue still exists.

I can print locally but when I am on the server printer redirection is not happening. There are no group policies configured on the server.  My server details windows 2016. 

Please do let me know if you have any suggestions to resolve my issue.

Thanks 

SM

Hi!

I am testing RDS 2019 with RemoteApp, and I have problems with startup splash screens. Each splash screen creates a button on the client’s taskbar and does not disappear from desktop and taskbar after the appearance of the main window. For example, I run three RemoteApp and I have three splash screens and three program windows on my desktop. And even if I close these windows, the splash screens will still remain on desktop and cannot be closed. This happens only in RemoteApp and does not occur with a remote desktop mode. I tried to recreate an RDS farm again, but it does not help.

This does not happen with all programs (having splash screen), but with many. At the same time, there were no such problems at RDS 2012R2/2016. 

As RDCB and RDSH used Windows Server 2019 with latest cumulative update (2019-01). As clients used Windows 10 1709/1809 with same update.

We have a Dell TS130 running Windows Server 2016 system which is supposed to server as a Remote Desktop Services server.  It lets two people connect via RDP and then says we have limited connections and all of the connections are in use, try again later.  Considering we have ten licenses something is clearly wrong.  The Remote Desktop Licensing Diagnoser says no problems detected.   4 licenses issued 6 left available. It sees the licenses and it issuing the licenses but only allows two connections at a time.  I spent all day yesterday  on the phone with Dell.  They can't find a problem and sent me to a Microsoft phone number which leads me to this situation.

Microsoft told me on the phone that the service ticket must be initiated online but the URL they directed me to will not allow me to submit a ticket because we don't have a support contract and it will not let me submit a per incident ticket because it says we are an "Azure Client"??  The only Azure connection is a couple of laptops that predate the server.  I'm very frustrated and I wonder if Microsoft can come up with any other ways to piss me off.

If anyone has any helpful suggestions I would appreciate them.

Error: 

Configuration:

We have few servers on WORKGROUP however i have made single server as RDS License server and on rest all servers did below configuration

<style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style>Local group policy on each server
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing

"Use the specified RD license servers" = myservername

"Set the Remote Desktop licensing mode" = Per User

Solution that i always apply to fix this by removing the REG Key and reboot the server

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

We have all the licenses and configuration in place still why we get the error after every 180 days..... What needs to do to avoid this 

Dayanand Gavas

I'm trying to set up 2019 RDS to replace our 2008R2 Terminal Server.  I used this paper as a guide, but did not publish any apps, just using session based desktops: https://gallery.technet.microsoft.com/Windows-Server-2016-Remote-ffc383fe

I have a broker server, gateway server, web server and two session hosts.  Licensing server is running on the broker server but not activated yet.  I also haven't enabled the gateway server yet as I'm just testing internally. So far I have just one collection pointing to one of the session host servers. We are not testing any remote apps, just session based desktops.

Here's the problem:

• I'm able to initially get two users connected (either directly on the broker server, or through the Remote Desktop Web Access page) If a third tries to connect, it hangs at a black screen and eventually gives the message "failed to reconnect to your remote session.  Please try to connect again".  I would expect to see a message about not enough licenses or do you want to bump someone else off.
• During the black screen time, and before the error message, the active two users get bumped off, but then automatically reconnect.
• If I then log off one or both of the active users, I'm unable to log anyone into the server again.  They all get the black screen and the error message.  At this point I'm only able to log into the server on the console.  The only way to fix this is to reboot the broker server, and the cycle begins again.

Here's what shows up in the Event Viewer on the Broker server:

• When active users get bumped out theTerminalServices-LocalSessionManager log shows an error like this: “Session 3 has been disconnected, reason code 3489660929”. Also shows reason codes 12 and 0.  Also get this error in the same log: “An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070102)”

• In the RemoteDesktopServices-RdpCoreTS Operational log, we get lots of weird errors:

-TCP socket READ operation failed, error 10054”; “RDP_TCP: An error was encountered when transitioning from StateUnknown in response to Event_Disconnect (error code 0x80072746).”;

-RDP_SEC: An error was encountered when transitioning from FStateProcessingData in response to FEventPostReceiveFailed (error code 0x80072746).”

-RDP_SEC: An error was encountered when transitioning from FStatePassthrough in response to FEventCheckAndCompleteReadsFailed (error code 0x8007139F)”.

-Failed InputMgr->GetHandles' in CUMRDPConnection::GetInputHandles at 4043 err=[0x80070102]”; “'GetInputHandles Failed' in CUMRDPConnection::GetInputHandles at 1401 err=[0x80070102]”

Here’s what I’ve tried:

• All servers are updated
• Removed and recreated my collection
• Rebooted many times
• Restarted the Windows Audio service
• Tried both from the RD Web Access page and directly connecting to the Broker server
• Tried disabling firewalls on all RDS servers

I’m kind of at a loss and it’s driving me bananas. Any suggestions would be much appreciated!

George Moore

I setup a RD Gateway on both Windows server 2016 and Windows server 2019. That should be a strainght forward process following Microsoft doc and multiple other website (https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-deploy-infrastructure).

When I try to connect I received that error message Event Log Windows->TermainServices-Gateway

The user "DOMAIN\Username", on client computer "IP", did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP". The following error occurred: "23003".

I found many documentation that claim that registering the NPS server (https://docs.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-register) should fix that issue, I register the server. Both are now in the "RAS and IAS Servers" Domain Security Group. But We still received the same error. Can in the past we broke that group effect?

I continue investigating and found the Failed Audit log in the security event log:

I have then found that thread which claim that I should disabled NPS authentifaction

https://social.technet.microsoft.com/Forums/windowsserver/en-US/f49fe666-ac4b-4bf9-a332-928a547cff77/remote-desktop-gateway-denying-connections

I try it but disabling the NPS authentification leave me a bad impression...

Did anyone have a clue why I cannot resolve the domain.

For the testing/debuging purpose and I install The RD Gateway on a AD member server in main network, no other firewall than the windows one.

The only thing I can suspect is that we broke the "RAS and IAS Servers" AD Group in the past.

Hi everyone, 

I currently have a License Server outside of a domain.
I have multiple domains with RD Servers (no trust between domains), and I want them to point to the License Server.

Based on an article and Microsoft Support, what I mention above is not possible (article doesn't mention Win Server 2016).

There's a similar question where some people answer that it IS possible, assuming Per Device CALs are used.

In my current test, the license diagnoser (installed in RD Server) shows no errors, but CALs are never vended. 

Questions:

1. Any pointers or possible solutions to have A SINGLE License Server provide licenses to multiple domains? 
2. If I include the License Server in a domain and set up trusts between all other domains (RD Servers), will a trust be set up between RD Server domains?

Links: (My account is not verified, so no links allowed)

* Article: Search for "Best practices for setting up Remote Desktop Licensing (Terminal Server Licensing) across Active Directory Domains/Forests or Workgroup"

* Other question: Search for "Terminal Services Licensing Server Cross-Domains"

Thanks!

I have Windows 10 Pro and Windows 10 Home computers, both fully up to date, nether on a Windows Domain.

Home can connect, with the (old) Windows Desktop RD client, to connect to the Pro.

Home will not connect to the Pro with the Windows Store RD Client.  The error is that the Username or password is not correct.

I've searched and see there are a lot of problems reported with connecting from the Windows Store RD client and tried some of the options suggested. I've also seen that the Windows Store RD client reputedly has better security, so good it can't connect!

So:

1) How can I connect with the Windows Store RD client?

2) Is it worth the effort of persisting with the Windows Store client or is the old desktop client just as good?

Hi All,

Just wanted to check with you all on is there a possibility to provide a maintenance window on RemoteApp collection level.

We have Production collection and Test Collection in an event we need to take down the production collection. For this purpose, we send emails to our client saying that that environment will not be available. Is there a way that we can let them know when they launch the RemoteApp?

We have 400+ end users that we need to notify when there is a maintenance window. 

BTW we have Window server 2012 R2 for all RDS servers.

I really appreciate your help.

Shekar-Technet

I'm having an issue on a single RDS 2016 server at the moment where the start menu doesn't open.  

I've gone though lots of steps including sfc /scannow  (No errors)   DISM with all the options (No Errors)

I've cleared the Registry in firewall policy\restricted services\configurable\system.

I believe the issue is that I don't have any applications registered in the get-appxpackage at all, it just comes back blanks where as on working machines I get a list of about 15.

I've tried to install the packages by hand using variations of 

Add-AppxPackage -DisableDevelopmentMode -Register C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml -Verbose 

This returns the following;

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.
An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
NOTE: For additional information, look for [ActivityId] 5597e571-c93a-001c-e6eb-97553ac9d401 in the Event Log or use the command line Get-AppxLog -ActivityID
5597e571-c93a-001c-e6eb-97553ac9d401
At line:1 char:1
+ Add-AppxPackage -DisableDevelopmentMode -Register C:\Windows\SystemAp ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Windows\Syst...ppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

If I then use Get-AppxLog -ActivityID5597e571-c93a-001c-e6eb-97553ac9d401

Time                      ID           Message
----                      --           -------
20/02/2019 17:22:29       301          The calling process is powershell.exe
20/02/2019 17:22:29       603          Started deployment Register operation on a package with main parameter: AppxManifest.xml and Options: 0. See
                                       http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       10002        Creating Resiliency File
                                       C:\ProgramData\Microsoft\Windows\AppRepository\75f29027-c919-4974-89c9-f53bb4413b5f_S-1-5-21-1787921346-3847137862-2124306101-500_1.rslc for
                                       Register Operation on Package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy.
20/02/2019 17:22:29       607          Deployment Register operation on package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy has been de-queued and is running
                                       for user FISRDS1\Administrator.
20/02/2019 17:22:29       613          Adding uri to the list of Uris: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml.
20/02/2019 17:22:29       447          GetFullyQualifiedReference from the String Resource Map for package full name:
                                       Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy and reference string: Microsoft Corporation failed.
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.visualElements windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.search windows.fileOpenPicker windows.fileSavePicker windows.cachedFileUpdater
                                       windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch windows.fileTypeAssociation windows.protocol
                                       windows.appointmentsProvider windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks
                                       windows.webAccountProvider windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService
                                       windows.appointmentDataProvider windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience
                                       windows.dialProtocol windows.restrictedLaunch windows.accountPictureProvider windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.activatableClass.collector .
20/02/2019 17:22:29       10000        About to service package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy. Setting the package state to disabled returned
                                       with 0x80070490.
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.stateExtension windows.applyDataExtension windows.repositoryExtension
                                       windows.capability windows.MRT windows.visualElements windows.alarm windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.gameExplorer windows.search windows.fileOpenPicker windows.fileSavePicker
                                       windows.cachedFileUpdater windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch
                                       windows.fileTypeAssociation windows.contentType windows.protocol windows.appointmentsProvider windows.defaultPrograms
                                       windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks windows.webAccountProvider
                                       windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService windows.appointmentDataProvider
                                       windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience windows.dialProtocol windows.restrictedLaunch
                                       windows.integrityExtension windows.licensing windows.accountPictureProvider AppSync windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.DeviceSetupManager windows.activatableClass.collector windows.certificates windows.preCompilationExtension
                                       windows.ntServices windows.wmiProviders windows.iisModules windows.performanceProviders windows.eventProviders windows.runTime
                                       windows.DeviceAccess windows.indexedDB windows.MicrosoftAccountClient.SignOut windows.searchIndexer windows.geolocation windows.userDataAccess
                                       windows.repositoryExtension.remove windows.stateExtension.remove .
20/02/2019 17:22:29       827          Capability parsing started for the package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy
20/02/2019 17:22:29       5252         An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       306          error 0x800705AA: While processing the request, the system failed to register the windows.stateExtension extension due to the following error:
                                       Insufficient system resources exist to complete the requested service.
                                       .
20/02/2019 17:22:29       316          error 0x800705AA: Cannot register the request because the following error was encountered during the registration of the windows.stateExtension
                                       extension: Insufficient system resources exist to complete the requested service.
                                       .
20/02/2019 17:22:29       5252         An internal error occurred with error 0x80070002. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       331          error 0x80070002: While reverting the request, the system failed to de-register the windows.stateExtension extension due to the following
                                       error: The system cannot find the file specified.
                                       .
20/02/2019 17:22:29       300          error 0x80073CF6: Cannot register the Microsoft.Windows.Cortana_cw5n1h2txyewy package due to the following error: Package could not be
                                       registered.
                                       .
20/02/2019 17:22:29       605          The last successful state reached was ResolvedDeferredRegistrations. Failure occurred before reaching the next state RegistrationChanged. hr:
                                       0x80073CF6
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.stateExtension windows.applyDataExtension windows.repositoryExtension
                                       windows.capability windows.MRT windows.visualElements windows.alarm windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.gameExplorer windows.search windows.fileOpenPicker windows.fileSavePicker
                                       windows.cachedFileUpdater windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch
                                       windows.fileTypeAssociation windows.contentType windows.protocol windows.appointmentsProvider windows.defaultPrograms
                                       windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks windows.webAccountProvider
                                       windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService windows.appointmentDataProvider
                                       windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience windows.dialProtocol windows.restrictedLaunch
                                       windows.integrityExtension windows.licensing windows.accountPictureProvider AppSync windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.DeviceSetupManager windows.activatableClass.collector windows.certificates windows.preCompilationExtension
                                       windows.ntServices windows.wmiProviders windows.iisModules windows.performanceProviders windows.eventProviders windows.runTime
                                       windows.DeviceAccess windows.indexedDB windows.MicrosoftAccountClient.SignOut windows.searchIndexer windows.geolocation windows.userDataAccess
                                       windows.repositoryExtension.remove windows.stateExtension.remove .
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.visualElements windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.search windows.fileOpenPicker windows.fileSavePicker windows.cachedFileUpdater
                                       windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch windows.fileTypeAssociation windows.protocol
                                       windows.appointmentsProvider windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks
                                       windows.webAccountProvider windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService
                                       windows.appointmentDataProvider windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience
                                       windows.dialProtocol windows.restrictedLaunch windows.accountPictureProvider windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.activatableClass.collector .
20/02/2019 17:22:29       10001        Finished servicing package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy. Setting the package state to enabled returned
                                       with 0x0.
20/02/2019 17:22:29       401          Deployment Register operation with target volume C: on Package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy from:
                                       (AppxManifest.xml)  failed with error 0x80073CF6. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       404          AppX Deployment operation failed for package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy with error 0x80073CF6. The
                                       specific error text for this failure is: An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160
                                       for help diagnosing app deployment issues.

I can't seem to get the system to re-register those applications!

Open to any suggestions?  (Please no, have you restarted the server!)

This happens on all users including local admin and new accounts.  Happens in Safe and Clean Boot.

Thanks.

Everything was working fine until about 2 months ago.

I have a Windows 7 system that I access with Remote Desktop Connection from a Windows 10 system.  One day I found that my user account, which had been given administrator rights quite some time ago, couldn’t log on remotely.  The Windows 7 system was configured for remote access with the setting “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”. When I tried to log on, I got an error stating “The Local Security Authority cannot be contacted”. 

If I configured Windows 7 to “Allow connections from computers running any version of Remote Desktop (less secure)”, then I could log in but I didn’t want to use this less secure setting.

Doing some experimentation, I found that if I enabled the built-in Administrator account, then the Administrator could log in remotely using “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”.

If I created a new standard user called Test.  I found that Test could also could log in remotely using “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”.

If I promoted Test to an administrator, then Test couldn’t remotely log on.  He got the LSA error.  If I demoted my account to a standard user then I could log in remotely using “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”.

When I promoted my account back to an administrator, the logon failed with the LSA error.

All users have valid passwords that are set to never expire and are members of the Remote Desktop Users group.  The only thing that is changing is whether or not the users have administrative privileges.

Is this a permissions issue, or a behavior change cause by an update to Windows 7?

Mark Wilson

Hey TP [] looking for you to do some consulting work, see here:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/f18f0cc6-a1c8-40d0-984b-7a5b8af2b0a3/rds-consulting-and-services?forum=winserverTS#f18f0cc6-a1c8-40d0-984b-7a5b8af2b0a3

Just need a way to contact you.

We have one user who gets this "RemoteApp Disconnected" very frequently.

I have 1 Server that can't RDP or be RDP'd, access file shares or have its file shares accessed from other servers on a different subnet. 

I can access the file shares and RDP to and from it from other servers in the same subnet. 

Windows Firewalls are off, no I cannot change the IP address for testing because web and application services are dependent upon it. 

Other servers can access shares and RDP across the subnets just fine. It's literally just this 1 server that's having the issue.