The unofficial Shadow Defender Support Thread.

That's good info, I've been a user for years and had never ran across that. How did you run across that?

 

Actually, I´ve used SD only for a month or so, and after I enter shadow mode, what I always see is this:



And I had never clicked on the empty box.

 

You're not the only one; I've seen other users in here who have missed this option altogether, even after using SD for a while. If people don't play around with the settings of new software, they would most probably have missed it.

When the "Exit All Shadow Modes" button is used with multiple disks in Shadow Mode, then there has to be another menu that allows the user to also choose which disks should have their changes committed. Maybe Tony wanted to leave things simple, so he included the Commit All option only upon each individual drive selection.

 

When I install Zemana Antilogger Free, SD becomes hidden.

In shadow mode, I install Zemana Antilogger Free. When the installation finishes, the "Shadow Mode" bar in the desktop disappears, and Task Manager doesn´t show the SD processes.

However, if I launch SD again, it shows shadow mode active, the bar and the processes reappear, and after reboot the Zemana installation is not found, as expected.

So, after the installation, SD is working, but hidden. Why does this happen?

(SD 1.2.0.355 x64, Windows 7)

 

I don't know much about this but...this is my hunch
I think that this is some sort of kernel driver conflict...both use kernel drivers and zemana has "Improved kernel mode keylogger detection"

check this page out

 

When I installed Shadow defender, it crashes touchcontrol.exe on my laptop on every startup. But this doesnt bother me too much.

 

I've had to give up on Shadow Defender after it has twice destroyed my File System Transaction Log, following a reboot. This resulted in the the Task Scheduler corrupting with no new tasks being able to be created. Fortunately using the command "fsutil resource setautoreset true" fixed it, but I'm not prepared to risk it any further until this problem is fixed.

 

Scoobs72
Which version of Shadow Defender were you using when this happened? Which operating system etc? Have you reported it to Tony?

To every Shadow Defender user
Has anyone else experienced this problem?

Patrick

 

SD 1.1.0.325 32-bit XP home.
3 plus years using SD and never have I experienced this type of behavior or any other problems. SD has always worked to perfection here.

 

I also see corruption and errors in the Task Scheduler. I have been using SD 2.0.355 on Windows 7 x64.

These problems appeared recently (in the last week or so).

 

Hello,

I have seen this on my Windows 8 Pro x64 system using SD 1.2.0.355 along with the default settings issue discussed earlier. I have changed my usage of SD from basically full time to only on demand when trying new software as I try to minimize the problems. I am patiently waiting a new version to solve these issues. I did also go back to the previous version of SD (1.2.0.346) and problems were still there but did not occur quite as often.

 

I was using 1.2.0.346, with RAM cache enabled on Win7 32bit. It was a week old fresh install of Win7. EMET wasn't installed.

I will be reporting it to Tony as it's fairly easy to recreate using Total Uninstall. The issue is that if you are monitoring the installation of a program that requires a reboot, when you click "Yes" to reboot at the end of the install process, Total Uninstall automatically creates a scheduled task to complete the monitoring process after the reboot is complete. SD screws up something at this point and results in the Task Scheduler becoming corrupted. RAM cache may be a prerequisite for this corruption to occur.

 

I have observed Task Scheduler corruption, as posted above, but I don´t use RAM cache.

 

Second Edit: Okay, I made a mistake, I installed the 32bit version and not the 64bit which is why it didn't work initially but it is working now. Still the email address isn't working.


I've just reinstalled my system and now it says that Shadow Defender doesn't support my operating system. It supported it yesterday, so I can't work out what's changed. The error message also has a spelling mistake and I get a pop up with Igor Pavlov's name. Very, very strange.

Edit: Oh and to make this a lot worse, I've just tried the support address for Shadow Defender and it doesn't work.

 

To those reporting task scheduler corruption, is the error for a specfic task? ...or what?

 

No, it is complete destruction of the task scheduler resulting in an inability to create new tasks. It's not a specific task and it cannot be fixed by the usual methods when problems are seen with the Task Scheduler. The problem is corruption of the File System Transaction Log. At least that's the problem I've had.....

 

In my case, it wasn´t related to specific tasks, the problem seemed more general. The "Task status" (translated) and the "Active task" boxes were blank, except for error messages in both.

Sorry I can´t post an image. I unistalled SD, reimaged the system and reinstalled Returnil. The Task Scheduler now shows correct information in the two boxes mentioned above.

 

I've been using 1.2.0.346 (x64) since it was first released on my W7x64 laptop. I see no indication of any task scheduler corruption, in fact it's been running so flawlessly I haven't even thought of updating it to build 355. I always run SD on-demand (never at startup) - might that have something to do with this issue?

Cruise

 

I do the same.

 

Guys i m afraid we have the "Rollback syndrome"...

I tried "TrimCheck" with Shadow Defender and RAM cache set to 0. So, everything should be written on the SSD.

TRIM is NOT working...

Can someone with SSD please repeat the experiment and verify?

http://files.thecybershadow.net/trimcheck/

You need to run it twice. Wait 30 seconds between runs, just to be sure of the result.

 

Without even going into shadow mode, I ran this tool and it said for me to do what needed to be done to enable TRIM on my SSD. But, according To Windows 7 TRIM is enabled. So, I really don't understand how this works or if it is working at all.

Gary

 

Win 7 with fsutil command, simply tells whether Windows sends TRIM command or not. Whether the command is then executed is another story. Same issue was discussed in Rollback thread.

The proggie basically writes on a specific position. It then attempts to delete the data in the exact same position and then tries to re-read the exact position. When the TRIM command is successful, the data is full of 00 and you get the message that TRIM is enabled. If the data is still there, you get that TRIM is not working.

 

Thanks - ran the test before shadow mode, worked as intended showing TRIM was working. Ran in shadow mode - did not delte the file and said TRIM was not working or had not kick in.

Did the same test with Deep Freeze 7.6 after going back to an old image and the test did not work when system was frozen - said TRIM was not working or not kicked in and did not delete the file.

So if this test is accurate I guess for now neither program is allowing full functioning or any functioning of TRIM.

Gary

 

Version 1.2.0.368 released - February 14, 2013

Changelog:
Add: Encryp write cache.

-http://www.shadowdefender.com/download/SD1.2.0.368_Setup.exe-

 

Three months - three probably still unstable versions with bugs...what is happend with SD??