KB4580346 hides/deletes User Accounts, and leaves Dashboard Connector unusable!

Question

I installed KB4580346 yesterday evening, and restarted the server as directed.

After the restart, the PCs here could no longer connect to the server with the Dashboard Connector under the Windows Essentials Experience.

I am able to connect to the server through the network folder and login information.

Upon opening the Windows Server Essentials Dashboard, no user accounts are shown, and the "Add a user account", an error pops up "Window Servers Essentials: The task "Add User Account" did not complete successfully.

An error also pops up "Health Alert Error: Alert Notifications are not available for Health Monitoring due to an error or incomplete action, or service has stopped working. If the problem persists, contact that person who administers your server."

I tried rebooting the server again, which did not fix the problem. I also rebooted one of the PCs on the network which also did not repair the problem. I then uninstalled, downloaded and and reinstalled the Connector software to which also did not repair the problem. The error persisted "Cannot connect so server" and the Dashboard connector box remains gray instead of green.

Seems some of these updates do more HARM than good.

Update:

I uninstalled KB4580346 and the user accounts were restored in Windows Server Essentials Dashboard.

I also found and downloaded the wushowhide.diagcab tool and installed it to hide KB4580346 which is apparently bug ridden.

It would seem only fair that if customers are going to be used as Guinea pigs than we should be able to bill Microsoft and get paid for the HOURS lost chasing down problems that their poor and obviously not thoroughly vetted updates cause!

Answer 1

To @Jenny Yan-MSFT :

Since Windows 10, Microsoft practically tries to SHOVE automatic updates down your throat.

Seems you can only TEMPORARILY stop changes.

If I choose to not install one update, and another pops up later, I must then install both the older and new update as I do not see a way to "pick and choose".

Answer 2

As there seems to be no way to reply to a inquiry, but only "comment" which is limited to 1000 characters. This revised board is nearly useless. Compared to what was microsoft TechNet this is truly convoluted.

To @Anonymous :

I am sorry I have not replied sooner as there have been other things going on around here.

The log states that the DNS name doesn't exist? How can this be, tonewheels.local IS what was originally set up, is if possible that the update changed this and therefore the accounts cannot be accessed? I checked the configuration of the other PCs on the network and for instance the full computer name of one of the PCs is "Panalaptop-PC.tonewheels.local". Domain: "tonewheels.local" and this PC is connecting to the network fully.

Full log:

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "tonewheels.local":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.tonewheels.local

Common causes of this error include the following:

• The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

192.168.1.254
192.168.1.81

• One or more of the following zones do not include delegation to its child zone:

tonewheels.local
local
. (the root zone)

Answer 3

Hi,
1.For the notification email of the QA forum, please follow the steps in our documentation to enable e-mail notifications.

2.As for the failure of installation of Connector software, kindly consult the listed issues and suggestions from below link:
Troubleshoot connecting computers to the server in Windows Server Essentials

https://learn.microsoft.com/en-us/windows-server-essentials/support/troubleshoot-connecting-computers-to-the-server-in-windows-server-essentials

3.It is always suggested to test the update or patch KB on a test VM before you would like to apply it into production environment in case of any risk.

---

Hope this helps and please help to accept as Answer if the response is useful.

Thanks,
Jenny

Answer 4

Oddly I am not receiving any email notifications of a response. I just happened to check-in here a few minutes ago.

It is not clear to me which error file(s) on the server I should review.

My bigger problem now is, that I thought it might be a problem with the connector software when the Windows 7 machine use everyday now will reconnect to the server.

I followed the procedures explained here by Eve Wang:

windows-essentials-2016-server-not-available

I also removed this computer from the domain as directed by the procedure, and deleted the computer from the back-ups as directed but did not delete the back-up archives.

Upon trying to first re-add the computer the domain I received an error that the server cannot be found, though it did seem to recognize the domain name, and the account when a warning popped up that "this is a Administrator account". Beyond that it hangs for a very long time and then rejects with the "server not found error".

After deleting the connector software, clearing out the logs and task manager entries on this Windows 7 client computer, I tried I downloaded the Connector software from the server and opened the file.

However I can open the server folders through the network icon on my desktop and access all files. Unfortunately the Dashboard software cannot be installed and automatic back-ups have ceased.

Seems something is denying access, but I cannot figure out what it might be. Today I tried again with the anti-virus software on both the Client and server disabled but that did not alleviate the problem.

Answer 5

due to an error or incomplete action, or service has stopped working

What errors are found in the event logs?

--please don't forget to Accept as answer if the reply is helpful--