Home Search

DriveWorks Solo 22
Info: Microsoft .NET September 2022 Update Crash (KB22101401)

Send Feedback
Knowledge Base Article Ref:KB22101401
Last Updated:27th March 2023

DriveWorks v20 SP3

DriveWorks v20 SP3 includes a fix that fully resolves this issue.

Download DriveWorks Solo 20 SP3 (login required)

Previous DriveWorks Versions

DriveWorks v20 SP2 included a fix that in the vast majority of instances prevented this issue from occurring.

However we are aware that in some instances only, selecting certain sections of the Capture Assistant (in the SOLIDWORKS Add-in) will crash the Add-in and SOLIDWORKS.

If this occurs apply the fix detailed here: Workaround 1: Suppress the new behavior caused by the update (Preferred).

Info: Microsoft .NET September 2022 Update Crash

DriveWorks is aware of an issue, where opening certain stages in DriveWorks Solo will crash immediately with UpdateExtent shown in the title of the crash dialog.

This issue is related to a recent Microsoft .NET update which is rolling out to some customers.

DriveWorks is still investigating the root cause of this issue to determine an appropriate course of action, however, in the meantime, see the workarounds below.

Microsoft Update Details

The Microsoft .NET Updates that are currently known to trigger this crash are as follows.

If you are experiencing an UpdateExtent crash, you can check your Windows Update history to determine if one of the following updates is installed.

Windows 11 
.NET Framework 3.5, 4.8 KB5017264 
.NET Framework 3.5, 4.8.1 KB5017267 
Microsoft server operating system version 21H2 
.NET Framework 3.5, 4.8 KB5017265 
.NET Framework 3.5, 4.8.1 KB5017268 
Windows 10 21H2 
.NET Framework 3.5, 4.8 KB5017262 
.NET Framework 3.5, 4.8.1 KB5017266 
Windows 10 21H1 
.NET Framework 3.5, 4.8 KB5017262 
.NET Framework 3.5, 4.8.1 KB5017266 
Windows 10 Version 20H2 
.NET Framework 3.5, 4.8 KB5017262 
.NET Framework 3.5, 4.8.1 KB5017266 
Windows 10 1809 (October 2018 Update) and Windows Server 2019 
.NET Framework 3.5, 4.7.2 KB5017270 
.NET Framework 3.5, 4.8 KB5017263 


The workarounds described below should be applied to every machine where DriveWorks is installed.

Workaround 1: Suppress the new behavior caused by the update (Preferred)

Microsoft have provided the capability to disable the new behavior in this update, but it requires a registry change.

Manually Updating the Registry

This registry change can be made manually by using the registry editor to create the following value:

Value NameSwitch.System.Windows.Controls.VirtualizingStackPanel.OptOutOfCollectionChangeFix
Value DataTrue

Note that neither the AppContext key, nor the Switch.System.Windows.Controls.VirtualizingStackPanel.OptOutOfCollectionChangeFix value are likely to already exist.

If you need to create the AppContext key then you can do so by right clicking on .NETFramework in the tree on the left of the registry editor.

To create the Switch.System.Windows.Controls.VirtualizingStackPanel.OptOutOfCollectionChangeFix value, with the AppContext key selected in the tree, right click in the values area on the right hand side, and choose New -> String Value.

Automatically Updating the Registry

There are a number of possible options for automatically updating the Windows Registry.

The first is to create a file containing the change, and double click it to apply the changes. In addition, your IT organization might be able to automate this change centrally.

To apply the first option, create a text file with the following contents:

Windows Registry Editor Version 5.00


Name this file with a ".reg" extension:

For example, PreventCrash.reg

Once created, double click the file to run.

The registry editor will ask whether you really want to apply the change.

This will require administrative privileges.

The key shown in the image below will be created:

Workaround 2: Uninstall the Microsoft.NET update

It is possible to remove the relevant update from the above table from your operating system, which will resolve the issue.

For more information on how to do this for your operating system, please consult the Microsoft documentation Windows Update: FAQ (microsoft.com).

This will require administrative privileges.