If you agree with me that Microsoft Money is the BEST personal (and small business) financial management software package available, then you’ve come to the right place for improving Money’s OFFLINE capabilities.

  • Even though Microsoft has elected to divorce the program from the MSN Money servers as of January 31st, 2011 (which did much more than just grab statement downloads, including independent stock and fund quotes for ALL of your investments, passing through third-party web-scrapes of your data, supporting Online banking, investment news, tax and exchange rates, LiveID password authentication, etc.), they have made available a **FREE**  legal copy (the SUNSET edition) of the latest updated  OFFLINE  version of  Microsoft Money Plus Deluxe that you can download, even if you’ve never used Money before!  On its own, it will only update via OFX statement files that you download through the websites of your financial institutions.
  • Now by installing Python and downloading Bobby’s PocketSense script package that runs on Python, you will be able to essentially mimic those Online functions that Microsoft will no longer be providing.
  • For those that only need to update quotes (no Account Statement updates) and don’t wish to install Python scripting, Hung Le had written a Java app a year ago that has been recently updated and the link in the original Blog page has been updated with this new version.
  • Another new program is now available for updating quotes from MSN in a very similar fashion to Money’s original online updates.  It is called MSMoneyQuotes and you’ll find links to it in this blog post.
  • I have developed Ameridan’s addon package to PocketSense that allows you to run these scripts (and review your Online investment data) from within your Money program.
Make sure you check out the Look Up Your OFX Settings Blogpage with links to all of the sources of OFX settings that I am aware of.  All of the known working sites.dat settings that I am aware of are listed (and continuously kept updated) in this blog page.

IMPORTANT!! (Courtesy of Cal Learner)

People using LiveID (Passport) in Microsoft Money should turn that off by logging in offline.   You may have to do this to accomplish that:

Disconnect from the Internet. If using Money Plus, change the date on your computer to a date in January, such as 2011 Jan 15.   Start Money, and log in offline.    Remove your LiveID.   Do not attempt to change your LiveID.

To remove the Live ID, go to File-PasswordManager, and choose to remove your LiveID.   To remove or add a conventional password, also see File->PasswordManager.

If you get a warning that you cannot remove the LiveID, turn off Tools->Settings->ReceiveAccountUpdatesFromMsnMoneyMyAccounts if you set that, even if you leave on Live ID to work with Ultrasoft Money.

I’ve recently optimized the Blog widget settings to make navigating within this Blog as easy as possible. I hope you find it a little easier to find things – I pledge to continue doing my best to keep it up-to-date as a resource of helpful material for Microsoft Money users as well.

Other helpful information courtesy of Cal Learner {downloads}

US Money Sunset (Works with US and Canadian Files only; others see below)

Self-contained installation files for use (including if the original disk requires activation).   No direct online access works with the Sunset versions. See for an explanation of the Sunset versions

US Money Plus Deluxe Sunset

Downloadable from  [static link]
or use

US Money Plus Home and Business Sunset
Downloadable from  [static link]
or use

Notes for North America:
1. US and Canadian Money 2005 and Essentials users — as well as other US and usually Canadian users — can use Money Plus Deluxe Sunset if they have to reinstall at some point. See  for information.
2. Some US users of older versions of Money (Money 98 through Money 2003)  may have to use an additional step, described in  , of first installing a verson of US Money 2004 or 2005 to perform a file conversion before installing Money Plus Sunset. Here is a link to a minimally functional version of US Money 2005 (filename webinst.exe) that can be used for conversions:

Money 2005 UK – QFE2
Self-contained UK Money 2005 file including all available patches. Replaces all MS Money UK 2005 installation discs. Usually solves “Money cannot locate the file because it’s a read only file or you do not have permission to change it” error message.
Download from

Money 2005 International English QFE2
Self-contained Money 2005 International English installation file from Microsoft, including all updates (For Australia, New Zealand, Hong Kong and all other English versions other than for US, Canada, UK).
Download from

Money 2005 French – QFE3
Self-contained French Money 2005 file including all available patches. Replaces all MS Money French 2005 installation disks.
Download from

Notes for all versions…

It is suggested that all Money users keep a good copy of the installation file, even if the need is not immediate. It will be needed if you reinstall Money in the future. Those links can change, so do a search if you don’t find the file you need. Since we don’t know how long these files will be available, it is best to keep a copy of your appropriate installation file in a safe place.

Regional versions

Money data files are in a different format for each region. The correct regional version of Money must be used or the data file will not open.

It is possible to convert from one region to another only by exporting data as loose qif and importing to the new regional version of Money. See  and  .

Old Money versions will run only under 32-bit Windows

Old versions (Money 2000 and earlier) include 16-bit code so can run only under 32-bit Windows (XP, Vista, 7 and 8).

To be able to use data files from these older versions on a new PC with Sunset:

  • Download m12usweb.exe to the new computer.
    MD5 is 1c62413858e2184eb39862f1b2afba44See
  • Put the latest *.mny and *.mbf files into the Documents folder of the new computer
  • Temporarily uninstall Sunset if you had already installed on new computer
  • Disconnect from the Internet (may not be needed, but recommended)
  • Set the computer date to 2004/1/1 (or there about)
  • Install trial Money 2004 by running  m12usweb.exe
  • Let that convert your *.mny file. Check that it seems to work. Save the converted file. Maybe change the name so that you can distinguish the converted file. Close Money 2004
  • Set the date right. Install/reinstall Money Plus Sunset. Let it uninstall Money 2004. Let Sunset convert the Money 2004 *.mbf file to Sunset
  • Make extra copies of Sunset install and data files onto other media

64-bit Windows

The U.S. Sunset versions of Money, downloadable above, run great in Win32 mode of Windows 8 and 10.  It is not a 64-bit program though, so hopefully,  Win32 remains supported within Windows for many years yet.  However because of a bug in the file mnyob99.dll, there may be issues with with certain OS updates.   It is recommended that a patched version of this file be used to resolve these issues and insure compatibility.  Read more (and find a link to the patch) here.

Internet Explorer

Money uses Internet Explorer as the GUI, so do not delete the program from your PC.  If Microsoft ever switches over exclusively to Edge, Money may cease to function.

Money version downloads

The latest versions are free for anyone to use, but are not supported by Microsoft. The download links above might become unusable at any time.

Remember to keep a secure copy of the downloaded installation file for when you need to re-install. Your data will be inaccessible if your Money program becomes corrupted and you cannot reinstall Money or if you procure a new PC and cannot install Money.



Comments off

Chase OFX downloads

Having just set up multiple Chase accounts to work with Pocketsense, here are my findings:

  • Quicken downloads are offered on the web, but only to the primary account holder, and only after you have logged onto the web, click on top left button and then click on Profile & Settings > Manage Account Security > Desktop apps > activate Quicken.  Otherwise, you will only be offered pdf downloads.
  • Then clear you account credentials (if any): Pocketsense > Setup > Delete Account
  • Add your Chase account:  Pocketsense > Setup > Add Account
  • For each account user, after running Pocketsense > Setup > Test Account, you will get an error informing you that you have a secure message requiring your verification.  Logon to your web account, click on top left button and then click on Secure Messages and then click on the link within your most recent message to activate downloads.
  • Now you can test once again and you should have a successful download that you’ll need to Send to Money so that you can match with the appropriate account in Money.
  • Test each account individually and match to Money accounts before running the regular combined downloads.

sites.dat settings

     SiteName : CHASE 
     AcctType : BASTMT     #bank accounts 
     fiorg : B1 
     url : 
     fid : 10898 
     bankid :     #use appropriate routing number  
     brokerid : 
     appid : QWIN
     appver : 2400
     ofxVer  :    103
     mininterval : 

     SiteName : CHASE CREDIT CARD  
     AcctType : CCSTMT     #credit card  
     fiorg    : B1 
     url      :  
     fid      : 10898
     bankid   : 
     brokerid : 
     appid    : QWIN
     appver   : 2400
     ofxver   : 103


Comments (5)

SSL exception (Universal AT&T, Citicard, Searscard…)


It’s been a while since I’ve written an article, indicative of how smoothly Money, and our supportive scripts, are running for us on a daily basis.

For those of you that haven’t upgraded Python in a while (I was at version 2.7.6), it appears that the banks are upgrading the security on their OFX servers and we need to be communicating with software that addresses recent security vulnerabilities, to avoid getting errors like the one bounced back to me from Citibank these past few days:

** An ERROR occurred sending POST request to www accountonline com
Exception type :
Exception val : [Errno 1] _ssl.c:507: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
An online error occurred while testing the new account.

I posted my issue on the Pocketsense forum and Robert so kindly responded with a reminder that the error above was probably due to an older version of Python.  Apparently last month, Python released 2.7.14, and having just upgraded Python, I’m happy to report that all is good for me again.  For those of you using 2.7.12 or 2.7.13, I don’t know that it is necessary to upgrade already, but I was way behind.  This indicates to me that the banks don’t move too quickly either, as they probably don’t make many changes to their servers, unless (like us 😉 ) they are actually experiencing security or hardware issues.

Comments (4)

Schwab downloads not working

Sometime towards the end of July 2017, access to their OFX server appears to have been tightened down, effecting a large number of users via various access methods – including Pocketsense, Moneydance, Quicken, and others.   The story is that blocks of IP addresses were entered into the firewall (removed from their “white list”?) a little too aggressively, in an attempt to curtail malicious (Bot) attacks on their server.

Several of us have already had success by calling Schwab Tech Support @ (866) 855-9102 option [3], to have our dynamic IP address “range” added to this white list, so hopefully that success will continue, as our IP providers assign us a new IP address whenever they feel like it.  I’m assuming that they guesstimate the dynamic IP address “range” based on a common mask of, or perhaps they loosen it up even more.

[Update 9/29/2017]

My IP address has changed many times during the last two months, and yet my Schwab downloads have worked perfectly since being added to their white list, so apparently they have resolved this issue properly.

Leave a Comment

Discover has changed your Account ID

This week, the cause of the errors when using Pocketsense to download Discover transactions is that, without telling anybody, Discover has changed your Account ID needed to access their OFX server, and the only method of revealing what your ID has been changed to, is by downloading and reviewing a statement from the website.

Instructions to determine your new Account ID

  • Log into your Discover account on the web
  • Download your most recent statement in Quicken format
  • Find the downloaded QFX file (probably in your Downloads folder)
  • Pull up in a text editor and find your new Account ID (for the OFX server)

Once you have your new Account ID, although the OFX server information in your Pocketsense sites.dat remains the same, you’ll need to run the Setup script to:

  • Delete your login credentials by deleting your Discover account
  • Create a new Discover account with your new Account ID
  • Select Test, and send the statement to Money
  • Re-matching this new import to the Discover account in Money

The 3 items needed to download from the OFX server

1. account ID (was simply your account #)
2. username (same as your web access username)
3. password

Unlike the previous round of unexplained changes by Discover’s IT department that required Robert to rewrite a good portion of code, the latest change (changing your Account ID needed to access their OFX server) seems explainable in the name of improved security. Perhaps they are trying to prevent hackers that know 2 of the 3 logon criteria (i.e. your account # and your username) from guessing at the 3rd item (your password) until a successful logon has been achieved.

I thought I would document this change, as the possibility exists that other financial institutions may have been advised to take this action in the name of improved security as well, so that we’ll know what to try should we suddenly be unable to access our data.

Comments (8)

Eliminating the “online updating”delays and errors when opening Money

It seems that even though Microsoft tweaked the Sunset edition of Money to no longer phone home for online updates and activation purposes, remnants of the online handshaking with MSN Money remain in the program and I suspect that, because the address of the MSN Money servers has changed over the years, some serious delays are occurring in the program, as evidenced by the spinning icon near the upper right corner soon after the program is opened to “retrieve quotes, news and exchange rates” according to the Update Results.  This 1 to 2 minute delay can get very annoying, as nothing can be done until the program finally gives up with the handshake and can even cause errors when OFX scripts are waiting to be processed.

By running netstat /b  as an administrator while firing up Money, I got a list of servers that Money is attempting to access:


  • TCP    168.0.44:64477     ESTABLISHED  [msmoney.exe]
  • TCP    168.0.44:64478   ESTABLISHED  [msmoney.exe]
  • TCP    168.0.44:64479     a-0003:http            ESTABLISHED  [msmoney.exe]
  • TCP    168.0.44:64480     ESTABLISHED  [msmoney.exe]
  • TCP    168.0.44:64481     ESTABLISHED  [msmoney.exe]
  • TCP    168.0.44:64482     hans-moleman:http      ESTABLISHED  [msmoney.exe]
  • TCP    168.0.44:64495     hans-moleman:http      ESTABLISHED  [msmoney.exe]


The first entry is believed to be the MSNbot which used to be within but the address of that page is now and that may be the first clue as to what is stalling the Money program.  Hans_MolemanI liked Ron’s statement in the Microsoft Money forum regarding the last 2 entries – “I have no idea why my MSMONEY is trying to connect to a Simpson’s character.  Hmmm.  My first guess is that it is a programmer’s joke…”

Fortunately, there is a resolution to this issue and since Money is offline now, we’ll help it by using Windows Firewall to cut it off from the internet so that it doesn’t work so hard trying to resolve finding the MSN Money pages for a useless handshake.   Note that doing this will make any links to web pages like banks and MSN Money inoperable from with the Money browser.  Pocketsense scripts, MoneyQuotes, OFX / QIF file imports and file backups to Dropbox will continue to function though.  Money will simply act like your PC isn’t hooked up to the internet.  It has been reported that Money will also shut down quicker when exiting the program by doing this.

Simply run “Windows Firewall with Advanced Security” which you will find in Windows Administrative Tools, Click on “Outbound Rules”, select “New Rule” > select “Program” > select “This Program” and enter or browse for the path (which should be
%ProgramFiles%\Microsoft Money Plus\MNYCoreFiles\msmoney.exe
– you can try just pasting this in) > select “Block this connection” > leave the defaults > and then name your new rule something like “Microsoft Money block”.  Once the rule is created, it can be disabled and enabled very easily within the Firewall program if you wish to experiment its effect.

One other adjustment that I advise:
Customize your Money’s Home Page such that the only two modules are Reminders and Favorite Accounts.  Other modules like Bills & Deposits can consume some time and prevent you from working with your file right away.

Now you’ll experience minimal delays, if any, when using your Money program, as it no longer will struggle to get hold of non-existent servers and process upcoming bills.

Comments (27)

Windows 10 free upgrade / my experience

I finally took the plunge and upgraded my Windows 7 PC (that was since upgraded to Windows 8.1) to Windows 10 and was very pleased with the outcome.  Not only did Microsoft Money function perfectly, but I was surprised to see my entire desktop appear exactly the same as it was prior to the upgrade.  I should mention that I don’t really like the live tiles Start Menu that Microsoft pushes and therefore use a program called Classic Shell to give me my Windows 7 desktop experience and that too carried over through the upgrade.

One program that “upgraded” itself that I didn’t care for is the Windows Calculator – the new one doesn’t even have the % key button, and there are a few other items that I don’t like as well.  I was able to easily install the Windows 7 version by downloading the modified program at    but note that rather than overwrite the Windows 10 version, it installs as calc1.exe, so the Money keyboard shortcut will still bring up the newer version (calc.exe).  Just pin a new shortcut to the taskbar to bring the Windows 7 version calculator up instead.

The Windows 10 upgrade is free until July 29th, but I just leaned today that for those wishing to postpone the free upgrade past that date, they can do so by “claiming” your entitlement under the free upgrade offer and then rolling back to your prior operating system. With that entitlement in place, you can schedule the final upgrade for when you’re ready, even if that’s after July 29th.   A step-by-step guide is presented at

Microsoft no longer seems to be using an Internet Explorer version longer than 15 characters, so at least for now, there is no need to alter the registry in order to get Money to function with Windows 10.   I’m leaving all that advice in the blog though, just in case…

Comments (11)

Resolving errors for those having multiple accounts at Chase and other OFX 103 banks

[UPDATE: It is no longer necessary to use this logic, as Pocketsense has since been updated to accommodate ofxver 103]

A commenter on the Pocketsense blog named John has come up with a solution for those that are getting errors while trying to download OFX data for multiple accounts from a particular financial institution.  I encouraged Kevin N. to try this out and he has verified that these instructions function as written.  It is very possible that Robert will incorporate these suggestions into Pocketsense in the future, or a similar strategy, but I’m writing this up to help others having difficulties with Chase and some other banks needing a solution.


This situation only arises if that bank or brokerage house has chosen to upgrade to their server to OFX version 1.03, which adds an additional requirement of a 128- bit universally unique identifier (UUID) number being part of the OFX request, as another layer of security.  Pocketsense currently allows for this requirement by generating a value and appending it to your sites.dat file as the variable ClientUID (if it doesn’t already exist in that file).  Should you have multiple accounts at that institution though, you are going to run into problems trying to use that same ClientUID for the subsequent data requests.  Some users that have 2 accounts at one bank (Chase as an example) – one for them and another for their spouse, get around this by running two separate instances of Pocketsense to get around this annoyance.  But say you had some IRA accounts there as well, a Roth and a traditional and the same in your spouse’s name and a joint checking account, etc.  Well this is where John’s solution saves the day.

Script modification:

John has a nice color coded presentation for his modification at , (you just delete the text that is brown and add the text that is green to your and scripts), so I am not going to try and duplicate that effort.  Essentially what he has done is come up with yet another variable for each sites.dat entry for those multiple accounts at the financial institution causing you headaches, called siteClientUID which you manually enter and is used instead of  ClientUID.  An easy method for coming up with a version 4 UUID value to assign to these siteClientUID entries is by simply going to .

SiteName : CHASE
AcctType : BASTMT
fiorg : B1
url :
fid : 10898
bankid : (use appropriate routing #)
brokerid :
appid : QWIN
appver : 2400
mininterval :
ofxver : 103
siteClientUID  :

Read the rest of this entry »

Leave a Comment

Older Posts »