[GH-ISSUE #735] Can not install Barrier on Windows 10 Home 32 bits Spanish #574

Closed
opened 2026-05-05 06:42:25 -06:00 by gitea-mirror · 9 comments
Owner

Originally created by @navascogt on GitHub (Jun 3, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/735

Operating Systems

Server: MacOS Catalina 10.15.4

Client: Windows 10 Home, 32 bits, x64 processor, Spanish Language
Version 1903 (OS Compilation 18362.836)

Barrier Version

2.3.2 (BarrierSetup-2.3.2.exe)

Steps to reproduce bug

  1. After downloading the most recent version of Barrier, I ran the setup.
  2. After installing, leave checked the "Launch Barrier" option and press "Finish"
  3. A popup window message is showed with the following information:
    Title: Setup
    Unable to execute file:
    c:\Program Files\Barrier\barrier.exe

CreateProcess failed; code 216
Esta versión de %1 no es compatible con la versión de Windows que está ejecutando. Compruebe la información de sistema del equipo y después póngase en contacto con el anunciante de software.

In english this would be the message:
This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and the contact the software publisher

Other info

  • I tried with a user with administrator rights.
  • Also I tried right clicking and use the "run as administrator" option without success.

I am suspecting the error is either due to the 32 bits version of the Windows or due to the Windows language because is difference than english (spanish version).

Originally created by @navascogt on GitHub (Jun 3, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/735 ### Operating Systems ### Server: MacOS Catalina 10.15.4 Client: Windows 10 Home, 32 bits, x64 processor, Spanish Language Version 1903 (OS Compilation 18362.836) ### Barrier Version ### 2.3.2 (BarrierSetup-2.3.2.exe) ### Steps to reproduce bug ### 1. After downloading the most recent version of Barrier, I ran the setup. 2. After installing, leave checked the "Launch Barrier" option and press "Finish" 3. A popup window message is showed with the following information: Title: Setup Unable to execute file: c:\Program Files\Barrier\barrier.exe CreateProcess failed; code 216 Esta versión de %1 no es compatible con la versión de Windows que está ejecutando. Compruebe la información de sistema del equipo y después póngase en contacto con el anunciante de software. In english this would be the message: This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and the contact the software publisher ### Other info ### * I tried with a user with administrator rights. * Also I tried right clicking and use the "run as administrator" option without success. I am suspecting the error is either due to the 32 bits version of the Windows or due to the Windows language because is difference than english (spanish version).
gitea-mirror 2026-05-05 06:42:25 -06:00
Author
Owner

@shymega commented on GitHub (Jun 3, 2020):

Hm, I think it states in the README.md that we don't actually support
32-bits versions of Windows. I'm sure that must be frustrating,
though..

Sorry :/
On this date - Wed, Jun 03, 2020 at 03:33:02PM -0700, navascogt wrote:

Operating Systems

Server: MacOS Catalina 10.15.4

Client: Windows 10 Home, 32 bits, x64 processor, Spanish Language
Version 1903 (OS Compilation 18362.836)

Barrier Version

2.3.1 (BarrierSetup-2.3.2.exe)

Steps to reproduce bug

  1. After downloading the most recent version of Barrier, I ran the setup.
  2. After installing, leave checked the "Launch Barrier" option and press "Finish"
  3. A popup window message is showed with the following information:
    Title: Setup
    Unable to execute file:
    c:\Program Files\Barrier\barrier.exe

CreateProcess failed; code 216
Esta versión de %1 no es compatible con la versión de Windows que está ejecutando. Compruebe la información de sistema del equipo y después póngase en contacto con el anunciante de software.

In english this would be the message:
This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and the contact the software publisher

Other info

  • I tried with a user with administrator rights.
  • Also I tried right clicking and use the "run as administrator" option without success.

I am suspecting the error is either due to the 32 bits version of the Windows or due to the Windows language because is difference than english (spanish version).

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/735

--
Kind regards,
Dom Rodriguez (shymega)

<!-- gh-comment-id:638519428 --> @shymega commented on GitHub (Jun 3, 2020): Hm, I think it states in the README.md that we don't actually support 32-bits versions of Windows. I'm sure that must be frustrating, though.. Sorry :/ On this date - Wed, Jun 03, 2020 at 03:33:02PM -0700, navascogt wrote: > ### Operating Systems ### > > Server: MacOS Catalina 10.15.4 > > Client: Windows 10 Home, 32 bits, x64 processor, Spanish Language > Version 1903 (OS Compilation 18362.836) > > ### Barrier Version ### > > 2.3.1 (BarrierSetup-2.3.2.exe) > > ### Steps to reproduce bug ### > > 1. After downloading the most recent version of Barrier, I ran the setup. > 2. After installing, leave checked the "Launch Barrier" option and press "Finish" > 3. A popup window message is showed with the following information: > Title: Setup > Unable to execute file: > c:\Program Files\Barrier\barrier.exe > > CreateProcess failed; code 216 > Esta versión de %1 no es compatible con la versión de Windows que está ejecutando. Compruebe la información de sistema del equipo y después póngase en contacto con el anunciante de software. > > In english this would be the message: > This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and the contact the software publisher > > ### Other info ### > > * I tried with a user with administrator rights. > * Also I tried right clicking and use the "run as administrator" option without success. > > I am suspecting the error is either due to the 32 bits version of the Windows or due to the Windows language because is difference than english (spanish version). > > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/debauchee/barrier/issues/735 -- Kind regards, Dom Rodriguez (shymega)
Author
Owner

@navascogt commented on GitHub (Jun 4, 2020):

Ohhhhh I did search for the requirements before post the message, maybe was too fast that I did not read the last FAQ... Thanks for your message and reminder me to full read...
And yes, it is frustating...

<!-- gh-comment-id:638527689 --> @navascogt commented on GitHub (Jun 4, 2020): Ohhhhh I did search for the requirements before post the message, maybe was too fast that I did not read the last FAQ... Thanks for your message and reminder me to full read... And yes, it is frustating...
Author
Owner

@shymega commented on GitHub (Jun 4, 2020):

Yeah. I think you may be able to compile it 32-bits though..

Ideally I'd like for 32-bit and Windows 7 to still be supported, as
they're still widely used for various reasons.

I'm sure it must be frustrating though.

On this date - Wed, Jun 03, 2020 at 05:22:19PM -0700, navascogt wrote:

Ohhhhh I did search for the requirements before post the message, maybe was too fast that I did not read the last FAQ... Thanks for your message and reminder me to full read...
And yes, it is frustating...

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/debauchee/barrier/issues/735#issuecomment-638527689

--
Kind regards,
Dom Rodriguez (shymega)

<!-- gh-comment-id:638898723 --> @shymega commented on GitHub (Jun 4, 2020): Yeah. I think you may be able to compile it 32-bits though.. Ideally I'd like for 32-bit and Windows 7 to still be supported, as they're still widely used for various reasons. I'm sure it must be frustrating though. On this date - Wed, Jun 03, 2020 at 05:22:19PM -0700, navascogt wrote: > Ohhhhh I did search for the requirements before post the message, maybe was too fast that I did not read the last FAQ... Thanks for your message and reminder me to full read... > And yes, it is frustating... > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/debauchee/barrier/issues/735#issuecomment-638527689 -- Kind regards, Dom Rodriguez (shymega)
Author
Owner

@navascogt commented on GitHub (Jun 8, 2020):

Maybe in a future I can try to compile in 32bits... Thanks again!

<!-- gh-comment-id:640866107 --> @navascogt commented on GitHub (Jun 8, 2020): Maybe in a future I can try to compile in 32bits... Thanks again!
Author
Owner

@shymega commented on GitHub (Jun 16, 2020):

Closing for now.

For the record, I'd like for our build infrastructure to provide 32-bit versions for Windows 7/8/8.1/10 at the very least until its proven decisively that its not needed. This issue here proves that we have some 32-bit PC users..

<!-- gh-comment-id:644950684 --> @shymega commented on GitHub (Jun 16, 2020): Closing for now. For the record, I'd like for our build infrastructure to provide 32-bit versions for Windows 7/8/8.1/10 at the very least until its proven decisively that its not needed. This issue here proves that we have some 32-bit PC users..
Author
Owner

@mirh commented on GitHub (Jul 25, 2020):

I mean, it's not like there is even a 64-bit windows version without wow64.
And since barrier doesn't seem the kind of software that would benefit from using GBs and GBs of memory, or whatever advanced x86-64 instruction, I don't see why you couldn't as well just ship 32bit builds for everyone.

<!-- gh-comment-id:663848001 --> @mirh commented on GitHub (Jul 25, 2020): I mean, it's not like there is even a 64-bit windows version without wow64. And since barrier doesn't seem the kind of software that would benefit from using GBs and GBs of memory, or whatever advanced x86-64 instruction, I don't see why you couldn't as well just ship 32bit builds for everyone.
Author
Owner

@shymega commented on GitHub (Jul 25, 2020):

It wasn't my decision. My personal view is that 32-bit builds are still useful. With regards to using GBs and GBs of memory, yes, perfectly true, in theory - but Barrier does have several memory leaks.. so uh, maybe it would! 🤣

<!-- gh-comment-id:663866311 --> @shymega commented on GitHub (Jul 25, 2020): It wasn't my decision. My personal view is that 32-bit builds are still useful. With regards to using GBs and GBs of memory, yes, perfectly true, in theory - but Barrier _does_ have several memory leaks.. so uh, maybe it would! :rofl:
Author
Owner

@fretta commented on GitHub (Dec 13, 2020):

It doesn't make any sense, especially considering that you can use Barrier in 32 bit Linux machines without any kind of problems. Maybe the developers should learn that in the less developed countries there are still millions of PCs running windows on 32 bit machines and that because of the difficult economic situation a software like Barrier is a big advantage just for the simple reason that saves $ in extra hardware.

<!-- gh-comment-id:744050383 --> @fretta commented on GitHub (Dec 13, 2020): It doesn't make any sense, especially considering that you can use Barrier in 32 bit Linux machines without any kind of problems. Maybe the developers should learn that in the less developed countries there are still millions of PCs running windows on 32 bit machines and that because of the difficult economic situation a software like Barrier is a big advantage just for the simple reason that saves $$$ in extra hardware.
Author
Owner

@shymega commented on GitHub (Dec 13, 2020):

It doesn't make any sense, especially considering that you can use Barrier in 32 bit Linux machines without any kind of problems. Maybe the developers should learn that in the less developed countries there are still millions of PCs running windows on 32 bit machines and that because of the difficult economic situation a software like Barrier is a big advantage just for the simple reason that saves $ in extra hardware.

Sure, if you want to submit a PR adding 32-bit support, go ahead. I don't have the motivation to do it myself, and there's only one other developer.

<!-- gh-comment-id:744080545 --> @shymega commented on GitHub (Dec 13, 2020): > It doesn't make any sense, especially considering that you can use Barrier in 32 bit Linux machines without any kind of problems. Maybe the developers should learn that in the less developed countries there are still millions of PCs running windows on 32 bit machines and that because of the difficult economic situation a software like Barrier is a big advantage just for the simple reason that saves $$$ in extra hardware. Sure, if you want to submit a PR adding 32-bit support, go ahead. I don't have the motivation to do it myself, and there's only one other developer.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#574
No description provided.