The unofficial Shadow Defender Support Thread.

Hi Peter, I have two Win 10 machines, and have upgraded one without any problems although I have uninstalled all security programs including Shadow Defender. Now reading about stapp warnings about SD and the CU upgrade, I might wait to do the second machine until Tony gets a fix for this upgrade...

 

Yes, I was the one that wrote about the problem at tenforums which was referenced above. Good to see that he's aware of a problem and working on a resolution for SD. The email reply was quick as well.

 

Thank you for the warning, I honestly haven't tried to install SD version 648 yet, as I'm still checking the functionality of the new CU upgrade...

 

I've just installed SD 648 on 2 Win 10 CU machines and everything seems to be fine, of course some other systems may be affected for all sorts of reasons...

 

Same here. I have used SD 648 several times on 1703, have found no problems.

 

Glad SD is working for some. I won't try to install again until Tony releases the new version since 648 twice made CU fail to boot right after installing SD and I don't wish to go through it all again. I have what I think is a pretty vanilla Skylake system, 6700K, 32 GB RAM, Asus RX 480 video; although I do have the OS on an Intel M.2 drive rather than a SATA. I don't know what the problem is but I'm glad Tony has seen a problem and perhaps his fix will solve it for this system.

 

Shadow Defender 1.4.0.665 is now available: http://www.shadowdefender.com/download.html

 

v1.4.0.665:
The driver for Windows 10 is now digitally signed from: "StarSoftComm(China) Ltd.", and co-signed by Microsoft.
And it is correctly signed
Edit: and i can see correct digital signatures for all other executables + the installer itself

 

Installed 1.4.0.665 with no problems on Creators Update as I previously had. Thanks Tony!

 

Version 1.4.0.665, from installer file:

SHA256 digital signature

Spoiler

Is this right or wrong?
It don't matter?
Any suggestions.

 

What is the hash of your downloaded installer? Is it the same hash? (see below)

 

Same as yours. I'm on Win 8.1 fwiw.

Code:

File     : SD1.4.0.665_Setup.exe
Size     : 3.52 MB
MD5      : 7C5B2FDFA36CC20ECF610BD6C1EFCFC9
SHA1     : 5C60C61F260670D70EFC96347B3FE2852A7BB059
SHA256   : 5556C62A0CF9BEA32F8B5F8AF34650D673A03E083AE357DE075058E08DBD8817

 

Looks like Tony just got a new cert last week for both the sha1 and sha256, the old one was going to expire in two months and at some point, I don't have all the old installers so can't say when he switched from using the symantec timestamping service to the WoSign timestamping service which is also where he gets his certs from.

Odd enough the non-win10 diskpt.sys still uses symantecs timestamping so that doesn't share this issue. However the Service.exe also has the timestamp not being properly signed/chained back to WoSign and Defender, cmdtool and commit so quite a few he'd need to correct actually.

I'd guess he forgot to set a certain flag or had a typo unless it's a WoSign problem with their sha256 setup on timestamping

 

I looked at all old installer on my hard disk, and Symantec has always been used for timestamping.
With the newest version, WoSign-timestamping has been introduced.

 

I noticed that as well. Something's wrong with sha256 signature.

 

@Mister X

Found the problem. Do you use WFC or something similar? If so, that's the issue.

I use it, thought i would set it to lower filtering to check and it was indeed because of that. Now it shows that signature is okay.

 

WTH?

Set WFC to low filtering, downloaded the installer and now the darn file (digital sign.) is just fine.

Set back to medium filtering, downloaded a new copy and digital signature is fine as well.

Guess I'm going to restart my PC and re-download it anew to see what happens...

 

Yes, apparently it has something to do with Windows not getting updates to its trusted root certificates.

No matter how many times you download the file now, it's all fine with it. It just needed a little bit of Internet access to update the root certificates.

 

I've just installed SD version 665 on 2 Win 10 machines: It's working flawlessly, both systems seem to be snappier and rebooting out of shadow mode is faster than in version 648. This program never fails to amaze me, very stable, it only needs yearly updates... Great work Tony...

 

Two days ago, I had a nasty experience upgrading some software. It virtually bricked my computer. Anyway, after going back to the retail outlet that sold me the laptop, someone managed to try somethings, and got into the settings, and managed to uninstall the program that caused me the problem, i.e, WinPatrol WAR upgrade to v2017.4.711.

I only went back to the retailer that sold me laptop, because I had no success contacting Microsoft customer service in Australia, which really means the Philippines. I had been disconnected 5 times, when using the telephone.

https://www.wilderssecurity.com/thr...r-support-thread.293075/page-197#post-2642576

https://www.wilderssecurity.com/thr...-supp.ort-thread.293075/page-197#post-2642577

Anyway, I just tried to open Shadow Defender, and it has opened the GUI. It would seem that WinPatrol WAR was the reason that it was blocked, previously.