eylenburg/linoffice

LinOffice - Microsoft Office launcher for Linux

LinOffice enables you to run Microsoft Office applications in Linux. In the background, it runs a virtual machine with Windows and Office installed which is then accessed via FreeRDP. LinOffice’s aim is to be a "1-click" setup for Microsoft Office in Linux.

By default, Microsoft Office 2024 (Home & Retail) is installed, containing Word, Excel, Powerpoint, Onenote and Outlook. If you have a Microsoft Office 365 subscription you can log in with your Microsoft account and it should upgrade from 2024 to 365.

The project utilises Winapps, Dockur/Windows, FreeRDP, Podman, and Qemu. You can run LinOffice alongside WinApps - all the names and …

LinOffice - Microsoft Office launcher for Linux

The project utilises Winapps, Dockur/Windows, FreeRDP, Podman, and Qemu. You can run LinOffice alongside WinApps - all the names and RDP ports have been changed to avoid conflicts between the two.

Screenshot

Features

Automatic non-interactive setup
Run Microsoft Office apps as if they were native Linux apps
Office apps have access to /home folder and Linux clipboard
Run Publisher or Access, if manually installed by user
Quickly access useful tools such as Powershell, Command Prompt, Windows Explorer, Registry Editor, Office Language Settings
Run a full Windows session via RDP or VNC
Automatic suspension of the Windows container when inactive, resume when starting an Office app
Automatic deletion of Office lock files (like ~$file.docx)
Force time sync in Windows after Linux host wakes up from sleep, to avoid time drift (time zone is always set to UTC for simplicity)
Automatic detection of language, date format, thousand and decimal separator, currency symbol, keyboard layout etc
Toggle settings such as display scaling, auto-suspend on/off, network on/off (to prevent Windows and Office from "phoning home")
Circumvent geo-blocking for the Office installation
Install updates for Windows and Office
Tidy Quick Access pane in Windows File Explorer
Automatically debloats Windows and disables telemetry and ads, using Win11Debloat
Troubleshooting functions e.g. force cleanup of Office lock files, recreate .desktop files for the Office apps, reboot the Windows container, container health check Planned features

Planned features

Logo to use for the GUI
Translations for the GUI
Deliver as Flatpak or AppImage, which would have these benefits:
Bundles dependencies such as FreeRDP and Podman-Compose; only Podman would need to be installed on the system already
Installation and uninstallation more straight-forward for Linux beginners
Code changes needed:
APPDATA folder should not be hardcoded (in setup.sh, linoffice.sh, mainwindow.py, installer.py, linoffice.py, TimeSync.ps1, FirstRunRDP.ps1, and RegistryOverride.ps1) or at least only hardcoded in one of them and then read by the others (like uninstall.sh is doing).
Flatpak would not allow creatingfiles in the config folder inside the app’s folder (compose.yaml, linoffice.conf, oem/registry/regional-settings.reg), so it might be better to to move this whole folder out of the app directory and change the file references (perhaps copy to the APPDATA folder)

Nice to have but lower priority

ARM support (should be possible as both Windows and Office have ARM versions)
Support for non-core Office apps (e.g. Access, Publisher, Visio)
Support for older Office versions (e.g. 2016, 2019, 2021)

Comparison with other options to run Microsoft Office in Linux

*requires manual setup, e.g. VirtIO-win and WinFSP or Samba when using Virt-Manager/Qemu, or Virtualbox Guest Additions for Virtualbox

**PlayOnLinux 4 has install scripts for Office 2016 and below that may or may not work

Installation

All Linux distributions are supported.

Hardware requirements:

Sufficient resources (the Windows VM is allowed to take up to 4 GB RAM, 64 GB storage and 4 CPU cores if needed). The script will check that you have at least 8 GB RAM and 64 GB free storage before proceeding.
Virtualization support (using kvm)
x86_64 CPU (ARM is currently not supported, although it would be possible)
Fast Internet connection as you will need to download several GB from Micrsoft

Quickinstall

To download and install LinOffice and all the necessary dependencies, run this in a terminal:

curl -sSL https://github.com/eylenburg/linoffice/raw/refs/heads/main/quickstart.sh -o quickstart.sh && chmod +x quickstart.sh && ./quickstart.sh

This should automatically install all the required dependencies for most distros and should work with most distros.

Note

The script will install Podman, Podman-Compose, FreeRDP3, Python3 and PySide6 on your computer. If they are not available in your repo, they will be installed via Flatpak or Pip where possible.

Warning

The quickstart script will fail if you are using NixOS, Guix System, Slackware, Gentoo, or Alpine. In this case you will need to do install the dependencies yourself (see below).

Manual install

Dependencies

Dependencies that need to be installed:

Podman
Podman-Compose
FreeRDP (v3)
Python3 (optional, for the GUI)
PySide6 (optional, for the GUI) How to install the dependencies
Ubuntu & Debian: sudo apt install podman podman-compose freerdp3 python3 pyside6
make sure your repo has FreeRDP v3 is only available from Debian 13 and Ubuntu 24.04 onwards; in older versions you need to use backports or install the Flatpak version of FreeRDP
PySide6 is only available from Debian 13 and Ubuntu 24.10 (!) onwards; in older versions you need to use backports or install them via pip
Arch: sudo pacman -Syu podman podman-compose freerdp python pyside6
OpenSUSE: sudo zypper install podman podman-compose freerdp python3 python3-pyside6
Fedora: sudo dnf install podman podman-compose freerdp python3 python-pyside6
Fedora Atomic: rpm-ostree install podman-compose freerdp python-pyside6, then reboot (podman and python3 are already preinstalled)
OpenMandriva: sudo dnf install podman podman-compose freerdp python pyside6

Podman-Compose and PySide6 can also be installed via pip. FreeRDP can also be installed as a Flatpak, but make sure to give it permission to access the /home folder.

Run the installer

First, install the dependencies (see above).

Then:

Download this repo (e.g. release version or latest git version)
Unzip and save in a convenient folder (e.g. ~/.local/bin/linoffice)
Either run the setup script (chmod +x setup.sh && ./setup.sh) or start the GUI which will automatically set things up (python3 gui/linoffice.py)

The installation should do everything automatically but will take quite a while. You need to download about 8 GB in total and wait until both Windows and Office are installed. In my experience, on a modern laptop (2023 mid-range AMD Ryzen CPU) and with fast Internet (250 Mbps download), it took about 15 minutes all in (breakdown: 3 minutes Windows download, 8 minutes Windows install, 4 minutes Office download and install).

If the setup succeeds without issues, please share your system setup which will be very helpful in order to know where LinOffice works out of the box.

Notes on the Windows version

By default, Windows 11 Pro will be installed. If you want, you can also install Windows 10, which should be a bit snappier. To do that, replace VERSION: "11" with VERSION: "10" in the config/compose.yaml.default file before running setup.sh. Microsoft will end mainstream support for Windows 10 in October 2025, but after the installation you can use Microsoft Activation Script (MAS) to extend Windows 10 updates until 2028.

Unfortunately it is not allowed to redistribute Microsoft software, otherwise I would have just prepared a pre-made VM with Office installed, which would cut down the installation time and make this whole project much simpler. At the moment, the script downloads Windows, installs it into a VM, then downloads Office and installs it in the VM, as well as various other tweaks to integrate Office.

Updating

LinOffice: There’s a built-in updater in the GUI. Otherwise, you can manually download the newest version and replace the old files with it. Don’t delete all of your old files (as there are some files that will be created during the initial setup), just overwrite any existing ones.
If you already have a working Windows VM from LinOffice v1.0.7 and below, and you want to update, all the files in linoffice/config/oem will need to be manually copied again into C:\OEM in the Windows VM, overwriting any existing ones. In the RDP session (./linoffice.sh windows) you can access your Linux /home folder at \\tsclient\home.
Windows & Office: Should auto-update but there’s also an update script in the GUI (or you can run ./linoffice.sh update from the terminal.)

Uninstall

You can run the uninstall.sh to remove everything or click on the Uninstall button in the "Troubleshooting" menu.

Where are the files saved?

If you want to manually remove the files:

The self-contained folder where you have saved the linoffice.sh script
The appdata folder for temporary files is in ~/.local/share/linoffice
The .desktop files (Excel, Onenote, Outlook, Powerpoint, Word) will be created in ~/.local/share/applications
The Podman containers, which include the Windows VM, can be removed with podman rm -f LinOffice && podman volume rm linoffice_data

Usage

Starting Office applications

After installation, you should find the launchers for the Office applications in your app menu.

Opening Office files

You can open files from your file manager with Right-click -> Open with.

Using the GUI

You will find a launcher for "LinOffice" in your app menu.

Using the terminal

If you are using the terminal commands often, you might want to create an alias by running echo "alias linoffice='/home/user/.local/bin/linoffice/linoffice.sh'" >> ~/.bashrc && source ~/.bashrc - but make sure to adjust the username and path to where your linoffice.sh script is saved. This will enable you to run the LinOffice script from anywhere with the linoffice command.

linoffice [excel|word|powerpoint|onenote|outlook]: runs one of the predefined Office applications
linoffice manual [msaccess.exe|mspub.exe]: run Microsoft Access or Microsoft Publisher, if installed (they are not part of the default Office version installed by LinOffice)
linoffice manual [explorer.exe|regedit.exe|powershell.exe|cmd.exe]: runs a specific Windows app in the Windows PATH
linoffice manual "C:\Program Files\Microsoft Office\root\Office16\SETLANG.EXE": like above, but for any application (here: Microsoft Office Language Preferences tool)
linoffice windows: shows the whole Windows desktop in an RDP session
linoffice update: runs an update script for Windows in Powershell
linoffice reset: kills all FreeRDP processes, cleans up Office lock files, and reboots the Windows VM
linoffice stopcontainer: stops and then removes the podman container (but not its data) and cleans up all associated resources
linoffice cleanup [--full|--reset]: cleans up Office lock files (such as ~$file.xlsx) in the home folder and removable media; --full cleans all files regardless of creation date, --reset resets the last cleanup timestamp

The setup script (setup.sh) has these CLI options:

./setup.sh --desktop: Only (re)create the .desktop files (app launchers)
./setup.sh --firstrun: Force RDP and Office installation checks (can be used after the Windows VM has finished installation)
./setup.sh --installoffice: Only run the Office installation script script (in case the Windows installation has finished but Office is not installed)
./setup.sh --healthcheck: Check that the system requirements are met and dependencies are installed and the container is healthy (there is also a button for this in the GUI)

Office activation

You will need an Office 2024 license key or Office 365 subscription to use Office. During the first 5 days after installation, you can use Office without activation by clicking on "I have a product key" and then on the "X" of the window where you are supposed to enter your product key.

The Microsoft Activation Scripts (MAS) will also work if you have, let’s say, trouble with activation - just run ./linoffice.sh manual powershell.exe from the script’s directory to open a Powershell window where you can then paste the command to run MAS.

Printing

The Office application are running in a virtual machine with Windows, meaning that the printers you have set up in Linux are not available. There are two options if you need to print from Office:

Print to PDF / export to PDF and then print the PDF from Linux
If you have a network printer you can easily install it in Windows. Find out its local IP address (e.g. with lpstat -v), then open the Windows VM (e.g. via the Tools menu in LinOffice), then Settings -> Printers and Scanners -> Add Device -> Add a new device manually -> Add printer using IP Address

Troubleshooting

Problems with the setup

If you have problems with the setup script, such as Office not being found or FreeRDP not connecting, do the following:

Access the VM through 127.0.0.1:8006 in the browser (password to log in is MyWindowsPassword) and check:

Does the VM run and let you log in? If not, check windows_install.log (in ~/.local/share/linoffice) to see what could have gone wrong.
Is Microsoft Office installed? If not, try to download and install Office manually, then create an empty file (not folder) called success in C:\OEM\, then sign out (!) of the Windows account using the Start Menu but don’t shut down Windows

After this, run ./setup.sh --firstrun from Linux

If it works now, congratulations.

If you still get an error, test if you can connect to the VM using RDP.

Make sure you are not still logged in via VNC (i.e. in the browser); if you are, sign out the Windows user account
Check what the correct command for FreeRDP is on your system. This can be xfreerdp3 or (less likely) xfreerdp, or if you have installed it through Flatpak, it would be flatpak run --command=xfreerdp com.freerdp.FreeRDP.
Run this command, but make sure to use the correct FreeRDP command at the beginning: xfreerdp3 /cert:ignore /u:MyWindowsUser /p:MyWindowsPassword /v:127.0.0.1 /port:3388 — It should open a window showing the Windows VM. If yes, close the window.
Run this command, but make sure to use the correct FreeRDP command at the beginning: xfreerdp3 /cert:ignore /u:MyWindowsUser /p:MyWindowsPassword /v:127.0.0.1 /port:3388 /app:program:explorer.exe — It should open a window with the Windows File Explorer. If yes, close the window.
Run this command, but make sure to use the correct FreeRDP command at the beginning: xfreerdp3 /cert:ignore /u:MyWindowsUser /p:MyWindowsPassword /v:127.0.0.1 /port:3388 /app:program:excel.exe — It should open a window with Excel. If yes, close the window.
After this, run ./setup.sh --firstrun from Linux again and hopefully it succeeds now.

If there is still a problem in the setup, even though you have just confirmed that Office is installed and you can launch Office applications from Linux using FreeRDP, do this:

In ~/.local/share/linoffice/ edit the file called setup_progress.log and add the line office_installed at the end if it doesn’t yet exist
Run ./setup.sh --desktop to create .desktop files (app launchers in Linux)

Now you should be able to find the "Linoffice" GUI as well as the starters for Word, Excel etc. in your Linux menu.

If you still can’t get the setup to work, please create a bug report ("setup didn’t work") with these information:

The windows_install.log and setup_output.log (in ~/.local/share/linoffice)
The setup.log, setup_office.log, and setup_rdp.log (if they exist) in C:\OEM in the Windows VM (if you can only access the VM through the browser/VNC, there is no clipboard sharing with Linux, so a screenshot is fine)
Your system information (LinOffice version, Linux distribution, desktop environment, Wayland or X11, how did you install podman, podman-compose and freerdp?)

Logging in to Microsoft

Some users have reported the issue that when they try to log in to Microsoft (e.g. in order to activate Microsoft 365) they login window would hang and not progress. The workaround for this access a "full" RDP session (in GUI: Tools -> Access Windows desktop via RDP; in CLI: ./linoffice.sh windows). You should be able to log in in this session. Afterwards, you can close the window and use LinOffice as usual.

Window management

In my experience, window management can be wonky, particularly if you’re using Wayland instead of X11 or if you’re using multiple monitors.

A potential solution for multimonitor issues could be to open the file config/linoffice.conf and in the last line (RDP_FLAGS) adding /multimon. This is supposed to add multimonitor support to FreeRDP, but a FreeRDP bug may result in a black screen, in which case you should revert this change.

Examples

Using multiple Office documents/windows can be tricky. For example, opening an Office window might not open until you start it a second time and you may or may not get two windows then. Or, opening a new Office window might close already open ones. Don’t panic - your documents are not lost. Just launch the latest Office window again and you should now see both the new one and old one. Sometimes, opening a new windows might also have the quirk that the focus is on the older Office window which is sitting in the background. The solution is to minimize the old one so that the focus is gone..
Moving and resizing windows does not always work well, particularly on setups with multiple monitors. Most desktop environments use the shortcut "Meta or Alt + Left-Click" for moving a window and and "Meta or Alt + Right-Click" for resizing; this is a very reliable to move around or resize Office windows.
Dialog boxes (commonly encountered when working with charts in Excel for example) spawn as new, separate windows, but they can sometimes appear behind the main window and at the same time block the main window until you close the dialog box.
Dialog windows may also have a bad size, e.g. the "edit chart data" window in Excel often cuts off the "OK" at the bottom. The solution, again, is to resize the window using a shortcut like "Meta or Alt + Right-Click" in order to access the "OK" button.

I believe that these are FreeRDP issues. If it becomes too bad, you can try ./linoffice.sh reset to kill all FreeRDP processes and reboot the Windows VM - but be aware that you will lose any unsaved Office documents this way.

Wrong keyboard layout

Theoretically, this should be done automatically by the setup script but it might fall back to the US layout if it doesn’t detect your Linux keyboard layout or can’t match it to a Microsoft keyboard layout. There are two ways to manually set the keyboard layout:

Option 1:

In the GUI, you can choose the keyboard layout in Settings. If you’re not using the GUI you can achieve the same thing manually:
In the LinOffice folder, open the config/linoffice.conf and find the row saying RDP_KBD="".
Check this list of keyboard layouts to find the numeric code for your keyboard layout in the first code.
Edit the line in the config file like these examples: RDP_KBD="/kbd:layout:0x0809" for the UK keyboard or RDP_KBD="/kbd:layout:0x0407" for the German keyboard

Option 2 (if the above doesn’t work):

Access the Windows VM, either via RDP (./linoffice.sh windows) or VNC (127.0.0.1:8006 in the browser, password is MyWindowsPassword)
Open the Windows Settings app and set your keyboard layout in there.
Open the Command Prompt (cmd.exe) and enter: REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layout" /v IgnoreRemoteKeyboardLayout /t REG_DWORD /d 1 (this tells Windows to use its own keyboard layout and not whatever the RDP client uses)

If you are using multiple keyboard layouts in Linux (e.g. a Latin and non-Latin script, changing the keyboard automatically is not supported yet (i.e. syncing the Windows keyboard layout with the Linux one whenever it is switched), but there is a workaround: winapps-org/winapps#43 (comment)

Orphaned lock files

There is a strange issue that Microsoft Office will not clean up the lock files in the Linux /home folder. If you open, say, "Book1.xlsx" then Excel will create a file called "~$Book1.xlsx" which is just a few bytes in size and serves the purpose of "locking" this file so other users can’t edit it at the same time. Normally these files should be deleted when you close the file, but this doesn’t happen for whatever reason. The /home folder is mounted by FreeRDP and appears in Windows as a network drive accessed via RDP Drive Redirection (RDPDR).

LinOffice searches and deletes these lock files when the last Office process is closed. If this fails for any reason you can manually delete all lock files by running ./linoffice.sh cleanup --full or by using the button in the "Troubleshooting" window.

How to hide these lock files in KDE’s Dolphin file manager

Go to KDE System Settings -> Default Applications -> File Associations, then search for the mime type corresponding to .xlsx (in this case it’s called application/vnd.openxmlformats-officedocument.spreadsheetml.sheet). Select the existing filename pattern (*.xlsx) and click - Remove and then click + Add and enter [!~][!$]*.xlsx. Do the same for docx and pptx, and, if you use them, odt, ods, odp, docm, xlsm and pptm.

(By default files starting with ~$ have the mime type application/x-trash. By making the above change, a file like "~$Book1.xlsx" will be seen as a trash file rather than a spreadsheet.)

Open Dolphin, go to Configure Dolphin -> View and check [x] Also hide backup files when hiding files.

("Backup files" in this case actually refers to all files with the application/x-trash mime type.)

For developers

These are the files that are part of LinOffice and their functions:

File list

quickstart.sh: Script that installs all required dependencies (new ones are remembered in ~/.local/share/linoffice/installed_dependencies, downloads the latest version of LinOffice from GitHub and then launches src/gui/linoffice.py, which will most likely end up running the graphical installer
src/setup.sh: Install script for LinOffice. Checks requirements are met and dependencies are installed, calls locale_lang.sh and locale_reg.sh to set various location settings, downloads Windows and sets up a Windows VM, installs Office in the VM, tries to connect via RDP, executes FirstRDPRun.ps1 script in Windows, and creates app launchers.
src/linoffice.sh: Main script that is used when running LinOffice. It manages the Podman container (e.g. start or unsuspend) and runs the correct FreeRDP command for the Office (and other) applications.
src/uninstall.sh: Uninstall script. Removes program launchers in ~/.local/share/applications, removes all LinOffice files in ~/.local/bin/linoffice/ and ~/.local/share/linoffice/, offers to removes dependencies that were installed by quickstart.sh (as noted down in ~/.local/share/linoffice/installed_dependencies), offers to remove the LinOffice Podman container and its data.
src/updater.py: Checks if a newer version of LinOffice is available on GitHub and updates the files.
src/gui/linoffice.py: Either starts the installation process (installer.py) or launches the LinOffice GUI (mainwindow.py).
src/gui/mainwindow.py: The main GUI for LinOffice.
src/gui/*.ui: Various XML files defining the graphical user interface for the main app.
src/gui/installer/installer.py: Graphical version of the installer, which mainly just runs setup.sh.
src/gui/installer/remove_container.sh: Script to remove the Podman container if the installation is aborted.
src/gui/installer/*.ui: Various XML files defining the graphical user interface for the installer.
src/config/locale_lang.sh: Copies the compose.yaml.default to a new file called compose.yaml, copies the linoffice.conf.default to a new file called linoffice.conf. Determines the language settings in the Linux host (system language, region, keyboard layout) and applies them to compose.yaml and linoffice.conf.
src/config/compose.yaml.default: Template compose file. The version created by locale_lang.sh, compose.yaml, is used by podman-compose to create the Windows container. It also includes some settings the user can change before installation, e.g. using a different Windows version.
src/config/linoffice.conf.default: Template config file. The version created by locale_lang.sh, linoffice.conf, is used by linoffice.sh to read various settings, including the auto-pause timer for Windows, keyboard layout, display scaling, and various FreeRDP flags.
src/config/locale_reg.sh: Determines additional language settings in the Linux host that are particularly relevant for Excel (decimal and thousand separator, currency symbol, date format) and creates a registry file in src/config/oem/registry/regional_settings.reg which is the applied by install.bat.
src/config/languages.csv: List of keyboard layouts and their corresponding Windows/FreeRDP codes
src/config/oem/install.bat: Script that runs at the end of the Windows installation, before the desktop is shown for the first time. It applies the registry settings (all files in src/config/oem/registry, including the regional_settings.reg created by locale_reg.sh), creates NetProfileCleanup.ps1 and TimeSync.ps1 as scheduled tasks, sets the time zone to UTC, runs Win11Debloat, schedules running InstallOffice.ps1 after a reboot and then reboots the VM.
src/config/oem/OfficeConfiguration.xml: Config file for the automatic installation of Office, e.g. which version of Office to install. It is used by Office Deployment Tool.
src/config/oem/InstallOffice.ps1: Scheduled by install.bat. Downloads Office Deployment Tool from Microsoft and runs it to install Microsoft Office using the configuration in OfficeConfiguration.xml. Then creates an empty file called C:\OEM\success and reboots the machine. This is the fourth reboot (three occur during the Windows installation) which will signal to setup.sh that the virtual machine is all set up now.
src/config/oem/NetProfileCleanup.ps1: A scheduled task created by install.bat. It renames the current network profile to LinOffice and deletes all other ones.
src/config/oem/TimeSync.ps1: A scheduled task created by install.bat. It syncs the time if a file called \\tsclient\home\.local\share\linoffice\sleep_marker is detected, which is created by linoffice.sh after the Linux host machine is suspended (which would introduce a time drift between the host and the VM).
src/config/oem/FirstRDPRun.ps1: Creates a success file in Linux if the C:\OEM\success file exists in Windows (confirming a successful Office installation) and runs QuickAccess.ps1. This script is called by setup.sh.
src/config/oem/QuickAccess.ps1: Cleans up the quick access in Windows File Explorer by unpinning all folders and pinning the Linux /home folder instead.
src/config/oem/RegistryOverride.ps1: Applies changes to certain localization settings when they are change in the LinOffice GUI. This works by reading registry_override.conf (created by mainwindow.py) and applying the settings to the Windows registry.
src/config/oem/UpdateWindows.ps1: An script to update Windows and Microsoft Office. Can be called by the LinOffice GUI or linoffice.sh directly.
src/config/oem/dns_off.bat: An script to "break" DNS resolving for the Windows VM, for users who don’t want the VM to be able to connect to the Internet. (Though it doesn’t block connection to IPs directly.) Can be called by the LinOffice GUI or linoffice.sh directly.
src/config/oem/dns_on.bat: Undo what dns_off.bat did.
src/config/oem/registry/explorer_settings.reg: Various settings for Windows Explorer, e.g. enabling file extensions by default. These settings are applied by install.bat.
src/config/oem/registry/linoffice.reg: Various Windows settings, e.g. allow any app to be run as RemoteApp via RDP, disable automatic logon, allow long file paths, prevent Windows Update from rebooting the machine etc. These settings are applied by install.bat.

Legal information

This project is licensed under the GNU AGPL 3.

The main script (linoffice.sh) is forked from Winapps, AGPL license.

The Windows VM is set up using the Dockur/Windows OCI container, MIT license.

Windows and Office are directly downloaded from Microsoft. This project contains only open-source code and does not distribute any copyrighted material. Any product keys found in the code are just generic placeholders provided by Microsoft for trial purposes. You will need to provide your own product keys to activate Windows and Office.

LinOffice - Microsoft Office launcher for Linux

LinOffice - Microsoft Office launcher for Linux

Screenshot

Features

Planned features

Nice to have but lower priority

Comparison with other options to run Microsoft Office in Linux

Installation

Quickinstall

Manual install

Dependencies

Run the installer

Updating

Uninstall

Usage

Starting Office applications

Opening Office files

Using the GUI

Using the terminal

Office activation

Printing

Troubleshooting

Problems with the setup

Logging in to Microsoft

Window management

Wrong keyboard layout

Orphaned lock files

For developers

Legal information

Similar Posts