The issue wasn't fixed by updating to B4A 10.5, at some point in time you've obviously ran B4A SDK Manager and one of the updates fixed your emulator. After the emulator was updated (again) in the manager, the emulator started working again and that was while using B4A V10.2.
Basically, it was not a B4A issue...