[GH-ISSUE #945] Error 10013 #657

Closed
opened 2026-02-27 15:51:17 +03:00 by kerem · 3 comments
Owner

Originally created by @lefty73 on GitHub (Mar 19, 2021).
Original GitHub issue: https://github.com/quasar/Quasar/issues/945

I was using Quasar just fine until yesterday, when I updated my Windows 10 to the new 20H2 version (OS Build 19042.868).
Since then I keep getting the following error when opening the program -

"An unexpected socket error occured: An attempt was made to access a socket in a way forbidden by its access permissions
Error Code: 10013"

I have tried looking to see if any other applications are using the same ports etc using netstat, but I can't see anything conflicting.

Any ideas what could be causing this?

quasar error

Out of curiosity, I rolled back to a previous version of Windows 10 v1909 (OS Build 18363.1440) and Quasar once again worked fine, so the issue must lie somewhere within the update to the latest win10 release.

Originally created by @lefty73 on GitHub (Mar 19, 2021). Original GitHub issue: https://github.com/quasar/Quasar/issues/945 I was using Quasar just fine until yesterday, when I updated my Windows 10 to the new 20H2 version (OS Build 19042.868). Since then I keep getting the following error when opening the program - "An unexpected socket error occured: An attempt was made to access a socket in a way forbidden by its access permissions Error Code: 10013" I have tried looking to see if any other applications are using the same ports etc using netstat, but I can't see anything conflicting. Any ideas what could be causing this? ![quasar error](https://user-images.githubusercontent.com/80961050/111779984-b490af00-88ae-11eb-80bb-b5d46ac71fc2.png) Out of curiosity, I rolled back to a previous version of Windows 10 v1909 (OS Build 18363.1440) and Quasar once again worked fine, so the issue must lie somewhere within the update to the latest win10 release.
kerem 2026-02-27 15:51:17 +03:00
  • closed this issue
  • added the
    duplicate
    label
Author
Owner

@BurntDog commented on GitHub (Mar 19, 2021):

I have updated my Windows to the latest and Quasar works fine. Did you compile the whole project on the newly updated windows as I did?

<!-- gh-comment-id:802908473 --> @BurntDog commented on GitHub (Mar 19, 2021): I have updated my Windows to the latest and Quasar works fine. Did you compile the whole project on the newly updated windows as I did?
Author
Owner

@MaxXor commented on GitHub (Mar 19, 2021):

It seems to be related to your antivirus blocking quasar from using that port. https://answers.microsoft.com/en-us/windows/forum/windows_7-networking/socket-10013-error-when-trying-to-connect-some/2cc71cb6-24b2-4b63-8f60-32bb444eb8fd

<!-- gh-comment-id:802967682 --> @MaxXor commented on GitHub (Mar 19, 2021): It seems to be related to your antivirus blocking quasar from using that port. https://answers.microsoft.com/en-us/windows/forum/windows_7-networking/socket-10013-error-when-trying-to-connect-some/2cc71cb6-24b2-4b63-8f60-32bb444eb8fd
Author
Owner

@MaxXor commented on GitHub (Mar 19, 2021):

https://github.com/quasar/Quasar/issues/651

<!-- gh-comment-id:803015590 --> @MaxXor commented on GitHub (Mar 19, 2021): https://github.com/quasar/Quasar/issues/651
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
starred/Quasar#657
No description provided.