Sorry but after I open Recuva, it crashes instantly. The Recuva window flashes for about half a second and then crashes. I am using WinXP SP3 and the problem doesn't exist when I was using WinXP SP2.
Please render some help since I really need this. Thanks.
SP3 had a bad reputation for breaking XP.
Perhaps a Recuva registry entry under SP2 has been broken by SP3 and Recuva portable would avoid that problem.
Failing that,
Did Recuva work for you before you installed SP3 ?
If so it would be informative to know if the same version of Recuva still works under SP3.
You can get the old versions from
SP3 per se isn't the problem. I, and probably many others, have been running Recuva under SP3 for yonks. But there again I guess that there are many ways of installing SP3. H's suggestion is probably the best at the moment.
To add a bit to what Alan was saying about SP3.
_____
There are many people who run SP3 machines with no problems, but there are also many who have lots of problems with SP3.
The trouble is, that SP3 changes the way XP functions in respect to random address layout & makes changes to key system areas.
While this may not be a factor for a lot of people, it certainly does cause problems with certain hardware/software configurations.
Far more so, than SP2.
While it is true that switching hardware & updating software (if they even have an update for some programs) may or may not fix things, one should not have to switch hardware every time they write a few new lines of code.
In general, SP2 is stable. And in general, also SP3. But less so than SP2 has been my experience when working across multiple machines.
Could be wrong on this, but sure seems like SP2 machines break less often (read: crash less, experience fewer problems, re-install less) than SP3 cousins.
I may be wrong on all this, but it is what seems to be my experience. While I do know that there are SP3 machines that users appear to have no problems, I also know that everyone uses different software (and such, the problems arise).
So for now, I tend to side with the belief of Alan, as my experience across multiple PC machines & configurations gives me the impression that SP2 machines are a wee bit more stable & less crashy than their SP3 cousins (cause fewer problems in general with the widest range of older + newer software).
_____
I happenced to not mention a clean SP3 install, seeing that the reader suggested that it worked fine in SP2, but went squirrelly the moment he switched to SP3.
This instant flashing and crashing when launched is usually caused by a conflict of some sort, as shown here ...
I had XP Home with SP2 on an Acer Laptop,
and a lot of experience of previous versions of Windows going belly up.
When SP3 became available I decided to be one of the last of the lemmings to jump off the cliff,
and sure enough a lot of "early adopters" got their due reward
I decided that I would not run the risk of SP3.
Eventually, after a partition image backup in anticipation of a disaster, SP3 was installed and I found I was unexpectedly lucky.
I know that only a minority of systems were damaged by SP3,
but there were far more complaints in forums from those who suffered than reports of success.
Actually, upon reflection, I was one of those that benefited from a successful SP3 but like others I failed to report success.
I do not know the ratio of failure to success,
I just know that I was not alone in being afraid of the disasters that were being reported.
Sorry but after I open Recuva, it crashes instantly. The Recuva window flashes for about half a second and then crashes. I am using WinXP SP3 and the problem doesn't exist when I was using WinXP SP2.
Please render some help since I really need this. Thanks.
I second this problem. Same manifestation with the most recent version 1.44.778.
I'm running Windows XP, SP3, with an older AMD chipset. Recuva is operating on a second hard drive installed. All of the latest updates from Microsoft have been installed as offered. The program was downloaded using Comodo Browser which is a flavor of Chrome.
I'd note that Recuva was working fine for several versions under this configuration but this latest version has a problem for me.
I initially saw the update at FileHippo and opted to download it and allowed it to install and overwrite the existing version (1.43.623). When I started the program it immediately launched, gave a brief flash of the splash screen, then locked my system up big time. I could not bring up the task manager to kill it and had to go for the power switch.
I thought the update was flawed so I did a full uninstall and took a fresh download from FileHippo since it is a designated download site. The fresh install still locked up my system, so even a fresh install and restart was still a problem. It seems to give a brief display of the flash screen but then locks the system up, or is using lots of CPU or memory to the point that it disables all functionality.
After uninstalling the new version (1.44.778) I went to FileHippo and took the last version back (1.43.623) and installed that. The prior version came up and worked just fine and is what I have installed now.
So, given that at least 2-4 past versions of Recuva have been working for me without a problem under Windows XP, SP3, and the re-installation of 1.43.623 is working, for me at least the suggestion is that something that changed in 1.44.778 is my problem, not a system conflict with another program. If there is a system conflict it was built in to 1.44.778.
The question then becomes, 'what?'
DMK
Sunclad
If there is a system conflict it was built in to 1.44.778.
I've got no argument with that, but if you guys give safe mode a try, and it works, then that will give the devs something to work with. If it doesn't, then that information is also helpful.
Welcome to the forum by the way Sunclad.
So, given that at least 2-4 past versions of Recuva have been working for me without a problem under Windows XP, SP3, and the re-installation of 1.43.623 is working, for me at least the suggestion is that something that changed in 1.44.778 is my problem, not a system conflict with another program. If there is a system conflict it was built in to 1.44.778.
The question then becomes, 'what?'
Possibly something in the announcement, i.e.
The latest version might be stuck with difficulties that were ignored by the previous version. e.g.
Files greater than 1 GB ;
more than 1 million files ;
Issues with Outlook Express ; recycle bin ; mini-SD ;
Windows services that might be required and expected for VHD imaging, such as VSS, etc;
exFAT labels ; A.D.S. ; USB drives ; etc.
Your report clearly identifies that 1.44.778 fails but 1.43.623 works on your system of XP + SP3.
This is much more testable than the first report which probably refers to different version of Recuva under different versions of SP?
Please run Recuva in Debug mode.
http://www.piriform.com/docs/recuva/troubleshooting/running-recuva-in-debug-mode
After you do (and it crashes) please post the log to this thread (you may have to change it's extension from .log to .txt)
also hold on to the dmp file (if one is created) as it may be needed later
I've been using Recuva portable for years with WinXP SP3
The latest build is the only one I've ever had problems with
The previous version RecuvaPortable1.43.623 works fine
RecuvaPortable1.44.778 crashes every time during startup
It is most definitely not a Windows problem
Eventually someone at Piriform will figure that out
Until then I will just stick with the previous working version which is 1.43.623
Any posts entertaining the notion that Windows XP SP3 is broken are a total waste of time
Trust me, I've been fixing things all my life
I am sure the devs will read this thread, I also agree that it has nothing to do with XP SP3.
No one seems to have indicated whether they are using 32 bit or 64 bit versions of Windows.
This can make all the difference in the world.
I suggest everyone who has a problem should report what version of Windows XP is being used
This bug report is no good if developers investigate 32 bit XP when the problem could be with 64 bit XP which is known to have
poorly implemented 64-bit system components like drivers
see post date Thu Nov 22, 2012 8:31 am in
http://forum.palemoo...php?f=15&t=1700
That may possibly be the reason Firefox has apparently abandoned 64 bit version development of browsers.
Specifically relevant to 64 bit versions of XP is the fact that Palemoon has till now provided full release (not crashable nightly) versions of both 32 bit and 64 bit for XP, Vista, and Windows 7,
but as at version 15.3 they can no longer support 64 bit XP because Microsoft have chosen to exclude this from the capability of Visual Studio 2012 as per topic
http://forum.palemoo....php?f=1&t=1647
See also the post dated Tue Nov 20, 2012 12:02 am in
http://forum.palemoo...php?f=15&t=1664
Any posts entertaining the notion that Windows XP SP3 is broken are a total waste of time
In my view it is a waste of time on such little evidence to categorically exclude the possibility that SP3 has broken XP because :-
this was a problem for a minority of SP3 upgrades in the past ;
and this topic commenced with the post which stated that this problem occurs with XP + SP3 but does not occur with XP + SP2.
After 30 years of developing/proving fail-safe software, and debugging software created by previous engineers,
I have learnt not to exclude any possibility.
Obviously all the evidence so far points to new features in Recuva version 1.44.778 being incompatible with at least 3 computers that are running XP + SP3,
and no one is yet reporting problems with alternative versions of Windows.
I was, and am, in full agreement with Hazelnut's suggestion of trying the Portable version,
but your experience shows that even this is not a solution.
We are unable to recreate this on XP SP3 too. I will request dmps/logs from the OP.
Still having problem when using Recuva portable version.
But it can operate well in WinXP SP3, and the problem exists after I upgraded my computer to SP3 until now.
Really hope that can be fixed.
By the way, although it is not really related to this, but other software from other company will have the same problem, for example, GIMP.
Now what can I do is to think carefully whether I need to delete the files I don't want...
But it can operate well in WinXP SP3, and the problem exists after I upgraded my computer to SP3 until now.
Is this a 32 bit or a 64 bit system.
I understand that a probably cause for Mozilla abandoning 64 bit browsers is that 64 bit drivers are more defective than 32 bit,
hence 64 bit "nightly" was less stable than 32 bit "nightly".
I think I remember that Microsoft recently included XP support in Visual Studio and as a result Palemoon switched to using Visual Studio for browser development.
Then Palemoon found that Microsoft do NOT support 64 bit XP - hence 64 bit XP users now can only use the 32 bit Palemoon browser.
If Microsoft cannot support 64 bit XP in Visual Studio that indicates that 64 bit drivers and API's for XP were not developed with the same care as their mainstream 32 bit siblings.
I guess that is because when XP was being developed the target at that time was the majority population of 32 bit systems.
So, to anyone with a problem using Recuva under XP + SP3
Is this on a 32 bit or a 64 bit system ?
What happens on a 64 bit system if you employ the 32 bit version of Recuva ?
I do not know about Installed Recuva, but I do know that Portable Recuva unzips into both 32 bit and a 64 bit versions,
and if you delete the 64 bit version Recuva64.exe then you can launch the 32 bit Recuva.exe and then Recuva.exe will run.
My experience in the past was that launching 32 bit Recuva.exe would result in a default execution of 64 bit Recuva64.exe if Recuva64.exe was present.
We are unable to recreate this on XP SP3 too. I will request dmps/logs from the OP.
did you provide dumps and log?