The autorun.inf file is missing or damaged
papahotel94 -
Since the last update of W10, Money 2005 no longer recognized external storage devices.
I therefore uninstalled Money 2005 to reinstall it. Mission impossible because "the autorun.inf file is missing or damaged."
I bypassed the problem by using a CD of Money 2005 that I had.
Money 2005 installed fine, but in the previous version, the one before the Patch for W10.
So no "Treasury" function, for example.
Moreover, it's impossible to open the files from previous backups, even though Money finds them in an automatic search.
Incomprehensible.
3 answers
-
-
Hello,
It would be nice in any case not to post multiple times about the same thing.
https://forums.commentcamarche.net/forum/affich-38003120-impossible-installer-money2005-telecharge-sur-le-site#dernier
That said, I installed 2005 on my Windows 10 virtual machine to play the guinea pig (I use 2001), but as I mentioned in the link above, not with a CD, just directly from the CCM link (stripped of its extra exe in the name).
There’s no problem opening my mny work file that I copied (other than that it skips any Pro categories, which is normal since I have 2001 in Pro version), no autorun.inf story (it’s not a CD), no dubious Patch story and the cash flow is easily accessible, so everything works.
I also mentioned in the other link, without any further response to this day other than this multipost, that it’s tiring, that if for some reason or another the restoration of the backup doesn’t work there’s surely an mny file that will work and, even if that were not the case (why?) it would be necessary to try to work around it by regenerating it from that backup in the version of Money where it was created.
-
-
Thank you to JCB40 for their response; unfortunately, the links provided are no longer active...
Thanks also to Brucine for their feedback; it’s a relief to learn that your issues aren’t affecting others.
Indeed, the Money file provided by CCM is not a CD, but the error message "missing autorun.inf file" does appear, and the problems described are still not resolved to this day!
Thank you all for your understanding.
For your information, I posted a second question because the first one was incomplete and did not reflect the full extent of the problem.
-
Hello,
When people are trying to help you and you're being unpleasant, it doesn't help...
Your previous post mentions that you installed Money 2005 from the CD (and that it installed correctly), the most common cause of the autorun.inf error is the CD, which you still mention in your initial message, hence my clarifications.
If it has now been reinstalled from the link of this forum (or another one), we should have relied on our divination skills, which are documented as the cause of this error (by the way, it applies to all Windows versions) is:
-an incomplete uninstallation of the previous Money version: uninstall, manually clean up if you know how to do it or with the help of tools like Revo Uninstaller, reinstall-an unexpected entry in the registry (note that in my Windows 10 installation, it does not exist):
https://www.memoclic.com/forum/117270-installation-de-money-sous-seven/
-it's not necessarily a Money error, it could be a Windows corruption due to a virus or not: as a last resort, try reinstalling Windows.
-
-
Good evening brucine,
I indeed had to install Money 2005 from an old Money 2005 CD, as the installation of the file provided by CCM on the forum was impossible due to the issue: "the autorun.inf file is missing or corrupted."
For the uninstallation, I meticulously followed the procedure indicated everywhere (Revo, deletion of hidden files, deletion of the file in HEY_Current_User, etc...).
I also renamed the autorun.inf registry key that had the value @="@SYS:DoesNotExist" to SAutorun.inf as suggested by MemoClic.
Nothing works, the message concerning the autorun.inf file always appears, preventing the installation of Money2005-FR-QFE3.exe.
Indeed, the issue may stem from W10 since my problems started after the latest Microsoft update, but I was hoping to find a solution before, as a last resort, attempting to reinstall W10. Windows....
Sincerely,