Glasswire Idle service gone craszy

so just watching youtube nothing else it goes on for longer than the picture shows. on the lastest build .64

Wow, that’s crazy. When you installed the update was it a clean install, or did you install it over a previous version? If you installed it over a previous version can you try the “clean install” option?

after counting 250 Idle processes. been running ,64 for a good week?

luckily got 64GB of ram

Before upgrade
I unisstalled .54?
Installed new version
kept my .db intact

I hate to sound like a broken record but I think a clean install is the way to go. We made so many changes between 1.1 and 1.2, and it seems to be causing unexpected problems for some people. I apologize for the inconvenience and I’ll ask the dev team if they have another idea.

no problem things happen.

just wanted to inform you :slight_smile:

That is definitely odd. It’s also odd that so many of us have had no difficulty with the 1.1 to 1.2 conversion and some get haywire issues. Just a comment – with all the variables in computers, OSs and installed software it definitely is less odd, but wow!

1 Like