Would it be better to use a specific cursor handle value for when it isn't initialized yet? The issue can also be reproduced with any window procedure that handles `WM_SETCURSOR` to do nothing. We currently ask the driver to set an invisible cursor handle in this case whereas on Windows it ends up with some random cursor, probably the last one used for the desktop.