Discussion in 'sandboxing & virtualization' started by Cutting_Edgetech, Feb 14, 2011.
How did you add exclusions? File or folder? Can you post the full line showed in SD?
Overkill, a couple years ago when I detected something similar with bookmarks getting corrupted while in Shadow mode, I found certain things had to be done or set for that to happen
I dont use Chrome so I cant test Chrome, what I experienced was with Firefox.
First of all, if I allowed Firefox bookmarks in Sandboxie and in Shadow defender, there was no problem.
The problem occurred only if and when I ran Firefox in a sandbox where I also allowed access to other Firefox files in Sandbox settings, like prefs.js. If I did, my bookmarks got corrupted after exiting Shadow mode.
So, maybe this also applies to Chrome.
If I was you, and you are using SBIE when running Chrome, test in Shadow mode not using SBIE and see what happens. Perhaps you wont get the problem.
You can also test running Chrome sandboxed but dont allow anything out of the sandbox in Sandbox settings. And see the results. Dont allow bookmarks or anything else.
Third test. Allow only bookmarks in Sandbox settings, nothing else. See what happens.
I'm not using sbie on the PC that i'm having the bookmarks issue with
Try excluding also:
I did once before and it didn't help
your other alternative is to change the location of the chrome user data to another drive. This is how I have FF setup so I
can share the profile on my multi-boot systems. Never experienced any SD problems this way.
any giveaway build is aasking about permission from SD-server if the giveaway is still valid. not valid -> no install.
use a sniffer to verify yourself
concerning chrome bookmarks - you need to exclude the whole profile folder - chrome is protecting itself with hashes. you cant rewrite a single file - chrome will drop it because the hash for the current file outside is NOT valid for newest bookmarks. chrome assume hacking or malware working on its profile.
Encountered this today, Shadow Defender in Shadow Mode.
(desktop tip become visible again after a few minutes).
Shadow Defender 184.108.40.2062 is out, no changelog is (yet) available.
Installer throws a pop-up on Win7 about a missing KB which has recently been replaced by a cumulative rollup. Specifically, KB3033929 superseded by KB3185278. This may be confusing to some if they can't find the old KB on their system. The old KB was released on 2015-03, so I assume the pop-up has been there all along suppressed until now.
Maybe Tony should just forget about the pop-up which should no longer apply to systems updated past 2015, or reword it to something more generic. I.e.
Shadow defender may not work if SHA-2 code signing support for Windows is missing on your system
I vote for getting rid of the pop-up.
I've installed version .672 on one of my Win 10 computers, and everything seems to be fine so far, thanking PaulBB for the info...
I just experienced the same popup on my W7 system (from SD build 672). I never got this popup with any prior SD release! Have you notified Tony about this? - or perhaps Patrick (@sdmod) can do that...
You never got the pop-up before because the now old kb mentioned, was installed on your system. I believe the Sept. Cum-Update replaced that fix and SD now decided it wasn't there. No, I've not contacted Tony. I don't have any info where or how to get in touch with him. It's no big deal just ignore the message and continue the install. I do think the message should be removed though.
I have emailed Tony about the popup problem and will post here if/when I hear anything.
That sounds likely, and if that's the case I would expect to get the popup again if I were to reinstall build 665. I may do just that when I have the time.
Thanks Patrick - would you also ask him to post build 672's changes (from 665)?
Can SD works on UEFI/GPT computers and protects the GPT like its protection for the MBR?
Yes, SD works on UEFI.
How about protection for GPT drive?
Yes. It provides protection for UEFI/GPT scheme.
Hi Patrick, Thanks for your feedback. I have updated the setup package to solve this problem. Please try it. Best regards, Tony
On 11/14/2017 12:52, Admin wrote: Tony, I don't know if you are getting my emails because I haven't had a reply for many months but there is a problem with the installer on the latest version 220.127.116.112.
'Installer throws a pop-up on Win7 about a missing KB which has recently been replaced by a cumulative rollup. Specifically, KB3033929 superseded by KB3185278. This may be confusing to some if they can't find the old KB on their system. The old KB was released on 2015-03, so I assume the pop-up has been there all along suppressed until now.'
Patrick -- Admin <shadowdefenderforumATgmail.com>
Shadow Defender V1.4 Change History
Version 18.104.22.1682 - November 11, 2017
New: Supports Windows 10 Fall Creators Update.
New: Change encryption algorithm to AES.
Fixed: Some minor bugs.
@sdmod Thanks for this quick update.
Separate names with a comma.