@Sachelis2
Have you tried the workaround mentioned by abetterfuture earlier?
Which Win 10 build version do you run?
