Visual Micro does not change or manage breakpoints other than adding the demo breakpoint if one does not exist and if tutorial mode is enabled.

In essence the breakpoint system is entirely a VS2017 c++ feature. I haven't heard of this issue before but they are making a lot of fixes and changes for VS2017 therefore please ensure you are on an update to date version and if that doesn't fix it try a repair of vs.

Out of interest. Can you confirm you are not debugging during the change of break-point properties?

Thanks, okay sounds like a visual studio bug. Ensure on the latest release of vs2017 and run a repair.

If that fails please confirm if the issue happens in a new project. If the new project is okay then we need to look at the files of your current project. If I recall vs puts breakpoints in the .sln but I am sure it would only save changes when closing the solution therefore can't be a readonly/permissions issue.

It's a strange one, hopefully the repair fixes but bear in mind that Visual Micro doesn't know if the dialog is open or not. Do you have same problem if you "right click the breakpoint > action", that uses the inplace breakpoint editor instead of dialog.