ID 596537 - Export Presets can be deleted without warning if the Additional Nodes field contains special characters like ● ►▼ on Windows

Problem summary:
Export Presets can be deleted without warning if the Additional Nodes field contains special characters like ● ►▼ on Windows
 
The presence of special characters also prevents all other Presets from saving correctly.
 
Customer reported version:
Nuke Studio 15.1v4
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke Studio and create a New Project.
2) Navigate to File > Import File(s)... and select some media.
3) Drag and drop a Clip from the Project Bin to the Timeline.
4) Right-click the Clip and select Export...
5) Select the Basic Nuke Shot preset, and then click the "Duplicate selected preset" button.
6) Open the Additional Nodes section, and paste in the following NoOp node:

NoOp { name NoOp1 selected true xpos 891 ypos -203 addUserKnob {20 User} addUserKnob {7 test l "Value ●"}}

7) Optionally, make other changes to the Export Presets, such as duplicating Transcode Shots DPX or adjusting the Version token number
8) Close the Export window, and save your changes when prompted:

9) Close and reopen Nuke Studio, observing how the Export Preset(s) have not been saved.
 
Expected behavior:
Export Presets should be written to disk correctly when the user indicates they would like to save their changes, regardless of any special characters present. 
 
Actual behavior:
If a node uses certain special characters in its knobs, adding that node to the Additional Nodes field of an Export Preset will prevent all Presets from saving correctly on Windows. Besides newly created Presets not being saved, placing the node with special characters inside the Additional Nodes field of an existing Preset seems to completely delete that XML file's contents. In earlier versions of Nuke, existing XML files would not be overridden like this, but no other changes would be saved still. 
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke Studio 16.0v1 - Windows 11, Windows 10
Nuke Studio 15.2v1 - Windows 11
Nuke Studio 15.0v1 - Windows 11
Nuke Studio 14.0v1 - Windows 11
Nuke Studio 13.0v1 - Windows 11, Windows 10
 
Unable to reproduce in:
Nuke Studio 16.0v1 - macOS 14 Sonoma, Rocky 9
 
Earliest version tested:
Nuke Studio 13.0v1 - This issue appears to be in all tested versions of the product on Windows