Not able to run "Windows Update" on a Windows 10 Pro PC in an SBS2008 domain

I have a network consisting of an SBS2008 server, 7 Windows 7 Pro workstations, 1 Windows 10 Pro laptop. The laptop is also in the domain
- NOTE: I removed the WSUS from the server well over a year ago due to, too many issues to resolve. Microsoft was involved in all attempts to resolve.
- Anyway, We have been updating the workstations and the server manually with no issues.
- The Windows 10 Pro laptop was fully updated to version 1709 prior to placing in the domain. The laptop functions fine in the domain

However
- The SBS2008 console shows the laptop's "Security Status" unavailable. I expected this since the SBS2008 server's group policies don't work well with Windows 10

From the Windows 10 laptop:  When trying to force searching for windows updates, there’s a message “Some settings are managed by your settings” and the updates fail.
-      I tried to run the updates after disabling the firewall to no avail.
-      NOTE: I am curious to see if the updates work when not on the local network. I will ask the user to take the laptop home and try to do the Windows updates.
Please see attached screenshot of the Windows Update message I see when attempting the updates.
Windows-Update-message.jpg
LVL 1
Andreas GieryicComputer Networking, OwnerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jesse BruffettM&F-ing SorcererCommented:
here is one link that might help:
http://youritsource.org/msft/how-to-remove-wsus-settings-and-restore-windows-update-defaults/

Also check your GPO's and make sure they are still trying to make the machine look for the WSUS server.
1
Cliff GaliherCommented:
First thought is that you didn't remove the policies that point clients to the WSUS server.  Removing WSUS isn't enough. You have to remove the policies as well.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andreas GieryicComputer Networking, OwnerAuthor Commented:
Performed this

Remove WSUS Settings Manually
Click Start and type regedit into the start search box, then Right Click and Run as Administrator.
Navigate to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\
Right Click and Delete the registry key WindowsUpdate, then close the registry editor.
Open the Services Console by entering services.msc in the start search box.
Locate and Restart the Windows Update Service
- the registry key WindowsUpdate was not there. This explains why the PowerShell option failed. Its been a while but I may have already removed the WSUS correctly.

I will research how to remove the policy that points workstations to the WSUS
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Andreas GieryicComputer Networking, OwnerAuthor Commented:
I looked at this
https://blogs.msdn.microsoft.com/george_bethanis/2014/07/29/how-to-check-for-the-wsus-server-settings-and-gpos-on-confmgr-clients/ 

In the registry on the Windows 10 laptop, the WindowsUpdate does point to the WSUS server. I removed all keys except the default. I compared  it to a Windows 10 laptop thats not in a domain

On the actual SBS2008 server, I went into "Group Policy Management, Group policy objects and saw all 3 related update services policies - disabled
0
Andreas GieryicComputer Networking, OwnerAuthor Commented:
https://blogs.msdn.microsoft.com/george_bethanis/2014/07/29/how-to-check-for-the-wsus-server-settings-and-gpos-on-confmgr-clients/  
 
The fix I found came from the above link.
- Compare the below registry keys on a "problematic" machine, with the same  registry keys from a “working” machine:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU
0
Andreas GieryicComputer Networking, OwnerAuthor Commented:
If it wasn't for the two comments provided by Cliff and Jessie, I would not have been able to find the fix. They led me in the correct path, therefore I want to award the points to them
0
Andreas GieryicComputer Networking, OwnerAuthor Commented:
Thank you for your quick responses
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.