[German]Microsoft has already released an update for the .NET Framework 3.5, 4.7.2, 4.8 for various Windows 10 versions on August 20, 2019. But the update comes with some issues. It bricks Veritas Backup Exec.
Already on August 13, 2019 there was an update, as mentioned in the German comments here (and this article). But Microsoft has probably added to the 20.8. The colleagues of Deskmodder took it up here and published the following list of cumulative updates for various Windows versions.
- Windows 10 1809: KB4511517 .NET Framework 3.5 and 4.7.2
- Windows 10 1809: KB4511522 .NET Framework 3.5, 4.8
- Windows 10 1803 KB4511521 .NET Framework 4.8
- Windows 10 1709 KB4511520 .NET Framework 4.8
- Windows 10 1703 KB4511519 .NET Framework 4.8
- Windows 10 1607 KB4511518 .NET Framework 4.8
These updates can also be downloaded from Microsoft Update Catalog. Microsoft states that the update fixes a crash in the Bass Class Library (BCL) that occurs after event logs are broken down.
Attention with BackupExec 20.4
Two days ago blog reader Axel T. contacted me via e-mail and pointed out a big problem. He listed the details at administrator.de. Here is the translation of his German post:
I just installed the August updates on our Windows Server 2012 R2. Before that I checked all hints for possible issues with the new updates; like every month. Then I started our backup software BackupExec 15 on one of the servers because I planned to change a setting before the backup tonight.
And the software doesn’t start anymore.
Error message “BackupExec does not work anymore”. In addition some MS-Prosa, that was it. Restarting the server does not solve the problem either. Restart of the services also not.
There are no messages regarding the backup software in the Event Viewer. Associated services all run, can also be stopped and restarted. All this without error messages in the Event Viewer.starten. Auch das alles ohne Fehlermeldungen in der Ereignisanzeige.
The blog reader identified the .NET Framework update as the root cause. Then I got today another German Comment from blog reader Sebastian, reporting the same issue:
I’ve also installed the .net 4.8 update. (Server 2008 R2)
Important – who uses BackupExec 20.4:
.net 4.8 bricks BE – the backup can’t start anymore after installing the update.
Now I unistalles .net 4.8 and reinstalled 4.7.2.
It now runs again – if necessary all BE services have to be restarted
Sebastian writes that there is already a KB article (Backup Exec console crashes after installing .NET Framework 4.8).
After installing .NET Framework 4.8 on the Backup Exec media server , the Backup Exec console crashes when starting, as shown in the following screenshot.
This issue is also observed on servers or workstations with the Backup Exec Remote Administration console installed.
The event log contains an error 0xe0434352 for BackupExec.exe, version: 20.0.1188.186. Veritas identified .NET 4.8 as the cause and recommend uninstalling the update:
Uninstall .NET Framework 4.8 and reboot server. This update will be listed as KB4486105 (Windows 2012 R2), KB4486081 (Windows 2012), KB4486129 (Windows 2016), KB4486153(Windows 2019) in the list of installed updates. For Windows 2008 R2, remove .NET 4.8 through Programs and Features in Control Panel.
The fix for this issue will be included in the next release (20.5) of Backup Exec. This article will be updated when 20.5 is available.
Maybe it will help those affected. Addendum: The crash might be fixed with update KB4511555 released on August 30, 2019.
Cookies helps to fund this blog: Cookie settings