<div>
Here is a list of phone numbers<br />
<br />
<a href="https://www.microsoft.com/en-us/licensing/existing-customer/activation-centers.aspx" rel="ugc">https://www.microsoft.com/en-us/licensing/existing-customer/activation-centers.aspx</a><br />
<br />
It may be better to use Chat. I have done this at no charge. Calling them on the phone will likely cost you for support.
</div>


<div>
Hi Fred Marshall,<br />
<br />
Please use the below link.<br />
<br />
System will ask you for get Started<b>--&gt;</b> Tell Your Problem and product which you are using<b>--&gt;</b> After selecting your product you are using &nbsp;and Support Category --&gt;<br />
<br />
You will get the for Options there<br />
--&gt; Call me back<br />
--&gt; Schedule a Call<br />
--&gt; Chat<br />
--&gt; Ask the Comunity<br />
Need assistance with your Microsoft product:<br />
<b><a href="https://support.microsoft.com/en-us/contactus/" rel="ugc">https://support.microsoft.com/en-us/contactus/</a></b><br />
<br />
Regards,<br />
Tapan Pattanaik
</div>


<div>
I don't usually do this so I'm not sure if I should be surprised or not. &nbsp;<br />
My experience with other companies is that generally it's possible to enter a bug report. &nbsp;<br />
Instead I was connected to an Answer Desk. &nbsp;I don't need an &quot;answer&quot;...<br />
A support service was offered. &nbsp;I don't need support in any normal sense.<br />
I feel that I need to report an important bug.<br />
So, I'm now supposed to be getting contact information for the Legal Dept. &nbsp;???<br />
Maybe I shouldn't have used the word &quot;damage&quot; relating to the outcome of the current update process. &nbsp;:-)
</div>


<div>
I suggest you start with a Chat. They can log into your machine and, if warranted, escalate the bug.
</div>


<div>
John Hurst:<br />
<br />
I did start with a chat. &nbsp;That's where I encountered the Answer Desk.<br />
<br />
How or why would one want to have them remote into one machine of MANY??<br />
Am I to assume that MANY computers have a &quot;bug&quot;. &nbsp;That doesn't seem reasonable.<br />
I remain of the opinion that the update *process* either by design or by accident is doing this. &nbsp;So, I think the shoe is on the other foot.
</div>


<div>
I assumed that was one bug on a number of machines, so I would try from one machine with the bug. <br />
<br />
If you have numerous bugs on numerous machine, call from the numbers posted earlier, ask for assistance and get someone, but you would probably need to pay.
</div>


<div>
Also, have you posted bugs here?<br />
<br />
If so, please provide a link.<br />
<br />
If not, post a couple and see if we can help.
</div>


<div>
I've not heard of any such issues and between EE and about a dozen different mailing lists I'm on, some private with MS staff and other MVPs attached, I've not seen any issues like this for any Windows OS. &nbsp;The proper way to do it is to open a support call. &nbsp;It's expensive, but if you can prove it's a bug (they can't explain why it happened or show you documentation that it would if you did x, I've found them happy to refund the call.<br />
<br />
If you want to post details, I'll see if some others can take a look and pass along the info. &nbsp;But if you want direct feedback, call support, open a ticket, find out why it happened and how to fix it, then if it happened because of a bug, it will get escalated.<br />
<br />
Of course, you could always set your firewall rules in a group policy and then you don't have issues like this - even if they get blown away, they are re-applied.
</div>


<div>
Lee W: &nbsp;Well, first of all, this is on a peer to peer network so a group policy isn't available is it?<br />
<br />
Here are the details:<br />
I set up firewall rules for WMI and, also, File and Printer Sharing to work across 3 subnets.<br />
This is done by adding the &quot;other two&quot; subnets to the Remote Address Scope in addition to the default &quot;Local Subnet&quot;.<br />
When recent Windows 10 updates occur, the computers drop their remote subnet connections.<br />
When I realize this has happened, I inspect the firewall rules and find the Remote Address Scope additions have been removed.<br />
<br />
This is evidenced by file shares not being reachable from other subnets. &nbsp;That includes our backup system. &nbsp;So I see the results on the backups right away - which is monitored daily.<br />
<br />
This is evidenced by our SIEM connections via WMI to stop working. &nbsp;One day a workstation can be connected for monitoring and the next time we look, it's no longer connecting. &nbsp;When I go through all the settings necessary for it to work, I find things are missing that *had* to be there previously. &nbsp;The remote subnet scopes are the most obvious because if they aren't there, things aren't going to work.<br />
<br />
There may be other things that are tweaked at the same time but I figure to focus on the one that I believe is clearly justified in raising.<br />
Is this enough detail?<br />
<br />
We've been using these settings for quite a long time and, like you, I too had never seen this happen. &nbsp;But very recently indeed it's been happening. &nbsp;Windows 7 was stable in this regard. &nbsp;We added little experience with Windows 8 and a couple of months ago went fully into Windows 10. &nbsp;Since then we've been seeing this happen.<br />
I have no complaints about Windows 10 particularly. &nbsp;All seems to be working well. &nbsp;But these firewall setting deletions are disruptive and add work.
</div>


<div>
Lee W: Without setting up a &quot;field laboratory&quot;, there's no way to reproduce what's already been done by someone else. &nbsp;And, even that's doubtful. &nbsp;Is the environment provably the same as it was when the incident occurred? &nbsp;Is the estimate of when the incident occurred correct? &nbsp;Is my proposed process the same as theirs? &nbsp;That's asking (and assuming) a lot.<br />
<br />
It's not reproducible <b><i>for me</i></b> because I'm not doing it.<br />
<br />
And reading every KB article isn't my role in life just to find out that the deletion of settings was intentional. &nbsp;If one were to find that then that would be an altogether new discussion. &nbsp;<br />
<br />
All I want to be able to do seems normal business practice and reasonable: &nbsp;<br />
Report what appears to be a bug (not necessarily a software bug - maybe a process bug) and feel that the information has been effectively conveyed.<br />
If what I report was intentional then they will know it (much better than I). &nbsp;Perhaps they will reconsider doing that in the future.<br />
If what I report wasn't intentional (which I suspect and hope) then they will know what to do about it.<br />
<br />
I have never been one of those Microsoft bashers and I have no intention of starting now. Here, I have the feeling that the shoe is being put on the other foot. &nbsp;The notion of asking users to put their money at risk just to satisfy a strange support model is contorted. &nbsp;The notion of &quot;if you've observed a problem then it's YOURS&quot; ... is odd. &nbsp;Well, I do understand it to a point. &nbsp;If I'm doing something with one of their &nbsp;products and it isn't working right then maybe I need support. &nbsp;But, if I'm not doing <i>anything but watching</i> and I see their processes acting strangely and perhaps detrimentally then why is that MY problem to investigate and solve??? &nbsp;I'm not overly disposed to get sucked into that stylized scenario.<br />
<br />
But, it appears that you did answer my question:<br />

<blockquote>
<b><i>In order to provide feedback to Microsoft, you have to (at a minimum) pay them for the privilege and hope that maybe they'll refund the money. &nbsp;If the conditions are right, they will.</i></b>
</blockquote>
I can't fault you for telling the truth even if I don't like it all that much.
</div>


<div>
If you think you deserve a refund, request it from the technician handling the case. &nbsp;If they decline ask for a phone number and then speak to a human being. &nbsp;As I said, I've never had a problem getting a refund when the issue is proven to be a problem with their product AND it was not PUBLICLY documented - tell them &quot;show me how I could have known the resolution without contacting support&quot; - if they can point you to public documentation then you didn't search well enough. &nbsp;If they can't, demand a refund. &nbsp;Dispute with your credit card company if you must. &nbsp;And keep us apprised.
</div>


<div>
<blockquote>
Did you read EVERY KB article on the updates applied? &nbsp;Perhaps this is expected behavior. 
</blockquote>
Well, I tried and didn't find anything very useful. &nbsp;Maybe I looked in the wrong place?? &nbsp;What might be suggested to do this AND meet the original objective that was in mind?<br />
<br />
I'm looking at one of the computers now. &nbsp;It shows only 3 updates in its history - which really can't be!<br />
So, I checked another. &nbsp;It only shows 3 updates in its history - KB3188128, KB3176936, Update v.1607. &nbsp;The first two on 9/21 and the last one on 9/20.<br />
Interestingly, if one goes to &quot;More Info&quot; in Windows 10 Settings one gets: &quot;This page doesn't exist&quot;. &nbsp;So that's a dead end in this quest.<br />
Further searching for Windows 10 Anniversary Update yields sales and marketing info but no technical info that I could find.<br />
So it appears that Update v.1607 has wiped out all previous updates from the history. &nbsp;Oh well, that's the one I suspect anyway.<br />
<br />
Later, I did find <a href="https://support.microsoft.com/en-us/help/12387/windows-10-update-history" rel="ugc">https://support.microsoft.com/en-us/help/12387/windows-10-update-history</a>&nbsp;which appears to give as much information as one is going to get. &nbsp;It's not very informative regarding what I might be looking for is it?
</div>


<div>
<div class="content wysiwyg-content">
I have an issue that I believe only Microsoft can address. &nbsp;I would say it's a bug but it may be more than that.<br />
<br />
I have a large number of computers that have been configured with firewall settings for a variety of purposes.<br />
When recent Windows updates installed, some of the firewall setting were obliterated. &nbsp;This calls for a lot of work to fix them. &nbsp;It's not appreciated and viewed as damage.<br />
<br />
Where would one go to create a meaningful input / dialog with Microsoft?
</div>
</div>


I have an issue that I believe only Microsoft can address.  I would say it's a bug but it may be more than that.

I have a large number of computers that have been configured with firewall settings for a variety of purposes.
When recent Windows updates installed, some of the firewall setting were obliterated.  This calls for a lot of work to fix them.  It's not appreciated and viewed as damage.

Where would one go to create a meaningful input / dialog with Microsoft?

How to effectively contact Microsoft?

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.