You can now reset settings to defaults with the new command-line switch in X410 version 3.1.0

June 6, 2022|

  • /reset command-line switch is added

    When this command-line switch is used from PowerShell or Windows Command Prompt, X410 initializes all its settings to defaults. Other command-line switches or arguments must not be specified while using this switch; this command-line switch will be ignored if you do.

    x410.exe /reset
  • VSOCK option for WSL2 is now labeled as ‘experimental

    Some users are reporting that X410 becomes unresponsive when the VSOCK option for WSL2 is enabled. Although we’re unable to observe such problems in our testing devices, we added the ‘experimental’ label to indicate that there can be an issue.

    As also mentioned in our other posts, the VSOCK support in WSL2 was never officially announced from Microsoft. Hence if you do experience any problem with the VSOCK option for WSL2, please report back to us and help us track down its culprit.

    For disabling the VSOCK option when X410 becomes unresponsive, newly added /reset command-line switch should be handy. Before using /reset command-line switch, please make sure no instance of X410 is running (ex. check the 'Details' tab in Windows Task Manager).

  • This new version also includes minor improvements and bug fixes.

X410 version 3.0.1 fixes showing multiple instances of its Settings window

May 9, 2022|


X410 version 3.0.1 no longer shows multiple Settings windows even if you click the tray icon multiple times rapidly. For your information, X410 Settings window is managed by a separate helper executable and forcefully terminating it via Windows Task Manager doesn't affect the main X410 program or the currently running X-Window client apps.

X410 version 3.0.0 now offers automatic protection against unsolicited TCP connections for WSL2 and Hyper-V virtual machines

April 25, 2022|

  • All new Settings window!

    X410 now has a modern popup window for its settings. It should give you easier access to all the options available for X410; you can even just mouse click to enable options that were only available through command-line switches (ex. Hyper-V VSOCK support).

  • VSOCK is now supported for WSL2.

    If you're having problems while using TCP for connections between WSL2 and Windows host (ex. X410 connections are severed or hanged after your computer is coming back from Windows sleep mode), you should definitely try using the new VSOCK connection method.

    VSOCK is only for connections between virtual machines and their host, or among virtual machines. Hence you should get much stable experience that doesn't affected by the TCP/IP network changes in Windows. You also don't need to worry about firewall settings as other external computers cannot connect to your Windows via VSOCK.

    However, please note that although WSL2 seems to be using VSOCK for its internal communication with Windows host, Microsoft has never officially released any documentation or API's for third-party developers like us to utilize the VSOCK. Hence, the new VSOCK feature for WSL2 in X410 may not work in future iterations of WSL2, but we'll surely do our best to keep it compatible with all future versions of WSL2.

  • You can now control available connection methods for X-Window GUI apps from X410 Settings.

    For TCP connections, you can now specifically only allow connections from Hyper-V virtual machines and/or WSL2 just by clicking options; you don't have to set up any firewall rule, yet you can instantly improve the security of your Windows as it automatically blocks connections from external computers.

  • Improved seamless experience of X-Window GUI apps running in Windowed Apps mode on Windows 10/11.

  • Standalone version is now available for X410.

    Along with the existing Microsoft Store version of X410, we now offer a completely separate Standalone version. Both versions have the same core functions and features, but the Standalone version is not linked to a Microsoft account and also offers a site licensing option.

X410 version 2.9.4 features minor enhancements and bug fixes for Linux GUI apps running in Windowed Apps mode

September 19, 2021|

  • Graphic rendering routines are updated to minimize flickering issues in theme-based GUI apps with transitioning animations (ex. GTK based Emacs).
  • Fixed popup menu selection problems in some traditional X-Window apps when X410 DPI scaling option is enabled.
  • Fixed the content updating problem in some popup dialog windows (ex. 'About' window in GNU Octave).

Want to snap GNOME apps to your screen edges like Windows apps? Get the new X410 version 2.9.3!

September 11, 2021|


If you already purchased a license for X410 via Microsoft Store, Windows will automatically update your installation of X410. You can also update X410 manually by using the 'Downloads and updates' menu in Microsoft Store app. The following summarizes what's new in version 2.9.3.

  • You can now snap Linux GUI app windows just like Windows apps!

    While using a Linux GUI app such as gedit that has a custom title bar in X410 Windowed Apps mode, you can now simply drag it to the edge of your screen and enjoy the snap feature just like any other Windows apps. You can also use the Windows standard keyboard shortcuts (ex. [ Windows Logo Key ] + [ Right Arrow ]) for snapping your Linux GUI app windows.

  • X410 now adds drop shadow to Linux GUI app windows in Windowed Apps mode when a Linux GUI app has input focus but doesn't have a standard Windows title bar.
  • Keyboard shortcuts or menus for changing input focus to another window should now work as expected (ex. CTRL+ALT+] in IntelliJ IDEA).
  • Fixed window size related problems in Windowed Apps mode while toggling full-screen mode for Linux GUI apps (commonly enabled by pressing the F11 key).
  • Fixed intermittently showing corrupted window content while resizing Linux GUI apps in Windowed Apps mode.
  • Improved maintaining a window stacking order in Windowed Apps mode when Linux GUI apps are running alongside Windows apps.
  • Constant micro memory allocations for internal messages have been consolidated and X410 now instead utilizes Windows standard message queues. This should improve memory management and app stability in X410.