Connecting the dots, another user experienced the same problem ( Issues with an error saying disconnected from graphics adapter since the latest update. ). Major clue: that user also has Intel UHD 630 graphics. With only two data points, I cannot confidently conclude this Shapr3D glitch doesn’t affect other graphics adapters (it may be specific to UHD 630 after the latest Shapr3D update), but it strongly suggests that Shapr3D’s code change is the ultimate source of the problem, NOT my UHD 630 AND the UHD 630 of another user (Occam’s razor a.k.a. the principle of parsimony: the simplest explanation is usually the correct one).