Apparently, some developers using VS2017 who got a Windows update that installed .NET 4.7 have been getting this crash as well, it appears the recommended workaround for now is to turn touch support off.

2 Answers
2

Update: Microsoft has now fixed this problem in a manual update (as noted by Jürgen), personally I will stick with the workaround until the fix is in the automatic update because it would be a lot of work to make every user install a manual update.

This is obviously a bug in .Net 4.7 that affects Windows 7 and 8/8.1 systems that have a touch input device. Therefore one can hope that Microsoft addresses this in a future update. Meanwhile the only way to retain full functionality is by uninstalling and hiding the update.

Other option is disabling the stylys and touch support either in app.config (like in your link) or in the code if the app is compiled with 4.6 or newer. You didn't specify why that is not ideal but I assume those features are needed? Notice that the disabling doesn't mean that every app is unusable with touch devices, but rather that they only use features that are accessible with a mouse. Update: Apparently touch device users without a mouse will have trouble using UI that requires scrolling.

Unfortunately, the app is mostly used on touch devices that may not even have a mouse/keyboard connected, so disabling touch is maybe impossible instead of not ideal. I do appreciate the suggestion, and would imagine that this would work for most cases.
– NimbusHexJun 19 '17 at 14:43

Normal actions that can be done with a mouse still work after disabling. So taps on touch devices translate to clicks. I suppose only the advanced functions, like multi-touch and pressure sensitivity, would not work.
– teemuJun 20 '17 at 6:06

Scrolling in grids and listboxes has given some unpredictable results with this, so I've decided to go the heavy handed route of uninstalling and blocking .NET 4.7 on client machines for now. I'm in a unique position where I have control over this, for anyone else who does as well, you may want to issue a WUSA uninstall command for the appropriate KB. blogs.msdn.microsoft.com/dotnet/2017/06/13/…
– NimbusHexJun 23 '17 at 2:08