Okay, let me tell you about this Vanguard error 148 thing in League. It popped up for me a while back, right after one of those updates, I think. Super annoying, couldn’t even get into a game.
So, first thing I did, the usual stuff. Closed the League client completely, made sure it wasn’t running in the background. Then I opened it again. Nope, same error. Error code 148 staring me in the face.
Next step, the classic restart. Turned off my whole computer, waited a bit, turned it back on. Fired up League again. Still no luck. That error just wouldn’t go away. Started to get a bit frustrating, you know? Just wanted to play a game.
Digging a bit deeper
Alright, I figured maybe it was Vanguard itself acting up, not just League. Vanguard is that anti-cheat thing Riot makes you install. Sometimes it gets weird.
So, I went looking for how to handle Vanguard directly. I remembered you can uninstall it separately.
- I went to my Windows settings, found the “Apps” or “Add or remove programs” section.
- Scrolled down until I saw “Riot Vanguard”.
- Clicked on it and hit “Uninstall”. Followed the prompts to get rid of it.
This next part seemed important: After uninstalling Vanguard, I didn’t immediately try to run League. I restarted my computer again. Gotta let things settle, right?
The Reinstall and Test
After the PC rebooted, I launched the League of Legends client. This time, instead of the error, the client itself told me that Vanguard wasn’t installed and needed to be installed to play. Perfect, exactly what I wanted.
I let the League client download and install Vanguard again. It did its thing. Then, guess what? It asked for another restart. Yeah, Vanguard loves restarts.
So, I restarted my computer one more time. The third restart in this whole process, I think?
Finally, after that last restart, I opened the League client. Waited for it to load up. And bam! No error 148. I could log in, queue up, everything was back to normal.
It seems like completely removing Vanguard and letting the League client handle a fresh reinstall did the trick for me. It was a bit of a hassle with all the restarts, but way better than not being able to play at all. Hope this helps someone else out there stuck on that error.
