Known issue ONLY on Windows Server 2016 OS - This has been resolved in KB4512517 (2019-08 Cumulative Update released August 13, 2019).
The client crash will occur after applying the following Windows Update:
2019-07 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4507459 & KB4507460)
The NovaBACKUP client crashes on opening the User Interface, resulting in the following dialog:
The Support tab is essentially a Microsoft Internet Explorer embedded IFRAME.
KB4507460 appears to have changed the way the contents of the Support Tab load after opening the software, which starts a few seconds after opening the software.
To mitigate this issue, you need to Enable Script Debugging using one of the following ways.
You can configure the below registry key:
Registry setting: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main
Value: Disable Script Debugger
Or you can Enable Script Debugging in Internet Settings. You can open Internet Setting by either typing Internet Settings into the search box on Windows or by selecting Internet Options in Internet Explorer. Once open, select Advanced then Browsing and finally, select Enable Script Debugging.We are working on a resolution and will provide an update in an upcoming release.
Workaround (1) install KB4512517 (2019-08 Cumulative Update for Windows Server 2016) released on 08/13/2019 via Windows Update. Updating to KB4512517 is the recommended resolution as it allows you to retain the latest Windows updates. The update is large at 1.4 GB and requires a reboot.
Workaround (2) uninstall the KB4507459 & KB4507460 updates and pause Windows Updates.
Workaround (3) Adjust the Internet Options to allow script debugging
NOTE: This is a per-user solution. Each user that needs to use the NovaBACKUP software on the Server will need to make this change.
- Open Internet Options (via Control Panel or the Internet Explorer menu)
- Navigate to the Advanced tab
- In the "Browsing" section, clear the checkbox next to
Disable script debugging (Other)
- Click [Apply], then [OK]
- Open the NovaBACKUP Software to confirm
Workaround (4) Add
127.0.0.1 static.zdassets.com to the Windows Hosts file
# Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 18.104.22.168 rhino.acme.com # source server # 22.214.171.124 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost 127.0.0.1 static.zdassets.com
Always create a copy of your Windows Hosts file somewhere before adjusting its contents, as a mistake made in editing can cause loss of connectivity.
To save the Hosts file, you will need to either save to an alternate location, then copy over the original, or run notepad.exe as administrator. It is always a good idea to edit this file using notepad.exe. Alternatively, you can use the program Notepad++ to perform the file edit and when attempting to save the file it will prompt you to reload the program in Administrator mode and that will allow you to then save the file.
Do NOT attempt this unless you are familiar with the hosts file.
If a mistake is made in editing this file or you corrupt this file in any way, many other functions can be impacted, and that can result in lack of network connectivity.