-
Notifications
You must be signed in to change notification settings - Fork 156
runas.node not found #253
Comments
@InfamousKing13 Can you paste your log here, please? You can find it in |
2017-01-09T23:40:53.781Z - error: UncaughtException |
What OS? Windows 10 64 bit? |
yes |
dam sounds like i wont be able to use it for a while than fml lol |
@InfamousKing13 @KilogramHours What AV (anti virus) are you running? I have a feeling it's deleting the file. |
I just have Windows Defender. (I assume AV means Anti-Virus). |
Weird. I've tested a fully updated Windows Defender running on Windows 10, and I still can't reproduce. I'll have to keep trying. Thanks. |
I'm still having the issue where Championify starts, but it is a blank page with the gray background with Jinx and Vi. I've tried to reinstall Championify, even the new version, and also completely erased and reinstalled League of Legends itself and it hasn't worked. Also tried to Run as Administrator and also nothing. Can't figure out for the life of me why it is happening. Without the updated Item Sets that Championify gives me the game just feels worse. |
@KilogramHours If you're experiencing a blank background, please open a new issue with your log file output, as I think it would seperate from this. Most users experiencing this don't get that far. |
has this been fixed or no? |
Nope it still isn't fixed, at least for me. Sucks because I really liked the application and it was really useful for staying up to date on the recent builds. |
Yep. Even after two new updates I still have the issue of it not starting, only showing the blank screen. I feel like I'm never going to be able to use Championify again, which really sucks. |
Closing as stale, a good amount has changed for elevation since this issue. Those still having the issue can open a new one if they're still experiencing issues. |
When last updated the app opens and it shows like this and it does the same thing reintstalled or ran as admin and I am unable to use it https://gyazo.com/20c969d2ce293dad96897cc7e93bfafe
The text was updated successfully, but these errors were encountered: