Within our company, we run active scans against all systems.  On all the Windows servers that is used as on-premise pollers, we run into the following:

This is showing up on versions 5.1.0, 4.6.3, and 5.0.0.  Is there a way to edit the config and/or registry to remove those weak algorithms or on the next update, is there plans to make it more secure?  If so, can you provide a date that is planned so I can put in an exception request for all the servers instead of removing it?