Joly0

> @Joly0 tried your fork, but ended up in the same error.. Do you mind creating an issue over at my fork for this issue and provide as much useful...

> After fixing the Error MemoryInMB i got a different error. There seems to be an error while initializing Windows Sandbox. Any recommendations? > >  Hey, have you tried...

> Heyy i just have tried it but i still recieve the same error. Where is the .wsb file located? Hey, should be under `C:\Users\YOURUSER\AppData\Local\Temp`

Ok, good to know. But it seems to ve fixed in upstream already 4 days ago.

Yep, works correctly with this version

Also, for additional information here is the command for the signal-cli directly `signal-cli-native --config /home/.local/share/signal-cli --output json -a +4OBFUSCATED listGroups -d` and the output: ``` SLF4J(I): Connected with provider of...

I think this line `SLF4J(I): Connected with provider of type [ch.qos.logback.classic.spi.LogbackServiceProvider]` might be the reason?

Yes, works with that version

Ok ,thank you for your respond. Regarding the autoamtic trigger, would it be possible to have a startup parameter or so, so i could run that on a cron job...

I guess yes, would work. Though how exactly are you planing to implement it? Maybe I could then better give my opinion on this