brunodev85
container shuts down immediately
So recently. I opened a container however it shutdown and returned me to the containers screen immediately. Whats causing this. I attempted reinstalling system files but didnt work
https://github.com/user-attachments/assets/0d9ce4d5-5686-46c5-b823-05108e30db14
Attemped low or new box64 but it didnt work. I guess that immediate shutdown was a bug that is bugging me
Either try reinstalling Winlator itself or share the logs files (enable by going to Winlator in-app settings (hamburger menu at top left corner > Settings) > Enabled Wine logs and set Box64 logs to "Minimal" > Enable "Save logs to file") by launching the container once after enabling the logs.
Either try reinstalling Winlator itself or share the logs files (enable by going to Winlator in-app settings (hamburger menu at top left corner > Settings) > Enabled Wine logs and set Box64 logs to "Minimal" > Enable "Save logs to file") by launching the container once after enabling the logs.
Here is the revealed logs
This sometimes happens to me, and the best fix I know is to install winlator again (no need for uninstalling, just install the apk as an update) and it will be fixed.
Hello @BlueandresMedia , from what I understand the container was opening normally and now it doesn't open anymore, or did it never started?
Hi, I would like to share some info which is seemingly the same issue. For me, I seems to happen randomly when I change my graphics driver (or possibly the DX wrapper), which after launching and later shutting down the container, when I enter winlator next time, seems to break all containers ability to launch, even new ones. The only fix I found was installing the winlator apk file again as an update, which fixes it. Although replicating it seems quite inconsistance, since it has happened to me out of seemingly nowhere as well.
Hello @BlueandresMedia , from what I understand the container was opening normally and now it doesn't open anymore, or did it never started?
Hi, I would like to share some info which is seemingly the same issue. For me, I seems to happen randomly when I change my graphics driver (or possibly the DX wrapper), which after launching and later shutting down the container, when I enter winlator next time, seems to break all containers ability to launch, even new ones. The only fix I found was installing the winlator apk file again as an update, which fixes it. Although replicating it seems quite inconsistance, since it has happened to me out of seemingly nowhere as well.
Hello @BlueandresMedia , from what I understand the container was opening normally and now it doesn't open anymore, or did it never started?
Thanks. It worked. Your the coolest guy ive ever seen. By the way. BlueAndresmedia was my old yt username and i didnt change it in github because i abandoned this account for 2 years
Olá, gostaria de compartilhar algumas informações que parecem se referir ao mesmo problema. No meu caso, ele ocorre aleatoriamente quando troco o driver da minha placa de vídeo (ou possivelmente o wrapper DirectX). Depois de iniciar e fechar o contêiner, ao acessar o Winlator novamente, todos os contêineres, inclusive novos, param de funcionar. A única solução que encontrei foi reinstalar o arquivo APK do Winlator como uma atualização, o que resolve o problema. Embora a reprodução do problema pareça bastante inconsistente, já que ele também ocorreu comigo aparentemente do nada.
Olá @BlueandresMedia , pelo que entendi, o contêiner estava abrindo normalmente e agora não abre mais, ou nunca chegou a abrir?
Obrigado. Funcionou. Você é o cara mais legal que eu já conheci. Aliás, BlueAndresmedia era meu antigo nome de usuário no YouTube e eu não o mudei no GitHub porque abandonei essa conta por 2 anos.
Isso às vezes acontece comigo, e a melhor solução que conheço é instalar o Winlator novamente (não precisa desinstalar, basta instalar o APK como uma atualização) e o problema será resolvido.
Man, thank you very, very much, you don't know how you saved me, I was using version 9.1 V2, because Winlator 10 and 11 had this same problem on my Mi9 (SD 855), I had the effort to go back and create an account just to thank you, 9.1 V2 is good, but obviously W11 is much more optimized and better for playing, I tried countless ways and was unsuccessful, you solved my problem, Thanks again!
