Windows 10 Start Menu, Cortana, Not Working for Domain Users, But OK for Local Users

I looked at several of the posts out there about the issue where Windows 10 system Start Menu, Cortana, etc works fine with a local account, but when added to the domain, Start Menu hangs and Cortana/Windows Search does not work.

I tried copying the file(folder) ‘C:\Users\Administrator\AppData\Local\Packages\windows.immersivecontrolpanel_cw5n1h2txyewy’ to C:\Users\\AppData\Local\Packages\windows.immersivecontrolpanel_cw5n1h2txyewy’.

Didn't work.  Plus, the folder was the same size as what I copied.  Thought it may have been corrupted, but no change.

Went to the event log (should have went there first) and noticed all these errors from source:ESENT dealing with logging/recovery.  Error details was:
WebCacheLocal database recovery restore failed with unexpected error - 1907

Looked this up and found that deleting (actually renamed) the C:\Users\Administrator\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat.   Now the start menu and Cortana works properly.  Wierd, but resolved.  Thanks to Cannot open up Microsoft Edge or Internet Explorer in newly created profiles

WinRM Error number: -2144108526 0x80338012

I have two Windows 2012 servers in a Windows Failover cluster.  I was trying to look at the shares under the Fileserver role.  It kept spinning and returned error: “There were errors retrieving the file shares.”  One of the troubleshooting steps is to check WinRM.

When running the command:  winrm id -r:myserver
I received the standard error:


 Message = The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".  Error number:  -2144108526 0x80338012




On my workstations, winrm is working correctly, so I was unsure where the problem was.


When I run winrm enumerate winrm/config/listener  I got this weird:


Listener [Source="GPO"]
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = null
Listener [Source="Compatibility"]
    Address = *
    Transport = HTTP
    Port = 80
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = null
Listener [Source="Compatibility"]
    Address = *
    Transport = HTTPS
    Port = 443
    Hostname = server.network.home
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint = d1 ef b5 c3 64 48 c1 24  9b 3f h8 24 bb 68 8f 0354 27 64 df
    ListeningOn = null




The "ListeningOn = null" was strange.  I have WinRM configured using group policy.  After some research, discovered article Unable to Use Server Manager Remotely to help me realize that my group policy IPv4 filter was not set.  The article suggested that I create a new instance of the HTTP Listener for all IPs using (winrm create winrm/config/Listener?Address=*+Transport=HTTP )  .  But I have that configured in GPO.  I double checked between the two GPOs that I have for clients and servers, and discovered that I did not set an IPv4 filter for servers.


Once I entered it, ran gpupdate on servers and restared WinRM Service, all was good again.