Don
Best answer by DonC
View originalBest answer by DonC
View originalBaldrick,@ wrote:
Hi DonC
Would it be out of place to ask what the script does, as I am wondering if by any chance it is not the script that WSA is objecting to but rather the activities/actions that it is performing?
The above is a longshot, and I am aware that there have been some sporadic issues with WSA and scripts run at 'sensitive' times...so to be honest it looks like your best bet would be to Open a Support Ticket, explaining to the Support Team exactly what is being run; a sample of the script would be a useful addition if that is possible, and then see what they think as to what the issue may be.
Should that be the course of action you take then please do post back here with information as to the outcome. This sort of feedback is extremely useful to usehere in the Community, to assist users in future with the same or similar issues.
Regards, Baldrick
Yes, it is.@ wrote:
Hello!
Is the script still set as "Allowed" list when you restart?
I certainly recommend as Baldrick said and opening a support ticket. Please let us know the outcome and what the issue was.@ wrote:
Yes, it is.@ wrote:
Hello!
Is the script still set as "Allowed" list when you restart?
Well, that's a start at least...@ wrote:
OK, I did as requested by Support. I disabled Webroot and rebooted my system. My startup script ran as expected all the way to completion. I then collected and uploaded the logs to Support, per request. Let's see where it goes from here.
Don
That is odd. I wonder if that affects some way that Webroot detects scripts?@ wrote:
OK, it appears that is as far as we are going. Everything is working fine. We just can't explain why! So, the solution for this problem seems to be:
I just don't like problems without an explanation! What changed? The only thing I can figure is that the script executed once without Webroot stopping it and SOMEHOW that fixed the problem. What changed when the script executed without being stopped by Webroot? Did Windows 8.1 flag the file in some way? Even though the script showed up as an exception before doing any of this, did this somehow cause Webroot to flag the script in some other way? I, at least, don't know. The good thing is the problem no longer exists!
- Disable Webroot
- Run the script
- Reboot
- Webroot is re-enabled and everything is working fine.
Baldrick and Corey, thanks for hanging with me on this one! I know from my experience as a Netwire SysOp that it's guys like you who make the whole software process workable for those of us less "in-the-know". I really appreciate your help!
Don
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.