Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - JLJ

Pages: [1] 2
1
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: January 03, 2019, 10:57:03 pm »
Happy New Years everyone!

Here is 4.70...

www.voodooshield.com/Download/InstallVoodooShield470.exe
SHA256:    4d292bf8c66fa91fa3c03dcc94e96469002b9a046cfc11c910bb67f06953d651

Hopefully, all issues with upgrades are fixed in this version, along with the mode not being saved on exit, along with a few other bug fixed.


4.70 appears to be working perfectly on my Win 7 x64 system -- problems with profile switching encountered with each release after 4.28 all seem solved. Thanks for all the hard work.  :D

2
VoodooShield / VS 4.53 and multiple Windows profiles problem
« on: August 21, 2018, 08:15:59 pm »
After much hand-wringing and suspense I've isolated the WHAT, if not the WHY, of a problem encountered since updating VS from 4.28 to 4.53, wondering if anyone else has experienced it / can recreate it and offer ideas about resolution (I'm in touch by email with Support):

I have two user profiles, one Standard, one Admin. VS 4.53 (service and GUI) works normally but only in whichever profile is directly booted into at startup -- switching user profiles within a running Windows session causes the VS GUI to fail to load in either from that point on. To make sure that's clear:

(A) boot at startup into Admin profile: VS service and GUI work normally in that profile
(B) boot at startup into Standard profile: VS service and GUI run normally in that profile
(C) boot at startup into either profile, switch to the other without rebooting: VS service runs but GUI does not load in current profile

This holds true regardless of profile loading order or switch method (load both simultaneously / unload one before loading the other). It also means that the VS GUI fails to load on wake from sleep (not hibernate), presumably because that is a condition equivalent to not booting directly into a user profile.

Am attaching an edit of the most recent DeveloperServiceLog.log -- the isolated section indicates errors and debug info that might explain or help isolate the cause of these problems for anyone who can really read it.

Meantime reverting to 4.28 which works flawlessly. Any ideas appreciated (except maybe "reinstall Windows") ~ THX JLJ

3
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: August 18, 2018, 02:09:08 am »
Windows 7 Home Premium x64 ~ VS 4.28 was working perfectly but after upgrade to 4.53 I'm getting errors on startup -- see screencaps. Despite these errors VS remains visible in the systray; both the app and service appear running in Task Manager; and it responds correctly to a manual test by flagging an unrecognized app. These kinds of errors are above my pay grade, any ideas appreciated, more details provided as needed. THX

After in-place update: https://imgur.com/a/POaI1Ce

After clean install: https://imgur.com/a/mqPLyCW
When you say clean install, did you...

1. Uninstall VS via Control Panel
2. Manually delete all remnants from C:\ProgramData\VoodooShield and C:\Program Files\VoodooShield (including those folders).
3. Reboot
4. Install VS v4.53

If you did NOT do those things I would recommend them to you.

Yes to all, and more (deleted settings and logs during uninstall; reg scan with CCleaner & RegSeeker; file/folder orphan scan with Agent Ransack). Will try again. JLJ

4
VoodooShield / VoodooShield v4 STABLE Thread
« on: August 17, 2018, 05:12:47 pm »
Windows 7 Home Premium x64 ~ VS 4.28 was working perfectly but after upgrade to 4.53 I'm getting errors on startup -- see screencaps. Despite these errors VS remains visible in the systray; both the app and service appear running in Task Manager; and it responds correctly to a manual test by flagging an unrecognized app. These kinds of errors are above my pay grade, any ideas appreciated, more details provided as needed. THX

After in-place update: https://imgur.com/a/POaI1Ce

After clean install: https://imgur.com/a/mqPLyCW

5
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: June 25, 2018, 06:14:29 pm »
Quick question on VS 4.28: I can't find the control to restore all program setting defaults -- has it been removed? if not, where is it / how is it done? The user guide shows a dedicated full-program restore button in the UTILITY section, but it doesn't show on my system -- there's one labelled RESTORE SETTINGS FROM FILE but I don't readily see a file of defaults, and I didn't back them up before monkeying around. ?? THX

6
As noted in the main VS STABLE thread, I found the problem on my system: Internet Explorer / Internet options / Connections / LAN settings / disable "Use a proxy for your LAN"

HTH anybody else having this issue :-)

7
VoodooShield / SOLVED! Re: VoodooShield v4 STABLE Thread
« on: June 17, 2018, 07:13:11 pm »
Hi all ~ apologies if doing this is a terrible forum faux pas, if so don't yell, I promise not to repeat it ~ but I'm referencing my own other post because desperate  :o

OP at https://calendarofupdates.org/index.php?PHPSESSID=ak8sk0dgonsrla6pupvg4a5s42&topic=1898.0

Bottom line: under Windows [7 x64] VoodooShield v4 does not connect to the internet for file upload/analysis or program updates unless run as an Administrator, and for overall security I use a Standard / Limited user account at all times. None of my other security apps have this limitation.

Is it possible to release a version of VS that does not require Admin superpowers? If so, one vote for such from me.

Solved! Still confused but solved! I found the chokepoint at which VS could not establish a live net connection -- it doesn't make sense to me, but I found it, so maybe it will make sense to somebody here:

Internet Options under IEx86 (I never use it, and I'm running Win7 x64, but of course IE 32-bit is the system default) was set to use a local proxy filter for LAN connections. When enabled, VS failed to recognize my ethernet connection; when disabled, VS succeeded: update checks and the option to scan programs in the cloud functioned correctly.

Still confusing is the fact that the proxy does not filter connections to known Google sites, so the VS ping to Google (never reported as having failed) should have gone through. Even more still confusing is that the LAN setting was in place in the Admin account as well, and VS did not have a problem with it there.

So at this point everything is working correctly in both user accounts, Admin and Standard, and all is well. Anything as to cause is above my pay grade. I thank everybody for their time and help  8)

8
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 14, 2018, 10:34:22 pm »
Quote
F13Reboot asked for his account to be removed so don't expect a reply back from him.

That's odd. I think.
Is that odd? or am I just unskilled in the Ways of the Forum?

9
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 14, 2018, 09:04:11 pm »
A few days ago, I had the same problem, "Internet connection not detected".
(VS 4.28 free, Win 10 Pro with April Update, default settings firewall). I looked at this forum in the hope that I would find a solution.
 
I did everything that was advisable, set administrator privileges, enabled / disable .NET framework, I spied VS using TCPView and ProcMon for his "internet conversation"  ;D (he saw ("Update check") and not seen at the same time, and there were no clues in the logs) - unfortunately nothing helped. Till this day.

Today I have updated the drivers for the wifi network card and ... it works! VS has regained the ability to connect to the internet. So… JLJ - try to update/reinstall the device drivers with which you connect to the internet. For me it solved the "Internet connection not detected" problem.

/sorry for my quasi-English from the translator  ::)

Well... maybe. Not sure I want to bother messing with Everything Else That Isn't Broken at this point, esp since (1) all other applications can connect correctly now; and (2) VoodooShield does recognize my connection normally when run with Admin creds. Perhaps after my next full system backup. THX though!

10
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 12, 2018, 12:51:41 am »
Well: no news. No grand discoveries, no lightning bolts of understanding. Sorry, chief. It may just remain one of life's great mysteries: what's wrong with John's machine?

The only thing I can add now, if ever, is that I installed AppCheck 2.5.4.2 alongside VS -- installed it from within the LUA using Admin creds -- and it is working correctly: all internet traffic it requires in either direction is allowed, logged, and successful. So the VS block remains the only such thing. I appreciate all the input along the way. THX

11
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 03, 2018, 10:40:04 pm »
Re my firewall: apologies, I misspoke -- VS is logged for outbound connections correctly when run with Admin creds -- in other words, as I said, it works correctly when it works correctly. Since it won't recognize the connection at other times there's nothing to log. Sorry for the confusion.

Re CryptoPrevent: yes, it was completely rolled back and uninstalled prior to my first install of VS. If anything is left over I'm not aware of it, though clearly it's not impossible.

Re my image backups: I make one about every two months, so there's not much to lose -- still, I don't think it called for since this one program, however nifty, is the only problematic one.

I'm supposed to see if Support identified something in the logfile in a few days, will report back. THX

12
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 03, 2018, 04:49:38 am »
Whether or not switching account rights multiple times is what led to the root cause of this issue is beyond my pay grade, but with my luck it's a possibility.
...
So pending your Sudden Insight or me running out of hair to pull out ...

We-e-e-ll, my thinking is that Windows per se isn't the culprit (this bit is hard for me, as I've always considered Windows to be a malware you have to pay for).  However, bits of Windows, and some accessories as well, do misbehave from time to time.  Certainly fiddling with account rights is not to be recommended without a Restore Point in place.  Not just Windows, but any modern OS is sufficiently complex they make race-horses look positively mellowed out.  dotnetnightmare may have a point, as some things are easier fixed by a reinstall--just something to keep in mind, but I'm not sure it's called for ATM.

It would be interesting to check your firewall logs, and see if VS produces a "block" entry when it complains about lack of internet.  You could also check the Ruleset...  FWIW, I just had a surprise on this box, when the Safely Remove applet got caught phoning out to Akamai.  Of course I permanently blocked that behaviour  >:(

And a favourite trouble-shooting tactic is to re-boot into Safe Mode to see what happens.

Restore points have their uses, I prefer redundant full image backups which have saved my bacon on occasion. VS leaves no trace I can find anywhere in my firewall -- still it seems to function correctly when it... functions correctly... so I've been taking a "You're running the latest version" result of an update check to demonstrate a working connection (esp since it replaces "no connection detected"). I was asked to submit one of the VS logs to Support, which I did, and there are "exceptions" -- or one instance repeated -- noted, which might be clue, culprit and solution path all in one. We shall see. As for reinstalling Windows, the time it takes to do so, update, reinstall applications and get everything set the way you like it is prohibitive, hence the redundant image backups. Simply put: not gonna happen for a single application no matter what it is. I appreciate the help very much, but one must draw the line somewhere. ;-)

I'll try Safe Mode-ing tomorrow and report. THX

13
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 02, 2018, 06:56:30 pm »
@JLJ - You could try uninstalling from Admin, then reinstall in your User Account.  (This will test my theory as well as going toward solving your problem :))
EDIT: Don't install "As Admin" within your LUA, just make a non-elevated install.

I've tried every combo pack of uninstalls/wipes/reinstalls and still have the same result. Indeed the very first time I installed VS was from within the LUA. At this point I don't remember if the installer demanded Admin creds or not at the time, but if not it isn't a solution.

The only flavor I haven't tried is reducing the original Admin account rights, but I don't think I want to risk that. Whether or not switching account rights multiple times is what led to the root cause of this issue is beyond my pay grade, but with my luck it's a possibility.

I also tried both taking ownership of the entire VS folder(s) and granting full control rights to my LUA, but neither worked.

The vexing part is that no other related app -- A/V, firewall, et al -- ever had this problem. Indeed my reason for looking into VS is as a quasi-replacement for CryptoPrevent, which used significantly more RAM and seemed to make things a little sluggish (and I'm already a little sluggish thanks to MS' Meltdown mitigations).

Possibly worth noting is this: the app SendAnywhere, which installs to your phone (mine's Android) and PC for wireless file transfer in either direction, had a recent update which caused the app to simply not respond to send/receive commands unless loaded w/ Admin creds. This had not previously been the case. I wrote to the author and he noted it as a widely-reported bug which he would fix in the next release -- and did (fixed version is 8.4.55151.459 -- will try to find previous version number.) The app now functions perfectly from within an LUA. Whether or not there is any fundamental relation to my VS issue I don't know, but the behavior was essentially identical: no ethernet connection w/o Admin rights.

And yes, I've tried turning it off and on again. Thanks, Roy.

So pending your Sudden Insight or me running out of hair to pull out, whichever comes first, seems I'll either jettison VS entirely, take the time to load it manually w/ Admin creds at logon, or try a third profile. THX

14
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 02, 2018, 06:24:06 am »
... And the day I pay somebody at Microsoft to monkey around with my system is... just plain not ever gonna arrive.

+ the fact that W7 will cost an arm and a leg being out-ofservice...

Anyway--I'm running W7HPx64 SP1--let's see if we can't do better than M$ :)

First, which flavour of W7?  It does matter.

Second, are you going through a router, or direct-to-modem?

Third, my practice has forever been to install as Admin and (if given the choice) select "For all users".  As a trouble-shooter, I must ask this question: Did you click on "Utility<Use individual settings for each user"?  See the attachment :)  I wish this forum gave us the option to show thumbnails  >:(

You need to be in Admin to set that one, and you will need a restart after.

Thanks for your assistance. First, I'm running the same, Win7 HP x64 SP1. Ethernet connection to an AT&T U-Verse modem/router (Arris, with AT&T custom firmware). Second, I have two profiles, Standard (daily) and Admin (for installs/updates) and I'm conversant in the benefits and uses of each. Third, unfortunately I'm using the free version of VS for these tests, so I have no access to any program settings within VS itself (other than running mode, which I leave at Whitelist / Smart). The only rights accesses I have are through Windows per se.

But I have sorta-kinda narrowed the problem down a touch further without actually getting any closer to the cause: there is something in my Standard user profile settings that is cripping VS. I know this because the problem does not occur running the Admin profile, nor does it occur if VS is manually loaded as/by that profile from within a Standard user session, but -- this being the point -- it DOES occur if the Standard profile is changed to Admin and VS is then installed and/or run: no good. Further, if from within the changed, now-Admin daily profile, Vs is manually loaded "as an administrator" it works correctly.

So bottom line: VS works correctly in one profile but not in the other. So far no matter what, running it as my regular daily user profile, whether set to Standard or Admin, cripples it.

What the conflict is I don't know -- is it obvious to anyone? -- but the next logical step would be to create a third user profile and try things from that. We'll see if I have the patience and fortitude for that.

Cheers.

15
VoodooShield / Re: VoodooShield v4 STABLE Thread
« on: May 02, 2018, 12:28:40 am »
This is definitely an error on your system configuration. It could be in permissions, firewall, antivirus, or any number of issues. I see 2 users have reported this. Your original posting of "*UPDATE* VS latest reports" is not the way to label a post asking for help  as this is neither an update to VS or a latest reports. It's a bug post that effects 2 users and is not due to VS. Reinstall Windows 7 is the only guaranteed fix if your level of expertise does not include trouble shooting your system configuration. Not trying to be a jerk. I would contact Microsoft support and they can remote access into your system and fix it for you.

Not even VoodooShield is worth reinstalling Windows when absolutely every other aspect of it is working perfectly. And the day I pay somebody at Microsoft to monkey around with my system is... just plain not ever gonna arrive. And I'm comfortable enough with my general ability to troubleshoot my system, which of course doesn't mean I can solve every given issue, which is why I asked for help here with this one. BTW I did email Dan and he was very responsive -- though no fix. Oh well. Back to the sulphur mines of Mizar-5 for me.

Pages: [1] 2