This applies to Windows 10 x64 Professional Insider Builds 14295 and previous 14200 series builds with Spywareblaster 5.4 with auto-updating. It does not apply to the 10586 builds of Windows 10 x64 Pro. SWB sets up the auto-update in Task Scheduler and everything appears to be set up properly. However, auto-update never runs on system log in or on the once a day schedule. If I open the Task Scheduler and attempt to run it manually, SWB generates a system error message that the Task Scheduler is not present. If I manually change the "on log in" trigger to "on computer start", this message does not appear and SWB does run on computer startup via the Task Scheduler Also, I run with UAC set to "Never Notify". Running auto-update via the Task Scheduler or manually causes UAC to trigger and change to "Always Notify". This also occurs when I enable or disable protection on the SWB Protection page. It took me a while to determine that SWB is what was causing this issue. On my other systems using the official Windows 10 x64 public release Build 10586 SWB works as designed with auto-updating and UAC set to "Never Notify".
Thank you for the heads-up. If you have an avenue to report the bug to Microsoft as well, it would be very much appreciated. (We'll reach out ourselves, but it's often helpful to have multiple sources report a bug.) It sounds like some changes Microsoft made caused broken Windows / Task Scheduler functionality, but my understanding is that is to be expected as a possibility in the current round of Windows insider testing. Quote: Source: https://blogs.windows.com/windowsex...ncing-windows-10-insider-preview-build-14251/ Thanks again for the heads-up. (To anyone else reading this thread: This is in reference to testing builds of Windows 10, made available as part of the Windows Insider Preview program - not the publicly-available Windows 10 release.) EDIT: Missed the bit about UAC settings changing. There is nothing SpywareBlaster is doing that should cause that - it also shouldn't be possible. That's definitely a Windows beta bug - please try reporting that to Microsoft as well.
The weird part is that the UAC issue only occurs if Chrome Protection is changed...either all or individual items. Of course the Enable All or Disable All would change the Chrome Protection and UAC is changed to Always Notify. Chrome is my Default Browser. I can manually change Internet Explorer or Restricted Sites and it does not cause UAC to go to Always Notify.
Please also note that there does appear to be a bug in SWB concerning Chrome Protection. If I disable Chrome's Cookie and Script Protection and then click on Enable All, it does not enable the last 7 items under Script Protection. The box for Script Protection is check marked. To enable the last 7 items I have to uncheck the Script Protection box and recheck it. Then the last seven items become enabled.
The UAC issue continues between SWB and Windows 10 Insider Build 14328. UAC gets set to the highest level when SWB updates and protection is enabled.
Just so you are aware - I've extensively tested the UAC situation on several Windows 10 Insider Builds (starting with 14295), and I cannot reproduce it any which way. There is also nothing about how SpywareBlaster works that should be able to cause the issue. So there may be something else about your configuration that is triggering a general issue/bug with the User Account Control setting sticking. Doing some quick searching, I've found other references to people having issues with Windows 10 and UAC settings sticking: http://answers.microsoft.com/en-us/...r/742946f1-d88d-4378-a59c-901bbf7c4dac?auth=1 One possible cause:
After months of trying to isolate the cause of this issue with UAC and SpywareBlaster, I finally gave up and decided to perform a formatted/fresh install of Windows 10x64 Pro Build 14393.51. That fixed it!
Thank you for the update! Yeah, as mentioned previously, we were never able to reproduce this issue locally. And based on other posts of people having the issue with other programs, I suspect corrupt Windows settings may have been the underlying cause. Glad you got it all fixed, though!
