So I deleted the old exe in all the Kaspersky rules i had - and i now want to make new rules for the new exe - but i don’t have it in Kaspersky and for the love of God i can’t figure out how to add it so i then can exclude it. By default, Kaspersky intercepts connections to certain webpages. Avast enables TLS interception by default. I now looked at the FS exe in Kaspersky app control, and found out the exe had still the path where it was on the S drive! And now it made sense why the exe still was blockt, because every whitelisting and excluding i did - it wasn’t for the new exe on C - it was all for the old (none existing) exe on S! Progress! Take, for example, Avast, Kaspersky, and ESET. i have cloned the old drive - so everything stayed the same - except way faster now (old was 2.5" classic SSD - new is a very fast M.2 drive).īut i still had FS2020 on an classic SSD (drive S) - so i changed the install dir to C (moved in Steam) - and then had to make a complete reininstall in FS2020.Īnd I think THAT’S the problem, because after that FS worked, but PG and ATC did not. I’ll think i might know where things did go wrong.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |