ADB server version (40) doesn't match this client (41) {Not using Genymotion}

**Disclaimer:** this is not a duplicate to this SO question as the source of the question is different and the answers don't apply.* I hope, it is correctly placed in AE and that the note about not using *Genymotion* does not confuse the reader. The reason to include it in the title is that it is so dominantly present in other answers, but it does have nothing to do with this question, as I don't use any emulator including *Genymotion*. ---- So I'm trying to install LineageOS on my Fairphone FP3+ using Windows 10. But: This also applies to other products with other respective versions - in this case, the device uses **Android 10** (with Build number 8901.3.A-0054.20200929). For the installation I need **ADB** - at first to access the fastboot mode . For that, I first installed the latest *Android Studio* from here but actually only needed the *SDK Platform Tools*, which you can find here (not to be mistaken with the *Command line tools* from the link before ). I unlocked the bootloader and ran the following command which is displayed with it's output: D:\Setups\XXXXX\Lineage FP3\platform-tools_30.0.5(ADB_1.0.41)>adb devices adb server version (40) doesn't match this client (41); killing... * daemon started successfully List of devices attached This SO question I mentioned in the disclaimer didn't help, as abd didn't even print any devices - so the setting is quite different. I also went through these linked questions: link 1 , link 2 , link 3 and link 4 among others. **Genymotion** is as said not used here, but referred to in almost any Q/A except here , but also no soulution for me to be found there. I already checked the PC for any software that could have installed another adb version, but neither me nor cmd's where could find any (4 , 7 , 8 ; 9 , 11 or 10 ). --- adb kill-server adb start-server Did also not change a thing as suggested here or here . I restarted all devices and software multiple times and tried getting rid of all adb processes too (6 , 13 or 12 ). I also reinstalled Android Studio to try it without using the cache as suggested in this SO answer from a possibly related question that unfortunately also has no leads. I can imagine that some questions like that one or this SO one could also be helped here.