1. Already found and tried the previous version, didn't work. 2. I uninstalled it, and it still didn't work, so it isn't my antivirus that is the problem. 3. C:\Program Files (x86)\Stardock\WindowBlinds 4. Yes, no errors found
Thank you. IObit Malware fighter includes the bitdefender antivirus engine, as well as it's own anti-malware and anti-ransomwhere engines. Anyways, I uninstalled it, so that isn't the problem. I want to give something a try though, if possible. Is there a way I can download the previous version of WindowBlinds, to see if it might be an issue with the current version? Nevermind, I found a copy of 10.83 online and tried it, still no luck.
Did you even read what I posted? I already said I run IObit Malware Fighter 8.4 pro. I would really appreciate it if you would actually read everything I post, so I don't have to keep goining over things with you that I've already covered. Did you even notice that in my original post there are 2 files that don't seem to be getting registered? Please, I beg you, reread everything I have typed in before you s
As already stated, I turned off my antivirus, as well as Windows Defender. I normally run IObit Malware Fighter 8.4 pro. I also already tried a clean boot.
If you look at my original post, I already did that, in fact, I've done it several times, so telling me to do the same thing I've already done is pointless. Furthermore, I installed the latest version of WindowBlinds via both the standalone installer and via Object Desktop Manager.
Intel Core i7-7700K @ 4.2GHz, on an MSI Z270-A Pro motherboard, with 64GB of DDR4-2400 memory, and an NVIDIA GeForce GTX 1080.
I recently reinstalled WindowBlinds after a long period without using it, and when I try to activate a skin from the config program, I get the skin's loading screen for awhile, then it just goes back to the Windows default, the skin itself never seems to load. There is also no WindowBlinds icon in the system tray. I downloaded and ran Purge_WB.bat, thinking there might be some remnants from when I last ran the program, and got the following messages: "The module &ldq