GitHub – winapps-org/winapps: Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration. Hard fork of https://github.com/Fmstrat/winapps/

Run Windows applications (including Microsoft 365 and Adobe Creative Cloud) on GNU/Linux KDE Plasma, GNOME Or XFCESeamlessly integrated as if they were native to the OS.

WinApps works by:

1. running windows in a Docker, Podman Or libvirt virtual machine.
2. Querying Windows for all installed applications.
3. Creating shortcuts to selected Windows applications on the host GNU/Linux OS.
4. using the FreeRDP As a backend to seamlessly render GNU/Linux applications as well as Windows applications.

• GNU/Linux /home The directory is accessible through Windows \\tsclient\home Mt.
• integration with NautilusAllows you to right-click files to open them with specific Windows applications based on the file MIME type.
• The official taskbar widget enables seamless administration of Windows subsystems and provides an easy way to launch Windows applications.
• Microsoft Office links from the host system (such as ms-word://) automatically open in the Windows subsystem. (Note: You may need to use the User Agent Switcher browser extension and set the User-Agent to Windows, as Office WebApps usually hide the “Open in desktop app” option for Linux users.)

WinApps supports All Windows Application. However, support does not extend to kernel-level anti-cheat systems (such as Riot Vanguard).

Universal application support is achieved by:

1. Scanning Windows for any community-tested applications (listed below).
2. scanning windows for someone else .exe Files listed in the Windows Registry.

Community tested applications benefit from high-resolution icons and pre-populated MIME types. It enables file managers to determine which Windows applications should open files based on the file extension. Icons of other discovered applications are drawn .exe files.

Contribution to the list of supported applications is encouraged through submitting a pull request! Please help us grow the WinApps community.

Please note that the provided list of community-tested applications is community-driven. Thus, some applications may not be tested and verified by the WinApps team.

	adobe acrobat pro (x) Icon in the public domain.		Adobe After Effects (cc) Icon in the public domain.
	adobe audition (cc) Icon in the public domain.		adobe bridge (CS6, CC) Icon in the public domain.
	Adobe Creative Cloud (cc) Icon under MIT license.		Adobe Illustrator (cc) Icon in the public domain.
	adobe indesign (cc) Icon in the public domain.		adobe lightroom (cc) Icon in the public domain.
	Adobe Photoshop (CS6, CC, 2022) Icon in the public domain.		Affinity Designer 2 Icon under CC-BY-SA 4.0 via Serif Ltd.
	intimacy photo 2 Icon under CC-BY-SA 4.0 via Serif Ltd.		Affinity Publisher 2 Icon under CC-BY-SA 4.0 via Serif Ltd.
	Affinity (v3) by Canva Icon in the public domain.		command prompt (cmd.exe) Icon under MIT license.
	file Explorer (Windows Explorer) Icon in the public domain.		Internet Explorer (11) Icon in the public domain.
	Microsoft Access (2016, 2019, o365) Icon in the public domain.		Microsoft Excel (2016, 2019, o365) Icon in the public domain.
	Microsoft Word (2016, 2019, o365) Icon in the public domain.		Microsoft OneNote (2016, 2019, o365) Icon in the public domain.
	Microsoft Outlook (2016, 2019, o365) Icon in the public domain.		Microsoft Powerpoint (2016, 2019, o365) Icon in the public domain.
	Microsoft Publisher (2016, 2019, o365) Icon in the public domain.		Microsoft Visio (Standard/Prof. 2021, Plan 2) Icon in the public domain.
	Microsoft Project (Standard/Prof. 2021, Scheme 3/5) Icon in the public domain.		Microsoft Visual Studio (Comm./Pro./Ent. 2022) Icon in the public domain.
	autodesk fusion 360 Icon in the public domain.		merck Icon in the public domain.
	powershell Icon under MIT license.		windows (full RDP session) Icon in the public domain.

Both Docker And Podman Backends are recommended for running Windows virtual machines, as they facilitate the automated Windows installation process. Also compatible with WinApps libvirtAlthough this method requires significantly more manual configuration, it also offers more virtual machine customization options, All three methods take advantage of KVM The hypervisor ensures excellent virtual machine performance. Ultimately, the choice of backend depends on your specific use case.

The following guides are available:

If you already have a Windows VM or Server that you want to use with WinApps, you will still need to follow the last steps described in libvirt Documentation.

Install required dependencies.

• Debian/Ubuntu:

  sudo apt install -y curl dialog freerdp3-x11 git iproute2 libnotify-bin netcat-openbsd

• Fedora/RHEL:

  sudo dnf install -y curl dialog freerdp git iproute libnotify nmap-ncat

• Arch Linux:

  sudo pacman -Syu --needed -y curl dialog freerdp git iproute2 libnotify openbsd-netcat

• openSUSE:

  sudo zypper install -y curl dialog freerdp git iproute2 libnotify-tools netcat-openbsd

• Gentoo Linux:

  sudo emerge --ask=n net-misc/curl dev-util/dialog net-misc/freerdp:3 dev-vcs/git sys-apps/iproute2 x11-libs/libnotify net-analyzer/openbsd-netcat

flatpak install flathub com.freerdp.FreeRDP
sudo flatpak override --filesystem=home com.freerdp.FreeRDP # To use `+home-drive`

Create a configuration file here ~/.config/winapps/winapps.conf Containing the following:

##################################
#   WINAPPS CONFIGURATION FILE   #
##################################

# INSTRUCTIONS
# - Leading and trailing whitespace are ignored.
# - Empty lines are ignored.
# - Lines starting with '#' are ignored.
# - All characters following a '#' are ignored.

# [WINDOWS USERNAME]
RDP_USER="MyWindowsUser"

# [WINDOWS PASSWORD]
# NOTES:
# - If using FreeRDP v3.9.0 or greater, you *have* to set a password
RDP_PASS="MyWindowsPassword"

# [WINDOWS DOMAIN]
# DEFAULT VALUE: '' (BLANK)
RDP_DOMAIN=""

# [WINDOWS IPV4 ADDRESS]
# NOTES:
# - If using 'libvirt', 'RDP_IP' will be determined by WinApps at runtime if left unspecified.
# DEFAULT VALUE:
# - 'docker': '127.0.0.1'
# - 'podman': '127.0.0.1'
# - 'libvirt': '' (BLANK)
RDP_IP="127.0.0.1"

# [VM NAME]
# NOTES:
# - Only applicable when using 'libvirt'
# - The libvirt VM name must match so that WinApps can determine VM IP, start the VM, etc.
# DEFAULT VALUE: 'RDPWindows'
VM_NAME="RDPWindows"

# [WINAPPS BACKEND]
# DEFAULT VALUE: 'docker'
# VALID VALUES:
# - 'docker'
# - 'podman'
# - 'libvirt'
# - 'manual'
WAFLAVOR="docker"

# [DISPLAY SCALING FACTOR]
# NOTES:
# - If an unsupported value is specified, a warning will be displayed.
# - If an unsupported value is specified, WinApps will use the closest supported value.
# DEFAULT VALUE: '100'
# VALID VALUES:
# - '100'
# - '140'
# - '180'
RDP_SCALE="100"

# [MOUNTING REMOVABLE PATHS FOR FILES]
# NOTES:
# - By default, `udisks` (which you most likely have installed) uses /run/media for mounting removable devices.
#   This improves compatibility with most desktop environments (DEs).
# ATTENTION: The Filesystem Hierarchy Standard (FHS) recommends /media instead. Verify your system's configuration.
# - To manually mount devices, you may optionally use /mnt.
# REFERENCE: https://wiki.archlinux.org/title/Udisks#Mount_to_/media
REMOVABLE_MEDIA="/run/media"

# [ADDITIONAL FREERDP FLAGS & ARGUMENTS]
# NOTES:
# - You can try adding /network:lan to these flags in order to increase performance, however, some users have faced issues with this.
#   If this does not work or if it does not work without the flag, you can try adding /nsc and /gfx.
# DEFAULT VALUE: '/cert:tofu /sound /microphone +home-drive'
# VALID VALUES: See https://github.com/awakecoding/FreeRDP-Manuals/blob/master/User/FreeRDP-User-Manual.markdown
RDP_FLAGS="/cert:tofu /sound /microphone +home-drive"

# [DEBUG WINAPPS]
# NOTES:
# - Creates and appends to ~/.local/share/winapps/winapps.log when running WinApps.
# DEFAULT VALUE: 'true'
# VALID VALUES:
# - 'true'
# - 'false'
DEBUG="true"

# [AUTOMATICALLY PAUSE WINDOWS]
# NOTES:
# - This is currently INCOMPATIBLE with 'manual'.
# DEFAULT VALUE: 'off'
# VALID VALUES:
# - 'on'
# - 'off'
AUTOPAUSE="off"

# [AUTOMATICALLY PAUSE WINDOWS TIMEOUT]
# NOTES:
# - This setting determines the duration of inactivity to tolerate before Windows is automatically paused.
# - This setting is ignored if 'AUTOPAUSE' is set to 'off'.
# - The value must be specified in seconds (to the nearest 10 seconds e.g., '30', '40', '50', etc.).
# - For RemoteApp RDP sessions, there is a mandatory 20-second delay, so the minimum value that can be specified here is '20'.
# - Source: https://techcommunity.microsoft.com/t5/security-compliance-and-identity/terminal-services-remoteapp-8482-session-termination-logic/ba-p/246566
# DEFAULT VALUE: '300'
# VALID VALUES: >=20
AUTOPAUSE_TIME="300"

# [FREERDP COMMAND]
# NOTES:
# - WinApps will attempt to automatically detect the correct command to use for your system.
# DEFAULT VALUE: '' (BLANK)
# VALID VALUES: The command required to run FreeRDPv3 on your system (e.g., 'xfreerdp', 'xfreerdp3', etc.).
FREERDP_COMMAND=""

# [TIMEOUTS]
# NOTES:
# - These settings control various timeout durations within the WinApps setup.
# - Increasing the timeouts is only necessary if the corresponding errors occur.
# - Ensure you have followed all the Troubleshooting Tips in the error message first.

# PORT CHECK
# - The maximum time (in seconds) to wait when checking if the RDP port on Windows is open.
# - Corresponding error: "NETWORK CONFIGURATION ERROR" (exit status 13).
# DEFAULT VALUE: '5'
PORT_TIMEOUT="5"

# RDP CONNECTION TEST
# - The maximum time (in seconds) to wait when testing the initial RDP connection to Windows.
# - Corresponding error: "REMOTE DESKTOP PROTOCOL FAILURE" (exit status 14).
# DEFAULT VALUE: '30'
RDP_TIMEOUT="30"

# APPLICATION SCAN
# - The maximum time (in seconds) to wait for the script that scans for installed applications on Windows to complete.
# - Corresponding error: "APPLICATION QUERY FAILURE" (exit status 15).
# DEFAULT VALUE: '60'
APP_SCAN_TIMEOUT="60"

# WINDOWS BOOT
# - The maximum time (in seconds) to wait for the Windows VM to boot if it is not running, before attempting to launch an application.
# DEFAULT VALUE: '120'
BOOT_TIMEOUT="120"

# FREERDP RAIL HIDEF
# - This option controls the value of the `hidef` option passed to the /app parameter of the FreeRDP command.
# - Setting this option to 'off' may resolve window misalignment issues related to maximized windows.
# DEFAULT VALUE: 'on'
HIDEF="on"

chown $(whoami):$(whoami) ~/.config/winapps/winapps.conf
chmod 600 ~/.config/winapps/winapps.conf

• If you are using an already existing Windows RDP server on your LAN, you should use RDP_IP To specify the location of Windows Server. You may also want to configure a static IP address for this server.
• If running using a Windows VM libvirt When NAT is enabled, skip RDP_IP Commented out and WinApps will automatically detect the local IP address for the VM.
• For domain users, you can cancel and change comments RDP_DOMAIN,
• On high-resolution (UHD) displays, you can set RDP_SCALE On the scale you want to use (100, 140 or 180).
• To add additional flags to the FreeRDP call (e.g. /prevent-session-lock 120), remove comment and use RDP_FLAGS Configuration options.
• For multi-monitor setup, you can try adding /multimon To RDP_FLAGSHowever, the FreeRDP bug may result in a black screen, in which case you should revert this change,
• To enable non-English input and seamless language switching, you can try adding /kbd:unicode To RDP_FLAGSThis ensures that client inputs are sent as Unicode sequences,
• If you enable DEBUGA log will be created at each application start ~/.local/share/winapps/winapps.log,
• If using a system that does not have the FreeRDP command xfreerdp Or xfreerdp3can be specified using the correct command FREERDP_COMMAND,

1. Test establishing an RDP session, by running the following command /u:, /p:And /v: Values ​​with correct values ​​specified in ~/.config/winapps/winapps.conf,

   xfreerdp3 /u:"Your Windows Username" /p:"Your Windows Password" /v:192.168.122.2 /cert:tofu
   
   # Or, if you are using Podman
   podman unshare --rootless-netns xfreerdp3 /u:"Your Windows Username" /p:"Your Windows Password" /v:127.0.0.1 /cert:tofu
   
   # Or, if you installed FreeRDP using Flatpak
   flatpak run --command=xfreerdp com.freerdp.FreeRDP /u:"Your Windows Username" /p:"Your Windows Password" /v:192.168.122.2 /cert:tofu

   • Please note that is correct FreeRDP The command may vary depending on your system (e.g. xfreerdp, xfreerdp3etc.).
   • Make sure you use the correct IP address for your Windows instance in the above command.
   • If prompted in the terminal window, choose to accept the certificate permanently.

   If the Windows desktop appears in a FreeRDP Window, configuration was successful and the correct RDP TLS certificate was enrolled on the Linux host. Disconnect from the RDP session and skip the following debugging steps.

2. [DEBUGGING STEP] If an old or expired certificate is detected, FreeRDP The command will display output like the following. In this case, the old certificate must be removed and a new RDP TLS certificate must be installed.

   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   @           WARNING: CERTIFICATE NAME MISMATCH!           @
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   
   The hostname used for this connection (192.168.122.2:3389)
   does not match the name given in the certificate:
   Common Name (CN):
           RDPWindows
   A valid certificate for the wrong name should NOT be trusted!
   
   The host key for 192.168.122.2:3389 has changed
   
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
   
   IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
   Someone could be eavesdropping on you right now (man-in-the-middle attack)!
   It is also possible that a host key has just been changed.
   The fingerprint for the host key sent by the remote host is 8e:b4:d2:8e:4e:14:e7:4e:82:9b:07:5b:e1:68:40:18:bc:db:5f:bc:29:0d:91:83:f9:17:f9:13:e6:51:dc:36
   Please contact your system administrator.
   Add correct host key in /home/rohanbarar/.config/freerdp/server/192.168.122.2_3389.pem to get rid of this message.
   

   If you experience the above error, remove any old or outdated RDP TLS certificates associated with Windows, as they may prevent FreeRDP By establishing relationships.

   These certificates are located within ~/.config/freerdp/server/ and follow the naming format _.pem (As, 192.168.122.2_3389.pem, 127.0.0.1_3389.pemetc.).

   If you use FreeRDP for purposes other than WinApps, make sure you only delete certificates related to the relevant Windows VM. If no relevant certificates are found, no action is required.

   After deletion, retry establishing the RDP session.

With Windows still running, run the WinApps installer.

bash <(curl https://raw.githubusercontent.com/winapps-org/winapps/main/setup.sh)

Once WinApps is installed, a list of additional arguments can be accessed by running winapps-setup --help,

It’s easy to add your own applications with custom icons and MIME types in the installer. Simply copy one of the application configurations apps Folder located within the WinApps repository, and:

1. Modify the names and variables to reflect appropriate/desired values ​​for your application.
2. replace the icon.svg With an SVG for your application (make sure the icon is appropriately licensed).
3. Delete and reinstall WinApps.
4. Once you have tested and verified your configuration (optional, but encouraged) submit a pull request to add your application to WinApps as a community tested application.

WinApps provides a manual mode for running applications that were not configured by the WinApps installer. It is completed with manual flag. Executables that are in the Windows PATH do not require an absolute path definition.

winapps manual "C:\my\directory\executableNotInPath.exe"
winapps manual executableInPath.exe

The installer can be run multiple times. To update your installation of WinApps:

1. Run the WinApps installer to remove WinApps from your system.
2. Get the latest changes from the WinApps GitHub repository.
3. Reinstall WinApps using the WinApps Installer winapps-setup,

WinApps Launcher provides a simple system tray menu that makes it easy to launch your installed Windows applications, open a full desktop RDP session, and control your Windows VM or container. You can start, stop, pause, reboot, or hibernate Windows, as well as access your installed applications from a convenient list. This lightweight, optional tool helps streamline your overall WinApps experience.

First, follow Step 1 of the general installation guide to create your VM. Then, install WinApps according to the following instructions.

After installation it will be available below winappsWith available under installer winapps-setup
and available under alternative launchers winapps-launcher.

First, make sure that the flex and nix Orders are enabled. in your ~/.config/nix/nix.conf,

experimental-features = nix-command flakes

nix profile install github:winapps-org/winapps#winapps
nix profile install github:winapps-org/winapps#winapps-launcher # optional

# flake.nix
{
  description = "My configuration";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";

    winapps = {
      url = "github:winapps-org/winapps";
      inputs.nixpkgs.follows = "nixpkgs";
    };
  };

  outputs =
    inputs@{
      nixpkgs,
      winapps,
      ...
    }:
    {
      nixosConfigurations.hostname = nixpkgs.lib.nixosSystem rec {
        system = "x86_64-linux";

        specialArgs = {
          inherit inputs system;
        };

        modules = [
          ./configuration.nix
          (
            {
              pkgs,
              system ? pkgs.system,
              ...
            }:
            {
              environment.systemPackages = [
                winapps.packages."${system}".winapps
                winapps.packages."${system}".winapps-launcher # optional
              ];
            }
          )
        ];
      };
    };
}

Flexes are not real and they can’t harm you.. However, if you still don’t want to use flexes, you can use WinApps with flake-compat like:

# configuration.nix
{
  pkgs,
  system ? pkgs.system,
  ...
}:
{
  # set up binary cache (optional)
  nix.settings = {
    substituters = [ "https://winapps.cachix.org/" ];
    trusted-public-keys = [ "winapps.cachix.org-1:HI82jWrXZsQRar/PChgIx1unmuEsiQMQq+zt05CD36g=" ];
    trusted-users = [ "" ]; # replace with your username
  };

  environment.systemPackages =
    let
      winapps =
        (import (builtins.fetchTarball "https://github.com/winapps-org/winapps/archive/main.tar.gz"))
        .packages."${system}";
    in
    [
      winapps.winapps
      winapps.winapps-launcher # optional
    ];
}