Stephen I know you are up against it with all that is going on, I am hoping you can look into another situation since you are so close to it when you have a moment.
The following site:
http://4rochester.com
Is returning the following error:
Server Error in ‘/’ Application
I have put in ticket number RS #EMR-66165-524 but was told:
It’s a code error. you need to contact your programmer/developer about this issue.
What I don’t understand about this is that there have been no coding changes done that I am aware of in months on that site and .NET worked just fine until the H-Sphere Update situation started.
Thanks!
This is the error it is giving:
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Data at the root level is invalid. Line 1, position 1.
Source Error:
Line 1: <?xml version='1.0' encoding='utf-8'?>
Line 2:
Line 3:
Source File: /App_Browsers/default.browser Line: 1
Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053
I did this:
Developer technologies - Microsoft Q&A
removed frontpage generated files and it fixed.
This may hve happene due to reconfiguring frontpage on the domain and it making dupe copies of config files.
Thank You Stephen!
That particular site only had the FrontPage extensions on it for being able to do some publishing via http:// Don’t have any need for hit counters blah blah blah! 
I think though that maybe the upgrading is doing some hosing of extensions (maybe?) so hopefully you guys can use that information for any other possible similar situations on Win servers?
Thanks again Stephen for going the extra mile…time for a raise! 
Another follow-up here hoping it might help anyone following this.
I have gone through 5 windows sites (on different servers) so far this morning that require and use the FrontPage Extensions. In every case I was unable to login via http:// until I went into the control panel for that site and did a repair of the FrontPage extensions.
So it seems to me to be pretty certain that something with the H-Sphere upgrade has probably corrupted the Extensions.