The unofficial Shadow Defender Support Thread.

To camelia
If the FastStart is enabled:
- turning off the computer - changing the shadow mode is saved (hibernation);
- computer restart - changes in the shadow mode are not saved;
If the FastStart is disabled:
- turning off the computer - changing the shadow mode is not saved;
- computer restart - changes in the shadow mode are not saved;
This works on Windows 10 and Windows 8.1.
First post here.

 

Since I didn't see the option at all, because hibernation is not enabled on my machine, I have to open Command Prompt as Admin and type:

Code:

powercfg /hibernate on

And Reduce the Size of my Hibernate File

Code:

powercfg /h /type reduced

I hope my computer doesn't hibernate

I will post if I am still having problems

Thanks
Came

Update 1

Now i am lost

 

Click here

 

@stapp
@aldist

Thank you very much, working all day, rebooting several times no issues until now

Came

 

I'm wondering if anyone else has experienced degraded drive performance when Shadow Defender is protecting your C-drive? It so happens that when SD (build 672) is protecting my C-drive it totally clobbers the performance of the drive (an otherwise fast SSD)!!!

Below are benchmark performance comparisons of my drive with and without SD enabled (all other conditions are the same):

ATTO Benchmark with SD enabled. ......... ATTO Benchmark without SD.


AS-SSD Benchmark with SD enabled. .................................. AS_SSD Benchmark without SD.


As you can see, my results are quite dramatic! While it's entirely possible that what I'm experiencing may be unique to my system, you just may want to find out if (and by how much) SD impacts your drive's performance. ATTO and AS-SSD Benchmark apps are readily available on the internet for download and do not require installation in order to run a test.

 

Casual observation may be deceiving. Why not run a benchmark comparison (as I have) and post the results.

 

@Cruise If I use ram only case (no matter the size allocated) I have similar results when copying data over 500 megabytes. But on that machine I rearly do (so does not bother me).

 

If you use your HDD/SDD instead of RAM for SD's cache don't you get similar results?

 

Pete, as can be seen in my OP, I used the ATTO and AS-SSD benchmark apps as they are readily available on the internet for download and do not require installation in order to run a test. But use whatever benchmark app you prefer.

 

Have not tested it without ram cache so do not know.

 

I would expect using RAM for SD's cache to result in much faster HDD/SDD throughput for large data copies/transfers, wouldn't you?

 

Pete, I imagine that whether or not one notices a slow-down while SD is protecting the drive depends on what you are doing on your PC. For example I don't notice any slow-down when posting on forums, receiving and sending emails, or word-processing. But I definitely see data-transfer degradation when performing database and photo-editing operations!

 

Ah ha, there ya go!

 

To use SD, the system and the data must be separated in different partitions. If data is kept on the OS partition, all the work done in a session will be lost after a reboot. SD is intended to shadow the system partitions, not the data ones. So, it may be that some data operations are slower when using SD, but this is irrelevant in practice.

 

@Robin A. I'm well aware of that issue (notwithstanding Pete's work-around). In any case I do store my data in a separate partition, but my database and photo-editing programs maintain their 'scratch-files' (where complex data operations are conducted) on the system partition. Consequently those programs often transfer data between data and system partitions and performance is impacted when SD is protecting the system partition. I plan to try excluding those scratch files in SD to see if that eliminates performance degradation.

 

Poor choice of words on my part. How about we change work-around to alternate method?

 

Same here, I can't see any difference, I'm using standard hard drives on 5 machines, and there is no change whether it is a fast CPU or slow one.
I have however noticed that if I use RAM Write Cache, downloading more than 10 GB (a very rare event) tends to slow down the whole computer even though I assign 4 GB to RAM Cache out of 12 available. It never happens using SD without RAM Write Cache.

I also use 'commit' systematically without any problem.

 

I understand that there is a commit feature and can see the benefit for this to be used occasionally. But in general is the idea not to avoid doing work that is intended to be committed while in Shadow Mode?