Windows 10 loses contact with Server 2012 R2 Essentials domain after updates

Hi,

I have a server running Server 2012 R2 Essentials with some Windows 10 Pro clients.
Whenever there are major updates to Windows 10 (the ones that tells you "we have upgraded your PC" at first logon), the PC loses contact with the domain. I can log on due to the cached account, but if I try to access server resources (redirected folders or mapped drives), I am asked to enter the user credentials. This works fine until next reboot of the PC.

Checking "remember the credentals" doesn't help.

I know that the PC has indeed lost the domain connection, because if I try logging on with a new user that hasn't a user profile yet, I am being told that there are no domain controllers available.

The workaround so far has been to uninstall the Essentials Server connector, leave the domain and re-join the domain using the Server connector, but I cannot go on like this everytime a Windows 10 update is released!

Another issue that comes with this, is that it now takes about a minute to create a new folder on a server share, even after a sucessful re-join. The only way I have found to get rid of this problem, is to reinstall the computer! Then everything works perfectly... until the next Windows 10 update!

Any ideas?
DataingAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
DataingConnect With a Mentor Author Commented:
I reinstalled Windows 10, joined the domain, so far so good, and installed the 1607 update.
Still OK.
So I let Windows Update do its thing (thank you, Microsoft, for not letting me choose updates one by one!), and the domain connection broke again.

Uninstalling the updates manually, it appears that I have found the culprit:

KB3176935!

I downloaded the update again from Windows Catalog to re-install and double-check if this is indeed the problem cause, but I just got a .cab file with lots of .cat and .mum files. How do I install all this?

Running Windows Update again, KB3176935 does not re-appear.
0
 
McKnifeCommented:
Try to reproduce this with a clean installation of 1511.
Install 1511, join it to your domain, install no additional software, then upgrade to 1607 and test.
0
 
DataingAuthor Commented:
I've found a temporary fix: Open an elevated command prompt and run
DISM /Online /Cleanup-Image /RestoreHealth

Open in new window

@McKnife: I'll try as you suggest and let you know.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
McKnifeCommented:
So far, it seems you found the culprit, but you want to reproduce it again by reinstalling the update.
The cab file can be installed using pkgmgr.exe like this:
Pkgmgr /ip /m:c:\somefolder\yourcab.сab

Open in new window

0
 
DataingAuthor Commented:
Running the command (elevated) gave no results; no visible reaction, and immediate return to the command prompt.
0
 
McKnifeCommented:
But you modified the path, did you?
0
 
DataingAuthor Commented:
Yes, I moved the file (all-windows10.0-kb3176935-x64_baf9da8bed676d32ffaf22667bfc6f5afc423af0.cab - what a name!) to a folder C:\Install and ran the command
pkgmgr /ip /m:c:\Install\all-windows10.0-kb3176935-x64_baf9da8bed676d32ffaf22667bfc6f5afc423af0.cab

Open in new window

(again, from an elevated CMD window) As said, nothing seemed to happen.
0
 
McKnifeConnect With a Mentor Commented:
I am not sure if that is an indication of "windows thinks that patch is unneeded".
Maybe better start again with a vm with 1511, do a snapshot, patch it and test.
0
 
DataingAuthor Commented:
McKnife,

I set up a VM just as you suggested, and for some reason, I do not get the KB3176935 update from Windows Update anymore. Has it been recalled or superseeded, perhaps?

And installing it manually with the PKGMGR command doesn't work in my VM either. As described earlier, nothing happens.

So I'll conclude that KB3176935 is the reason, and I hope that it will not pop up on my computers again!

Thank you for your assistance!
0
 
DataingAuthor Commented:
Uninstalling the KB3176935 update has solved the problem on all my PCs, and I have not been able to reproduce the problem, as the update appears to be unavailable now.
0
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.

All Courses

From novice to tech pro — start learning today.