The unofficial Shadow Defender Support Thread.

Patrick,
I would suggest that if you decide to re-installing SD, to refrain from connecting or disconnecting while in shadow mode. I would also report it to Tony. It sounds like it could be a bug or a software conflict to me.

 

Hi Baedric, I have been connecting and disconnecting, in and out of Shadow Mode for years without a problem. I don't keep my connection permanently on.
I am in touch with Tony.
I am currently trying an unreleased version which has gone some way near to a fix. I could connect/disconnect in shadow mode, out shadow mode or whatever, re-boot, shut down and everything was ok until I completely turned off from the power at the wall to wired modem and pc and then when I booted up 'fresh' the ras-hangup 668 errors appeared again.

 

Well good luck getting it sorted out. It sounds like you have had your hands full.

 

Thanks very much, Baedric, much appreciated.

After re-booting the pc 9,000,000 times (Well, It feels like that anyway) and re-installing stuff... I'm numb,
Apart from my eyes turning wild and my lips going blue I'm perfectly fine....really...perfectly fine....yes...perfectly fine....perfectly fine...perfectly fine

The version that Tony sent me was (to some degree better than previous ones)
I just wish that Tony wasn't thousands of miles away and that we both spoke the same language.

I'm putting out an appeal


What does anyone know about Hangup - RasHangup 668 error?
I've scoured the internet and I can't find out much about it.
I think that it has something to do with an app disconnecting before the Ras connection thingee has time to cope with it and then it gives an unobtainable port ...or something along those lines. then you just can't re-connect again without turning pc off, modem off, maybe re-set TCP/IP and winsock or repair or reset LAN....

Makes me feel like the most stupid person in the world. I wish I could talk to a network guru. They'd probably say 'Oh! you mean that old Ras 668 problem" and clickety click click and it would be fixed.

Patrick

 

RAS means RASPPPOE? if that driver then its to keep a dial up connection active when system is idle.. I think so it is.. Someone told me , I can't be so sure about it...
Error Msg: 688 ERROR WRITING DEFAULTOFF

Source: http://www.dslreports.com/forum/r3233570-RASPPPOE-won-t-connect.error-678-Win-2k

Sorry if I'm wrong..

 

Thanks stapp and ginson,
Ginzon, I think that RASPPPOE is possibly a way through this problem for me as long as it allows me to use it in and out of shadow mode and to turn it on and off in both modes I don't like a connection to be on all the time.
If I knew more or had more access to network expertise then this might not be such a big problem as it has turned out for me.
What baffles me is I don't know what damage was done.
I can get back online now with configuration gymnastics when my connection breaks when I go into and then out of Shadow Mode but it's not really usable. I could run for weeks this way. It's something to do with Shadow Defender. If not now, when I installed that version that killed all my settings etc. The version that I am trying at the moment seems different. There is no hibernate. I've never used hibernate on a computer, it would be one of the first things that I turn off after installation along with automatic updates of any kind.

This test version of Shadow Defender is better in some way because when I have my LAN straight, winsock and TCP/IP right and network adapter right, I can at least connect in non shadowed re-boot and it finds it again good
when I go into Shadow Mode the same good and restart good

complete shutdown in both modes Shadow and ordinary the same good

but

when I shutdown and turn modem and pc off at the power plug on the wall and wait for a bit

On booting up and trying to get a connection get the error 668 rashangup again in both modes, then it's back to square one with fixing because it wont connect after that without re configuration.

It's extremely frustrating and exhausting...I've spent most of this week attacking this from every angle until I'm blue in the face.

It seems to unhook a setting that shouldn't be unhooked but I don't know what.

The information on the Internet about RasHangup error 668 is so thin. It will just say something like disconnection error

I have read somewhere that this is a problem to do with virtual environments.

I suspect that in that version of Shadow Defender that I think caused the problem it just went deeper than all the settings and stripped them out somehow.
You might ask what is my reasoning.

From the very early development of Shadow Defender there have been occasional problems with loss of icons, loss of Anti Virus settings, loss of registration for programs (Nero) and recently loss of chosen themes, Windows sound being turned back on, screen saver being turned back on etc and all of these things are about reverting to a default setting.
I believe that this is because Shadow Defender runs at kernel level and in an attempt to not be knocked off the perch by lesser software it nudges them out of play occasionally.
That is my laman's way of trying to describe what ( I think) is going on.
This version that I am trying just now is much lighter in feel than the last couple of versions with the hibernate etc..and I also noticed that Avast didn't flag it as a virus (which it has done recently).
This makes me think that it was just running too deep and with security in mind thought of it's own survival first but missed out maintaining the integrity of the Operating system somehow. That's my uneducated 'take' anyhow. I would just like to say however, that I still love Shadow Defender and only want it back on as was before. Having so much data on my system I think that I'll have to keep away from the 'cutting edge' testing aspect in future unless I'm well backed up, running a new system that I can throw away or a non important pc.
This time it's acted like a virus to me. I'm convinced that was not the intention of the developer but I believe that it's worth bearing in mind. Sometimes when these problems occur you might not notice them straight away.
That is what happened to me this time. I thought that I was ok, so I backed up (cloned) my complete system to two drives. It's helped me to re-consider my backup strategy and Peter has given me some good tips.
before all that though I need to get my system up running properly. I use XP sp3 wired adsl ethernet. Any advice welcome.

Patrick

ps One thing that i failed to mention is that when this ras 668 problem happens...simply going back to an earlier Shadow defender doesn't work. At the moment I can't use most of the earlier Shadow Defenders...the ras error occurs with each. This test one has been to (some degree) better but is not a complete fix yet. It only allows me to go further without the fault occuring.

I suspect that this may be a very good version but the damage has been done.

 

News:
Latest Release
Shadow Defender Version 1.4.0.566 November 16, 2014

Patrick

 

hi
seems Enable hibernation in Shadow Mode removed

 

nothing in common but RASPPOE by schlabbach ist a ten years old and outdated software, which was used up to XP/Svr2003. Windows Vista and newer dont need this stupid stuff. since xp IS more than DEAD for end users i think there is nothing to discuss about.

 

Still on .566

 

Yes I understand that the 'fix' software is old but I've had a problem that there is not much information about and I was willing to consider anything
As for XP, I know that a lot of people are still using XP and some of the operating systems that came later weren't all that marvelous anyway making usage and configuration more difficult rather than easier in some cases.
I've just had an XP user posted to my forum that they like the latest version of Shadow Defender and thanked me for my input.
Issues very similar to my own are still occuring on Windows 7 and later versions are probably not problem free..
People use different versions of Shadow Defender and different versions of Windows and this forum is here specifically to discuss those things. If XP is dead to you and there is nothing to discuss, that is fine but some of us here use it in conjunction with Shadow Defender and like to talk about it without censure or admonishment. Newer is not always better.

Patrick

 

I get the feeling that this version of Shadow Defender 1.4.0.566 is going to be a good version.
It installs very lightly and is without the hibernation additions (which I think caused most my trouble)
It seems once you get the problem that I have, it doesn't matter then which version of the light virtuallization you put on it will still happen. The damage has been done to my system but others have not reported the same errors.
Often on The Official Shadow Defender Forum, I have a post or a pm from a member who is experiencing a problem that is unique to them.
Other people with the same operating systems don't have a problem. Everybodys system is configured differently and hosts all sorts of apps with their own unique relationship to each other and the operating system. As far as the developer is concerned, he can't produce a software that will suit everyone all the time. We add apps, we take away, apps, things are constantly moving and changing. With these security type apps that run deep you can easily find that your saviour becomes your enemy. I know that this is true of rollback/snapshot apps. One day they will just turn around and bite you when you least expect it.. Shadow Defender in essence is very stable and many of the problems that people have experienced have been with the newer versions that tried to address particular issues that had arisen for individuals.
I know that security programs have to keep up with the latest attacks and latest Operating systems and it this constant change of parameters and usage that must cause developers to have nightmares or at best find it challenging. I long for a modular, solid state, Operating system with an inviolable core, where everything else is just a plugin that can't damage the integrity of that core. Nothing dainty, something that can take everything that is thrown at it and never be disturbed and that can internally extend itself to meet all demands. Sort of future proof. Oh well...I'l dream on

I am currently in Shadow Mode in the latest version and connected and I hope that when I shut down or re-boot my problem doesn't re-occur. I think, though, that at this point it is not to do with Shadow Defender, as such. It is just because Shadow Defender is an app of this type.
That is what these Ras-RasHangup error 668 seem to be about.

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

Update 18th Nov Well the rashangup error 668 problems continue but I found out this about it but I don't know what to do with it. It was on a forum. I'd appreciate any advice from members that knows about these things.

....................
'Remarks

An application should not call RasHangUp and then immediately exit. The connection state machine needs time to properly terminate. If the system prematurely terminates the state machine, the state machine can fail to properly close a port, leaving the port in an inconsistent state. Also, an immediate attempt to use the same connection may fail leaving the connection unusable. A simple way to avoid these problems is to call Sleep(3000) after returning from RasHangUp; after that pause, the application can exit. A more responsive way to avoid these problems is, after returning from RasHangUp, to call RasGetConnectStatus(hrasconn) and Sleep(0) in a loop until RasGetConnectStatus returns ERROR_INVALID_HANDLE.'

 

Running XP here on my desktop machine along with SD 519. Still rock solid, no problems and nothing to complain about. Haven't had any malware or experienced any other type of vulnerabilities in many many years. And XP continues to perform just as well as my Win 7 Pro machine.

 

Thanks, running great here on Win 8.

 

Now I can hibernate my system normally. Great product!
WINDOWs 8.1 with newest intergrated updates.

 

I'm glad that members are enjoying the latest version. It seems like a nice clean version and I know that Tony appreciates the feedback.

Patrick

 

Hi Patrick,

Verson 1.4.0.566 is working flawlessly for me on Windows XP SP3. For me, Shadow Defender really is the perfect complement to AppGuard.

While we are discussing feedback, I would just like to say thanks to you too for the time and effort you put in to supporting Shadow Defender, liaising with Tony, and running the Official Shadow Defender Forum.

Regards
pegr

 

Thanks pegr, that's much appreciated

Patrick

 

Tom, Patrick - to refine - xp is dead for end users. some enterprises pay a lot of money for updates for their xp used machines included XPE. compare your background security programs with mine in combinationen with the xp vulnerabilities - i am very sure you have much more than 1. any newer windows since vista is more secure by design. either shadow defender nor sandboxie not any other security suite can prevent intrusion or data stealing while those vulnerabilities (number is growing fast) are present.
and somehow some software still supports xp this has nothing to do with end users, only with those enterprises. even developers meanwhile need to switch the compiler because some newer libraries dont work by design on xp.
from time to time i am tilting at those windmills to correct some thoughts that xp is secure forever (stable or not).

 

Anything of major significance from ver. 519 to ver. 566?

 

I tried version .566 in my W7 32 bits laptop today. And got same Event Warning as did previously when trying another version. This warning (Ntfs 136) is the reason why I have preferred to stay with .346. Someone else reported something similar at the Shadow Defender forum. I am back with .346.
http://shadowdefenderforum.com/index.php?topic=149.msg997#msg997

Bo

 

bo,
I have e-mailed Tony about this today 19 Nov 2014 giving page link and your last description of error.
I'll post here and on official forum if I hear anything from Tony.

Patrick

 

Thanks, Pat.

Bo