@MainActor behaves different on Windows and macOS

I'm not sure it is just about reporting. When ParsableCommand (not async) is used, Thread.isMainThread gives expected result. Another issue with MainActor and RunLoop.main lead me to this issue SDL, game loop and Swift Concurrency - #3 by Eugene_Gubin

How to get it on Windows? Debug descripton gives <Thread: 0x000002806581dba0>