![]() I set that up and found that I could still choose to have a choice of conditions applied to that exception to make it as safe as possible - the one condition that I had to leave disabled being ‘if it is digitally signed’. I’d run into that issue with other program installers and indeed had a really nice exchange with Dan, the VS developer, who explained the problem, and how with VS this could be worked around by creating a rule to make an exception for the particular Temp folder. I should explain that it’s highly problematical behaviour of various installation programs to run programs or scripts from uniquely-named folders or files, because they can’t be whitelisted, and are thus a problem for security software to recognise as safe. – And yes, that is from when I reverted back to the earlier GW version, but it does highlight a significant point. I’ve saved the list as a txt file, which I’d be happy to send you so you get a better idea of what VS was up to, but here’s the one User Allowed entry: There should have been one for each installation. Weirdly, I could find only one entry saying ‘User Allowed’, for that would be one where I responded to the prompt. I’ve extracted the VS log entries covering the period during which I did the installations. So, yes, I do need to remember to temporarily turn-off VS for installations of programs I trust! Although I allowed that each time, it occurred to me that there was a possibility that by delaying that particular action VS might have been causing a glitch each time in the overall installation process and so slightly corrupting the program or its configuration. That may have been significant because part way through each of the previous installations, each time VS had intercepted a command line that it regarded as suspicious and gave me a prompt-alert. Before starting the installation I temporarily turned-off my power AV, VoodoShield. However, there was one little difference about the installation this time. In other words, 2.2 installed smoothly and ran smoothly, and, after my evening meal recess and starting up the computer again, GW 2.2 still running smoothly!! But then when I was about to click the ‘Clean install’ checkbox I had another little surprise intuition, to experimentally see what happens now if I do a ‘dirty’ install first before trying to clean things up, and with no reboot unless anything had gone wrong.Īnd you know what? – The world came to an end most calamitously of course (we’re all just ghosts now)! ![]() I automatically thought to uninstall 2.1 first, but an inner nudge pointed me first to try installing it on top of 2.1 but as a clean install. Yes, after lunch today I got a strong intuitional nudge to have another go at installing 2.2. Well, after all that faffing around, 2.2 is now working fine on my system! I am going to start working on some new DefenderUI stuff now. I believe all reported bugs are fixed, but if you guys find anything else please let me know. So anyway, it should be a little lighter than before.Īlso, if the VoodooShieldService memory utilization gets to be too high, please let me know, I made some changes in that code as well, but I think we will be okay. Both VoodooShield and VoodooShieldService should pretty much have 0% utilization most of the time, but there will be times when VS has to do some heavy lifting, so from time to time VS will use small amounts of CPU. I also optimized the code to fix the issue of small cpu utilization spikes in the VoodooShieldService. ![]() ![]() Thankfully VS should have toggled to ON once the computer was at risk, but it was a good thing to fix either way. This was to fix a bug that was reported where VS would start in Training mode when the computer was restarted. I completely reworked the auto activation / reactivation / deactivation, and it is a lot more simplified under the hood, but if you guys notice anything funny please let me know. There were a couple of bug fixes and optimizations, and I think we are pretty much bug free after all of the changes in Version 7.00. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |