-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incompatible with Windows server #35
Comments
This is a known issue which I have posted about here #33 a month ago, but @cinit has not yet responded. |
oh, I understood, I quickly reviewed the issues, I thought that I was the first to have such a problem :') oops, I re-read, as I understood this problem from version 2304. is there a way to download earlier versions of WSA? |
I got the same issue. Hopefully should be patched soon. In the meantime, use older version of WSA 2303. I use WSA from here: (https://github.com/YT-Advanced/WSA-Script/releases/tag/v2023-05-10). I had to revert back to this version, and its working again. |
I have corresponded with @cinit and have been told that they are busy with their studies and will work on the patch in the coming weeks after they have some free time. I would revert back to 2303.40000.5.0 in the meantime by either getting WSA from here https://github.com/MustardChef/WSABuilds/releases/tag/Windows_10_2303.40000.5.0 |
New update: Worked on v2305. You can check via this prebuilt: |
You can get WSA Builds v2305 for Windows 10 from here: https://github.com/MustardChef/WSABuilds/releases/tag/Windows_10_2305.40000.5.0. I have tested that eveything is working. |
I have Windows 10 Pro installed (screenshot below), but WSA thinks I have a Windows Server, which is why it gives me an error.
The compiled patch has been installed to the latest version (20230119 - Add workaround for Windows Server :/)
I don’t really know who to contact, since I don’t have Windows 11 .. but I don’t have a Windows Server too, so I wrote here :(
The text was updated successfully, but these errors were encountered: