Whoops Posted October 16, 2012 Share Posted October 16, 2012 I'm recovering an external usb hard drdive that inadventertly was "quick formatted". There is approximately 1 t of data needed reocvery. When Recuva finishes I get the message when tagging all the files that the "maximum path length exceeded". I need this data (pic, documents, files) so are there alternatives to change the file names, over-ride the maximum path length, or are you telling me I need to go to a recovery service. Tell me it aint so Link to comment Share on other sites More sharing options...
Alan_B Posted October 16, 2012 Share Posted October 16, 2012 What is the destination for the recovered files ? You are more likely to hit the "maximum path length exceeded" problem when restoring to a long path, e.g. X:\My First Recovery attempt to a folder with a name that describes what I am thinking and doing\ Much better to use X:\ or X:\Y\ Link to comment Share on other sites More sharing options...
Moderators Nergal Posted October 17, 2012 Moderators Share Posted October 17, 2012 I've moved this topic to the recuva forum ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF. Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark) ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T. Support at https://support.ccleaner.com/s/?language=en_US Pro users file a PRIORITY SUPPORT via email support@ccleaner.com Link to comment Share on other sites More sharing options...
tanis Posted January 21, 2013 Share Posted January 21, 2013 I'm adding my 2 cents here. I tried that solution and it doesn't help. Recovering to C:\R\ doesn't work. Not even for just a file that lives in the root folder of the HDD I'm recovering. Link to comment Share on other sites More sharing options...
Alan_B Posted January 21, 2013 Share Posted January 21, 2013 I'm adding my 2 cents here. I tried that solution and it doesn't help. Recovering to C:\R\ doesn't work. Not even for just a file that lives in the root folder of the HDD I'm recovering. Obviously that solution worked for Whoops because he did not need to return for further information. That is my reasonable assumption which could be wrong - but is doing no one harm. You have an unreasonable assumption that your situation is identical to that of Whoops, and that assumption would harm anyone who takes notice of you and fails to attempt a solution that would help them. Link to comment Share on other sites More sharing options...
tanis Posted January 22, 2013 Share Posted January 22, 2013 I actually found the solution: downgrading to 1.40 works fine. Hence I suppose something has been broken after that release. Link to comment Share on other sites More sharing options...
Alan_B Posted January 22, 2013 Share Posted January 22, 2013 Thanks for the feedback. Sounds like it was broken at version 1.41, issued 11th October 2011. Link to comment Share on other sites More sharing options...
Moderators Augeas Posted January 22, 2013 Moderators Share Posted January 22, 2013 I'm closing this thread so we don't have two threads going on the same subject at the same time. Continue here http://forum.pirifor...topic=37713&hl= Link to comment Share on other sites More sharing options...
Recommended Posts