If you comment those lines out, Upgrades on modules will not be processed and there is one other rarely used event that won't happen when the Update link is clicked on the ModuleDefinitions screen. That second event updates the SupportedFeatures for the module so if the update button is clicked your SupportedFetures will get reset to 0 meaning that the system won't know that the module supports Search, Import/Export, and Upgrades.

If you aren't installing any modules commenting out those lines is a decent workaround for the problem for right now though.

No, the EventQueue behaviour has not been changed yet.  I'm still trying to determine the best way to handle this rare exception. 

I recently moved a site to a new host.  The host installs the latest version of DNN by default (in this case 4.3.7).  At odd times I get a Windows dialog box requesting Username/Login.  It is frustrating.  The host responded to a ticket saying that

"On further investigation, it appears that the reason for this is because of a problem with latest 4.3.6/7 versions of DotNetNuke operating under a secure shared hosting environment. The DotNetNuke developers are aware of this and are working on it. In the meantime there are two workarounds you can apply:

1. Log in with FTP to delete all files from their Portals/_default/EventQueue folder (then you will need to repeat this any time you add a module)

-or-

2. Delete all code from the Application_Start event in global.asax (no additional action would be necessary, even when adding modules)

Please let us know if you need anything else."

I deleted the contents of the EventQueue folder but the dialog box still appears.  Does anyone really have any insight into this issue?