Closed wazerstar closed 1 year ago
I have the same problem too. I have a wild guess about it but it might be due to the current Host version for the Desktop Client being 1.0.9007 while Discord Portable having 1.0.9006.
I've done the whole flushdns
thing and the people have said all over the net as well as clearing the cache + deleting my own copy of Discord portable and reinstalling it on a different drive yet the problem persists.
I have the same problem too. I have a wild guess about it but it might be due to the current Host version for the Desktop Client being 1.0.9007 while Discord Portable having 1.0.9006.
I've done the whole
flushdns
thing and the people have said all over the net as well as clearing the cache + deleting my own copy of Discord portable and reinstalling it on a different drive yet the problem persists.
Can confirm. I manually updated the portable version to the latest (1.0.9007), and it works now.
Behaviour
Steps to reproduce this issue
Expected behaviour
Actual behaviour
Configuration
App release / arch (ex. 1.0.0-2 win64) :
1.0.9006-13
Operating system (ex. Windows 10 Pro 64 bits) :
Windows 10 Pro x64
Winver screenshot :
https://i.imgur.com/5RYUy4H.png
Logs
Join the log file
log\[appname]-portable.log
to this issue. discord-portable.log