<div>
Check local group policy to see whether it is set to talk to the wsus. &nbsp;Look in c:\windows\windowsupdate.log to see what it is reporting. 
Is it trying but failing to connect or gas other issues/errors.
</div>

<div>
Related to proxy settings? 
 
If yes, the info below may be useful for you. 
 
&quot;I found cause of issue. 1. Windows 10 couldn't connect to wsus due to proxy settings (Win7 and Win8 had no problem with our proxy settings), I added proxy exception for wsus address. 2. We use alias DNS name for wsus server (name of server wsus.domain.com and alias is sus.domain.com), but we had SSL certification on IIS for WSUS site to use certification from our CA with name of server (wsus.domain.com). When I set new cert with name sus.domain.com for WSUS in IIS every PC connected without problem.&quot; 
 
Source: <a href="https://www.reddit.com/r/sysadmin/comments/3zf2ly/windows_10_computers_are_not_reporting_to_new/" rel="ugc">https://www.reddit.com/r/sysadmin/comments/3zf2ly/windows_10_computers_are_not_reporting_to_new/</a>
</div>

<div>
I had stated I had already looked at the clients Local Group Policy (RSOP.MSC) and the policy looks identical too all my other clients. As I had also stated the client did communicate with the WSUS server for a few weeks so I do not see this as being a certificate issue, as I have another Surface Pro 2 running Windows 10 that is communicating with it's own WSUS server. Any other thoughts?
</div>

<div>
What does the log show? Get baretail app, attach it to the windowsupdate.log file in follow mode, in elevated cmd run wuauclt /detect now and see what the log reports. 
Does it reflect access attempt to the local wsus server but failing, double check what the wsus server name resolves to to make sure it is not being overridden by an entry in c:\windows\system32\drivers\etc\hosts 
To make sure there is no ip wsus name defined there that points to the wrong ip.
</div>

<div>
We do &nbsp;not use a proxy at our locations, so the proxy is not an issue with this problem. Please keep in mind that this client was until a few weeks ago working fine connecting to WSUS. And the odd thing is that when I am at the client machine, and check for updates manually, it appears that the machine is obtaining it's updates and installing the updates, it just never notifies the server that the updates have been downloaded and installed. Also keep in mind that I have a duplicate Surface Pro2 at another location running Windows 10 on a different WSUS server, and group policy is exactly the same in both locations, and the Surface Pro 2 running Windows 10 is notifying the server with no issues.
</div>

<div>
When I get back to this location where I can get to the client, I will check the log files
</div>

<div>
So if anyone has any ideas with regards to the Windows 10 Update logs so I can obtain a bit of further assistance with this issue, here is a sample from the Windows 10 Client. 
016/03/30 11:04:56.6569641 964 &nbsp; 8052 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;* START * &nbsp; Init Search ClientId = UpdateOrchestrator 
2016/03/30 11:04:56.6569713 964 &nbsp; 8052 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;* START * &nbsp; Search ClientId = UpdateOrchestrator 
1600/12/31 18:00:00.0000000 964 &nbsp; 8052 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 18): GUID=4826f9c4-097a-f578-4845-bc95f26d5618 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 8052 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 119): GUID=f0c8e076-d97b-0fc6-05b2-d4a86c289aec (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 8052 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 123): GUID=f0c8e076-d97b-0fc6-05b2-d4a86c289aec (No Format Information found). 
2016/03/30 11:04:56.6602985 964 &nbsp; 8052 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Search ClientId = UpdateOrchestrator 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 20): GUID=4826f9c4-097a-f578-4845-bc95f26d5618 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 208): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 210): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 211): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 212): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 213): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 214): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 216): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 14): GUID=660c3846-d8b2-5440-48f2-9b67dac5f6cf (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 19): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 133): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 153): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 127): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 16): GUID=f3e52454-7646-4b91-8b2d-69132483d289 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 57): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 65): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 203): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 47): GUID=4826f9c4-097a-f578-4845-bc95f26d5618 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 312 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Unknown( 246): GUID=013afb4f-79c8-ea23-6ccd-39d1b3a02391 (No Format Information found). 
2016/03/30 11:04:58.2409167 964 &nbsp; 2072 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;*RESUMED* Search ClientId = UpdateOrchestrator 
2016/03/30 11:04:58.2417150 964 &nbsp; 2072 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Updates found = 0 
2016/03/30 11:04:58.2417164 964 &nbsp; 2072 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;* END * &nbsp; Search ClientId = UpdateOrchestrator 
2016/03/30 11:04:58.2421943 964 &nbsp; 8052 &nbsp;ComApi &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;ISusInternal:: DisconnectCall failed, hr=8024000C 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 14): GUID=660c3846-d8b2-5440-48f2-9b67dac5f6cf (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 133): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 153): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 127): GUID=cca8e6da-2811-3870-a850-a4f88966ba29 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 14): GUID=660c3846-d8b2-5440-48f2-9b67dac5f6cf (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 16): GUID=f3e52454-7646-4b91-8b2d-69132483d289 (No Format Information found). 
1600/12/31 18:00:00.0000000 964 &nbsp; 6844 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Unknown( 17): GUID=20df0e09-6ce9-bd6d-3996-d851bd253999 (No Format Information found). 
 
Also I removed WSUS and IIS from the server, and reinstalled the roles. I really have no idea if this is going to fix my issue but I thought it was worth the try. As of right now 20 minutes later and the client still has not checked in.
</div>

<div>
Due to the fact that I was willing to try anything. The removal of IIS and WSUS and the reinstalling the 2 roles did actually nothing, so now I will try your other suggestions. But my biggest question Arnold, did you see anything in the logs that I need to be overly concerned about? Other than the suggestions you have asked me to try?
</div>

<div>
Nothing to be concerned about, it seems the log reflects a list of updates either in the downloads or in the DB that updates maintains that it things are needed, but do not validate or are unknown, flushing the softwareDistribution or the contents of the downloads folder and having it rebuild may resolve the issue. 
After doing the previously suggested, visit <a href="http://windows.microsoft.com/en-us/windows-10/windows-update-troubleshooter" rel="ugc nofollow">http://windows.microsoft.com/en-us/windows-10/windows-update-troubleshooter</a>&nbsp;and get the windows update troubleshooter and see what it reports. 
 
IMHO, the server should be the last item one tries to fix. 
I've seen a whole mess created merely through the process of removing/adding roles. Those transitions at times run into issues creating a whole new sets of problems that are much harder to resolve/address. 
 
When one drives a car and hears knocking during a turn one does not replace the engine as the first course of action.
</div>

<div>
Thank you Arnold. I am really not sure what fixed the issue if it was renaming the software distribution folder, or the Windows update Fix, but the client is now checking in with the server!!! Yeah!!! Thank you so much Arnold you were awesome and patient!!!
</div>

<div>
<div class="content wysiwyg-content">
Hello Experts, 
I have one Windows 10 Client that was communicating with my WSUS server (Server 2012 R2), and when I first installed the client it was communicating for several weeks, and then it has stopped communicating. I have tried a lot of troubleshooting, such as the following: 
1. Ran RSOP.MSC and all the configuration are in order. 
2. I can access the WSUS server from IE 11 on the client 
3. Double checked the Registry and it does not seem to be an issue 
4. Restarted the Client several times, and ran windows update manually. Windows update does work, and it does appear that it is receiving the updates from my WSUS server, and it is installing them, but my WSUS server states that the client has not checked in for 11 days. 
5. Updates appear to be installing correctly. 
Any thoughts?
</div>
</div>

Hello Experts,
I have one Windows 10 Client that was communicating with my WSUS server (Server 2012 R2), and when I first installed the client it was communicating for several weeks, and then it has stopped communicating. I have tried a lot of troubleshooting, such as the following:
1. Ran RSOP.MSC and all the configuration are in order.
2. I can access the WSUS server from IE 11 on the client
3. Double checked the Registry and it does not seem to be an issue
4. Restarted the Client several times, and ran windows update manually. Windows update does work, and it does appear that it is receiving the updates from my WSUS server, and it is installing them, but my WSUS server states that the client has not checked in for 11 days.
5. Updates appear to be installing correctly.
Any thoughts?

Surface Pro 2 Windows 10 Client, was commincating with WSUS server but does not communicate any longer

Windows Server Update Services (WSUS), previously known as Software Update Services (SUS), is a computer program developed by Microsoft that enables administrators to manage the distribution of updates and hotfixes released for Microsoft products to computers.

WSUS

A monitor or a display is an electronic visual display for computers, usually comprised of the display device, circuitry, casing, and power supply. The display device in modern monitors is typically a thin film transistor liquid crystal display (TFT-LCD) thin panel, while older monitors used a cathode ray tube (CRT) about as deep as the screen size. They are connected to the computer via VGA, DVI, DisplayPort, Thunderbolt, LVDS or other proprietary connectors and signals.

Displays / Monitors

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.