This is a known issue on Windows 10 1903 update for LW 2018 and most of the 2019 series of releases. Many experienced this issue but some didn't. It was fixed in LW 2019.1.3. You will have to upgrade to LW 2019 to get the build that fixes this issue.
You also may want to wait to see if LW 2020 is released over the next few weeks like releases the previous 2 years and just upgrade to that rather than LW 2019. It will probably give you more bang for the buck plus bug fixes for the next year.