why can't I recover these files? [on hold]











up vote
-2
down vote

favorite












I hate Adobe so much.



I downloaded the Adobe Reader DC redistributable version.



I ran the command prompt command to extract contents of the exe because I wanted to grab the msi file.



acrordrdc.exe -sfx_o"c:UsersusernameDesktop" -sfx_ne



I expected this to extract the contents of the exe file to my desktop like any sane program would do.



Instead, it completely nuked my Desktop directory.



I had maybe 200 - 300 files there, most in folders.



I'm not really sure that anything there was critical, but the fact that Adobe can just nuke my entire folder without any warning, and do it so thoroughly, is mind-boggling and infuriating.



Granted, in the documentation I was following, https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/basics.html#expanding-exe-packages, it does specify that "it is best if you do not use an existing folder."



But I missed that detail. And even if I had caught that beforehand, I would have assumed it was a generic warning because it might overwrite files (in the unusual case that it extracts an already existing filename) or because you might "lose" the extracted files in a crowded directory.



Anyway, I've tried running:



Recuva: only found 30ish files to recover

GetDataBack: same

R-studio: same

EaseUS Data Recovery: same

PhotoRec: this program is useless for trying to recover files from a specific folder



How can Adobe destroy those files so thoroughly that I can't even recover them immediately after deletion using professional file recovery tools? Are they so maliciously incompetent that they go out of their way to delete all files in the destination directory and then run bleachbit on the deleted files just to make sure you're screwed?



In 30+ years of extracting files, I've never run into an extraction that would delete files without a warning and confirmation.










share|improve this question















put on hold as too broad by Máté Juhász, DavidPostill Nov 20 at 21:31


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.











  • 1




    The files were overwritten with extracted files. What’s strange about that?
    – Daniel B
    Nov 20 at 6:43










  • 30+ years and you've never thought to use a new empty folder for questionable/new/testing programs? You should've been stocking up on lottery tickets. PS PhotoRec should've recovered virtually everything that's readable, and you tried TestDisk?
    – Xen2050
    Nov 20 at 7:48












  • 30+ years ought to be long enough to know where your backup is.
    – Tetsujin
    Nov 20 at 10:05










  • @DanielB There were probably 50GB of files in that directory and the extraction is 200MB of files. There's not enough to be overwritten.
    – Daniel
    Nov 20 at 14:00






  • 2




    I see the title, but tbh, most of the post is rant - which is why it's descending into this comment-fest rather than just getting a straight answer. Maybe Adobe would know why.. but sh1t happens, which is why we have backups... As the saying goes, any data not stored in at least three distinct locations ought to be considered temporary.
    – Tetsujin
    Nov 20 at 14:19















up vote
-2
down vote

favorite












I hate Adobe so much.



I downloaded the Adobe Reader DC redistributable version.



I ran the command prompt command to extract contents of the exe because I wanted to grab the msi file.



acrordrdc.exe -sfx_o"c:UsersusernameDesktop" -sfx_ne



I expected this to extract the contents of the exe file to my desktop like any sane program would do.



Instead, it completely nuked my Desktop directory.



I had maybe 200 - 300 files there, most in folders.



I'm not really sure that anything there was critical, but the fact that Adobe can just nuke my entire folder without any warning, and do it so thoroughly, is mind-boggling and infuriating.



Granted, in the documentation I was following, https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/basics.html#expanding-exe-packages, it does specify that "it is best if you do not use an existing folder."



But I missed that detail. And even if I had caught that beforehand, I would have assumed it was a generic warning because it might overwrite files (in the unusual case that it extracts an already existing filename) or because you might "lose" the extracted files in a crowded directory.



Anyway, I've tried running:



Recuva: only found 30ish files to recover

GetDataBack: same

R-studio: same

EaseUS Data Recovery: same

PhotoRec: this program is useless for trying to recover files from a specific folder



How can Adobe destroy those files so thoroughly that I can't even recover them immediately after deletion using professional file recovery tools? Are they so maliciously incompetent that they go out of their way to delete all files in the destination directory and then run bleachbit on the deleted files just to make sure you're screwed?



In 30+ years of extracting files, I've never run into an extraction that would delete files without a warning and confirmation.










share|improve this question















put on hold as too broad by Máté Juhász, DavidPostill Nov 20 at 21:31


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.











  • 1




    The files were overwritten with extracted files. What’s strange about that?
    – Daniel B
    Nov 20 at 6:43










  • 30+ years and you've never thought to use a new empty folder for questionable/new/testing programs? You should've been stocking up on lottery tickets. PS PhotoRec should've recovered virtually everything that's readable, and you tried TestDisk?
    – Xen2050
    Nov 20 at 7:48












  • 30+ years ought to be long enough to know where your backup is.
    – Tetsujin
    Nov 20 at 10:05










  • @DanielB There were probably 50GB of files in that directory and the extraction is 200MB of files. There's not enough to be overwritten.
    – Daniel
    Nov 20 at 14:00






  • 2




    I see the title, but tbh, most of the post is rant - which is why it's descending into this comment-fest rather than just getting a straight answer. Maybe Adobe would know why.. but sh1t happens, which is why we have backups... As the saying goes, any data not stored in at least three distinct locations ought to be considered temporary.
    – Tetsujin
    Nov 20 at 14:19













up vote
-2
down vote

favorite









up vote
-2
down vote

favorite











I hate Adobe so much.



I downloaded the Adobe Reader DC redistributable version.



I ran the command prompt command to extract contents of the exe because I wanted to grab the msi file.



acrordrdc.exe -sfx_o"c:UsersusernameDesktop" -sfx_ne



I expected this to extract the contents of the exe file to my desktop like any sane program would do.



Instead, it completely nuked my Desktop directory.



I had maybe 200 - 300 files there, most in folders.



I'm not really sure that anything there was critical, but the fact that Adobe can just nuke my entire folder without any warning, and do it so thoroughly, is mind-boggling and infuriating.



Granted, in the documentation I was following, https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/basics.html#expanding-exe-packages, it does specify that "it is best if you do not use an existing folder."



But I missed that detail. And even if I had caught that beforehand, I would have assumed it was a generic warning because it might overwrite files (in the unusual case that it extracts an already existing filename) or because you might "lose" the extracted files in a crowded directory.



Anyway, I've tried running:



Recuva: only found 30ish files to recover

GetDataBack: same

R-studio: same

EaseUS Data Recovery: same

PhotoRec: this program is useless for trying to recover files from a specific folder



How can Adobe destroy those files so thoroughly that I can't even recover them immediately after deletion using professional file recovery tools? Are they so maliciously incompetent that they go out of their way to delete all files in the destination directory and then run bleachbit on the deleted files just to make sure you're screwed?



In 30+ years of extracting files, I've never run into an extraction that would delete files without a warning and confirmation.










share|improve this question















I hate Adobe so much.



I downloaded the Adobe Reader DC redistributable version.



I ran the command prompt command to extract contents of the exe because I wanted to grab the msi file.



acrordrdc.exe -sfx_o"c:UsersusernameDesktop" -sfx_ne



I expected this to extract the contents of the exe file to my desktop like any sane program would do.



Instead, it completely nuked my Desktop directory.



I had maybe 200 - 300 files there, most in folders.



I'm not really sure that anything there was critical, but the fact that Adobe can just nuke my entire folder without any warning, and do it so thoroughly, is mind-boggling and infuriating.



Granted, in the documentation I was following, https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/basics.html#expanding-exe-packages, it does specify that "it is best if you do not use an existing folder."



But I missed that detail. And even if I had caught that beforehand, I would have assumed it was a generic warning because it might overwrite files (in the unusual case that it extracts an already existing filename) or because you might "lose" the extracted files in a crowded directory.



Anyway, I've tried running:



Recuva: only found 30ish files to recover

GetDataBack: same

R-studio: same

EaseUS Data Recovery: same

PhotoRec: this program is useless for trying to recover files from a specific folder



How can Adobe destroy those files so thoroughly that I can't even recover them immediately after deletion using professional file recovery tools? Are they so maliciously incompetent that they go out of their way to delete all files in the destination directory and then run bleachbit on the deleted files just to make sure you're screwed?



In 30+ years of extracting files, I've never run into an extraction that would delete files without a warning and confirmation.







data-recovery adobe-reader photorec






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 at 5:40

























asked Nov 20 at 5:31









Daniel

153112




153112




put on hold as too broad by Máté Juhász, DavidPostill Nov 20 at 21:31


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






put on hold as too broad by Máté Juhász, DavidPostill Nov 20 at 21:31


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.










  • 1




    The files were overwritten with extracted files. What’s strange about that?
    – Daniel B
    Nov 20 at 6:43










  • 30+ years and you've never thought to use a new empty folder for questionable/new/testing programs? You should've been stocking up on lottery tickets. PS PhotoRec should've recovered virtually everything that's readable, and you tried TestDisk?
    – Xen2050
    Nov 20 at 7:48












  • 30+ years ought to be long enough to know where your backup is.
    – Tetsujin
    Nov 20 at 10:05










  • @DanielB There were probably 50GB of files in that directory and the extraction is 200MB of files. There's not enough to be overwritten.
    – Daniel
    Nov 20 at 14:00






  • 2




    I see the title, but tbh, most of the post is rant - which is why it's descending into this comment-fest rather than just getting a straight answer. Maybe Adobe would know why.. but sh1t happens, which is why we have backups... As the saying goes, any data not stored in at least three distinct locations ought to be considered temporary.
    – Tetsujin
    Nov 20 at 14:19














  • 1




    The files were overwritten with extracted files. What’s strange about that?
    – Daniel B
    Nov 20 at 6:43










  • 30+ years and you've never thought to use a new empty folder for questionable/new/testing programs? You should've been stocking up on lottery tickets. PS PhotoRec should've recovered virtually everything that's readable, and you tried TestDisk?
    – Xen2050
    Nov 20 at 7:48












  • 30+ years ought to be long enough to know where your backup is.
    – Tetsujin
    Nov 20 at 10:05










  • @DanielB There were probably 50GB of files in that directory and the extraction is 200MB of files. There's not enough to be overwritten.
    – Daniel
    Nov 20 at 14:00






  • 2




    I see the title, but tbh, most of the post is rant - which is why it's descending into this comment-fest rather than just getting a straight answer. Maybe Adobe would know why.. but sh1t happens, which is why we have backups... As the saying goes, any data not stored in at least three distinct locations ought to be considered temporary.
    – Tetsujin
    Nov 20 at 14:19








1




1




The files were overwritten with extracted files. What’s strange about that?
– Daniel B
Nov 20 at 6:43




The files were overwritten with extracted files. What’s strange about that?
– Daniel B
Nov 20 at 6:43












30+ years and you've never thought to use a new empty folder for questionable/new/testing programs? You should've been stocking up on lottery tickets. PS PhotoRec should've recovered virtually everything that's readable, and you tried TestDisk?
– Xen2050
Nov 20 at 7:48






30+ years and you've never thought to use a new empty folder for questionable/new/testing programs? You should've been stocking up on lottery tickets. PS PhotoRec should've recovered virtually everything that's readable, and you tried TestDisk?
– Xen2050
Nov 20 at 7:48














30+ years ought to be long enough to know where your backup is.
– Tetsujin
Nov 20 at 10:05




30+ years ought to be long enough to know where your backup is.
– Tetsujin
Nov 20 at 10:05












@DanielB There were probably 50GB of files in that directory and the extraction is 200MB of files. There's not enough to be overwritten.
– Daniel
Nov 20 at 14:00




@DanielB There were probably 50GB of files in that directory and the extraction is 200MB of files. There's not enough to be overwritten.
– Daniel
Nov 20 at 14:00




2




2




I see the title, but tbh, most of the post is rant - which is why it's descending into this comment-fest rather than just getting a straight answer. Maybe Adobe would know why.. but sh1t happens, which is why we have backups... As the saying goes, any data not stored in at least three distinct locations ought to be considered temporary.
– Tetsujin
Nov 20 at 14:19




I see the title, but tbh, most of the post is rant - which is why it's descending into this comment-fest rather than just getting a straight answer. Maybe Adobe would know why.. but sh1t happens, which is why we have backups... As the saying goes, any data not stored in at least three distinct locations ought to be considered temporary.
– Tetsujin
Nov 20 at 14:19















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

Paul Cézanne

UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

Angular material date-picker (MatDatepicker) auto completes the date on focus out