Build 11.0.064 sounds wrong somehow. Mine is 11.0.669, however it all depends on where you are and where the software comes from I guess.
Updates sometimes can alter permissions so make sure IIS is still allowed full access in SecurityCenter > Web and Email Protection > Firewall > Internet Connections for Programs
(Hint: to arrange them alphabetically click the word Program at the top of the list).
Find the item for IIS and click the Edit button to change it and whilst there you might experiment with switching off Netguard for that one to see if it improves matters.
You may also find something relevant in Ports and System Services but as I am not familiar with IIS I don't really know about that.
You might also want to open a ticket with Technical Support considering actual McAfee staff patrolling here is intermittent at best.
It's free via phone or online chat and linked under Useful Links at the top of this page.
Thanks for replying.
<Build 11.0.064 sounds wrong somehow.>
I dropped back to an earlier build when I restored a stable drive image via Acronis. This was the most expedient way to get back to work
<Updates sometimes can alter permissions so make sure IIS is still allowed full access in SecurityCenter > Web and Email Protection > Firewall > Internet Connections for Programs>
I did block access for IIS to the Internet after navigating to the screen you supplied directions for. However, after taking this step, I failed to reproduce the issues I mentioned in my first post.
I guess I'm reluctant to upgrade again and face the same issue. After all its going to take a fair amount of my time to recover from this, let alone the time it's going to take to deal with McAfee support. And I haven't even considered whether I'm going to be charged for this support. It may be easier just to uninstall McAfee and switch to another anti-virus product at this point.
I feel that I've given enough information for McAfee to attempt to reproduce this problem. And if they don't have McAfee staff monitoring this forum, they should.
The forums are mainly peer-to-peer support and rarely will an actual McAfee person patrol here. We are here to steer people in the appropriate direction. Support is free of charge, the only time they charge is for one-on-one virus removal, like any other antivirus provider.
What I meant was that it must have been blocked in the newer versaion and you needed to unblock it. But there could be other reasons of which we mods aren't aware. That's where support comes in.
When I finally got a few cycles this am I
1. Ran Windows update, restarted
2. Ran Security Center update, am now running 11.0.669
This time, I experienced no issues starting the IIS admin
console, or pulling pages from localhost.
It appears as though the McAfee upgrade was dependent
upon windows system upgrades being in place.
If this is the case, then my question is, why doesn't the McAfee
installation program test for the dependencies it needs before
I think the people who make these updates assume, perhaps rather optimistically, that people have kept their systems up to date, especially on the second Tuesday of every month: Microsoft Update Tuesday.
I agree it would be nice if everything that ever updated actually stated what it needed if missing. I think the only time I've seen that was when installing some backup software a while back when it said I needed .net 2 (or 3?) first.
They also assume that people keep every aspect of their machine up to date, including parts they may not use by default, Internet Explorer comes to mind as a particularly important one.
Nowadays that is so important with all the malware and DNS attacks out there.
Here's a helpful link for GetVersionEx function for the McAfee team:
When they assume an up to date system they make an *** out of u and me.