Is your Mac up to date with the latest version of the Mac operating system (macOS or OS X)? Is it using the version required by some product or feature? Which versions are earlier (older) or later (newer, more recent) than the version currently installed? To find out, learn which version is installed now.

Jun 04, 2020  How to Install macOS on a Windows PC. This wikiHow teaches you how to run macOS High Sierra on your Windows computer. To do this, you will need to download an app called Unibeast. You will also need access to a Mac, along with a supported.

If your macOS isn't up to date, you may be able to update to a later version.

Which macOS version is installed?

From the Apple menu  in the corner of your screen, choose About This Mac. You'll see the macOS name, such as macOS Mojave, followed by its version number. If some product or feature requires you to know the build number as well, click the version number to see it.

This example shows macOS Catalina version 10.15 build 19A583.

Which macOS version is the latest?

These are all Mac operating systems, starting with the most recent. When a major new macOS is released, it gets a new name, such as macOS Catalina. And as updates that change the macOS version number become available, this article is updated to show the latest version of that macOS.

If your Mac is using an earlier version of any Mac operating system, you should install the latest Apple software updates, which can include important security updates and updates for the apps installed by macOS, such as Safari, Books, Messages, Mail, Music, Calendar, and Photos.

Learn more

• Always use the macOS that came with your Mac, or a compatible newer version.
• Learn how to reinstall macOS from macOS Recovery.

Translations of this page:Français (Translators, please see Discussion page.)

Installing WineHQ packages

Official WineHQ packages of the development and stable branches are available for macOS 10.8 to 10.14 (Wine won't work on macOS Catalina 10.15). Please test these packages and report any bugs at http://bugs.winehq.org.

Prerequisites:

1. XQuartz >= 2.7.7
2. Gatekeeper must not be set to block unsigned packages.

Installing:

Both .pkg files and tarball archives are available at https://dl.winehq.org/wine-builds/macosx/download.html.

Installing from a .pkg file is recommended for inexperienced users.

To install from a .pkg file, double-click on the package, and the usual macOS installer wizard should open. The process should be self-explanatory. It is possible to install the package either for all users (needs administrator privileges), or just for your current user. After the installation is finished, you should find an entry 'Wine Staging' or 'Wine Devel' in your Launchpad. By clicking on it, a new Terminal window opens with a short introduction into some important wine commands. You can now directly start wine/winecfg/... from the Terminal, as the PATH variable is set correctly. For user convenience, the package also associates itself with all *.exe files, which means you can run windows executables just by double-clicking on them.

To install from a tarball archive, simply unpack it into any directory. There is no need to set DYLD_* environment variables; all paths are relative, so it should work as long as the directory structure is preserved (you can skip the /usr prefix though using --strip-components 1).

For more information, see https://www.winehq.org/pipermail/wine-devel/2015-December/110990.html and https://www.winehq.org/pipermail/wine-devel/2016-January/111010.html.

Installing Winehq packages using homebrew

Winehq packages can be installed using homebrew

XQuartz can be installed using;

To install wine the following command can be used;

wine-stable, wine-devel or wine-staging packages can be installed using the above example.The advantage of installing via homebrew means wine is available from a standard terminal sessionThe --no-quarantine line to used to above brew adding the quarantine bit

Building Wine

See Building Wine on macOS

Uninstalling Wine

• Remove the source tree and binaries.

Using Homebrew:

Using MacPorts, uninstall the wine package you previously installed:

Replace wine with wine-devel if you installed the development version.

Using Fink:

Replace wine with wine-dev if you installed the development version.

Otherwise and if you used `sudo make install`, revert it:

Then simply delete your local Wine source code directory:

• Clean-up pseudo C: drive and registry entries as well as all programs installed to C:

• Check the hidden directory `$HOME/.local/` where Wine stores some desktop menu entries and icon files as it interoperates with the X.Org Foundation and the Free Desktop.

Note: Files in this directory are unused on macOS unless you use a UNIX window manager and other X11 applications instead of the native MacOS apps.

Third Party Versions

Third party versions of Wine, such as Wineskin, Winebottler, and PlayOnMac, are not supported by WineHQ. If you are using one of those products, please retest in plain Wine before filing bugs, submitting AppDB test reports, or asking for help on the forum or in IRC.

See Also

Os X Wiki