“Autoconnect” was the culprit.
Still battling this issue but so far updating the network drivers seems to do the trick. One other piece of information, a majority of our network cards are Intel based. I wonder if that has anything to do with it?
One user today I told to turn off auto-connect. Delay would be most beneficial as most users want an auto-connect feature.
Super good data point!
u/Froggmann seems to be correct. On one report yesterday of ‘Reconciling’ we turned off Sophos. Did not solve the problem. Does not mean it is not causing it, but we checked the MSFT techs box. Nothing new to report unfortunately. We are still getting ~7 a day on average.
We have two separate cases open with Microsoft for this as well. They keep giving us the run around but if I have my updates on my end, I will be sure to post it here for everyone as well.
Auto-connect has been a problem for us too, but never had this particular error before until today.
We are Intel based as well… Although we have ~5 different SKUs of cards, and then mix wired/wireless and all having the same issue. Then throw in the majority of users that don’t have the issue.
Appreciate it. Crazy that I could not find anything related to ‘Reconciling…’ and Microsoft has no clue either.
Any update on your issue?
Sadly no. It’s to the point where Microsoft support won’t even respond to us in a timely manner and last conversation we had with Microsoft support, they were pretty much saying it’s an internal network issue.
Which is BS because the affected users work from their home with some on completely different ISP connection.
Wish I had better news
Same, MSFT is kicking the can down the road. I keep asking for escalations, nothing.