Wine Ported To OpenBSD

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

A draft Wine port has been proposed for OpenBSD, with its author reporting successful tests of dozens of 64-bit Windows programs, including games. The port is not presented as finished: WoW64 does not work, built-in tests are disabled, and the author advises using it at the user’s own risk.

A draft port of Wine, the compatibility layer for running Windows software, has been proposed for OpenBSD, with contributor Thomas Frohwein reporting successful tests of dozens of 64-bit Windows programs. The proposal could expand the software available to OpenBSD users, but the port remains under development and 32-bit Windows programs do not work through it at this stage.

Frohwein announced the proposal in a post to the OpenBSD ports mailing list on October 18, 2026. He described the work as a collective effort, crediting Andrii and Fabien with much of the technical work and thanking several other people for testing and contributions. The post presents a port draft, not a declaration that Wine is complete or ready for general use.

According to Frohwein, the development hurdle that opened the way was OpenBSD’s handling of the %gs register base. He said Andrii provided a software solution that emulates the %gs prefix on commands because the system cannot set the gsbase in the needed way. The mailing-list post does not give a detailed technical account of that implementation, but identifies it as a key step in getting Wine running.

Frohwein said the team had tested several dozen 64-bit Windows applications, mostly successfully. He cited Notepad++ as a relatively small program for people who want to test the port, and said the recent remaster of The Witcher 3 also ran, with the additional vkd3d-proton component required. These are the author’s reports of testing; the post does not provide an independent test suite or a complete list of applications and results.

A New Route for 64-Bit Windows Software

If the port matures, it could give OpenBSD users another way to run software written for Windows without switching operating systems or relying on a separate Windows installation for each application. The reported tests include both desktop software and games, suggesting the work may be relevant beyond a narrow set of command-line tools. That potential remains conditional: compatibility varies by program, and the mailing-list report does not establish broad or production-ready support.

The initial emphasis on 64-bit applications matters because, as Frohwein noted, more Windows software has moved to 64-bit versions than in earlier years. At the same time, the port’s biggest stated limitation is substantial: WoW64 is not working, so 32-bit Windows software is currently unusable through this effort. That excludes applications that have not moved to 64-bit and means users will need to check each program’s architecture before trying it.

There is also a security consideration. Frohwein characterized the software as run-at-your-own-risk and suggested testing from a separate, non-privileged user account while contributors explore whether further confinement, potentially using OpenBSD’s unveil facility, is possible. The post does not claim that such confinement is already implemented.

How the OpenBSD Port Took Shape

Wine is a compatibility layer that lets some Windows applications run on Unix-like systems; it is not itself a copy of Windows. The OpenBSD proposal followed earlier discussion about the %gs and gsbase issue, which Frohwein linked in his announcement. He said the software emulation approach to that issue enabled the porting work to move forward.

Frohwein pointed readers to screenshots and livestream recordings as examples of the work in progress, including footage of The Witcher 3. He cautioned that one recording looked less fluent than the game appeared during use because it was captured on the system with ffmpeg. Those examples document demonstrations, but they do not replace repeatable compatibility testing across different hardware and software.

The proposal also has unfinished test infrastructure. The Wine built-in tests are disabled for now, Frohwein said, because enabling them requires access to the X server and several tests still hang. He added that he had not seen those hangs during real-world testing with a number of games. That distinction is important: successful application demonstrations do not establish that the broader test suite passes.

“We have since tested several dozens of 64-bit Windows software, mostly successfully.”

— Thomas Frohwein, in the OpenBSD ports mailing-list post

Compatibility and Security Still Developing

The mailing-list post does not say when the port might be ready for wider use, whether it will be accepted into the OpenBSD ports tree, or what review remains before that could happen. It also does not give a full inventory of tested applications, system configurations, graphics hardware, or failure rates. The claim that dozens of programs mostly worked is therefore a useful progress report, not a guarantee for other users.

Several technical and safety questions remain open. WoW64 support is unavailable, built-in tests are disabled and some still hang, and possible confinement with unveil has not been reported as implemented. The post also does not specify the full scope of the port’s security review or whether additional dependencies and setup steps will change. Those details will matter to anyone considering installation or relying on the port for regular work.

Testing and Port Review Ahead

Frohwein invited people to test the draft and contribute to its development. He recommended Notepad++ as a small, relatively straightforward 64-bit application to try, and pointed to the port’s README for setup details, including the need for vkd3d-proton in the cited Witcher 3 example. Anyone testing should follow his caution and use a separate, non-privileged account, rather than treating the draft as a finished, secured package.

The next concrete signs of progress will be further testing, work on the disabled built-in tests, and updates from contributors about the port’s status and any security confinement. The source material gives no release timetable or confirmed acceptance date. Until those points are clarified, the development should be understood as an active port proposal with promising reported results for 64-bit software and significant limitations still in place.

Key Questions

What does the Wine port proposal do?

It proposes bringing Wine, a compatibility layer for Windows applications, to OpenBSD. Frohwein reports successful tests of dozens of 64-bit Windows programs, but the draft is still being developed.

Can it run 32-bit Windows applications?

Not at this stage, according to Frohwein. He said WoW64 does not work, leaving 32-bit Windows software unusable through the current port.

Which programs have been tested?

The post refers generally to several dozen 64-bit programs and names Notepad++ as a suggested test. It also reports that The Witcher 3 remaster ran with vkd3d-proton. The announcement does not provide a complete test list or independent verification.

Is the OpenBSD port ready for everyday use?

The announcement describes a draft port under active development, not a finished release. Its built-in tests are disabled, some tests still hang, and the author advises users to proceed at their own risk.

What should someone do before testing it?

Frohwein recommends using a separate, non-privileged user account while security confinement is still being explored. Testers should also consult the port’s README for requirements and setup information.

Source: hn