@PC Trek
Thanks for your reply regarding me pointing out that your application produces a Runtime error ‘0’. I see now there is another reporting the same.
I had hoped you could provide some information on what I can find to help you diagnose and improve your program so that it does not have to produce the Runtime error. Instead, it appears that the response is more centered on why your program might fail. It is as if you are satisfied with the program the way it currently is, and that you are willing to provide info on some hoops the user can jump through to get it to work for them. I really am not interested in that sort of answer; instead, I had hoped to help you fix the program so it would work for other users, not just me. As a programmer, I am always looking for ways to improve things, and users can provide lots of valuable information. With that in mind, understand why my response may seem a little harsh.
>Some chromium based browsers like Chrome, Opera or Vivaldi might won’t allow password decryption while browser is running. We have a workaround for this, but it some rare occasions it might fail.
Regardless of a workaround, your program should be able to detect if a browser is running that could prevent you from decrypting the passwords. In that case, display a message to the user that they need to close the browser in order for your program to have access, and I do mean browser by browser, not just a generic “close all browsers” message.
Obviously you could alternatively run your work-around to see if you can come up with some results, however if your work-around cannot determine if it was successful in decrypting all the passwords, then you would provide what information you have found, and still inform the user to close the browser to get the full results.
There is absolutely no case where you should be satisfied with a Runtime error to the end user.
>Please try to delete all files in your temp folder in you don’t need them and make sure no browser has been started even once before running our software. To go to your temp files just type %temp% in windows explorer.
You should be able to navigate through any temp files, ignore, or know where to access the correct location to access browser passwords, but don’t expect to put the burden on the user to clean you a playground so you can demonstrate you can jump rope.
FIREFOX:
As of September 2018, most Firefox users will not see any password results from your program.
Your online FAQs explain why a user may not get any passwords from Firefox due to the Firefox change that caused the push to a 64-bit edition. Your suggestion to have a user switch back to the 32-bit edition does not seem to be a viable solution. Users simply want the passwords decrypted as your advertising material suggests your program can do. Users will see the suggestion to switch back to a 32-bit edition as proof that your program cannot do what it advertised. Sure you could even suggest that users install Windows 95 with a Mosaic browser so your computer program can shine, but that is not what users are wanting to do.
Your alternative is to suggest users avoid the conversion to 64-bit Firefox, but it really amounts to the same thing; reinstall a 32-bit edition of Firefox.
The Mozilla website states “Users of 32-bit Firefox on 64-bit Windows systems with at least 3 GB RAM are being migrated to 64-bit Firefox, for increased stability and security.” Why do you think that users who have migrate to a more secure browser will want to give that up? You suggestion might have been viable for a month or two when that all started in October 2017, but now near the end of 2018, and several Firefox updates since then, it simply is not feasible to expect anyone to take your suggestion seriously.
Another part of your explanation is that Advanced Password Recovery Suite is a 32-bit program, and therefore cannot load the 64-bit libraries.
Again, think about what you are saying! It is 2018, and 64-bit applications are very common. If you need to upgrade your program to a 64-bit program, what is holding you back? If you need a compiler update, sooner or later, you will have to cough up the funds to join the 64-bit world. How long do you think you should advertise a program’s abilities, only to have users dig deeper to find out that it cannot do what it wished it could, and what the user expected it could, simply because you did not keep up?
If you can’t cut the mustard, don’t pretend you could dance with the stars.