I installed Win 7RC on a new build a few days ago and installed Kaspersky Antivirus 8.0 Technical Preview for Win 7. The AV is installed and working correctly but WHS does not detect that so it throws a critical network warning everytime I reboot my PC. The Connector software is installed and working correctly, the Win 7 PC is backed up every night. I do not update my WHS installtion often because I like to wait and see if new updates cause more problems. However, it is updated through PP2.

Not sure this should be in the Windows 7 forum.

Not sure this should be in the Windows 7 forum. I have the same issue only with AVG 8.5 antivirus on Win 7 RC64 bit. It's not clear if it is a Windowsissue or a Windows Home Server issue or something else. Quite possibly not specific to Win 7 though the problem began in Windows code since release of Win 7 beta.I've been searching WHS forumsas well. I understand it has been encountered with 32 bit versions of windows Vista and that that problem began for them a few months back with nobodyhaving changed anything though some automatic update may be a factor.I have not seen this problem on any computer running Win XP 32 bit nor have I seen any reports of it yet. I saw it immediately when I installed Win 7 RC 64 bit and WHS 64 bit connector software. I had not installed the connector onWin 7 Beta and the install of RC was a clean install.My WHS is fully up to date. In my case the red criticalhealth notification is displed for a brief time after login then the problem vanishs. Possibly some sort of communication between the Windows security center and the Windows home server is not happening quickly enough at login resulting in WHS reporting not Antivirus then the communcation happens and WHS reports everythnng normal. Others report seeing the problem when shutting down and various brands of antivirus have been in use. Reportedly One care had the problem but it has been resolved if you download and reinstall One care. It's clearly a Windows code issue but it's not clear which product. Seems most likely a Vista/Win 7 code base issue possibly introduced in recent months.