The unofficial Shadow Defender Support Thread.

Just now reading regarding August 2 vs. August 6 -
I had over-installed SD1.4.0.680 with SD1.5.0.726 - August 2
W10 Home 1909

File: SD1.5.0.726_Setup.exe
File size: 3.47 MB (3,640,296 bytes)
MD5 checksum: E9077833645033FD561E51B93C001A67
SHA1 checksum: BF760C2128A53A23764F9BF95A9B6DDC3398D0BA
SHA256 checksum: C724FF33C4877C92EEBA24BA956CCA9F6D8F6C7245B5500B528BABD6A8CC5973

vs.

File: Setup.exe
File size: 3.54 MB (3,714,768 bytes)
MD5 checksum: 83FC0514E0DDA3F10A9152EA2F3B55C1
SHA1 checksum: 9B5C607C33A977E342AA35FFE7506F698042B6C1
SHA256 checksum: 9D2B7851EACC1A2EB43D8DC1E8A999C592C9855DF3ED45C1FA26D09425B2D503

 

@stapp @bjm_

I don't want to put a dampener on anything and I know that we are all excited about the new releases but we have seen a change in the documentation as regards authorship and I experienced problems that I have never had before re installation of that latest Aug 6 version.
I know that when I installed Aug 6 that I hadn't installed August 2 version before (update over) to Aug 6 but it messed up my Laptop a bit during the installation which caused Windows 7 to do a 'repair' which is unusual to say the least.
Later today I will uninstall the 1.4.0.519 completely and then install August 2 fresh...and then try to upgrade to Aug 6 whilst Aug 2 version is still in situ and report back to the forum with results. Something feels wrong now.

Note, the main benefit of the upgrade was 'Version 1.5.0.726 - August 5, 2020
Fixed: Fix a bug related to Exclusion List on Windows 10.'

If Tony withdrew the Aug 2 version quickly it looks like something happened that , he himself didn't expect so the Aug 2 and/or Aug 6 may be suspect.

Patrick

 

Thanks all for sharing those results and potential issue related quirk?

Looking forward to seeing just what gives between the two versions. Wishing the best.

 

I strongly believe that if you are compelled to upgrade be sure a system image backup is in place before doing so!
I'm still running build 680 but will backup and attempt an upgrade this eve.

As bjm_ noted, those two 726 builds have different file sizes and different hashes - carrying the same build number and without any explanation? - that is not cool !!!

 

Regarding test of the Aug 2 and Aug 6 Shadow Defender setup files

I've just tested and it went as follows

I had 1.4.0.519 installed and working

I uninstalled 1.4.0.519 and rebooted laptop

I tried to install Aug 2 first

It seemed normal install and needed to reboot

On reboot Windows said it could not start and would do a repair

I let that happen and it gave me an unsigned driver error...shadow defender file

When that had finished I went to open Shadow Defender

I noticed that the file number in system tray was still 1.4.0.519

but went on to open Shadow Defender to enter my serial

After entering the serial and it being accepted

A strange password box came up and I could not get past that because I had not made any password

.........................

so I could not install Aug 2 to do an upgrade to Aug 6

..............................

I then decided to see if I could install Aug 6 clean
I uninstalled Shadow Defender and rebooted
I then went to install Aug 6 but the exact same thing happened as Aug 2

no go

.......................
I uninstalled Aug 6 and rebooted
..............................

I then installed 1.4.0.519 which installed normally and worked properly.

I believe that there is something wrong with both Aug 2 Shadow Defender 1.5.0.726 and Aug 6 Shadow Defender 1.5.0.726 later release

 

I have installed version .726 on August 2 as a clean install, I never install over old versions, and so far I haven't noticed anything different. What would be the reasons to resize a build and to have different hashes?

 

my email to support@

and reply

 

@bjm_ thanks for letting us know about email etc

Tony's reply seems incoherant and vague.

Almost unhelpful

Patrick

 

Thanks @sdmod

Think I wont risk it on 8.1-The current version is air tight with zero issues. Always am leery of updates anyway

 

It is unusual for support (Tony?) to reply to emails, which in this particular context, it is a positive omen. I was just about to send an email asking for some explanations, and decided against as I have never had replies in the past.

 

Well ater backing-up my Win 10 system I proceeded to ugrade from v1.4.0.680 to v1.5.0.726 (dated Aug. 6). No problem on the install other than having to re-enter my serial number. Since upgrading I've been testing SD for a few hours (during which Itime I restarted the system twice to make sure SD did its 'magic') and all seems to be well - so far.

 

So Russian or Chinese hacker backdoor? I'm thinking Chinese.

 

Big issues here with the newest version, not the one that came out lately but the first 1.5 version. So installed, created a new folder on my desktop just to check new version, restarted, got a blue screen, tried to fix by system restore, seems like SD deleted all my restore points, so tried a repair, it booted to a temp account, would not sign into my regular account and also deleted all of my browser extensions, had to restore from a old backup. So big issues for me.

 

I didn't have a version installed, just installed the new version. I just created a folder on my desktop to see how the new version works, basically created a folder in shadow mode, and then exited to see if folder is still there,was just testing.

 

So, we have three distributives v1.5.0.726. I updated everything over the top v1.4.0.680 -> v1.5.0.726 (DC 2 Aug) -> v1.5.0.726 (DC 5 Aug) -> v1.5.0.726 (DC 6 Aug). I did not notice any problems. Windows 10 v1809 x64.
An abrupt change of numbering from v1.4 to v1.5 without significant changes in the program may indicate a change in developer or owner.

 

I was on v1.4.0.680 and upgraded over the top to (Aug 2) v1.5.0.726 when it first announced here. This was uneventful, but requiring re-entering of license key.
So as not to tempt fate, will leave it like that for now, like @stapp.

Wonder if the reason for install issues can be isolated - it doesn't seem to be to do with OTT upgrade vs. clean install.

It is such a pity this unique and much-loved software has this unnecessarily murky origin.

 

I mentioned that I got an unsigned driver error message for Shadow Defender driver on one of the installs on Windows 7. Could that be the problem?


As I said, after all this I re-installed (clean) on the same system 1.4.0.519 and it installed sweetly and correctly.

Regarding communication with Tony

I have consistently sent reports and observations from myself and members for many years and where at one time I got civil replies to my emails, now I might send dozens of email without reply and when I do receive a reply it as if nothing has happened or nothing has been said. If I send a multi part email he might just refer to one part and disregards the rest without comment. I've emailed Tony many times about this. It is very frustrating.
This time, with the new version, for example, I sent an email regarding a typo in the history section of Shadow Defender website (Shadow Defender 1.5.0.726 was typed as Shadow Defender 1.5.0.762).
Yes it was a very minor thing but I noticed that, although it was changed immediately I never received any acknowledgement whatsoever.
When I get an email reply from Tony it is 'cut to the bone' to say the least.
This has bothered me over the years because I used to have a cordial 'to and fro', amicable dialogue with Tony.
I've often wondered if my constructive criticism of Shadow Defender in development and criticism of the unreliability of communication has offended Tony or maybe the Chinese Government who scrutinize all the emails passing through The Great Firewal of China. Just a thought.

Patrick