mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-25 15:25:59 +03:00
[GH-ISSUE #1186] Client error, This app can't run on your PC #873
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#873
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sayrats on GitHub (Jul 1, 2023).
Original GitHub issue: https://github.com/quasar/Quasar/issues/1186
Quasar version
1.4.1
Server installed .NET version
No response
Server operating system
Windows 11/Server 2022
Client installed .NET version
No response
Client operating system
Windows 11/Server 2022
Build configuration
Debug
Describe the bug
When I try to run the client I get the "This app can't run on your PC", I have added permission for the file disabled all the windows protection and still can't run it.
Is there anything I could have missed?
I also tried to run the file directly from the cmd in admin mod, get access denied message error.
How to reproduce
Try to run the client.exe in a new windows 11 installation that has all windows protection disabled and permission for the client.exe file
Expected behavior
client.exe to run
Actual behavior
This app can't run on your PC
Additional context
No response
@sayrats commented on GitHub (Jul 1, 2023):
It works when using version 1.3.0
@BurntDog commented on GitHub (Jul 1, 2023):
First make sure you have the correct .NET version installed.
@MaxXor commented on GitHub (Jul 1, 2023):
Quasar running on Windows 11 Pro server + client:
.NET Framework 4.8 is pre-installed with Windows 11, so it's working fine without any modifications. However you need to add an exception to your AV and/or temporarily disable Microsoft SmartScreen to allow it to run.