Frustrated
Tue Apr 01 09:02:02 CDT 2008
Here is the message I got from microsoft support:
Uninstall your current version of Microsoft Money on your computer by going
to Add/Remove Programs in the Control Panel. If you have the Trial Version of
Microsoft Money installed at this time, proceed to #5.
Open up Internet Explorer and go to
http://www.microsoft.com/money/freetrial_deluxe.mspx and click "Download the
Free Trial".
Once the program is installed, open the Microsoft Money program and once you
are prompted to install the update, do so.
Once the update is complete, open Microsoft Money and go to Help>About
Microsoft Money, check the version number. The last four numbers should now
be 1415.
Close Microsoft Money and go to "C:/Program Files/Microsoft Money Plus".
Right-click on the Microsoft Money Plus folder and select 'copy', then go to
your desktop and right-click on there and select 'paste'.
Go to Add/Remove Programs in the Control Panel and uninstall the trial
version of Microsoft Money. Reboot your system. Then install your CD version
of the product.
Once the program is installed, go to "C:/Program Files" and delete the
"Microsoft Money Plus" folder. Click and drag the Microsoft Money Plus folder
from your desktop into the Program Files folder or copy and paste. Once the
folder is copied to the Program Files folder, open Microsoft Money and check
the version number again.
After you open Microsoft Money and are not being prompted for the update,
delete the 'Microsoft Money Plus' folder from your desktop
"werethegoodguys" wrote:
> On Apr 1, 1:15 am, Dgalbraith <Dgalbra...@discussions.microsoft.com>
> wrote:
> > After hours of playing with this, I think I have improved Brett's procedure
> > so that it should work for most people.
> >
> > 1. Get hidden files turned on.
> > 3. Next, you don't need to run Money each time for this. Instead we will
> > just run theupdateprogram: daupdate.exe that is inside MNYCoreFiles.
> >
> > So here is how I got things working:
> > First goto:
> > Program Files/Microsoft Money Plus with hidden files displayed
> >
> > You should see:
> > MNYCoreFiles
> > MNYCoreFiles.NEW.{9D6EAA4F-27B2-4407-AC72-4BBD2FCB6ED1}
> >
> > Now get your task manager up and running, and kill off daupdate.exe
> > (processes) if it is running. Then run it again (its located in
> > MNYCoreFiles). Make sure you have run it at least TWICE, maybe THREE times.
> >
> > Now go back up one level of directories and rename that funky file:
> > MNYCoreFiles.NEW.{9D6EAA4F-27B2-4407-AC72-4BBD2FCB6ED1}
> > to be
> > MNYCoreFiles.NEW
> > instead....
> >
> > Now you can browse into the file. Go in and make sure that you do NOT see a
> > bunch of files File.xxx.PAT or any .CAB files if you do, then stop. Delete
> > the folder, and start over... You can try running the daupdate again... run
> > it three times this time... maybe it will work right... basically it needs to
> > apply all those pat files before and get the .CAB files to unpack before the
> > next step.
> >
> > If you do not see any .PAT files or any .CAB files, then everything is good.
> >
> > Next make sure you kill off daupdate.exe again... Then inside the .NEW
> > folder, do "Select All", "Copy". Go to the MNYCoreFiles, and paste. Answer
> > "Yes to All" for replacing the exsting files.
> >
> > Okay... Now start up Money. It's gonna want toupdateagain.. This time it
> > worked for me... Hope that helps you all out. Laters,
> >
> > -d.
> >
> > ps. I just got an email back from MS that they are aware of the problem and
> > working on it. If my fix doesn't work, they sent me another fix to install
> > the trial version, then install the CD version somewhere else and "merge" the
> > two ... That would probalby work as well.
>
> Dgalbraith:
>
> Thank you -- your process worked exactly as you described, and ended
> nearly an hour of frustration with this product. I kind of "fell
> into" your process before searching this group but what kept killing
> my effort was not ending the 'daupdate.exe' task...
>
> Now that the application is updated, I just can't activate it --
> presumably an issue with our proxy server but I hope to have that
> resolved soon also.
>
> Thanks again.
>