simplewall icon indicating copy to clipboard operation
simplewall copied to clipboard

[Bug] 3.7.7 Portable Update Server connection error.

Open 0lm opened this issue 1 year ago • 1 comments

Checklist

  • [X] I have used the search function to see if someone else has already submitted the same bug report.
  • [X] I will describe the problem with as much detail as possible.

App version

3.7.7

Windows version

Windows 10 64bit

Steps to reproduce

  1. Download simplewall 3.7.7 portable.
  2. Start Update
  3. Language Pack 04.01.2024 is found
  4. Click "yes", but it will give update server connection error: status 1073741738 (0xc0000056)

Expected behavior

Working Updates

Actual behavior

I am sorry in advance if this issue is related to only me and not for general. But since I tried it on different devices at home, it didn't work anywhere. I remember the languge pack before this newest one worked and it could be installed. But since portable v3.7.7, I don't seem to be able to update the language pack anymore.

Logs

No response

0lm avatar Jan 05 '24 15:01 0lm

I found the reason for this issue. On simplewall 3.7.7 portable, when an update is done (for example language update) a 'cache folder' is created in the directory of simplewall.exe. That cache folder is for the update progress, I assume.

The issue is, the cache folder denies access to it. I neither can click on it, nor can I delete it. But the cache folder automatically disappears, when you shut down simplewall.

So, currently, after an update (like language pack update), an undeleteable and inaccessible cache folder is created, which only removes itself automatically, when you shut down simplewall. If you don't, cache folder won't disappear and it will interfer with future simplewall updates by blocking them.

And the cache folder is created every time you do an update in simplewall. I only noticed this, because the device I used, was turned on for a longer time. So, simplewall was never shut down, either.

EDIT: Btw. I dont know if the same issue also happens with the install-version, since I am only using the portable version.

0lm avatar Jan 05 '24 22:01 0lm

installer/portable version binaries are the same, so it fixed (check last version), i think, if not - reply

henrypp avatar Apr 27 '24 11:04 henrypp