Windows 10 and ISBoxer: Yes, it works
2016-07-28: This post has been updated to reflect the most up to date information.
Inner Space and ISBoxer do support Windows 10 (since it was released), and I use Windows 10 myself. There are no changes you need to make to your Windows 10 system to use Inner Space or ISBoxer. If you are having trouble with Inner Space or ISBoxer, please start a new thread and describe your issues!
Note: Up until a few months ago, there was a crash issue that some people experienced with 64-bit vs 32-bit games launched by Inner Space/ISBoxer, notably affecting World of Warcraft. The issue was less prevalent on previous versions of Windows, and so this issue was often reported as a Windows 10 issue, leading to this thread.
The crash issue has been resolved, and there is a couple new Inner Space settings for those that wish to switch between 32-bit and 64-bit versions of World of Warcraft (and other games that may be affected in the future):
1. Right click Inner Space and select Configuration
2. Find the "32/64-Bit" heading near the bottom of the General tab (displayed by default)
3. The options are "Use 64-bit Inner Space Uplink" (enabled by default), and "Use same-bit game clients if possible (e.g. 64-bit client for 64-bit Inner Space)" (also enabled by default). If you wish to use 32-bit World of Warcraft, it is recommended to disable "Use 64-bit Inner Space Uplink", and leave "Use same-bit" enabled.
The effect of the new options is that Inner Space will automatically launch as 64-bit, and also launch World of Warcraft in 64-bit, for 64-bit Windows; or all 32-bit for 32-bit Windows. This eliminates any "bitness" related crashes that might otherwise occur for some people.
Inner Space and ISBoxer do support Windows 10 (since it was released), and I use Windows 10 myself. There are no changes you need to make to your Windows 10 system to use Inner Space or ISBoxer. If you are having trouble with Inner Space or ISBoxer, please start a new thread and describe your issues!
Note: Up until a few months ago, there was a crash issue that some people experienced with 64-bit vs 32-bit games launched by Inner Space/ISBoxer, notably affecting World of Warcraft. The issue was less prevalent on previous versions of Windows, and so this issue was often reported as a Windows 10 issue, leading to this thread.
The crash issue has been resolved, and there is a couple new Inner Space settings for those that wish to switch between 32-bit and 64-bit versions of World of Warcraft (and other games that may be affected in the future):
1. Right click Inner Space and select Configuration
2. Find the "32/64-Bit" heading near the bottom of the General tab (displayed by default)
3. The options are "Use 64-bit Inner Space Uplink" (enabled by default), and "Use same-bit game clients if possible (e.g. 64-bit client for 64-bit Inner Space)" (also enabled by default). If you wish to use 32-bit World of Warcraft, it is recommended to disable "Use 64-bit Inner Space Uplink", and leave "Use same-bit" enabled.
The effect of the new options is that Inner Space will automatically launch as 64-bit, and also launch World of Warcraft in 64-bit, for 64-bit Windows; or all 32-bit for 32-bit Windows. This eliminates any "bitness" related crashes that might otherwise occur for some people.