"The semaphore timeout period has expired" Occuring more frequently

[sonikun]

[Willy-JL]

Saw this reported twice in the f95zone thread aswell, and my best guess is microsoft did something. It is originating from a windows error, and google shows us that this exact error message has been spotted countless times in other obscure windows behaviors. i will look into it tho

[FaceCrap]

Since just posting a screenshot without any details, I'm curious if this happens regularly or if this was a one-off or incidental occurrence.

F95Zone regularly runs backups, if F95Checker happens to do a refresh in that period, I can imagine this happening. I also have run into a situation where the whole site was inaccessible due to a database error. Which also would cause F95Checker to fail

I don't know if these situations will cause this exact error, because I only do manual refreshes, but it's important to at least add the following info:

• the refresh method used,
• the time/date this happened (and which timezone you're in)
• if the suggested workarounds were used and if that made a difference or not
• number of workers in settings and the timeout value

[Willy-JL]

F95Zone regularly runs backups, if F95Checker happens to do a refresh in that period, I can imagine this happening.

That is true, but those are usually handled and F95Checker should show a "F95Zone backups are currently running, try again later" error message instead of the usual connection error. But of course if the message received from f95zone doesnt mention daily backups, even though the issue is daily backups, then it would not. However this error in particular seems to happen before the connection is established, no data is even received from f95zone, so telling the cause of the issue is trickier and likely its not on f95zone's side but on the client (unless its an f95zone outage / antispam protection).

However more information would indeed be useful

[Willy-JL]

I couldn't manage to reproduce the issue at all, but found some stuff online saying to just suppress the error so i did that and made it retry if it finds a WinError 121, try out build 651 and let me know

[sonikun]

Since just posting a screenshot without any details, I'm curious if this happens regularly or if this was a one-off or incidental occurrence.

F95Zone regularly runs backups, if F95Checker happens to do a refresh in that period, I can imagine this happening. I also have run into a situation where the whole site was inaccessible due to a database error. Which also would cause F95Checker to fail

I don't know if these situations will cause this exact error, because I only do manual refreshes, but it's important to at least add the following info:

* the refresh method used,

* the time/date this happened (and which timezone you're in)

* if the suggested workarounds were used and if that made a difference or not

* number of workers in settings and the timeout value

1% to 97% is usually fast but it becomes very slow 98 onwards and they pops this error at 100%

I get the updates for games only after retrying 4-5 times

The error is popping from 3 days as far as I have checked

[Willy-JL]

As I said I can't manage to reproduce this issue. From what I can read online though it is a very obscure Windows error than often originates deeper in Windows hell, from either hardware or driver layers. Since to my knowledge only a limited amount of people are experiencing this issue (4 that I know of) I opted for a compromise. Default behavior is the same, but I added a toggle in refresh settings to ignore semaphore timeouts and WinError 121's. The note for that setting also mentions that it should be used as a last resort, and the preferred fix would be repairing the system with sfc, DISM and driver updates. Build 655 contains this "fix", and it will be released in the next update unless a proper fix is found.

[Willy-JL]

Released in version 9.5