locked
Windows Updates Cause Problem with Money 2007? RRS feed

  • Question

  • I use Windows 8.1, which until now has worked well with Money 2007. Since the latest monthly batch of Windows updates on March 9, I've been unable to successfully complete the download of any bank statements into Money. The OFX and QIF files download from the bank okay, Money recognizes them, lists the number of transactions (but no $ amounts) on the Accounts page, and then promptly displays an error message and states the program must close.  Has anyone experienced this, and found a solution?  Thanks so much. 
    Saturday, March 21, 2015 8:53 PM

All replies

  • A problem like this was reported previously reported:

    https://social.microsoft.com/Forums/en-US/9dd81982-268b-4b59-b413-f012cedf5aff/windows-7-updates?forum=money

    but, unfortunately, no solution has been posted.  One thing that you might try is to apply the patch for mnyob99.dll as described in the first "sticky" post in this forum:

    https://social.microsoft.com/Forums/en-US/d28d6921-1f01-430f-b33e-f5a3ec47077b/money-plus-bug-and-solution-mnyob99dll?forum=money

    Note that the patched version on mny0b99.dol that is available for download on Ameridan's Blog:

    https://microsoftmoneyoffline.wordpress.com/2012/12/02/windows-8-64-bit-version-compatibility-with-sunset-money/

    is for Money Plus Deluxe Sunset.  You will either have to create a custom mnyob99.dll for Money 2007 or upgrade to Money Plus Deluxe Sunset.

    I would first try installing Money Plus Deluxe Sunset to see if that fixes the problem.  If not, then try patching with Ameridian's mnyob99.dll.  When doing this experimentation, be sure keep good backups of all your files and keep track of which file is which.  A file written by Money Sunset can't be opened by Money 2007.

    Let us know how you make out.


    Bill Becker


    • Edited by Bill Becker Sunday, March 22, 2015 2:10 PM fixed typo
    Sunday, March 22, 2015 3:41 AM
  • Thank you Bill, I will check out your suggestions this week when I return.  I'm surprised that no one else has reported this as an issue yet.  Although tedious, I also might consider uninstalling the latest Windows updates and re-installing one at a time until the culprit is discovered.  

    Rick 

    Sunday, March 22, 2015 6:33 PM