You can enforce this workaround by accessing the Shortcuts tab and adding ‘ -w‘ at the end of the target.
Weirdly enough, this ends up removing the DirectDraw requirement for a lot of legacy games including Diablo I and Diablo II. Now that you know every potential culprit that might be responsible for the apparition of this DirectDraw error on Windows 10 when attempting to play legacy games, here’s a list of confirmed methods that other affected users have successfully used to get to the bottom of this issue: Method 1: Forcing the Game to Run in Window ModeĪccording to a lot of affected users, you might be able to fix this particular DirectDraw issue by modifying the properties screen of the legacy game executable so that you force it to run in windowed mode. In this case, you can use a wrapper like dgVoodoo to make the game compatible renderable on Windows 10.
Direct play windows component how to#
Graphical Rendering issue – Graphical rendering issues can also contribute to the apparition of this issue if the legacy game doesn’t know how to use new technologies like Direct3D 11 and Direct3D 12.But since these technologies are deprecated and disabled by default on Windows 10, the only way to fix this issue is to re-enable them from the Windows Apps & Features screen. NET Framework 3.5 are Disabled – As it turns out, the vast majority of legacy games that were released when Windows XP was the latest OS from Microsoft will require Direct Play and. Fortunately, you can use compatibility mode to get around most issues by forcing the executable to run in compatibility mode with an older Windows OS.
However, a lot of affected users have confirmed that the issue no longer occurs if they force the game to run in windowed mode.