Why might Windows Firewall *insist* that a program has been determined to not have authorisation to access it's online components? I've got inbound and outbound rules, the program is in the list of exceptions...it makes no sense. I've searched high and low, and not found anything helpful in any write-ups on configuring firewalls. What would the potential list of causes be? It's annoying, because I've had this program 6+ years, and only at the end of July does the firewall magically decide an authorised program has no authorisation... Is there anything in anti-virus updates that might create a conflict? I've reinstalled the program, and it made no difference. I'm pretty sure the anti-virus has been updated plenty of times over the past 6 years, too, and nothing like this has ever happened. This pops up in the log for the program... Log: FIREWALL: Could not Authorize Log: FIREWALL: Freed XP.SP2 Firewall Object However, I'm not using XP Service Pack 2, I'm using Win 7. It isn't my computer, but my brother has no idea why this is happening. I think he has a virtual machine install, possibly recent, only noticed it very recently. Could that be causing a conflict?