[fariba]

This is so confusing i consider myself lucky cos i never had a problem with the Launcher Pro with Windows 10 Pro 1809. Now i updated to Windows Pro 1903 and my launcher Pro is working perfectly.

As Almaretto pointed out earlier in this thread, there is something wrong with Windows 1809 which Launcher 2.8.x doesn't like. Maybe your 1809 system has a crucial different setting compared to our 1809s, or maybe you are using Launcher PRO 3.x, since I've heard 3.x doesn't have a problem with 1809.

FYI, the first time I encountered this problem with E-Sys Launcher Premium 2.8.2, it was a few days after 1803 to 1809 update by Windows. So basically I thought there is something wrong with the 1803 to 1809 feature update, I spent the time installing a fresh 1809 system along with all the drivers and BMW utilities, only to find out it is not working with 1809. Then I installed a fresh 1803 system and turned off updates.


Personally, I have never succeeded in making Launcher 2.8.1 and 2.8.2 PRO / Premium work with Windows 10 1809, and kept my Coding PC at version 1803 all the while, preventing feature updates. Then just recently upgraded to 1903, after I became confident it is working with Windows 10 1903.

---

I am have other error . After static activation returt this error .

Your screenshot looks like Launcher PRO with Google Authenticator, so it's not 2.8.x. I've never seen version 3.x personally, but I think it is version 3.x. So it's completely a different problem. Network issues? Time zone issues? Have you tried setting your time to Pacific? It is a known fact that TokenMaster put preventative measures in his utilities. For example, I'm pretty confident all his 2017-2018 Premium Launchers and his current NCD CAFD Tool does not open on Windows with Iran time zone. (Russia? China? I'm not sure.)