Disabling Windows Firewall?

Only if you have a good third party firewall.  Otherwise there is not a good reason to disable it.

Troubleshooting network issues

You can't be bothered to figure out what firewall exceptions/policy you actually need

You want to make it easier to attack the endpoints

As an example, I recently was unable to add/adopt Ubiquity Unifi Wireless AP's to controller software on server without disabling the Windows firewall.  Despite there being allow rules added for it.  And this is a common problem I believe.  Will have to research why though.  

Disabling it temporarily is also a common troubleshooting step as mentioned above.

Windows Firewall however adds anything and everything you launch provided you are logged in with admin credentials.  I therefore also tend to use highest UAC level on my own PC as an extra step.

I agree only for troubleshooting should you disable it. Don't leave it disabled. Defense in depth even if you have a hardware firewall at your ingress/egress point.

Many thanks at all. Your descriptions are the same as my own mine.
I can not understand why many ITs are disabling all internal Windows Host Firewalls. What is, when a virus comes over USB, Mail, Web etc. in a Host? What are they thinking?
Thanks!

I am not sure what they are thinking. We do not disable Firewalls except for testing. In our case, as one example, we must configure for QuickBooks, but Intuit Support helps with the configuration

I can not understand why many ITs are disabling all internal Windows Host Firewalls.

Laziness probably.  Fix it quick, get paid, get out. Like disabling ipv6 it is a quick fix without understanding the underlying problem and how to fix it.